Managed vs unmanaged VPS: who does what, and do you need root?

Managed vs unmanaged VPS comes down to who runs the server, and at DreamHost the line falls at root access. DreamHost calls its unmanaged VPS self-managed: VPS Hosting gives you full root and a library of one-click app images, and the server's upkeep is yours. The Managed VPS page draws the line itself: For Docker, system-level changes or agents that need full server control, choose self-managed VPS.

To put a number on that upkeep, DreamHost built a small Debian web server from the package archive as it stood a month earlier and checked it on October 20, 2026. It had 20 updates waiting, PHP among them. Built from the archive of two months earlier, it had 55, with nginx and the system's C library on the list. On Managed VPS, DreamHost applies those. On VPS Hosting, you do. The results and method are further down.

Who does what on each

The Managed VPS page sums up the split: You run the website. We run the server. The table below follows DreamHost's Managed VPS and VPS pages as they read on October 22, 2026, and the Help Center articles listed under Sources for the cells those pages don't cover.

On cost, add a Professional Email plan to the VPS side if you want email at your domain, and count your own time for the updates and backups.

Managed VPS covers the server, and your code stays yours to build and fix. The Managed VPS page splits it as We maintain the server; you manage your application, and its FAQ adds that custom development, design and ongoing website management may need a separate service. If you install your own Node.js version, DreamHost's Help Center says support is unable to assist with custom installations.

On VPS Hosting, the VPS page FAQ says DreamHost guarantees the underlying infrastructure (hardware, network and uptime) and that its support team is available 24/7. DreamHost's Help Center VPS overview adds that you configure and maintain the server, and that a VPS doesn't include server management, automated backups or a 30-day money-back guarantee.

Managed Dedicated is the third path. DreamHost's Help Center says a Dedicated Server gives its admin user full root access through sudo, and the Dedicated page offers it fully managed or self-managed. The same managed vs unmanaged question on a whole server is answered in managed or unmanaged dedicated server, and when a dedicated server is the next step covers the move up. WordPress sites have their own comparison of DreamPress and Managed VPS, and if you haven't settled on a VPS at all, start with whether you need one.

Jobs that need root, and jobs that don't

Root is the server's administrator account, the one that can install system software and change any setting. You'll need it when your project changes the server itself. Websites run without it, and so do Node.js or Python apps installed with the Help Center's NVM and virtualenv steps.

Line up what you'll run against this list. Any No in the middle column points to VPS Hosting, or to Managed Dedicated if you'd still like DreamHost to run the server.

App developers should know about the Proxy Server row. The Help Center's Node.js article notes that a Node.js app on Managed VPS can't use ports 80 or 443, and that a Proxy Server set up in the panel passes web traffic to the port your app listens on instead. Its linger article covers keeping the app running. Docker is the firmer limit: its standard install guide runs every command with sudo, and Docker's install script requires root or sudo privileges.

AI coding tools fit on both. The Managed VPS page says a compatible AI coding tool connected over SSH can edit files, deploy updates and investigate logs within your account's permissions. Agents that need full server control belong on a self-managed VPS, per the Managed VPS page.

If you're leaving cPanel and want a control panel on a self-managed server, control panels that work on your own VPS compares the options.

Switching later is a manual move

You can change your mind, but you'll do it by hand. DreamHost's Help Center says the panel can't move content between a VPS and a Managed VPS in either direction, so a switch means copying your sites and data yourself. It also says managed hosting add-ons such as Bunny CDN and the SEO Toolkit can't be added to a VPS. If you're coming from DreamHost shared hosting, the Help Center describes a panel Transfer button on Managed VPS that moves your websites and users while your email keeps working.

Resizing works differently on each, per the Help Center's plan-change articles. A Managed VPS changes plan in the panel, down as well as up if your data fits, with a prorated credit for the old plan's remaining time. A VPS moves up from Stack 4 to Stack 32 with your setup intact, while going down a size means a new server and a manual move.

Managed VPS comes with a 30-day money-back guarantee, and DreamHost's Help Center says VPS Hosting doesn't. Its refunds article adds that when you cancel a yearly VPS plan, you get a prorated credit for the unused time, which you can spend on other DreamHost services.

When something breaks, who fixes it

On a Managed VPS, DreamHost fixes problems with the server itself. On VPS Hosting, the operating system and everything on it are yours to fix, and root lets you change any part of it the moment you find the problem.

A memory spike slows your site

On Managed VPS, Auto-Boost temporarily adds RAM, when available, during memory spikes, and resource graphs and alerts show you the demand. If higher usage continues, the Managed VPS page says to optimize your sites or move to a plan with more capacity. Moving a Managed VPS up in RAM doesn't restart it, per the Help Center's Managed VPS overview. A VPS has no Performance or Logs dashboard in the panel (the VPS overview lists both as managed features), so the digging starts on the server itself. Either one can reboot from the panel, and the Reset a VPS article explains that Restart Server reboots a VPS without erasing any data.

You delete or break files

Managed VPS includes daily automated backups, and you can restore a site's files from a backup on the Manage Websites page, as DreamHost's Help Center restore article explains. Databases restore separately, so also download a panel account backup, which copies your databases and mailboxes. On a VPS you restore from whatever backup you made yourself.

You lose your SSH key

The Help Center's VPS setup article says DreamHost doesn't store the login credentials you set on a VPS, so the fix for a lost key is Reset Server, which rebuilds the server from scratch and replaces everything on it. On Managed VPS, the Help Center has you create each user in the panel, so you regain access there.

Self-managed upkeep, measured

We ran this test on October 20, 2026, on a test VM. No DreamHost server was involved. We set up the same small web server several times, each from its distribution's package archive as it stood 30, 60 or 90 days earlier. The set was nginx, PHP-FPM, MariaDB, Certbot, OpenSSH and a few tools, 233 packages in all, with nothing configured. Then we pointed each one at the live archive and counted the updates waiting.

The 60- and 90-day Debian servers waited on the same 55 packages because both archive snapshots predate Debian's 13.7 point release on September 12, and nothing in this set changed between them. So the backlog arrived in a lump with the point release. Applying the Debian updates took 15 to 56 seconds of machine time. We didn't time the human part: reading the list, restarting what needs it, and loading each site afterwards.

The counts leave two things out. Containers have no kernel of their own, so kernel updates, which mean a reboot on a real server, aren't included. And apps you add, such as Docker images or WordPress plugins, bring their own updates on top.

These are the jobs a self-managed server hands you:

1. Apply updates every month

   On a self-managed VPS, the 20 to 55 updates above are yours to apply. Ubuntu installs unattended-upgrades by default and it applies some updates on its own; on Debian, check that it's installed. Either way, check what it left for you and plan a reboot when a new kernel arrives.

2. Check your sites after each round

   Our 30-day list already included PHP-FPM. Load each site and your app's main pages after updates go in.

3. Back up and copy it off the server

   A VPS has no panel backup or moving tool, per the Help Center's migration article. Script a copy of your files and databases to somewhere other than the server, and test a restore now and then.

4. Plan the next OS release

   Standard updates for Ubuntu 24.04 LTS run to May 2029, and for 26.04 LTS to May 2031, per Ubuntu's release cycle. Moving to a new release is a job you'll schedule and test.

If nobody on your side can take on all four of those jobs, pick Managed VPS. If root is on your list and the upkeep is covered, which Stack plan to start on sizes a VPS by what you'll run on it.

Managed vs unmanaged VPS FAQs