Two sites, same choice, and the bill comes due differently.
The one that went self-hosted for control is now months behind on security patches, because the person who understood the server moved on and nobody was assigned the job. The one that went managed for the convenience just hit a plan wall and a monthly charge that doubled. That is the shape of this decision on almost every site that runs long enough. Self-hosted versus managed CMS comes down to who does the operational work and what you pay for it: money, or your own time. Self-hosted means you run the software on hosting you control and own every update, backup, and security patch yourself. Managed means a provider runs it for you and you trade some control, plus a monthly fee, for never touching that. Most of the honest answer sits in one number nobody counts up front: how much maintenance the CMS actually demands. A database-free CMS like Devani, the free and open-source software running this blog, changes that number enough to reshape the whole comparison, which is why it shows up on both sides below.
Maintenance and patching
The factor that decides most of the cost, and the one the pricing page never shows. A traditional self-hosted CMS is a stack of software you keep current: core, theme, plugins, the database itself. Skip it and the site gets slow, breaks, or gets hacked. Managed platforms absorb that work, which is most of what you are paying them for.
Total cost of ownership
Self-hosting looks cheaper on the hosting line, sometimes a few dollars a month, but the real number includes the hours (or the developer rate) spent keeping it running. Managed carries a higher, steadier monthly fee that already covers that labor. Which one wins depends entirely on whose time the maintenance eats.
Security responsibility
When you self-host, a break-in is your problem and usually your fault: an unpatched plugin, a stale dependency, a weak admin password. Managed providers run firewalls, monitoring, and automatic patching, and carry that responsibility under an uptime commitment. The tradeoff you are weighing is control against having a team that answers the pager.
Control and lock-in
Self-hosting gives you the keys: any customization, your own server, your own data, nobody able to shut the account and take the site with it. Managed trades some of that for convenience, and the good ones let you export and leave, while the worst wall your content behind their platform. Ask how you get out before you get in.
Same software goal, opposite operational deal.
Neither model is the right answer for everyone. They are answers to different questions about who has the time and who wants the control.
Self-hosted CMS
Full control, and the maintenance that comes with it.
- ✓ You own the files, the server, and the data outright, with no account anyone can switch off
- ✓ Unlimited customization and, with open-source software, no per-seat or per-plugin fees
- ✓ Cheap on paper: an ordinary VPS runs about $5 a month
- × Updates, backups, security patches, and the occasional 2am outage are yours to handle or pay someone to
- × No support hotline; when something breaks, you are the support
Managed CMS
Someone else runs it, for a steadier monthly fee.
- ✓ Hosting, SSL, backups, CDN, and updates handled for you, usually under an uptime guarantee
- ✓ Live fast with little technical setup, and a real team to call when it breaks
- ✓ Predictable billing instead of a pile of separate line items
- × Higher monthly cost, and plan walls that can jump the bill as you grow
- × Less server access, some customization off-limits, and lock-in if export is an afterthought
Devani, either way
Free and open-source, with almost nothing to maintain on either side.
- ✓ Self-host it in one command on that same $5 VPS, or run it on a managed free tier, same site
- ✓ Database-free and no plugin stack, so the maintenance that defines this whole tradeoff barely exists
- ✓ Opt-in updates, automatic snapshots, one-click rollback, and export to HTML, Markdown, or JSON any time
- × Younger and smaller than WordPress, with no marketplace of thousands of plugins; a build that needs one specific niche plugin belongs elsewhere
The heaviest cost in self-hosting is the maintenance, so the real move is a CMS that has almost none to hand you.
The whole comparison assumes a heavy piece of software.
Read the standard version of this debate and it is really a debate about database-driven software like WordPress, Drupal, or a headless CMS on Node. Those systems are genuinely heavy to run yourself: a database to tune and back up, a server to keep patched, a stack of plugins or packages each on its own update cadence, and a security surface that grows with every addition. The published figures reflect that weight. Industry write-ups put self-hosted infrastructure at roughly $200 to $400 a month at team scale, on top of $1,500 to $4,500 a month in hidden engineering labor once you count patching, monitoring, and the unplanned downtime you chase down. Security patching alone is estimated at hundreds of developer hours a year per person. That labor, not the hosting, is why managed usually wins the total-cost math for those platforms. You are paying a provider to make a heavy thing somebody else's job.
Devani starts from the other end. The whole site is plain files, not a database, so there is nothing to query, tune, or back up in the usual sense. There is no plugin marketplace by design, so there is no stack of third-party code going stale and turning into an unpatched way in. Updates are opt-in and run on your schedule, every change snapshots with one-click rollback, and pages render as clean static HTML served from a CDN, which is why a Devani site scores around 100 out of 100 on Lighthouse out of the box rather than after weeks of caching-plugin tuning. Self-hosting a CMS that light is a genuinely different proposition from self-hosting the heavy kind. Most of the ongoing maintenance the comparison is built around simply is not there to do.
Still real value, even when the software is light.
Not wanting to touch a server at all is a completely legitimate reason to pay for managed, and it does not disappear just because a CMS is easy to run.
Even with almost nothing to patch, self-hosting still means you keep SSL certificates renewing, DNS pointed right, and a machine reachable. For a lot of owners that is exactly the kind of thing they never want to think about, and a managed provider taking it off the plate is worth real money. This is where the honest split on the two Devani sides sits. The free, open-source CMS is the self-hosted lead: your server, your files, about $5 a month, near-zero upkeep. If you would rather not run the server at all, Devani Hosting is the managed side, and a free `yoursite.devani.studio` subdomain can be live in under a minute, with paid plans adding custom domains, managed SSL, more sites, and an agency dashboard. If you are weighing that managed route in general, it is worth knowing exactly what managed hosting includes before you compare monthly prices, because two plans at the same figure often cover very different things.
The piece managed cannot hand you is control you have given away, and the piece self-hosting cannot hand you is a team that answers at 2am. What you should not accept is lock-in dressed up as convenience. A good managed platform lets you export and walk. Because the CMS underneath Devani is open-source, the worst case on either side is that you keep running your own copy, and your content leaves as portable HTML, Markdown, or JSON whenever you want it to. Moving between the two models is not a migration project; it is the same site on different hosting.
What each path actually runs per month.
Rough monthly ranges in USD, so the labor line is not hidden the way a hosting bill hides it. The maintenance column is the one people forget, and it is where the real difference lives.
| Path | Direct cost (USD) | Maintenance you own |
|---|---|---|
| Self-hosted, traditional CMS (budget) | $3 to $7 / mo hosting | High: updates, plugins, backups, security, all yours |
| Managed WordPress hosting | $15 to $35 / mo | Medium: host handles servers, you still mind plugins |
| Managed CMS / SaaS platform | $16 to $499 / mo by tier | Low: provider runs everything, plan walls apply |
| Devani, self-hosted | about $5 / mo | Near zero: database-free, no plugin stack to patch |
| Devani Hosting, managed | Free tier, paid plans add custom domains | None: managed servers, SSL, backups, updates |
The traditional self-hosted row is the one that misleads people. The $3 to $7 hosting figure is real, but the honest total for a properly run small-business build on that stack tends to land between $30 and $100 a month once a decent host, a theme, a couple of plugins, and any developer time are counted. It is not cheap so much as billed in more pieces. When the maintenance column collapses toward zero, as it does with a database-free CMS, the calculation stops being self-hosted versus managed and becomes a plain question of whether you want to touch a server at all.
Match the model to who keeps it running.
Self-host when you want full control and either the software is light enough that maintenance is not a real burden, or you have someone whose job is genuinely to own the server. If you run three or more sites on the same platform, or an agency doing this at volume, self-hosting also amortizes better than paying per-site managed fees. And if a specific load-bearing integration or an unusual compliance requirement forces your hand toward a particular stack you must run yourself, that is a real reason, not a preference.
Go managed when nobody on your side wants to own hosting, when you need to be live this week with a team to call, or when predictable billing matters more than the last increment of control. The classic trap is picking self-hosted for the price tag, underestimating the upkeep, and drifting into exactly the neglected, months-behind state from the top of this page. If the maintenance burden of a heavy CMS is what is pushing you toward managed in the first place, it is worth reading what actually happens when you go the other way and leave; the mechanics of leaving WordPress make the tradeoff a lot more concrete than a feature list does. And the reason a database-free CMS complicates this whole choice is that it lets you pick on preference instead of on fear of the upkeep, because the upkeep that usually decides it is mostly gone.
What is the difference between a self-hosted and a managed CMS?
Self-hosted means you install and run the CMS on hosting you control, and you own every update, backup, and security patch. Managed means a provider runs the software and infrastructure for you, handling hosting, SSL, backups, and updates for a monthly fee. The software can be identical; the difference is who does the operational work and who carries responsibility when something breaks.
Is self-hosting cheaper than managed hosting?
On the hosting line, almost always. A basic VPS runs a few dollars a month against a managed plan's higher fixed fee. But the honest total has to include maintenance time, and for a heavy database-driven CMS that hidden labor often makes managed cheaper overall. Self-hosting genuinely wins the cost math when the software is light to run, or when you are spreading the effort across several sites.
Is a managed CMS more secure than self-hosting?
Usually, for the average owner. Managed providers apply patches automatically, run monitoring and firewalls, and answer for uptime. Self-hosting is only as secure as whoever maintains it, and most break-ins trace to an unpatched component or a weak password rather than the core software. A CMS with a smaller attack surface, no plugin stack and no database, narrows that gap considerably, because there is far less to leave unpatched.
Can I switch from managed to self-hosted later?
It depends entirely on lock-in. With an open-source CMS you can, because the software and your content are yours to move; export as HTML, Markdown, or JSON and run your own copy. With a closed managed platform it can range from awkward to a full rebuild. Check the exit path before you commit, not after. Portability is the single feature that keeps this decision reversible.
Do I need technical skills to self-host a CMS?
For a traditional database-driven CMS, yes: you are choosing hosting, managing updates, and eventually touching configuration or code. For a database-free CMS installed with a single command, far less; running it is close to the effort of managed once it is up. If touching a server sounds like someone else's job and nobody is volunteering, a managed option or a free managed tier will serve you better than fighting an install you did not want.
Pick on preference, not on dread of the upkeep.
The maintenance is what usually decides this, so the useful move is to see how little of it a database-free CMS actually hands you. Self-host it for about $5 a month, or spin up the managed free tier in under a minute, same site either way.