Budget VPS vs managed hosting — true cost of “saving money”
A $12 unmanaged VPS looks cheaper than a $45 managed plan, until you price your own hours. The true cost, worked out with real numbers.
A $12/month unmanaged VPS looks like a bargain next to a $45/month managed plan. Same specs, sometimes better, for a quarter of the price. Then something breaks at 11pm, and you find out what you actually bought. We run both models for clients, so this is not a sales pitch for either side. It is the true cost of “saving money” on unmanaged, worked out with real hours.
The short answer
Unmanaged is cheaper only if your time is free, and it never is. If you can comfortably handle a kernel update, a failed TLS renewal, and a compromised site on your own, unmanaged wins on price by a wide margin. If any of those sentences made you tense up, the gap between $12 and $45 is buying back hours you would otherwise lose, and lose at the worst possible moment. Most small businesses without a sysadmin should pay for managed, or pay someone to manage the unmanaged box.
What the two words actually mean
Every hosting blog defines these, and most of them sell managed plans, so read their conclusions with that in mind. Unmanaged means the provider keeps the hardware and network alive; everything above the bare OS is yours: updates, security, web server, database, backups, email, the lot. Managed means the provider also handles the OS and usually a control panel, patching, backups, and support when something above the metal breaks.
The middle ground people forget is an unmanaged VPS plus a human who manages it for you. That is often the cheapest sane option once you price the alternative honestly.
The sticker price is the smallest number
Here is the trap. The $12 and the $45 are the only two numbers most comparisons show, so people decide on a $33 difference. But the sticker is one of four costs, and usually the smallest:
- The plan itself, the number on the invoice.
- Setup time, getting from a bare Ubuntu image to a hardened, serving box.
- Ongoing time: updates, renewals, log-checking, the monthly grind.
- Incident time, the 2am hours when something is down and revenue is bleeding.
Ignore the last three and unmanaged always wins, because you are comparing one cost against four. Count all four and the picture flips for most people.
Real hours on an unmanaged box
These are rough figures from boxes we actually run, for a straightforward WordPress or small-store site. Your mileage varies, but the shape holds:
| Task | Time if you know how | Time if you are learning |
|---|---|---|
| Initial setup + hardening | 3–5 hours | 10–20 hours |
| Monthly upkeep | 1–2 hours/month | 3–5 hours/month |
| TLS/renewal or config break | 30–60 min each | 2–4 hours each |
| Recovering a hacked site | 4–8 hours | a very bad weekend |
Put a number on your own hour, even a conservative $30, and do the math. Two hours of monthly upkeep at $30 is $60, on top of the $12 plan. You are now at $72 a month for the “cheap” option, and you are the one on call. The $45 managed plan, with someone else holding the pager, suddenly reads differently.
Where unmanaged genuinely wins
We are not anti-unmanaged. We run plenty of unmanaged boxes, because for the right operator they are the better deal:
- You already run Linux daily and a kernel update is muscle memory, not an event.
- You want a specific stack a managed panel would fight you on, like a custom nginx build, an odd PHP extension, or containers.
- You have several sites and can amortise one good setup across all of them.
- You treat the box as disposable: infrastructure as code, and a rebuild is twenty minutes, not a crisis.
If that is you, unmanaged is not a compromise, it is the correct tool, and the price advantage is real money in your pocket.
Where the cheap box quietly costs you
The failure mode we clean up most often: someone picked unmanaged to save $30, ran it fine for eight months, then hit one incident that ate a weekend and a chunk of sales. The savings from those eight months vanished in one Saturday. Unmanaged does not cost more on average. It costs more variance. The bad months are much worse, and they arrive without warning. If your business cannot absorb a surprise bad weekend, you are not really saving money, you are borrowing against a future outage.
How we actually decide with clients
Two questions settle it nearly every time. First: is there someone on the team who can confidently fix a down server, or does everyone go quiet when it breaks? Second: what does an hour of the site being down cost you, nothing or real orders? A hobby blog with a capable owner should run unmanaged and pocket the difference. A store doing steady revenue with no sysadmin should pay for managed, or hand the unmanaged box to someone who does this for a living.
The option in the middle
You do not have to choose between an expensive managed plan and a cheap box you babysit yourself. Take the $12 unmanaged VPS for the control and the price, and let us manage it: hardening, updates, backups, and being the one who picks up when it breaks. You keep the flexibility of your own server without the 2am hours. That is most of what our hosting and infrastructure support does, and if you are still weighing the raw options first, our comparison of AWS Lightsail against a plain VPS is a good next read.
For the wider view across all three hosting tiers, including shared plans and their renewal pricing, see our affiliate-free WordPress hosting comparison.
Next in the journal
- 19 Jul 2026 How to actually hit 99.9% WordPress uptime 99.9% uptime still allows 43 minutes of downtime a month. Where those minutes go on a WordPress site, and the habits that keep you…
- 19 Jul 2026 Automating server monitoring with cron + Slack Skip the per-server monitoring subscription. One bash script and a cron job that post to a Slack webhook only when something actually breaks.