Skip to main content
wordpressevaluation

Managed vs Unmanaged WordPress: What You're Actually Paying For

The SrvBot team

“Managed” and “unmanaged” are used loosely enough that the labels have stopped meaning much. The real distinction is simple: who does the server-level work — you, or the host?

What unmanaged really means

A cheap VPS is the clearest example of unmanaged: you get a server and root access, and everything above bare metal is yours. OS patching, the nginx and PHP configuration, security hardening, backups, SSL certificates, monitoring — all of it. That’s a genuinely good deal if you’re comfortable operating a Linux server. It’s a second job if you’re not.

What 'managed' should include (and often doesn't)

A real managed plan takes the operational layer off your plate: automatic OS and security patching, backups you can actually restore, SSL that renews itself, isolation between sites, monitoring, and support that understands the stack. The trap is that some hosts sell “managed” that manages very little beyond a control panel bolted onto an otherwise unmanaged box.

The hidden middle

Before you buy, ask a specific question: what do you actually operate on my behalf? If the answer is vague, or turns out to be “we give you a dashboard,” you’re closer to unmanaged than the label suggests — and you’ll find out the first time something at the server level breaks.

How we draw the line

On SrvBot, each site runs in its own dedicated container on Ubuntu with nginx. OS and security patching run automatically. Backups are taken daily and restore-tested. SSL renews on its own, credentials rotate on a regular schedule, and sites are isolated from each other. You manage your site — content, plugins, code. We manage everything underneath it.

The bottom line

Unmanaged can be the right call if operating servers is something you enjoy and have time for. If it isn’t, “managed” is only worth paying for if the host actually does the work. See exactly what’s included at /pricing, or read how the platform works in /help.