The managed vs unmanaged WordPress hosting decision is about who does the maintenance. Managed plans handle updates, caching, backups and security at server level, and cost more. Unmanaged plans hand that work to you and cost less. The right answer depends on what an hour of your time is worth and whether you will actually do the work.
Every comparison of these two options turns into a feature table, which is the least useful way to decide. The features are not really in dispute. What is in dispute is whether you should be spending your evenings on server maintenance.
This article gives you the work involved on each side, then a way to price it.
What “managed” usually includes
The term is not standardised, so read each provider’s definition. Most managed WordPress plans cover some or all of these.
- Automatic WordPress core updates, at least for minor security releases.
- Server-level page caching, already configured.
- Object caching with Redis or Memcached, where offered.
- Daily backups with a self-service restore.
- A staging environment, usually one click.
- Server-level security rules: login rate limiting, file access restrictions, malware scanning.
- A current PHP version, kept up to date for you.
- WordPress-aware support that will look at your application, not just the server.
- Free migration of your existing site.
The value is not in any single item. It is that these arrive configured and stay configured without you thinking about them.
What “unmanaged” leaves to you
Unmanaged usually means a VPS with an operating system and nothing else, or a plan where the host maintains the hardware and network and stops there.
The work you take on is real, and it is worth listing honestly rather than gesturing at.
Initial setup. Installing the web server, PHP, a database, and a control panel if you want one. Configuring a firewall. Setting up SSL and its renewal.
Caching. Installing and tuning page caching, object caching and OPcache. This is where most of the performance lives, and it is not a one-afternoon job to get right.
Security patching. Operating system and package updates, on a schedule, indefinitely. This is the part people abandon after three months, and it is the part that matters most.
Backups. Setting them up, storing them off-server, and testing a restore. A backup you have never restored is an assumption.
Monitoring. Knowing the server is down before a customer tells you.
WordPress maintenance. Core, plugin and theme updates, which you own on either side of this comparison.
Incident response. When something breaks at 11pm, you are the person who fixes it.
None of this is difficult in isolation. The difficulty is that it is continuous.
The cost comparison people get wrong
Managed WordPress hosting costs more per month than an unmanaged VPS of similar specification. That gap is the visible part of the comparison and it is the part most articles stop at.
The invisible part is your time. Price it properly:
- Estimate the hours of initial setup. For someone competent but not specialised, a properly configured, cached and secured WordPress server is a day’s work, not an hour’s.
- Estimate ongoing hours. Patching, monitoring and the occasional problem realistically costs one to three hours a month across a year.
- Multiply by what an hour of your time is worth. Use your actual billing rate if you have one.
- Add the cost of the failure you are underwriting. If your site is down for six hours on a Saturday because you were the only person who could fix it, what did that cost?
Run those numbers and the comparison usually resolves itself. For a developer who enjoys server work and has the habits to sustain it, unmanaged is genuinely cheaper. For almost everyone else, the managed premium is smaller than the time it replaces.
For the price bands themselves, see how much web hosting should cost.
Where managed hosting genuinely wins
You do not have a systems person. This is the deciding factor more often than any technical consideration.
The site makes money. Downtime on a store or a lead-generating site has a number attached. Managed hosting is partly an insurance product.
You want staging without building it. Testing updates before they go live prevents most self-inflicted outages, and it is the single most underused feature in WordPress hosting.
Security patching needs to happen whether or not you feel like it. An unmanaged server maintained enthusiastically for two months and then forgotten is worse than a managed plan, not better.
You want support that will look at a plugin conflict. Unmanaged support stops at the operating system by design. That boundary is reasonable and it is also where most WordPress problems live.
Where unmanaged genuinely wins
You need control. Custom PHP extensions, specific server software, a non-standard stack, a queue worker, Node.js alongside WordPress. Managed platforms restrict these by design.
You are running many sites. The economics change at volume. One well-administered VPS hosting fifteen client sites usually beats fifteen managed plans.
You have the skills and the habits. Not just the ability to set it up, but the discipline to keep patching it in month eleven.
You want portability. A standard LAMP or LEMP stack moves anywhere. Proprietary managed platforms can make migration out harder than migration in.
Cost is the binding constraint and your time genuinely is free. For a hobby project, this is a legitimate position.
The middle ground worth knowing about
The comparison is usually framed as two options. There are more.
Managed VPS. Reserved resources and root access, with the provider handling patching, monitoring and security. More control than managed WordPress hosting, less work than unmanaged. This is the right answer for a lot of growing sites and it is frequently overlooked.
Unmanaged VPS with a control panel. cPanel, DirectAdmin or a free panel removes most of the routine administration while keeping the price and the control. You still own patching and incident response.
Shared hosting with good caching. Worth saying plainly: many sites considering this question do not need either option yet. If your site runs comfortably on shared hosting, the upgrade can wait. The signs that it no longer does are specific enough to check rather than guess at.
A maintenance retainer. Unmanaged hosting plus an agency or freelancer handling updates. Sometimes cheaper than managed hosting and usually more responsive.
Questions that decide it
Answer these honestly and the choice is usually obvious.
- Is there someone on your side who will still be patching this server in twelve months?
- What does an hour of downtime cost you, in money or in reputation?
- Do you need any software a managed platform would prohibit?
- How many sites are you running?
- Do you actually enjoy this work, or do you tolerate it?
- If the site breaks while you are on holiday, who fixes it?
The last question decides more cases than any technical comparison.
One thing neither option covers
Worth stating clearly, because both sides of this comparison are sold as though they cover it.
Neither managed nor unmanaged hosting maintains your WordPress installation for you in any meaningful sense. Managed plans update core and sometimes plugins. Neither reviews whether a plugin is still maintained, whether your theme is abandoned, whether your forms still work, or whether your site has accumulated twelve plugins doing the job of four.
That is site maintenance, and it is a separate discipline from server maintenance. Buying managed hosting and assuming the site is looked after is a common and expensive misunderstanding. The security half of that work is set out in WordPress security hardening.
The short version
Managed WordPress hosting buys back time and reduces the number of ways you can break your own site. Unmanaged hosting buys control and costs less in money, more in attention.
Choose unmanaged if you have the skills, the habits and a reason for the control. Choose managed if the site earns anything, if nobody on your side wants to be a systems administrator, or if you are honest that the patching would not get done.
If you want to see what each looks like in practice, our WordPress hosting plans publish what is handled at server level, and the wider requirements are in our WordPress hosting guide.
Frequently asked questions
Managed hosting includes server configuration, caching, updates, backups and security handled by the provider. Unmanaged hosting supplies the server and leaves that work to you, at a lower monthly cost.
It is when the site earns revenue, when nobody on your side will maintain a server long term, or when you want staging and server-level caching without configuring them. It is poor value if you have the skills and want control.
Yes, if you are comfortable with the command line, a firewall and package updates. The harder part is not the setup but the sustained patching and monitoring over months.
Some plans do, some only update core, and some make it optional. Automatic plugin updates can break a site, so they are safest when paired with staging and a self-service restore. Check the specific policy before relying on it.
No. A managed VPS gives you reserved resources and root access with the provider handling patching and monitoring. Managed WordPress hosting is more restricted but more WordPress-specific in its tooling and support.
It maintains the server and usually WordPress core. It does not review your plugins, themes or site health. That is site maintenance and it remains your responsibility on either option.
