Managed vs Unmanaged VPS: Which One Do You Actually Need?

Two VPS plans with the same cores, RAM and disk can differ in price by three times. The difference is the word managed, and what it hides is who does the work of keeping a server running. Here is what that work is, so you can decide whether you want it.

What "unmanaged" includes

The virtual machine, an operating system image, an IP address, a console, and a support team that will confirm the VM is powered on. That is the whole product. It is the right product for people who run servers for a living and want nothing between them and the machine.

What you take on with it

A server that is not maintained does not stay where you left it. Over a year, an unmanaged VPS needs at minimum:

• Security updates — weekly, sometimes daily, with a reboot for kernel patches. Skipping them is how servers join botnets.
• Hardening — firewall, SSH keys, Fail2ban, removing unused services. Our 10-step checklist is an hour, once.
• Web stack setup and tuning — Nginx or Apache, PHP-FPM pools, the database's memory settings. Defaults are wrong for almost every workload.
• Backups — configured, stored off the machine, and tested. A backup nobody has restored is a hope.
• Monitoring — something that tells you the site is down before a customer does, and disk-full warnings before the database stops writing.
• Incident response — when it is down at 02:00, someone reads the logs and fixes it. If that someone is you, the site's uptime is your sleep schedule.
• Upgrades — PHP versions go end-of-life every year; MySQL major versions; the OS itself every few years.

Done properly, this is two to four hours a month for a single server, plus the occasional bad night. Done badly, it is nothing at all for a year and then a very expensive week.

What "managed" includes

The host's engineers do everything in the list above. Specifically, on a VPSPioneer managed VPS:

• OS installed and hardened before handover, with the web stack configured for your workload.
• Security patches applied, kernel live-patched where possible, reboots scheduled with you.
• Daily backups, 14-day offsite retention, restores on request.
• Monitoring every five minutes with an engineer paged on failure.
• Malware scanning and Anti-DDoS included.
• Any admin task — install a package, tune MySQL, add a cron job, debug a 502 — done through a ticket.

You still have root if you want it. Most customers never use it.

The cost comparison people get wrong

The obvious comparison is the monthly price: managed costs more. The one that matters is total cost, and it has two parts the price list does not show:

1. Your time. Three hours a month at whatever your hour is worth. For a freelancer billing £50/h that is £150/month — several times the management fee.
2. The incident you did not prevent. A single hacked server, or a database lost to a backup that never worked, costs more than a decade of management fees.

Unmanaged is cheaper only if your time is free and you already know how to do the list above. For a sysadmin, it often is. For a business owner or an agency, it almost never is.

A short test

Answer honestly:

• Do you know what sudo journalctl -p err -b prints, and would you know what to do about it?
• Have you restored a server from a backup, ever?
• If the site went down on a Sunday morning, who would notice, and who would fix it?

Three confident answers: unmanaged is fine and you will enjoy it. Any hesitation: managed, and spend the hours on the business instead.

The middle ground

Some hosts sell "semi-managed" — the host handles the OS and patches but not the application. It is a reasonable option if you have a developer who owns the app but not the server. Ask exactly where the line is; "we manage the server" can mean anything from full service to "we will reboot it".

At VPSPioneer there is one kind of VPS, and it is managed. If you specifically want an unmanaged machine, we are not the cheapest place to get one and we would rather say so. If you want a server that is somebody's job, that is what we sell.