Anyone running WHMCS on a budget VPS in 2026 — which one fits?

[Michael Wilson]

I run a small WHMCS install for a handful of clients from South Dakota, and the current shared setup is starting to show its limits during invoice runs. Nothing fancy here — just a handful of cPanel accounts and a couple of addons. I'm looking at moving to a budget VPS instead, but I'm not sure where to draw the line on specs. Some hosts push 1 GB RAM plans, others say 2 GB minimum just for PHP and MySQL to stay comfortable. I also worry about disk I/O during cron jobs and whether a cheap control panel is worth the tradeoff. I'd rather not get stuck migrating twice. If you've moved a similar-sized WHMCS install to a budget VPS, what RAM, storage type, and panel did you settle on, and what would you do differently?

[Waqas Ahmed Waseer]

@Michael Wilson I'd go 2 GB as the floor, and here's why from running a few of these.

 

At your size WHMCS itself isn't heavy. What eats memory is PHP-FPM workers plus MySQL/MariaDB with a sane InnoDB buffer pool, plus whatever panel you bolt on. On 1 GB it works until the cron, a backup and a few client logins overlap, and then you're swapping right when the invoice run is going. 2 GB with a small swap file gives you breathing room. Get NVMe or at least SSD storage. Cheap plans on spinning disk or heavily oversold storage are where cron jobs crawl, and you can usually tell by testing disk speed in the first week.

 

Before you move, check why the invoice runs struggle now. On shared hosting it's often not raw power but the account limits: CloudLinux LVE caps on CPU or entry processes, a short max_execution_time, or the cron being run through wget/curl over HTTP instead of the PHP CLI, so it gets killed partway. Your Activity Log and the cron output will usually show it. That tells you whether you need a bigger box or just your own limits.

 

On the panel: I'd keep WHMCS on its own server, separate from the cPanel server your clients are on. That way a client site getting hacked or hammered doesn't take billing down with it, and you're not paying for a cPanel licence just to host WHMCS. A plain Linux VPS with nginx or Apache, PHP-FPM, MariaDB and the ionCube Loader is plenty. If you don't want to manage it from the command line, a free or low-cost panel is fine. Just make sure it supports the PHP version your WHMCS release needs, since some lag behind.

 

Things I'd do differently looking back:

1. Set up off-server backups of the database and the attachments/downloads folders from day one, not after the first scare.

2. Run the cron as the site user with the PHP CLI, using the exact command shown under Automation Settings.

3. Plan the licence move. Your licence is tied to the server IP and directory, so reissue it from your WHMCS client area when you switch.

4. Put the admin area behind an IP allowlist or at least 2FA, since it's now on a box only you look after.

5. Pick a provider that lets you upgrade RAM in place. That's what saves you from migrating twice, more than guessing the perfect size now.

 

What PHP version and WHMCS version are you on? That narrows which OS image I'd start from.