Experienced sysadmins rarely frame this as a technical question. The real question is: who handles the 3am outage? Managed VPS means the provider does. Unmanaged VPS means your team does. Everything else — cost, control, configuration — follows from that answer. This guide walks through the decision framework that production teams actually use.
The Core Difference: What Managed and Unmanaged Actually Mean
| Responsibility | Managed VPS | Unmanaged VPS |
|---|---|---|
| OS updates and patches | Provider handles | Your team handles |
| Security hardening | Provider handles | Your team handles |
| Server monitoring | Provider handles (usually) | Your team builds and owns |
| Backups | Often included (verify scope) | You configure and test |
| Root access | Usually yes | Yes — full control |
| Emergency response at 3am | Provider on-call | Your team on-call |
| Monthly cost | Higher — includes support labour | Lower — raw compute only |
| Software stack | Provider’s approved list or limited | Anything — Docker, custom kernels, any runtime |
The Decision Framework Experienced Teams Use
Three questions determine the right choice for most production environments:
1. Do you have dedicated operations coverage?
This is the most important question. If your team has a DevOps engineer, an SRE, or a sysadmin whose job includes server maintenance — unmanaged is almost always the right call. You are already paying for that expertise. Adding managed hosting layers provider support on top of internal capability you already have, duplicating cost without benefit. If your developers are also expected to handle infrastructure in their spare time, managed reduces operational risk significantly.
2. Do you have mature operational tooling?
Unmanaged VPS works well when you have: infrastructure as code (Terraform, Ansible, Puppet), automated deployments, centralised logging, monitoring and alerting, documented runbooks for common failures, and tested backup restoration procedures. If these are missing, unmanaged means your team builds them under pressure when something breaks. If these are in place, unmanaged gives you full control at the lowest cost.
3. What does an hour of downtime actually cost?
For a development environment or internal tool, downtime is inconvenient. For a customer-facing SaaS, e-commerce platform, or regulated application, downtime has a direct revenue and compliance cost. When the cost of an outage significantly exceeds the cost of a managed plan, the premium pays for itself in risk reduction alone — especially if your team cannot guarantee fast incident response at all hours.
A Common Progression: How Teams Typically Move
- Start on managed hosting while the application and deployment process are still evolving — provider support covers the gap while the team focuses on shipping product.
- Automate provisioning, configuration, monitoring, and backups as the team grows.
- Document operational procedures and runbooks for common server failures.
- Move to unmanaged once server administration is routine, reproducible, and owned by a dedicated person — not an afterthought.
This progression is the norm, not the exception. Paying for managed hosting indefinitely is not a failure — it is the right call when the alternative is absorbing operational risk that the team is not staffed to handle.
Where Unmanaged VPS Has a Clear Advantage
- Custom software stacks: any runtime, any kernel version, any configuration — no provider approval layer.
- Docker and container workloads: full control over the container runtime, network configuration, and storage volumes.
- Cost at scale: unmanaged is significantly cheaper per instance when you are running multiple servers and the management overhead is already handled internally.
- Security posture: experienced teams often prefer to own their own hardening rather than rely on a provider’s baseline.
- Development and staging environments: low downtime cost, high value from configuration flexibility.
Where Managed VPS Has a Clear Advantage
- Small teams without dedicated infrastructure staff: developers should be building the product, not on-call for server failures.
- High-traffic production with strict uptime requirements: provider SLAs and 24/7 support reduce mean time to recovery.
- Regulated industries (healthcare, finance, legal): managed plans often include compliance-relevant features like audit logs and automated patching records.
- Client-facing applications where your SLA to clients depends on your infrastructure SLA.
Contabo Cloud VPS: Built for Unmanaged Production Workloads
Contabo’s VPS line is unmanaged — you get full root access and full control above the hypervisor layer. This is intentional: the target user is a developer or sysadmin who knows what they are doing and wants maximum performance per euro without paying for managed support they do not need.
What Contabo handles: the physical hardware, network, hypervisor, DDoS protection (always-on, included), and initial server provisioning. What your team handles: OS configuration, security hardening, updates, monitoring, backups, and application deployment.
For teams with the operational maturity to run unmanaged, the value proposition is straightforward: Cloud VPS 6 (6 vCPU, 12 GB RAM) at €6.00/mo, Cloud VPS 8 (8 vCPU, 24 GB RAM) at €11.20/mo (12-month term, incl. VAT, verified contabo.com/en-us/pricing/ Aug 2026). Copywriter: verify current plan names and pricing before publishing.
FAQ: Managed vs Unmanaged VPS
Choose unmanaged if your team has dedicated operations coverage, mature tooling (IaC, monitoring, documented runbooks), and the ability to respond to incidents at any hour. Choose managed if your team lacks dedicated infrastructure staff, your application has strict uptime requirements, or the cost of downtime significantly exceeds the cost of a managed plan.
Not inherently. Most large-scale production infrastructure runs on unmanaged servers because mature engineering teams have the tooling and staffing to manage them reliably. The risk is not in the server being unmanaged — it is in deploying an unmanaged server without the operational practices to support it. If you have IaC, monitoring, alerting, backup verification, and runbooks in place, unmanaged is both safe and preferable.
At minimum: the ability to connect via SSH, configure a firewall (UFW or iptables), install and update software packages, set up automated backups, and respond to alerts when something goes wrong. For production workloads: infrastructure as code for reproducible provisioning, centralised logging, uptime monitoring with alerting, and documented recovery procedures for common failure scenarios.
Contabo’s standard VPS plans are unmanaged — full root access, your team owns configuration and maintenance above the hypervisor. Contabo provides support for the infrastructure layer (hardware, network, hypervisor) and initial server provisioning. Application-level configuration, OS maintenance, and operational tooling are the customer’s responsibility. Verify current support scope at contabo.com.
Disclaimer: Product specifications, features, and prices mentioned in this article are subject to change and may vary by region, billing term, and active promotions. Please check each provider’s or brand’s official website for current figures, pricing, and local currency rates.
