Two VPS offers look alike on paper, but one says managed and costs more. Before you pay the difference, you want to know what the cheaper one leaves to you: the updates, the reboots, the backups, and the evening a disk fills up or a service stops. Here is who does each job on a self-managed VPS and on a typical managed server, what managed plans still leave to you, and how to put a number on your own time.
Quick answer: On a self-managed VPS, also called unmanaged, the provider runs the hardware, the network and the virtualization layer. You run everything inside the server: security updates and reboots, the firewall and SSH, monitoring, backups and restores, the software and your app. Managed hosting moves the operating system work to the provider, usually with monitoring that someone acts on, backups and a preinstalled stack or control panel. It rarely covers your own code, plugins, extra software or speed tuning, and some managed servers take away root access and Docker. Choose self-managed if you can rebuild the server yourself and the hours cost you less than the price gap; otherwise pay for managed.
Where the Line Sits
Every VPS has a line between the provider's work and yours. AWS draws it plainly for its EC2 virtual machines: AWS runs the components "from the host operating system and virtualization layer down to the physical security of the facilities", while customers are "responsible for management of the guest operating system (including updates and security patches), any application software or utilities installed by the customer on the instances", plus the firewall rules (shared responsibility model). A self-managed VPS from any host splits the work the same way.
Providers use different words for it. DigitalOcean says its Droplets "are completely unmanaged" and that its support team "cannot access your Droplets directly" (Droplet policies). Liquid Web calls the same level self managed: it supplies power, network and infrastructure, "leaving ongoing management, maintenance, and support of the system up to you" (management and support levels). Managed hosting moves the line up the stack, but rarely all the way to your app.
Who Does Each Job
| Job | Self-managed VPS | Typical managed server |
|---|---|---|
| Hardware, power and network | Provider | Provider |
| Installing the operating system | You pick an image and reinstall when needed | Provider installs the OS and a software stack |
| Security updates and kernel reboots | You, with unattended-upgrades doing the daily part | Provider |
| Firewall and SSH access | You | Provider; some give you only a normal user |
| Monitoring and acting on alerts | You | Provider watches key services and steps in |
| Backups and restores | You, or a backup service you add | Often included |
| Web server, PHP, database, mail | You install, update and repair them | Provider, for the stack it supplies |
| Other software, such as Docker or a game panel | You | You, or not allowed |
| Your code, plugins, themes and content | You | You |
| Speed tuning of your site or app | You | Usually you |
| Release upgrades, such as Ubuntu 24.04 to 26.04 | You | Provider, where it runs the OS |
The managed column follows two published scopes, both checked 31 October 2026: Hetzner's managed servers, which include a line of virtual servers, and Liquid Web's fully managed servers. Other offers draw the line elsewhere, so read the scope page of the plan you consider. Our managed VPS buying checklist lists the questions to ask, and our guide to what a VPS price includes covers support hours and backup costs.
What Managed Hosting Adds
These scope pages come down to four services:
- Updates and hardening. On Hetzner's managed servers, its technicians "continuously take care of security updates, hardware problems, backups, and the server's general administration". Its comparison page adds a managed firewall with standard rules and regular system hardening.
- Monitoring that someone acts on. Hetzner checks ping, HTTP, SMTP, POP3, FTP and DNS from outside every minute, and critical processes inside every 5 minutes. Liquid Web monitors HTTP, DNS, mail, MySQL or MariaDB, SSH and the control panel on managed servers; on self-managed servers it checks only ping and SSH, "with no remediation" (Linux scope of support). Cloudways says its support team acts on server and stack alerts without you having to contact it (support).
- Backups. Hetzner makes daily automatic backups that you restore in its konsoleH panel. Liquid Web helps you set up and restore backups from the backup products it supports.
- A supported stack. Hetzner preinstalls Debian, Apache, MariaDB and PHP, plus a mail stack. Liquid Web's fully managed servers run cPanel, Plesk or InterWorx, and its team troubleshoots Apache, MySQL or MariaDB, PHP, SMTP, FTP and SSH.
What Managed Hosting Leaves to You
The same pages are just as clear about the limits:
- Your code, content and speed. Liquid Web's fully managed support does not cover "Adding, removing, or modifying web pages, code, plugins, or themes" or "Code, database, or website performance optimization", and its Linux scope excludes custom Docker containers. Cloudways lists debugging custom code and application level security issues as out of scope on every support plan. Even malware clean-up is an extra: Liquid Web offers it as "an additional service for fully managed servers".
- Freedom to install. Hetzner's managed servers have no root access (SSH runs as a normal user, "no root, no sudo"), no virtualization such as Docker, and "In most cases, it is not possible to install additional (or other) software". A Node.js app in Docker, a game panel or an AI agent may not run there at all.
- Leaving. Cloudways also excludes moving your site to another provider.
So managed hosting pays off most when your software fits the stack the provider maintains.
What Self-Managed Means Each Month
Patches keep coming. In September 2026 alone, Ubuntu published 131 security notices that cover 24.04 LTS, 25 of them for Linux kernel packages (Ubuntu Security Notices). You don't install those by hand: on Ubuntu the unattended-upgrades package "is installed by default" and applies security updates once a day (Ubuntu automatic updates). What stays with you:
- Reboots.
Unattended-Upgrade::Automatic-Rebootdefaults tofalse, so a new kernel waits for you. The package's kernel hook writes the request to /var/run/reboot-required. - Repositories you added. Ubuntu warns that adding a repository will not make unattended-upgrades consider it, so packages from, say, Docker's repository wait for you, and so do Docker images and your app's own dependencies.
- Debian 12. If nothing sets
APT::Periodic::Unattended-Upgrade, apt's daily script treats it as0, which means off. Install the package and switch it on:
sudo apt install unattended-upgrades
sudo dpkg-reconfigure -plow unattended-upgrades
Then a short check once a month covers the rest. It works on Ubuntu 24.04 and Debian 12:
apt-config dump | grep -E 'APT::Periodic::(Update-Package-Lists|Unattended-Upgrade)'
systemctl list-timers 'apt-daily*'
sudo apt update
apt list --upgradeable
cat /var/run/reboot-required.pkgs
systemctl --failed
sudo journalctl -p err -b -n 30 --no-pager
df -h /
df -i /
- Both
APT::Periodiclines should show"1", which means daily;"0"or no output means automatic updates are off.list-timersshows when apt's two daily timers last ran and run next. apt list --upgradeableshows what is still waiting. On Ubuntu that is mostly non-security updates, which unattended-upgrades leaves alone by default; install them withsudo apt upgradewhen it suits you.- If /var/run/reboot-required.pkgs exists, it names the packages that asked for a reboot. Restart at a quiet hour with
sudo systemctl reboot. systemctl --failedlists units in a failed state, and the journalctl line shows the last 30 messages of priority err or worse from the current boot.df -h /shows the space left on the root filesystem anddf -i /the free inodes. When either runs out, nothing new can be written there.
The first setup is a one-time job: SSH keys and a firewall (UFW and fail2ban), a check from outside that alerts you when the server stops answering (Uptime Kuma), and backups stored off the server (restic over SSH) that you have restored at least once (restore drill).
Every few years comes a bigger job. Ubuntu 24.04 LTS gets standard security maintenance until May 2029 (release cycle), and Debian 12 has Long Term Support until 30 June 2028 (Debian). Before then you upgrade in place, or build a new server on the next release and move your data, which is the same work as a migration.
How to Judge Your Own Time
The price gap is printed on the order page; your time is not. Estimate it in three parts:
- Routine. Run the monthly check above once and time it, updates and reboot included.
- Yearly jobs. Add the first setup, your restore drills and your share of the next release upgrade, spread over twelve months.
- Incidents. If you have run a server before, count the evenings it cost you last year. If you haven't, assume there will be some.
Add these up per month and multiply by what an hour of your time is worth: what you earn in it, or what you would pay someone else. For example, an hour of routine a month plus one three-hour evening each quarter comes to two hours a month. If two of your hours cost more than the monthly price difference between the managed and the self-managed offer, managed is the cheaper choice.
Three questions matter as much as the sum:
- Can you rebuild the server without help? If you have never restored your backup end to end, you don't know your incident time yet.
- Who answers an alert at 3 a.m.? On a self-managed VPS, you do, or it waits until you are up. A managed provider's monitoring acts on it within its scope.
- Does your software fit a managed stack? Docker, Node.js services, game panels and AI agents often fall outside it. Then the choice is between doing the work yourself and paying someone to do it.
How Support Works on Our VPS
Our VPS plans are self-managed KVM servers with full root access in an EU data center. You manage the operating system, software, updates and application configuration; the hardware, the network and DDoS protection are ours. Human support answers from 08:00 to 20:00 UTC by live chat, Discord and email. Backups are not included in the plan price; you can arrange them through a support ticket. If you want help managing the server itself, ask support about the scope before you order.
Which One Fits
- Self-managed if you are comfortable with SSH, apt and logs, you need root or Docker, your service can wait until you are awake, and your hours times your rate stay below the price gap.
- Managed if you run a standard stack such as WordPress on PHP and MySQL, nobody on your team wants to handle alerts, and an hour of downtime costs more than the price difference.
- Neither if all you need is a website or a game server: with web hosting or a Minecraft server with a panel, the host runs the operating system for you. For a website, our shared hosting or VPS comparison helps you choose.
- Self-managed with help if your software needs root but you don't want every job: automate updates, add outside monitoring and backups, and pay an administrator for the rest.
FAQ
Is an unmanaged VPS the same as a self-managed VPS? Yes. In both, the provider runs the hardware and network, and you run the operating system and everything on it. DigitalOcean says "unmanaged", Liquid Web "self managed".
Will a managed provider fix my website or app? Usually not. Managed support covers the server and the stack the provider supplies. Liquid Web and Cloudways both exclude work on your code, and Liquid Web also excludes plugins, themes and site speed (checked 31 October 2026).
Do I keep root access on a managed server? Not always. Hetzner's managed servers give you SSH as a normal user with no root and no sudo, and no virtualization such as Docker. If your software needs root, ask before you order.
Are security updates automatic on a self-managed VPS? Security updates are on Ubuntu, where unattended-upgrades is installed by default and runs daily. On Debian 12, check that it is on. Reboots, packages from repositories you added and software outside apt stay with you on both.
Can I move from self-managed to managed later? Usually by moving to a new server, because a managed server runs the provider's own system, such as Hetzner's Debian-based distribution with its LAMP stack. Our VPS migration guide covers the move.
Sources
All opened on 31 October 2026:
- Space-Node: VPS plans and FAQ
- AWS: Shared Responsibility Model
- DigitalOcean: Droplet policies
- Liquid Web: Server Management and Support Scope, Linux scope of support
- Hetzner: Managed servers, Differences between managed servers and bare metal servers
- Cloudways: Support
- Ubuntu: Automatic updates, Release cycle, Security notices for 24.04 LTS
- Debian: Security support for Bookworm handed over to the LTS team
- unattended-upgrades 2.9.1: README, kernel postinst hook
- apt 2.6.1: apt.systemd.daily
- Man pages for Ubuntu 24.04: apt(8), apt-config(8), systemctl(1), journalctl(1), df(1)
- Man pages for Debian 12: apt(8), apt-config(8), systemctl(1), journalctl(1), df(1)