“Managed VPS” and “unmanaged VPS” describe the same underlying hardware — a virtual server — but the support boundary is completely different. Unmanaged is cheaper because you handle everything yourself; managed costs more because someone handles the boring stuff for you. The right choice depends on what you actually want to do with your time. This guide spells out the differences clearly and helps you pick.
What’s the same in both
- Hardware resources (CPU, RAM, disk, bandwidth) — sized by plan.
- Network connectivity, datacenter, uptime SLA.
- Root access (you can do anything with the server).
- Reboot and basic provisioning controls in client area.
What differs is who maintains and troubleshoots what runs on top.
Unmanaged VPS — what you get
- A blank Linux server (or chosen OS image).
- SSH access on day one.
- Bandwidth and DNS for the IP.
- Support for: hardware issues, network issues, the hypervisor.
YOU handle:
- OS configuration after install.
- Web server, database, mail server, all application installs.
- Security updates and patching.
- Firewall configuration.
- SSL certificates.
- Backups.
- Monitoring and uptime.
- Troubleshooting when anything you installed breaks.
- Email server setup (and ongoing deliverability work).
- DNS records.
Support will help with hardware/network, but anything inside the OS is your problem.
Managed VPS — what you get
- Everything in unmanaged PLUS:
- Control panel pre-installed (cPanel/WHM, DirectAdmin).
- Web server, database, mail server configured and tuned.
- Security stack pre-configured (CSF firewall, Imunify360 or equivalent).
- OS-level updates handled by us.
- Server-level monitoring with proactive intervention.
- Backups configured.
- Support that troubleshoots issues inside the OS.
YOU handle:
- Your application content and configuration.
- Site-level updates (WordPress core, plugins, themes).
- Things specific to your business logic.
The infrastructure tier is handled; the application tier is yours.
The hidden cost of unmanaged
Unmanaged looks cheaper on paper. Per month it is. Per result, it often isn’t:
| Task | Time on unmanaged | On managed |
|---|---|---|
| Initial LAMP setup | 1-4 hours | Done at provisioning |
| SSL setup for new domain | 15 min (Let’s Encrypt + Certbot) | 30 seconds (cPanel AutoSSL) |
| Setting up email for a new mailbox | 2-3 hours initial mail server config + 5 min per box | 30 seconds per mailbox |
| Monthly security updates | 30 min – 2 hours, can break things | Mostly handled |
| Restoring from a backup | 1-3 hours depending on what’s needed | JetBackup point-and-click |
| Diagnosing why mail isn’t sending | Hours of mail log spelunking | Open ticket, often resolved by us |
| Server compromise recovery | Full day or pay for cleanup | Our security team responds |
If your time is worth anything, the unmanaged savings disappear within months once you sum up the hours.
When unmanaged makes sense
- You’re explicitly learning server administration as a skill.
- Your use case is unconventional (running a custom application, Tor hidden service, specific service that requires kernel-level config we wouldn’t install on managed).
- You’re a sysadmin / DevOps professional and managing servers is your job.
- You have a single simple site and genuinely don’t mind doing the work.
- You need lower cost AND have the time to invest.
When managed makes sense
- You’re running a business and your time is better spent on the business.
- You have multiple sites, mailboxes, or domains to manage.
- You need email hosting (which is way more work than people realize on unmanaged).
- You’ll have collaborators (clients, team) who need access.
- You want to sleep at night without monitoring server alerts.
- You need real support when something goes wrong, not just “hardware is online, the rest is yours”.
For 95% of business hosting, managed is the right answer.
“Semi-managed” — the middle ground
Some providers offer “self-managed with extras” — control panel pre-installed but support is limited to panel-specific issues. Cheaper than full managed, more user-friendly than bare VPS.
Good for: users who like the control of having their own server but want cPanel/DA to handle the day-to-day, and who can resolve issues themselves with documentation but want a foundation that’s not totally bare.
Common questions
“Can I switch from unmanaged to managed later?” Usually yes, but it means installing the control panel on your VPS (which restructures the filesystem and overwrites your manual configs). Easier to pick correctly the first time.
“Does managed mean I have less control?” No. You still have root SSH. You can install anything you want. Managed just means we handle the standard stack. If you go in and break the stack with custom changes, that’s on you.
“Will managed slow my server down with extra stuff?” The control panel and security stack use some resources, yes — maybe 5-10% of a small VPS. On any reasonably-sized VPS this is negligible. The benefit of having those things running far outweighs the resource cost.
“What if I want a custom OS not supported by managed?” Most managed providers support specific OSes (AlmaLinux, CloudLinux, Ubuntu LTS). If you need something exotic (Arch, Gentoo, FreeBSD), you’re in unmanaged territory.
“How much support do I actually get on managed?” Depends on provider. iWebVault managed VPS includes server-level support — anything in the stack we install we troubleshoot. Application-specific issues (a WordPress plugin breaking) we’ll help where reasonable but aren’t your developer.
“Is dedicated server the same trade-off?” Yes — managed dedicated handles the stack and infrastructure; unmanaged dedicated gives you bare hardware. Same considerations as VPS, just larger scale.
A realistic budget for unmanaged
Going unmanaged isn’t just the VPS price. Realistic monthly time budget for a competent admin running a small unmanaged setup:
- Routine updates and monitoring: 2-4 hours/month.
- One thing breaks per quarter: 3-8 hours to fix.
- One real emergency per year: full day or two.
At even modest hourly rates this exceeds the managed price difference. If you’re paying yourself fairly, unmanaged is a hobby choice, not an economic one.
Decision framework
- Time vs. money: if your time has high opportunity cost, lean managed.
- Skill match: if you’re not already a sysadmin, the unmanaged learning curve will be steep.
- Workload: single static site = unmanaged feasible. Multiple sites + email + collaborators = managed essential.
- Risk tolerance: can you afford a multi-day site outage while you debug an unmanaged server? If not, managed.
- What you actually enjoy: if you’d rather build sites than maintain Linux, managed. If you genuinely enjoy server admin, unmanaged is fine.
What’s next
- If going unmanaged: LAMP/LEMP setup.
- SSH security on either type: SSH keys.
- cPanel basics (what you get on managed): File Manager guide.
Most users come asking about unmanaged because the price looks attractive, then end up wanting to switch within months. Save yourself the migration — be honest about what you want to spend your time doing, and pick accordingly. Unmanaged is fine for a specific kind of user; the people for whom it’s wrong learn this the hard way.
Was this helpful?
Thanks for your feedback!
