Managed vs Unmanaged VPS: What Support Actually Covers

Every week someone signs up for a cheap unmanaged VPS, gets a root password and a blank Ubuntu box, and then opens a ticket asking us to install WordPress on it. We can't — it's not our server. This is the single most common misunderstanding in VPS hosting, and it usually gets discovered at the worst possible time: when something breaks at 2 AM.

The Short Version

A managed VPS means the hosting provider is responsible for the operating system, security patches, the control panel, the web server, and (usually) fixing things when they break. An unmanaged VPS means you get root access to a bare server and everything past that is on you — OS updates, firewall rules, backups, and every "why is my site down" 2 AM debugging session.

Both are billed as "VPS hosting." The line between them is support scope, not hardware. That's the part people miss when they compare plans purely on vCPU and RAM.

What "Managed" Actually Includes

Scope varies by provider, so always check the fine print, but a reasonable managed VPS plan covers:

• OS and security patching (kernel updates, package updates, CVE fixes)
• Control panel installation and licensing (cPanel/WHM, Plesk, or a custom panel)
• Web server, PHP, and database setup and tuning (Apache/Nginx, PHP-FPM pools, MySQL/MariaDB)
• Firewall and basic hardening (SSH lockdown, fail2ban, CSF/ConfigServer rules)
• Automated backups, with restore support if something goes wrong
• 24/7 monitoring and a support team that will actually SSH in and fix a crashed service

What it usually does not cover: your application code, plugin conflicts, custom scripts you installed yourself, or anything you changed by hand outside the control panel. If you edited php.ini directly instead of using the MultiPHP INI Editor, don't be surprised if support asks you to revert it before they'll touch the ticket.

What "Unmanaged" Actually Means

An unmanaged VPS gives you root SSH access and, at most, a base OS image. Everything else is your job:

• Installing and updating the OS, kernel, and every package
• Configuring the firewall (UFW/iptables) and closing unused ports yourself
• Installing and securing a web server, PHP, and a database — or a full LEMP/LAMP stack
• Setting up your own backup strategy (there usually isn't one by default)
• Diagnosing and fixing anything that breaks, including the server not booting

Support on an unmanaged plan is generally limited to the hypervisor level: is the VM running, does it have network connectivity, can it reach the internet. If AlmaLinux won't boot after a kernel update or MySQL is refusing connections, that's a "you" problem, not a "them" problem.

The Support Ticket Test

The fastest way to tell which one you actually have is to imagine opening these tickets and picture the reply:

Notice that even on a managed plan, application-level bugs (a broken plugin, bad custom code) are rarely covered. "Managed" means the infrastructure is someone else's problem — it doesn't mean unlimited free WordPress support.

Who Should Actually Pick Unmanaged

Unmanaged makes sense when:

• You (or your team) already run production Linux servers and want full control over versions and configs
• You're deploying something non-standard — a custom Docker stack, a Node.js cluster with PM2, a K3s node — where a generic control panel would get in the way
• Budget matters more than hand-holding, and you can genuinely absorb a few hours of downtime while you fix something yourself

If your idea of "I know Linux" is having used Ubuntu once in college, this is the wrong box to learn on with a production site.

Who Should Pick Managed

• You run a business site or store and can't afford unplanned downtime while you Google an error message
• You want cPanel/WHM so you (or a non-technical teammate) can manage email, domains, and backups without SSH
• You'd rather pay a predictable monthly fee than gamble on an emergency sysadmin bill when something breaks on a Sunday

The Cost Math People Skip

Unmanaged plans look cheaper on the price page, and per month they usually are — sometimes by 30-50%. But that comparison only holds if nothing ever breaks. Add up what one bad weekend actually costs:

• Emergency sysadmin help, if you have to hire it ad-hoc, often costs more per hour than a managed plan costs per month
• Lost orders or leads for every hour a store or lead-gen site is down
• Your own time, if you're the one debugging a crashed MySQL instance instead of doing your actual job

If you'd genuinely enjoy fixing a kernel panic at midnight, unmanaged saves you real money. If you'd rather never find out what a kernel panic looks like, the managed plan is cheaper than it looks on the invoice.

A Middle Ground: Semi-Managed

Some providers, including Getwebup, offer a semi-managed tier: the OS, control panel, and core stack are maintained for you, but you keep root access for anything custom — installing your own Node app alongside cPanel, running a cron job, or SSHing in to debug. It's worth asking specifically what's included rather than assuming "managed" means the same thing everywhere; the term isn't standardized across providers.

Prevention: Ask These Questions Before You Buy

1. Does the plan include a control panel license, or is that a separate add-on?
2. Are OS and security patches applied automatically, or only on request?
3. What's the backup frequency and retention, and is restoring from one included or billed separately?
4. What's the actual support SLA — email only, or 24/7 with someone who can SSH in?
5. Is application-level support (WordPress, WooCommerce, a custom app) covered at all, even as a paid add-on?

Get these answers in writing before you migrate anything. "Fully managed" on a pricing page and "fully managed" in the terms of service don't always match.