DEPLOYMENT GUIDE

Self-hosted CMS: control comes with ownership

Self-hosting can improve control over data, deployment and customization. It also makes your team responsible for availability, patching and recovery.

Reviewed September 3, 20263 min readEditorial method

What self-hosted really means

A self-hosted CMS runs in infrastructure selected or managed by your organization. It may be installed on shared hosting, a managed server, a VPS, containers or a private cloud. “Self-hosted” describes control of deployment; it does not necessarily mean that your own staff manages every server.

The important boundary is responsibility. Write down who handles application upgrades, runtime patches, database backups, object storage, email delivery, monitoring, incident response and restoration tests.

Common self-hosted choices

CMSModelStackLicenseBest fit
WordPressTraditional / hybridPHPGPLv2 or laterPublishing, marketing sites, broad plugin needs
DrupalStructured / hybridPHPGPL-2.0-or-laterComplex content models, permissions and large organizations
JoomlaTraditionalPHPGPL-2.0-or-laterPortals, multilingual sites and structured publishing
GhostPublishing / headlessJavaScriptMITNewsletters, memberships and focused publications
StrapiHeadlessJavaScript / TypeScriptMIT (community edition)Custom apps needing an API-first editorial backend
DirectusHeadless / data platformTypeScriptBSL 1.1 / commercial termsTeams that want APIs and an admin layer over SQL data
GravFlat-filePHPMITFast documentation, portfolios and smaller content sites

Total cost of ownership

BUILD

Implementation

Design, content modeling, integrations, migration and accessibility testing.

RUN

Operations

Hosting, observability, backups, patching, security and support time.

CHANGE

Evolution

Upgrades, redesigns, new channels, content cleanup and exit costs.

Minimum operating baseline

  • Supported application, PHP or Node runtime and database versions.
  • Automated off-site backups with a documented restore test.
  • TLS, least-privilege admin access and multi-factor authentication where available.
  • Staging environment and repeatable deployment process.
  • Uptime, error and security monitoring with a named responder.
COMMON QUESTIONS

Frequently asked questions

Is self-hosted the same as open source?

No. Open source describes licensing and code access; self-hosted describes deployment. Some open source products have hosted services, and some source-available products can be self-hosted.

Is self-hosting cheaper than SaaS?

It can be, but only after counting infrastructure, maintenance, security, backups and staff time. Small teams may find managed services more economical.