You've outgrown shared hosting. Or you need full root access. The next step is a VPS — but which flavor? Managed or unmanaged? The wrong choice wastes time or money. Or both.
This checklist covers 12 concrete items. No fluff. Each item is a yes/no question or a test. Answer honestly, and you'll know exactly which VPS type fits.
1. Do you know how to secure a Linux server from scratch?
Unmanaged means you are the sysadmin. That includes: - Locking down SSH (disable root login, use key-based auth) - Configuring a firewall (iptables, nftables, or ufw) - Installing and configuring fail2ban - Applying kernel and package updates
If you can run this checklist without Googling every command, you can handle unmanaged. If not, start managed.
# Quick test: list all listening ports
ss -tlnp
# If you can't interpret the output, go managed.
2. What's your monthly budget for server administration?
Managed VPS costs more per month — typically 30–50% above the raw VPS price. But that premium buys hours of sysadmin time.
Calculate your own hourly rate. If you spend 5 hours per month on server upkeep, and your time is worth $75/hour, that's $375. Compare that to the managed plan fee. Often, managed is cheaper than your own time.
3. Can you troubleshoot a down server at 3 AM?
Servers fail. Unmanaged means you're on call 24/7. Managed providers have NOC teams. They'll fix issues while you sleep.
Real scenario: A kernel panic after an update. With unmanaged, you need out-of-band access (IPMI) or a rescue mode. With managed, you open a ticket and wait.
Test: Have you ever dug through dmesg logs to find a hardware fault? If yes, unmanaged is feasible.
4. Do you need cPanel, Plesk, or another control panel?
Most managed VPS plans include a licensed control panel. Unmanaged usually does not — you pay separately.
cPanel alone can cost $15–30/month extra. If you rely on a GUI for account management, managed is likely cheaper once you factor licensing.
5. How comfortable are you with the command line?
Be honest. "Somewhat comfortable" doesn't cut it. You need to edit config files in vim/nano, restart services, check logs, and parse error messages.
Quick test: Restart Apache from memory.
systemctl restart httpd # RHEL/CentOS
systemctl restart apache2 # Debian/Ubuntu
If you had to think twice, you'll benefit from managed support.
6. Is your site mission-critical with strict uptime SLAs?
Unmanaged VPS typically offers no SLA for server admin issues. Only network and hardware uptime. If your application crashes due to a misconfiguration, that's on you.
Managed providers usually include an SLA covering response times for critical issues. If downtime costs your business real money, the managed premium is an insurance premium.
7. Can you handle email server headaches?
Setting up and maintaining a mail server on an unmanaged VPS is notoriously painful. Deliverability, reverse DNS, SPF, DKIM, DMARC, greylisting — it's a long list.
Managed VPS often includes email support. Many unmanaged plans don't touch mail at all.
# Quick sanity check on your current mail server
hostname -f
# Does the PTR record match? If you don't know what that means, go managed.
8. Do you regularly monitor logs and performance?
Unmanaged means you're responsible for monitoring. You'll set up tools like Netdata, Nagios, or Prometheus. Or you'll rely on periodic "is it slow?" checks.
Managed providers often include basic monitoring and will alert you to issues like high load or disk space.
9. What's your backup strategy?
Unmanaged: you must configure backups manually — either via cron scripts, rsync to offsite storage, or third-party backup tools. Restoring also is your job.
Managed: backups are typically part of the package, with automated daily snapshots and one-click restore.
Test: Can you write a one-liner to tar /var/www and send it to an S3 bucket? If no, managed might save you.
10. How often does your server software stack change?
If you run a static site with nginx and nothing else, unmanaged is trivial. But if you need PHP, MySQL, Redis, Node.js, and custom modules, version conflicts happen.
Managed providers handle dependency management and updates. Unmanaged means you manually compile or install from repos, then deal with breakage.
11. Are you comfortable with security incident response?
A compromised unmanaged server is your problem. You'll need to triage, find the entry point, clean malware, and patch the hole.
Managed support teams have incident response procedures. They can isolate and restore from a known-good backup.
Quick test: If you found a suspicious cron job running a curl command, would you know how to investigate? If not, go managed.
12. Do you need scaling and migration assistance?
Unmanaged VPS requires you to upgrade resources manually (often a reboot) and migrate data yourself. Managed providers often assist with scaling — adding RAM or CPU can be a support ticket.
For growing sites, this can be a major time saver.
FAQ
Q: Can I start with unmanaged and switch to managed later? A: Yes. Most providers allow upgrades to a managed plan. However, migrating your existing server to a new plan may require data transfer.
Q: What if I have a good control panel but still want system-level support? A: Some managed VPS plans offer limited admin support — e.g., they'll handle the OS but not the panel's inside. Read the support scope carefully.
Q: Is there a middle ground? A: Some providers offer "semi-managed" plans — you get support for specific issues (like mail failures or firewall rules) but not full admin. This is less common but worth asking.
Q: What's the biggest red flag for unmanaged? A: Not having a backup. If you can't afford to lose data, ensure you have an automated, off-site backup before going unmanaged.
What to check first
Print this list. Answer every question. If you said "no" to more than three items, go managed. If you said "yes" to all twelve, unmanaged will work — but keep a backup and a monitoring plan.
The decision isn't permanent. Start with managed, learn the ropes, then switch to unmanaged later. Or stay managed and reclaim your weekends.