Same software, two very different jobs on your plate.
Managed hosting means someone else keeps the server patched, the SSL valid, the backups running, and the site online; self-hosting means every one of those jobs is yours. That's the whole distinction, and it's why the choice has almost nothing to do with the CMS itself and almost everything to do with who's willing to own the maintenance. The tradeoff people brace for, cheap-but-you-run-it against easy-but-you're-locked-in, is real but softer than it looks once you notice that some CMSes carry far less operational weight than others. Devani, the free and open-source CMS this blog runs on, is one of the odd ones that offers both models from a single codebase, so it's a useful reference point for seeing where the line actually falls.
Self-hosting
You run the server; you keep the lights on.
- ✓ Cheapest raw cost: a small VPS runs about $5 a month
- ✓ Full control of the server, the stack, and every config
- ✓ Your files, your data, no vendor who can switch you off
- × Updates, security patching, backups, and uptime are all your job
- × Setup and recovery assume you're comfortable in a terminal
Managed hosting
The provider owns the plumbing; you own the content.
- ✓ SSL, backups, CDN, caching, and updates handled for you
- ✓ Someone answers when the site goes down at 2am
- ✓ Scales through traffic spikes without you touching a thing
- × A monthly bill, typically $15 to $35 for a managed small-site tier
- × Less server-level control, and sometimes real lock-in to unwind later
Devani
Both models, one free codebase, far less to maintain either way.
- ✓ Self-host the open-source CMS on ~$5/mo hosting with one command, or use the managed free tier and be live on a devani.studio subdomain in under a minute
- ✓ Database-free with no plugin marketplace, so even self-hosted there's no stack to keep patched
- ✓ Automatic snapshots and one-click rollback on both paths; export your HTML, Markdown, or JSON anytime
- × The managed tier hosts Devani-built sites, not an existing WordPress install you point DNS at, and the ecosystem is younger than WordPress
It's not cost. It's who owns the upkeep.
Strip away the feature lists and the decision reduces to a single question: when a security patch drops, a backup needs restoring, or the server falls over during a traffic spike, whose problem is it? If you have someone technical who wants that responsibility, or you enjoy it yourself, self-hosting hands you the most control and the lowest sticker price. If nobody on your side is volunteering to own it, managed hosting earns its monthly bill precisely because it moves that whole category of work off your desk.
The trap is assuming self-hosting is the frugal choice because the server is $5 a month. The server was never the expensive part. Across the operations write-ups on this exact question the consensus is the same: the real cost of self-hosting is the labor, the recurring hours spent patching, monitoring, and cleaning up after the one update that broke something. One 2026 ops analysis put self-hosted setups at needing meaningfully more operational time than managed equivalents, with security patching alone eating a large recurring share of it. That time is invisible on the invoice and very visible on a calendar.
The license is free and the VPS is cheap. What you're really buying, or not buying, is your own time.
The jobs that quietly become someone else's.
"Managed" stays vague until you itemize it. These are the responsibilities that shift to the provider, and the same ones you inherit the day you decide to self-host.
Security and patching
Firewalls, malware scanning, DDoS mitigation, and applying the fix the day a vulnerability is disclosed. On a self-hosted box this is a standing job, and skipping it is how most sites actually get compromised: not through the core software but through something bolted on that nobody kept current.
Backups and rollback
Automatic, tested backups you can actually restore from, not a cron job you set up once and hope still runs. The difference between a five-minute rollback and a lost weekend shows up exactly once, on the worst possible day.
Performance and CDN
Edge caching, a global CDN, and load handling so the site stays fast under traffic. Self-hosted, you configure and tune all of it. Managed, it's on by default and someone else watches the graphs.
Uptime and monitoring
Round-the-clock monitoring and a support line, often with a 99.9 percent uptime commitment behind it. When something breaks at an inconvenient hour, the practical question is whether there's a team already awake and looking at it, or just you.
Updates and compatibility
Keeping the CMS current without breaking the site. The pain here scales with how many moving parts a platform has; a stack assembled from a dozen independently maintained plugins is where update-day surprises come from.
Scaling
Adding capacity when traffic grows. Managed platforms absorb this automatically; self-hosted, scaling is a project you plan and pay for, usually right when you're busiest and least want a project.
Where the money actually goes.
Line up the recurring costs honestly and the "self-hosting is cheaper" instinct gets more complicated, because the biggest item on the self-hosted side is the one that never lands on a bill.
| Approach | Typical monthly cost (USD) | Who owns the ops work |
|---|---|---|
| Self-hosted on shared or VPS hosting | $5 to $15 | You: updates, security, backups, uptime |
| Managed hosting, small-site tier | $15 to $35 | The provider, with support behind it |
| Managed CMS platform, business tiers | $49 to $500+ | The provider; priced for teams and scale |
| Your time to run a self-hosted box | Not on the invoice | The line that usually decides it |
| Devani, self-hosted or managed free tier | ~$5/mo, or $0 on the free tier | Minimal either way: no plugin stack to patch, snapshots built in |
Managed hosting for a single small site usually lands in the $15 to $35 a month range; dedicated managed CMS platforms priced for teams climb from around $49 into the hundreds. Self-hosting drops the cash cost to the price of a VPS, roughly $5 a month, plus a domain at $12 to $20 a year. Below a certain scale the convenience of managed tends to win on total cost once you count the hours; above it, once you're running several sites or paying steep per-seat SaaS fees, self-hosting's math flips and control plus lower recurring spend start to matter more. Neither answer is universal, which is exactly why the deciding question is who owns the upkeep, not which number is smaller.
When the platform itself carries less weight.
The whole managed-versus-self-hosted tension assumes self-hosting is heavy, and for most CMSes it is, because the ops burden comes from the moving parts: a database to keep healthy, a server-side stack to tune, and a pile of plugins to keep patched and compatible. Take those away and the calculation changes. Devani is database-free, so the entire site is plain files served statically from a CDN, which is also why it scores near 100 out of 100 on Lighthouse and loads sub-second out of the box. There's no plugin marketplace by design, so there's no plugin stack to go stale or conflict on update day. Updates are opt-in on your own schedule, every change snapshots automatically, and rollback is one click. That's a self-hosted setup carrying a fraction of the usual ops weight.
If you'd rather not touch a server at all, the same open-source CMS has a managed free tier: a free yoursite.devani.studio subdomain, live in under a minute, with SSL, backups, the media CDN, and updates all handled. Paid plans add custom domains with managed SSL, more sites, more CDN storage, and a single dashboard across everything. You're not stuck choosing your poison between "free but you run it" and "convenient but locked in," because it's one product either way and you can move between them: the CMS is open-source, your domain stays yours, and you can export the whole site anytime, so the lock-in that usually rides along with managed convenience mostly isn't there. Editing runs through the same builder on both paths, and it's MCP-native, so you can connect your own ChatGPT or Claude account and have the assistant edit live content and layout from inside the builder, no API keys or copy-paste. WordPress has since shipped its own MCP integration and the Vibe AI plugin, but those work well only inside its block editor; the distinction is an assistant working inside the builder rather than alongside it.
The things people ask before deciding.
Is self-hosting cheaper than managed hosting?
On the invoice, yes: a VPS runs about $5 a month against $15 to $35 for a managed small-site tier, and more for team-grade managed CMS platforms. In total cost, not necessarily. Self-hosting adds the recurring hours you spend patching, monitoring, and recovering, and that labor is usually the largest cost even though it never shows up as a charge. Below a few sites, managed often wins once you price your time; across several sites or steep per-seat fees, self-hosting's math starts to flip.
What's the difference between managed and self-hosted?
Both can run the same CMS. Self-hosted means you install and run it on infrastructure you control, and you own updates, security, backups, and uptime. Managed means a provider runs the infrastructure and takes those operational jobs off your plate for a monthly fee. The software is often identical; what differs is who's responsible when something needs patching or restoring.
Is managed hosting worth it?
If nobody on your side wants to own server maintenance, yes, because that's precisely what you're paying to remove. The monthly cost buys back the hours self-hosting would demand, plus a support line and usually a 99.9 percent uptime commitment. If you have the technical capacity and genuinely want full control, the value proposition weakens and self-hosting's lower recurring cost becomes the stronger draw.
Can I move from managed hosting to self-hosting later, or the other way?
It depends entirely on the platform, and this is where lock-in bites. Some managed services make it genuinely hard to leave with your content intact. Look for one that keeps the door open: an open-source or open-format core, clean export of your content, and a domain that stays registered to you. When those three hold, switching between managed and self-hosted is a migration you can actually do, not a hostage negotiation.
Is self-hosting secure?
It can be, but the responsibility is entirely yours. Most compromises don't come from the core CMS; they trace to an outdated plugin, a vulnerable add-on, or a weak admin credential nobody rotated. Self-hosting means you own the firewall, the patch cadence, and the monitoring. A platform with fewer moving parts, no sprawling plugin stack, and opt-in updates shrinks that attack surface considerably, whichever hosting model you run it on.
If you're mapping out what a hands-off setup actually removes from your workload before you decide, what managed hosting includes breaks the responsibilities down in detail. And if this question came up because you're weighing whether to stay on a heavier platform at all, the WordPress alternatives worth considering cover the rest of the field with the same maintenance-first lens.
Try the version that skips the tradeoff.
Spin up a site on the managed free tier and see how little upkeep it needs, or grab the open-source CMS and self-host it. Same site, your call on who runs the server.