The same virtual machine can cost four times as much with the word "managed" in front of it. Our earlier post, managed vs unmanaged VPS, covers which kind of person suits which. This one is the invoice view: for each task, who does it, what the price difference buys, and what it does not buy. We sell both lines on the same hardware sizes, so the numbers below come from our own price list.
The price gap, line by line
Same cores, RAM and NVMe storage in each row. USD per month.
| Size | Resources | Cloud VPS (self-managed) | Managed VPS | Difference |
|---|---|---|---|---|
| S | 2 vCores, 4 GB, 40 GB | $8.49 | $34.99 | $26.50 |
| M | 4 vCores, 8 GB, 75 GB | $15.99 | $49.99 | $34.00 |
| L | 6 vCores, 12 GB, 100 GB | $22.99 | $69.99 | $47.00 |
| XL | 8 vCores, 24 GB, 200 GB | $43.99 | $109.99 | $66.00 |
The hardware is identical, so the difference column is the price of the work. The question is whether you can do that work for less.
Who does what
This is the split on our two products. Use it as a template when reading any other host's page, because "managed" is not a standard and the line moves from one provider to the next.
| Task | Cloud VPS | Managed VPS |
|---|---|---|
| OS install | Automatic, you pick the image | We install |
| OS updates and security patches | You | We patch the server |
| Firewall, SSH hardening, Fail2ban | You | Set up before handover: SSH keys, root password login disabled, firewall, Fail2ban, automatic security updates |
| Web stack install and tuning | You | We tune the web stack and database for your real traffic |
| SSL certificates and renewal | You | Let's Encrypt installed and renewed automatically |
| Backups | Daily snapshot of the previous 24 hours, restorable from the client area. Anything older is yours | Daily snapshot plus offsite copies kept 14 days, restores on request within 4 hours |
| Monitoring | You | Uptime checks every 5 minutes, with CPU, RAM, disk and bandwidth alerts |
| Incident response | You | We act on the alerts |
| Installing software you ask for | You | Included, within the monthly admin allowance |
| Control panel | You install it; the licence is yours | We can install it; the licence cost is still yours |
The hidden cost of unmanaged: count the hours
Published figures for "hours of server administration per month" are guesses, and so would ours be. The useful number is your own, and you can get it in a month.
Step 1: list the recurring work
- Applying updates and rebooting for new kernels
- Reading logs and alerts
- Checking backups ran, and restoring one to prove it works
- Renewing or debugging certificates
- Disk space housekeeping
- Major upgrades: PHP, the database, the OS release
- Incidents: the site is down, the disk is full, the server is sending spam
Step 2: see what is waiting right now
On an existing server, these show the backlog:
# Debian, Ubuntu
apt list --upgradable 2>/dev/null | grep -c upgradable
[ -f /var/run/reboot-required ] && echo "reboot pending"
# AlmaLinux, Rocky
sudo dnf check-update --security
# any distribution
systemctl --failed
sudo journalctl -p err --since "7 days ago" | wc -l
sudo ss -tlnp
df -hIf the first command returns dozens of packages, a reboot is pending and you do not recognise half of the listening ports, the server is costing you nothing today because the work is not being done. That is a debt, not a saving.
Step 3: log it for a month
Write down every minute spent on the server rather than on the thing it runs, including time reading documentation. Then do the sum:
monthly cost of unmanaged = (hours logged x your hourly rate) + Cloud VPS priceA worked example
The rate below is an assumption for illustration; replace it with yours. We charge $35 an hour for admin work beyond the managed allowance, so use that as the value of an hour.
| Size | Price difference | Break-even at $35/hour |
|---|---|---|
| S | $26.50 | 45 minutes a month |
| M | $34.00 | 58 minutes a month |
| L | $47.00 | 1 hour 21 minutes a month |
| XL | $66.00 | 1 hour 53 minutes a month |
If you spend less than that per month and the work is genuinely done, unmanaged is cheaper. If you bill clients at twice that rate, halve the break-even times.
Tip: automation moves the number more than skill does. Unattended security updates and Fail2ban remove most of the routine work in an afternoon. What they do not remove is incidents, and incidents are where the hours go.
Tip: price the bad night separately. Routine work is predictable. The cost that decides this is one outage at the wrong moment, multiplied by what an hour of downtime costs your business. If that figure is small, unmanaged is a reasonable risk. If one lost afternoon of orders exceeds a year of the price difference, the decision is already made.
What "managed" does not include
Managed means the server is someone's job. It does not mean everything on the server is. Our exclusions, which are typical of the industry:
- Custom software development
- Debugging your own application code
- Third-party licence costs, such as control panels and commercial software
- Admin work beyond the included monthly allowance
- Data recovery outside the backup retention window
In practice the boundary runs between the platform and the application. If PHP-FPM runs out of workers, that is ours. If your plugin has a query that takes eight seconds, fixing the code is yours or your developer's.
The allowance matters too. Our plans include two hours of sysadmin work a month; beyond that it is $35 an hour, quoted before we start. Ask any managed host the same three questions: how much work is included, what the overage rate is, and whether you are told the cost before it is incurred.
Tip: read the backup line twice. "Kept 14 days" means a file deleted 15 days ago is gone. If you need monthly or yearly archives for accounting or legal reasons, keep your own copy somewhere else, whichever product you buy.
What unmanaged does include
On a Cloud VPS you can reinstall the OS, switch distribution, reboot and open the console from the client area as often as you like. The console is what saves you after a firewall rule locks you out of SSH. The daily snapshot covers yesterday's mistake; it is not a backup strategy.
What you should not expect from any unmanaged product is help with what is inside the machine. The configuration is yours. If you take this route, start with hardening the server on day one.
Choosing
| If this is true | Choose |
|---|---|
| You administer Linux already and your logged hours stay under the break-even | Unmanaged |
| The server is for development, testing or learning | Unmanaged |
| The server earns money and nobody on the team owns it | Managed |
| You have a developer for the application but not for the OS | Managed |
Not sure a VPS is the right step at all? Shared hosting or VPS covers that decision first. If it is, the honest test is the log from Step 3. A month of real numbers beats any estimate, including ours.