When you rent a VPS, dedicated server or cloud instance, you are usually offered two flavours: managed and unmanaged. The hardware and the price tag can look similar, but what you are actually buying is very different. Understanding managed vs unmanaged server options comes down to one question: who is responsible for keeping the server healthy, secure and running once it has been switched on?
What an unmanaged server includes
With an unmanaged server, the provider is responsible for the physical hardware, the network, power and cooling, and (for virtual servers) the virtualisation platform. They hand you a server with a fresh operating system and root access. From that point on, everything else is yours:
- Installing and configuring the web server, database, PHP or other runtimes.
- Applying security updates and handling reboots.
- Firewall setup and SSH hardening.
- Backups, and testing that they can be restored.
- Monitoring and responding to alerts, at any hour.
- Troubleshooting slowdowns, errors and outages.
- SSL certificates, email deliverability and DNS configuration.
Provider support for unmanaged plans is usually limited to "is the hardware and network up?" If your website shows a database error, that is your problem to solve.
What a managed server includes
With a managed server, the provider or a third-party management company also takes on some or all of the operational work. The scope varies a lot between providers, so read the details, but managed service typically covers:
- Initial setup and hardening to a known baseline.
- Operating system and core software updates.
- 24/7 monitoring with someone responding to alerts.
- Backup configuration and monitoring.
- Security measures: firewall, intrusion prevention, malware scanning.
- Performance tuning of the web server and database.
- Help with problems at the server level, often including control panel issues.
What is usually not included: fixing bugs in your own application code, developing new features, or supporting third-party software the provider does not know. Clarify where the boundary sits before an incident forces the question.
Managed vs unmanaged server: side by side
| Responsibility | Unmanaged | Managed |
|---|---|---|
| Hardware, network, data centre | Provider | Provider |
| OS installation | Provider (basic image) | Provider (hardened, configured) |
| Software stack setup | You | Provider |
| Security patching | You | Provider |
| Monitoring and alert response | You | Provider |
| Backups | You | Provider (check retention and restore terms) |
| Application code | You | You |
| Root access | Full | Usually yes, sometimes restricted |
The real cost comparison
Unmanaged servers look cheaper on the pricing page. The honest comparison adds the cost of the work you are taking on:
- Staff time: routine maintenance takes hours every month per server, plus unpredictable time for incidents.
- Out-of-hours cover: servers fail at night and on holidays. Someone must be reachable, or downtime lasts until Monday.
- Skills: secure configuration of Linux, web servers, databases and email requires specific experience. Mistakes can cost far more than the management fee.
- Risk: an unpatched server or untested backup is a liability that does not appear on any invoice until it is too late.
If you already employ an experienced system administrator with capacity, unmanaged can be the economical choice. If the "administrator" is a developer squeezing server work between features, or nobody at all, managed service is usually cheaper once the full picture is counted.
When unmanaged makes sense
- You have in-house Linux expertise and on-call coverage.
- You need complete control over every configuration detail, for example for unusual software stacks.
- The servers are for development, testing or learning, where downtime is harmless.
- Your infrastructure is defined as code and rebuilt automatically, so individual servers are disposable.
When managed makes sense
- Your website or application directly earns revenue or serves customers.
- You have no dedicated system administrator, or they are stretched.
- You need to demonstrate security practices to clients, auditors or insurers.
- You want predictable costs and a clear escalation path when something breaks.
Questions to ask a managed provider
- What exactly is included, and what is billed as extra work?
- What are the response times for critical and non-critical issues, and are they 24/7?
- How are updates handled: automatic, scheduled, and with what notice?
- How often are backups taken, where are they stored, how long are they kept, and how often are restores tested?
- Will I keep root access and full ownership of my data?
- What happens if I want to leave? Can I get a copy of all configuration and documentation?
The middle ground
You do not have to choose one model forever. Many businesses rent unmanaged infrastructure from a cloud or hosting provider of their choice, then contract a separate company to manage it. This keeps flexibility over where servers run while handing off the operational burden. If you are considering this route, our server management and database management pages describe what those services cover.
Whichever route you take, check the basics yourself from time to time: certificates valid (use our SSL checker), only expected ports open, and backups actually restorable.
Key takeaways
- Unmanaged: the provider runs the hardware; you run everything on it.
- Managed: the provider also handles setup, updates, monitoring, backups and server-level support.
- Compare total cost, including staff time, out-of-hours cover and risk, not just the monthly fee.
- Get the scope of management in writing, especially response times and backup terms.