Short answer: with a managed VPS, the provider also runs the operating system for you: security updates, monitoring, backups and help with the software on it. With an unmanaged VPS, the provider runs the hardware, the network and the virtualisation, and everything inside the virtual machine is your job, from the first apt upgrade to restoring a broken database. Unmanaged costs less money and more of your time. Managed is the reverse.
If you can set up a Linux server, or want to learn, unmanaged gives you more control for less money. If the server runs a business and nobody on your side can fix it in the middle of the night, pay for management, or choose managed web hosting instead of a server.
Who does what on a managed and an unmanaged VPS?
| Task | Unmanaged VPS | Managed VPS |
|---|---|---|
| Hardware, power, virtualisation | Provider | Provider |
| Network, and DDoS mitigation where offered | Provider | Provider |
| Installing or reinstalling the OS | You, from the provider's templates | Provider |
| Security updates | You (can be automated) | Provider |
| SSH, firewall, hardening | You | Provider, usually |
| Web server, database, runtimes | You | Provider sets them up. Your own application stays yours |
| Monitoring and alerts | You | Provider, usually |
| Backups | You, with the provider's tools | Provider, including restores |
| Fixing a server that will not boot | You, through the console | Provider support |
| Cleaning up after a break-in | You | Depends on the contract |
| Root access | Full | Full, limited or none, depending on the plan |
| Price | Lower | Higher |
The first two rows are the same on both. Every VPS, managed or not, depends on the provider for hardware and network. What you buy with “managed” is the administration of the system inside the VM.
What does “managed” actually include?
There is no standard definition. Some hosts call a VPS managed because it ships with a control panel. Others patch the OS, monitor it around the clock and repair your stack when it breaks. Before you pay for management, get these answers in writing:
- What do they patch? Only the OS, or also the web server, PHP, the database and the control panel?
- Is your application covered? Your code, your WordPress plugins and your containers are almost always excluded.
- How fast do they respond, and is that a promise in the contract or a line on the sales page?
- Do you keep root? Some managed plans restrict it so the provider can guarantee its setup. That rules out software they do not support.
- Where do backups go, how often do they run, how long are they kept, and is a restore included or billed?
- What happens after a compromise? Clean-up, a restore from backup, or a suspension until you fix it?
- Which work is billed by the hour, and is the control panel licence included in the price?
How much work is an unmanaged VPS?
You pay for the lower price with your time. On a single small server, the recurring work looks like this:
| Task | How often | How |
|---|---|---|
| Security updates | Daily, automatically | unattended-upgrades, set up once |
| Reboot after kernel updates | When an update needs it | A planned reboot in a quiet hour |
| Check disk, memory and errors | Weekly | df -h, free -h, journalctl -p err -b |
| Test a backup restore | Monthly | Restore to a spare directory or a test server |
| Review users, keys and open ports | Monthly | ss -tulpn, every authorized_keys file |
| Distribution upgrade | Every few years | For example Debian 12 to 13 |
| Incidents: full disk, crashed service, attack | Whenever they happen | You, with the console |
Once it is automated, the routine part takes little time. The real cost is the incident you have to solve yourself, at a time you did not choose. If that thought is fine with you, unmanaged is the better deal.
How do unmanaged servers usually get into trouble?
Most incidents on a server you run yourself come down to one of five things. Each can be spotted with one command long before it turns into an outage:
- The disk fills up. Logs, old backups and Docker images grow until the database cannot write. Check with
df -h, find the culprit withsudo du -xh --max-depth=1 / | sort -h, and shrink the system journal withsudo journalctl --vacuum-size=200M. ASystemMaxUse=line in/etc/systemd/journald.confkeeps it capped for good. - Updates stopped months ago.
apt list --upgradableshows what is waiting, and/var/log/unattended-upgrades/unattended-upgrades.logshows whether automatic updates still run. - Password logins are still open to the internet.
sudo journalctl -u ssh --since today | grep -c "Failed password"counts today’s guesses. Switch to keys and the count stops mattering. - Memory runs out. The kernel then kills a process, usually the one using the most memory, which is often the database.
sudo journalctl -k | grep -i "killed process"shows whether it has happened. Add swap, tune the service, or move to a bigger plan. - Backups exist but have never been restored. A backup you have not tested is a hope, not a backup. Restore one to a spare directory once a month and open a few files.
Watching for the first four is the kind of monitoring a managed plan sells. On an unmanaged server, a weekly five-minute look at these commands does most of the same job.
Which one should you choose?
Unmanaged fits when
- You or your team are comfortable in a Linux shell or with Windows Server.
- You run things a managed plan tends to restrict: Docker, a game server, a VPN, security tools, software the provider has never heard of.
- Price matters and you can spare a few hours a month.
- The server is reproducible: staging, CI runners, a bot, anything you can rebuild from a script or a backup.
Managed fits when
- The server earns money and nobody on your side can fix it quickly.
- An auditor or customer requires documented patching and monitoring.
- You would rather pay than learn server administration.
The middle paths
- Managed web hosting. If all you run is websites, a hosting account with a control panel gives you the managed part without a server to look after. The cPanel vs Plesk comparison helps you choose the panel.
- Unmanaged VPS with a control panel. Plesk or cPanel on your own VPS makes sites, mail and certificates clickable. The OS underneath is still yours to patch, and the panel needs its own licence.
- Unmanaged VPS plus a freelancer. Someone you pay for setup and emergencies costs less than a managed plan if you rarely need them.
If you go unmanaged: the first hour
Many compromised servers were never hardened in the first place. Do this before you install anything else:
apt update && apt full-upgrade -y
apt install -y sudo # missing on some minimal Debian images
adduser deploy && usermod -aG sudo deploy
# automatic security updates (preinstalled on Ubuntu; on Debian it depends on the image)
apt install -y unattended-upgrades
dpkg-reconfigure unattended-upgrades # answer Yes
# firewall: allow SSH BEFORE you enable it
apt install -y ufw
ufw allow 22/tcp # or your custom SSH port
ufw enablessh-copy-id deploy@203.0.113.10
ssh deploy@203.0.113.10 # test in a second window before you log out as rootThen turn off password logins for SSH, as described in securing SSH access. The initial server setup guide walks through the whole first session step by step.
On a Windows VPS
The split is the same. Windows Update, the Windows Firewall and Remote Desktop hardening are yours to set up: restrict who may reach the RDP port, use long passwords, and check that updates install. On a Windows VPS at VMHeaven you log in as Administrator, and the server runs on a time-limited evaluation licence until you activate your own key.
What unmanaged means at VMHeaven
VMHeaven’s VPS are unmanaged, and the service scope section of our acceptable use policy says so: we provide the platform, and you manage, configure and use your server. In practice:
- We run the hardware, the network, the always-on DDoS mitigation, the virtualisation and the customer panel.
- You run everything inside the VM, with full root on Linux and the Administrator account on Windows. Our terms say software installation and custom configuration are done only on request and billed separately.
- Backups are your responsibility under our terms. The panel makes them easy, but keep an independent copy elsewhere of anything you cannot lose.
The panel covers the parts of “managed” you are most likely to miss:
- Reinstall from a template: Ubuntu 24.04, 22.04 and 20.04, Debian 13, 12 and 11, CentOS Stream 9 and 8, Rocky Linux 9, Windows Server 2022 and 2019. It erases the disk, so take a backup first.
- Browser VNC console: a screen on the machine even when its network is broken, for the day a firewall rule or a network config edit locks you out.
- Backups taken by hand or on a daily, weekly or monthly schedule, and restored from the panel.
- Network reset: rewrites the network configuration from the addresses the panel has on record and reboots. It also regenerates the SSH host keys and resets the root password to the one stored in the panel.
- Reverse DNS for your IPs, set by you, and power controls to start, stop and restart the server.
Pick Standard KVM for general workloads, or Hi-CPU KVM on AMD EPYC for work that leans on one or two cores. If you want websites without any server administration, Plesk web hosting is the managed option: daily backups with up to ten restore points, and free migration of your existing sites. Dedicated servers are unmanaged by default too; a managed add-on is available on request from sales.
Frequently asked
Is an unmanaged VPS less secure than a managed one?
Not by design. The same software runs on both, and the difference is who applies updates and watches the logs. An unmanaged VPS with automatic security updates, key-only SSH and a firewall is well protected, while one that nobody patches is not.
Does VMHeaven offer managed VPS?
No. VMHeaven's VPS are unmanaged: you get full root and panel tools such as reinstall, a browser VNC console, backups, reverse DNS and power controls, and you run the system yourself. For websites without any server administration, VMHeaven offers managed Plesk web hosting.
Do I get root access on a managed VPS?
It depends on the provider. Some managed plans give you full root and ask you not to change what they maintain, while others restrict or withhold it so they can guarantee their setup. Ask before you buy if you need to install your own software.