Managed vs Unmanaged VPS:What You're Responsible For
What a managed VPS includes compared with an unmanaged one: updates, security, monitoring, backups and troubleshooting, plus the skills each option needs and the questions to ask a provider.
Table of Contents
With an unmanaged VPS, the provider supplies the virtual server, network and hardware, and you handle everything inside the server: updates, security, software, backups, monitoring and fixing problems. With a managed VPS, the provider takes on some or all of that work. The right choice depends less on budget than on whether someone on your team can reliably administer a Linux server.
Because "managed" means different things at different providers, the most important step is reading exactly what is included.
Who does what
| Task | Unmanaged VPS | Managed VPS (typical) |
|---|---|---|
| Hardware, network, virtualisation | Provider | Provider |
| Operating system installation | Provider (base image) | Provider |
| OS security updates | You | Provider |
| Web server, PHP, database setup | You | Provider, often with a control panel |
| Firewall and SSH hardening | You | Provider |
| Monitoring and alerting | You | Provider (often) |
| Backups | You (snapshots may be offered) | Provider (check frequency and retention) |
| Troubleshooting server issues | You | Provider |
| Your application code | You | Usually you |
Your website or application itself (WordPress plugins, custom code) normally remains your responsibility on both, unless the plan explicitly says otherwise.
Unmanaged VPS: who it suits
- Developers and sysadmins comfortable with Linux.
- Teams with infrastructure-as-code or configuration management.
- Projects needing unusual software or configurations.
- Budgets where staff time is available but money is tight.
What you need to know: SSH, package management, firewall configuration, web server and database configuration, log reading, backup tools and incident response. The Linux server hardening checklist gives a sense of the baseline work.
Managed VPS: who it suits
- Businesses without in-house server administrators.
- Agencies who want to focus on building sites, not running servers.
- Important workloads where a missed security update or failed backup would be costly.
- Anyone moving up from shared hosting who wants more resources but not more responsibility.
Questions to ask about any managed plan
- Which tasks are included, in writing?
- How quickly are security updates applied?
- Is monitoring 24/7, and what happens when an alert fires?
- How often are backups taken, where are they stored, how long are they kept, and who restores them?
- Is a control panel included, and is its licence extra?
- What is excluded (for example application-level debugging, custom software)?
- What response times does support commit to?
The hidden cost of unmanaged
An unmanaged VPS looks cheaper, but compare honestly:
- Time spent on updates, monitoring and fixes every month.
- Risk of a breach or data loss from a missed update or untested backup.
- On-call: who responds at night or on holidays?
If you would pay someone to do this work anyway, a managed plan is often the simpler way to buy it.
A middle path
Some teams use an unmanaged VPS with a control panel that automates much of the routine work, or use a managed plan but keep their own off-server backups and monitoring as a second layer. Whatever you choose, make sure someone is clearly responsible for every task in the table above.
Two scenarios
A growing online shop, no technical staff. The owner moved from shared hosting because the store kept hitting resource limits. Nobody in the business knows Linux. An unmanaged VPS would mean either learning server administration under pressure or hiring someone ad hoc when things break. A managed VPS gives the extra resources while the provider handles updates, security and monitoring; the shop's developer handles WooCommerce itself.
A small software team deploying a Laravel API. The team already uses deployment scripts and monitoring for other projects, and needs specific versions of PHP, Redis and a queue worker. An unmanaged VPS gives them full control at lower cost, and their existing processes cover updates and backups.
The deciding factor in both cases is not the size of the business but who will reliably do the server work.
A monthly workload estimate for an unmanaged VPS
To judge honestly whether you can run a VPS yourself, estimate the recurring work:
| Task | Typical frequency |
|---|---|
| Review and apply security updates | Weekly (automatic for most, with review) |
| Check backups and test a restore | Weekly check, quarterly restore test |
| Review monitoring alerts and logs | Daily glance, weekly review |
| Renew certificates, check disk space | Automated, with monthly checks |
| Plan OS and software upgrades | A few times a year |
| Respond to incidents | Unpredictable, sometimes urgent |
If nobody can commit to this, the cost of a managed plan is usually less than the cost of a single serious incident.
Frequently Asked Questions
Can I switch from unmanaged to managed later?
Often yes, though the provider may need to rebuild or audit the server to bring it under management.
Do I get root access on a managed VPS?
Many providers allow it, sometimes with conditions, because changes you make can conflict with their management. Ask before you buy.
Is managed VPS the same as managed WordPress hosting?
No. Managed WordPress hosting manages the application environment for WordPress specifically; a managed VPS manages a general-purpose server.
Compare plans
Compare ServerNeed managed VPS with the standard VPS plans. For the fundamentals, see what is a VPS, and for the next step up, VPS vs dedicated server.
Sources
Last updated 7 October 2026
