Best Self-Hosted CMS Platforms in 2026 (Honest Ranking)

Self-hosted CMS searches are up 38% year-over-year while SaaS CMS pricing hits new highs. Developers are realizing the math: a $20/month VPS handles what Contentful charges $300/month for, and you keep your data when the vendor changes their pricing page.

This is an honest ranking of the 10 self-hosted CMS platforms worth running in 2026 — what they're good at, what they're bad at, and which one actually fits your stack. TL;DR: WordPress is still the default for non-technical clients, Ghost wins for publishers, Payload and Strapi split the headless developer market, Statamic and Craft serve agency work, and UnfoldCMS is the new entrant for Laravel + React shops. The right answer depends on your team — there's no single winner. See also: the full self-hosted CMS reference for 2026.

Every platform here is truly self-hostable (run it on your own server, own the database, no required cloud account). Hosted-only options like Webflow and Wix are out. Hybrid platforms with a self-hosted tier (Sanity, Contentful) are also out — read self-hosted CMS vs SaaS CMS for that comparison.

How We Ranked These

Self-hosted CMS rankings get gamed all the time. Here's the framework we used so the ranking is honest and reproducible.

The five evaluation criteria:

1. Self-hostability — runs on a normal Linux server with documented requirements. No required cloud account, no licensing servers that must phone home.
2. Active development — at least one release every 6 months. We checked GitHub commit history through May 2026.
3. Production readiness — runs real customer-facing sites at scale, not just demos.
4. Developer experience — modern stack, good docs, sane data model, working API or extension point.
5. Total cost of ownership — license + hosting + plugin/add-on costs over 3 years for a typical mid-size site.

We deliberately excluded platforms that are end-of-life (Joomla 3.x), abandoned (some older Node CMSes), or niche to a specific use case (purely ecommerce platforms like WooCommerce/Magento).

The ranking below isn't strictly "best to worst" — different platforms win for different teams. We've ordered by breadth of fit (how many use cases each handles well) but each entry tells you who shouldn't use it.

Quick Comparison Table

The platforms compared on the dimensions that actually matter when picking:

Now the deep dive on each.

1. WordPress — Still the Default (For Better and Worse)

Stack: PHP 8+, MySQL/MariaDB, runs on almost any host License: GPLv2, free Repository: github.com/WordPress/wordpress-develop Latest release: 6.7 (Q1 2026)

WordPress runs roughly 43% of the web. Most CMS conversations start with "we want to move off WordPress" — but it's still the right answer for a specific kind of project: a non-technical client who needs to publish daily, hire affordable freelancers easily, and pick from 60,000+ plugins for niche functionality.

Honest pros:

• Largest ecosystem of any CMS — plugins, themes, freelancers, hosts
• Editor UX is good for non-technical users (Gutenberg has matured)
• Extremely cheap shared hosting available ($5/month tier works)
• Massive community knowledge — every problem has been answered on Stack Overflow

Honest cons:

• 250+ plugin vulnerabilities disclosed weekly in 2026 (Patchstack data)
• 43% of WordPress vulnerabilities are exploitable without authentication
• Plugin bloat is real — sites accumulate 30+ plugins, performance dies
• The PHP code feels like 2008 — global functions, hooks-and-filters paradigm, no type safety
• Custom development requires fighting the system — schema is rigid, ACF helps but adds another layer

Skip it if: you're a developer team building anything custom. The plugin economy is a feature for non-technical site owners and a tax on developers who want to ship clean code. Read why developers are leaving WordPress if that resonates.

Pick it if: your client is non-technical, your budget is tight, you need a freelance pipeline that can find help in any city, and you're shipping a content site (blog, news, magazine) without unusual data requirements.

For deeper analysis see 10 best WordPress alternatives in 2026 and the security-specific case in WordPress security problems in 2026.

2. Ghost — The Publisher's CMS

Stack: Node.js 18+, MySQL 8 (SQLite for dev only) License: MIT Repository: github.com/TryGhost/Ghost Latest release: 5.x (active monthly releases through 2026)

Ghost is what you pick when the site is a publication. Newsletter, blog, paid memberships, podcast notes, longform writing — Ghost is opinionated for that workflow and fights you on anything else.

Honest pros:

• Built-in newsletter + paid membership flows (Stripe integration is first-class)
• The editor is the best in its class — if your team writes a lot, this matters
• Native handlebars themes — predictable, well-documented
• Reasonable Node stack, modern enough to hire for, simple enough to host
• Excellent default SEO setup (clean markup, structured data, sitemap)

Honest cons:

• Not flexible — building "a website with a blog" is awkward; building "anything but a blog" is painful
• Custom content types need workarounds (no native fields-of-fields like Strapi or Payload)
• Theme system is server-side handlebars, not React/Vue — feels dated to JS-heavy teams
• The free self-hosted version is missing some Ghost(Pro) features (referrals, recommendations) that come and go between releases

Skip it if: you need flexible content types beyond posts/pages, custom data structures, or you want to use Ghost as a headless API for a JS frontend. The Content API works but isn't as polished as Strapi/Payload.

Pick it if: you're running a publication, newsletter, or paid-content business. Ghost optimizes for that workflow harder than any other CMS in this list.

3. Strapi — The Headless API Backend

Stack: Node.js 18+, PostgreSQL/MySQL/SQLite, optional Redis License: MIT (CE) + paid Enterprise tier Repository: github.com/strapi/strapi Latest release: v5 (released late 2024, mature through 2026)

Strapi is the most popular headless CMS in the self-hosted category. It generates a REST and GraphQL API from content types you define in the admin UI, and it's a reasonable choice as the data backend for a Next.js, Nuxt, or SvelteKit frontend.

Honest pros:

• API-first by default — REST + GraphQL out of the box, well-documented
• Visual content-type builder is genuinely useful for non-coders
• Good plugin ecosystem (auth, i18n, SEO, media library extensions)
• v5 brought a much-needed admin UI redesign and the Document Service API
• Self-hosting is straightforward (Node + Postgres + S3-compatible storage)

Honest cons:

• Performance suffers at scale — complex queries with deep populates get slow
• The Enterprise tier paywalls features many teams expected to be free (RBAC, SSO, content history)
• Database migrations between schema changes are still rough — easy to break things
• Customization beyond plugins requires knowing Strapi's internals (lifecycle hooks, services, controllers)
• v3→v4→v5 migrations were painful for early adopters; trust takes time to rebuild

Skip it if: you want a CMS with a frontend included, you're not building a JS-frontend project, or you don't want to maintain a Node backend separate from your frontend.

Pick it if: you're a JS-heavy team, you want decoupled content management, and you're OK with the Enterprise pricing if your needs grow. See UnfoldCMS vs Strapi for a direct comparison or migrate from Strapi if you're moving off.

4. Directus — Database-First CMS

Stack: Node.js 18+, any SQL database (Postgres, MySQL, SQLite, MSSQL, Oracle) License: BSL (Business Source License) → converts to MIT after 4 years Repository: github.com/directus/directus Latest release: v11 (active through 2026)

Directus is the inverse of most CMSes: instead of defining content types and getting a database, you point it at an existing database and get an admin UI + API on top. This makes it ideal when you have legacy data or when the database is the source of truth, not the CMS.

Honest pros:

• Works with any SQL database — including ones you didn't create in Directus
• Auto-generated REST + GraphQL API for any table
• Excellent for "internal tool + public API" use cases (admin for ops team, API for the website)
• Good RBAC and permissions model — granular per-collection, per-field
• BSL license is reasonable in practice (4-year MIT conversion, free for self-host under revenue threshold)

Honest cons:

• The frontend story is "bring your own" — there's no theme system, no SSR, no built-in site renderer
• Content modeling is database-shaped — relations, joins, foreign keys. Less "content" feel, more "admin panel."
• Smaller ecosystem than Strapi for editorial features (no native i18n flow, no draft workflow without setup)
• BSL license confuses some legal teams even though MIT-after-4-years is fine
• v11 admin UI is improving but feels less polished than Payload's

Skip it if: you want a traditional CMS where content modeling is intuitive, you need an editorial workflow with previews and drafts, or you don't have an existing database to wrap.

Pick it if: you're treating the database as the source of truth, you have legacy SQL data to expose, or you want one tool for both internal admin and public API. See UnfoldCMS vs Directus for the direct comparison.

5. Payload CMS — TypeScript-Native Headless

Stack: Node.js 20+, MongoDB or Postgres, Next.js 15+ (v3+) License: MIT Repository: github.com/payloadcms/payload Latest release: v3 (rebuilt on Next.js, 2024-2026)

Payload v3 reinvented itself in 2024 by moving entirely onto Next.js — the admin UI is a Next.js app, the config is TypeScript, and the API runs in Next.js routes. For TypeScript-heavy teams already on Next.js, the integration is exceptional. For everyone else, it's harder to justify.

Honest pros:

• Best-in-class TypeScript DX — config is fully typed, generated types for collections, end-to-end inference
• Admin UI is fast, modern, and customizable (you write React components for fields)
• Single codebase — admin + API + frontend all in one Next.js app
• MIT license, no paid tiers gating features
• Hooks system is clean and composable (beforeChange, afterRead, etc.)

Honest cons:

• Tight Next.js coupling means you can't realistically use Payload outside Next.js (in v3+)
• Stack lock-in: if you don't want to run Next.js, Payload is not for you
• Self-hosting Next.js + Payload + Postgres + media storage is more moving parts than a single Laravel app
• Editor UX for non-technical users is good but not Ghost-good; the admin feels engineered, not crafted
• Smaller community than Strapi or WordPress — fewer plugins, fewer Stack Overflow answers

Skip it if: you don't want Next.js as your runtime, you have non-technical content editors who'd struggle with a developer-feeling admin, or you're not on TypeScript.

Pick it if: you're on Next.js + TypeScript, you want a single deployable artifact, and you value type safety from database to render. See UnfoldCMS vs Payload for the direct comparison.

6. Statamic — The Designer-Friendly Laravel CMS

Stack: PHP 8.2+, Laravel 11+, flat-file (YAML/Markdown) or database License: Paid — $259 per site (Solo) or $1,990 unlimited (Pro) Repository: github.com/statamic/cms Latest release: v5 (active through 2026)

Statamic is the agency favorite for clients who want a CMS that feels designed. It's built on Laravel, ships with a flat-file storage option (content as Markdown + YAML in version control), and has the cleanest editor UX of any PHP CMS.

Honest pros:

• Flat-file storage means content lives in git — review content changes via PR
• Antlers + Blade templating gives Laravel devs immediate productivity
• The editor (Bard, the rich-text editor) is genuinely good — better than WordPress
• Native multi-site, multi-language, asset management
• Active development from a small but committed team
• Eloquent driver lets you swap to database storage when scale demands it

Honest cons:

• Paid license per site adds up — agencies running 50 client sites do the math
• Smaller ecosystem than WordPress for plugins/themes
• Flat-file storage breaks at scale (10k+ entries) — you'll move to database eventually
• Requires Laravel knowledge to extend, which limits the freelancer pool
• Antlers templating is its own thing to learn even if you know Laravel

Skip it if: you're not on a Laravel stack, you don't want a per-site license cost, or you need a free option.

Pick it if: you're a Laravel agency, you value content-in-git workflows, and the per-site license is fine for your client model.

7. Craft CMS — The Customizer's CMS

Stack: PHP 8.2+, MySQL 8/MariaDB or Postgres License: Free (Solo) / $299 one-time + $59/year (Pro) Repository: github.com/craftcms/cms Latest release: v5 (active through 2026)

Craft is what you pick when "every field, every relationship, every layout has to be exactly right." It's an agency tool — relatively flat learning curve for designers, deep customization for developers, and an editor that respects content structure over arbitrary text blobs.

Honest pros:

• Best-in-class custom field system — Matrix fields, relations, super-tables, all native
• Twig templating is fast, well-documented, easy to hire for
• Live preview is genuinely excellent — see your changes before publish
• Plugin ecosystem is curated (Craft Plugin Store), quality is high
• Built-in GraphQL API for headless use — no separate plugin needed
• Solo edition is free for single-user sites; Pro is $299 + $59/year for renewals

Honest cons:

• The full developer experience (Pro features, custom fields, multi-user) requires the paid tier
• Server requirements are stricter than WordPress (PHP 8.2+, modern MySQL/Postgres)
• Smaller community than WordPress means fewer answers to obscure problems
• Craft 4 → Craft 5 migration was significant — bigger sites took weeks to upgrade
• The custom field flexibility is a double-edged sword — projects can sprawl into 200-field content models

Skip it if: you need the largest possible plugin ecosystem, you're on a $5/month shared host, or your team doesn't have Twig/PHP comfort.

Pick it if: you're an agency building custom client sites, you value content modeling correctness over plugin breadth, and the per-site license is fine.

8. UnfoldCMS — Laravel + React + shadcn/ui

Stack: PHP 8.3+, Laravel 12, React 19, Inertia 2, MySQL/MariaDB License: Paid — $99 one-time (Core) / tiered Pro pricing Repository: source-available (paid customers get full source) Latest release: 2026 active development

Disclosure: this is our CMS — we built it, we run unfoldcms.com on it. The honest read: UnfoldCMS exists because we wanted a self-hosted CMS that didn't feel like 2008 PHP or require running a separate Node backend just to get a modern admin. It's a full Laravel app with a React + shadcn/ui admin (51 components, 205 admin pages) that ships as one deployable artifact.

Honest pros:

• Modern stack: Laravel 12 + React 19 + TypeScript + Inertia + shadcn/ui + Tailwind v4
• Single deployable: one repo, one server, one database — no separate frontend/backend services
• The admin is designed-not-engineered — built on shadcn/ui, dark mode native, three themes
• $99 one-time for Core (no per-site fees, no annual renewals on Core tier)
• Self-hosted with no license server phoning home to verify activation
• Active development (you're reading this on the product website, which runs on it)

Honest cons:

• Newest entrant — smallest community, fewest third-party integrations
• Currently a coupled Laravel CMS — public headless API (REST + GraphQL endpoints) is on the roadmap, not shipped yet
• Plugin ecosystem doesn't exist yet at any meaningful scale
• Theme marketplace is also small — 3 first-party themes, no community marketplace yet
• If you're not on Laravel + React, the stack alignment isn't there

Skip it if: you need a battle-tested platform with a large plugin economy, you're not comfortable on Laravel, or you need a public headless API today (not "soon").

Pick it if: you're a Laravel + React shop, you want a modern admin without paying per-record SaaS pricing, and you're OK being an early adopter. See pricing, book a demo, or read the CMS built on shadcn/ui.

9. Drupal — The Enterprise / Government CMS

Stack: PHP 8.2+, MySQL 8/MariaDB/Postgres License: GPLv2, free Repository: github.com/drupal/drupal Latest release: 11.x (active through 2026)

Drupal is the CMS for regulated, complex, multi-stakeholder sites — government agencies, universities, healthcare. It has the most powerful content modeling and access control system of any CMS in this list, and it's also the steepest learning curve.

Honest pros:

• Best-in-class permissions and workflow engine (states, transitions, role-based access)
• Multi-site, multi-language, multi-domain handled natively at scale
• Mature, audited, used by large institutions (US government, large universities, EU agencies)
• Strong accessibility defaults — matters for public-sector compliance
• Long support lifecycles (LTS releases supported for years)

Honest cons:

• Steepest learning curve of any CMS in this list
• Smaller (and shrinking) developer pool — hiring Drupal devs is harder year over year
• The custom-module ecosystem is split between contrib (community) and custom (your team) — both require deep Drupal API knowledge
• Page rendering is slower than modern frameworks; performance tuning is its own skill
• Drupal 7 → 8 → 9 → 10 migrations were brutal historically; the platform is still recovering trust

Skip it if: you're a small team, you need fast iteration, or your project doesn't have unusual access-control or compliance requirements.

Pick it if: you're a large institution with compliance requirements, complex permissions, and a multi-year project budget. The complexity pays off at that scale; it doesn't pay off below it.

10. Kirby — The Designer's Flat-File CMS

Stack: PHP 8.1+, flat-file (no database required) License: Paid — €99 per site (Basic) / €299 Enterprise Repository: github.com/getkirby/kirby Latest release: v4 (active through 2026)

Kirby is the niche pick for small designer-built sites — portfolios, agency sites, microsites. It stores content as folders of text files, has a clean Panel admin, and works without any database setup. If your site has 50 pages and one editor, Kirby is genuinely pleasant.

Honest pros:

• Zero-database setup — drop on any PHP host, works immediately
• Content as folders of text files = trivial to back up, version, move
• The Panel admin is clean and customizable
• Templating is straight PHP — no DSL to learn
• Tiny footprint, fast performance for small sites
• One-time license fee, no annual renewals

Honest cons:

• Doesn't scale past ~1,000 pages — flat-file lookup gets slow
• Paid license per site (€99) — not free
• Smallest community of any CMS in this list
• No native multi-user editorial workflow at scale
• Plugin ecosystem is small but quality is generally high

Skip it if: your site will exceed 500-1,000 pages, you need multi-user editorial workflows, or you want a free option.

Pick it if: you're a designer or small agency building small custom sites where flat-file simplicity beats database overhead.

How to Pick: A Decision Tree

The honest answer to "what's the best self-hosted CMS" depends on three questions: what stack are you on, who edits the content, and what's your budget?

Walk this in order:

1. Is your editor non-technical, plugin-dependent, and freelancer-supported? → WordPress. Stop here.
2. Is the site primarily a publication or newsletter? → Ghost. Stop here.
3. Do you need a public REST/GraphQL API as the primary integration point?
   • On Next.js + TypeScript? → Payload
   • On Node, framework-agnostic frontend? → Strapi
   • Wrapping an existing database? → Directus
4. Are you on Laravel + PHP?
   • Designer-led agency work? → Statamic
   • React-heavy admin needs? → UnfoldCMS
5. Is content modeling complexity (Matrix fields, relations, custom field types) the deciding factor? → Craft
6. Is the project for a regulated institution with complex permissions and multi-year scope? → Drupal
7. Is the site small (<500 pages), single-editor, and database-free a feature? → Kirby

If multiple answers fit, pick the one with the smallest mismatch with your stack — fighting the wrong stack is a year of friction; the right stack feels like home.

For a deeper look at the self-hosted versus SaaS question (which precedes this one), read self-hosted CMS vs SaaS CMS: which is right for your team. For the WordPress-specific alternative angle, see 10 best WordPress alternatives in 2026. For all of our direct comparisons in one place, the Compare hub lists every vs-X page we've published.

Total Cost of Ownership (3-Year Estimate)

The sticker price is misleading. Here's a realistic 3-year TCO for a mid-size site (10k pages, 3 editors, moderate traffic) on each platform:

These are rough ranges. Plugin costs scale with how much custom functionality you need. Drupal hosting trends higher because production Drupal sites usually need more RAM and managed hosting.

The cheap winners on TCO are Kirby (small sites), Ghost (publications), and UnfoldCMS (modern Laravel/React stack). The big-spend platforms are usually WordPress with 30 plugins or Drupal at enterprise scale.

What Changed in 2026

A few moves worth noting since 2024-2025 listicles get out of date fast:

• Payload v3 went all-in on Next.js (late 2024) — if you read older comparisons listing Payload as "framework-agnostic Node," that's no longer accurate.
• Strapi v5 shipped its Document Service API and admin redesign (late 2024, mature now). The migration from v4 was lighter than v3→v4.
• Directus v11 improved the admin UI significantly; the BSL license still trips up legal reviews even though MIT-after-4-years is well-established.
• WordPress core is steady — Gutenberg matured, but plugin vulnerability disclosure rate is still climbing.
• Ghost added native recommendations and tipping in 2025; still publication-shaped.
• Craft 5 released in 2024 with required PHP 8.2+ and a refreshed admin; the upgrade from Craft 4 was significant.
• UnfoldCMS entered the market as the Laravel + React + shadcn/ui option (us, 2026).

If you read a 2024 ranking, mentally adjust Payload (Next.js-locked now) and double-check Statamic/Craft licensing tiers — both shifted pricing in the last 18 months.

What to Do About It

If you're picking a self-hosted CMS in 2026, this is the order of operations that actually works:

1. Start with the editor question — who edits, how often, how technical? This narrows the list more than any feature.
2. Match the stack — fighting an unfamiliar stack costs a year. PHP shops should pick a PHP CMS unless there's a strong reason not to.
3. Test the editor UX live — every CMS in this list has a demo. Spend 30 minutes editing a post in 2-3 candidates. The one that doesn't annoy you wins.
4. Run the TCO math for your specific case, not the generic table — license + hosting + plugins + dev time over 3 years.
5. Read the migration guides for any platform you're leaving — WordPress, Contentful, Sanity, Strapi.

If you land on UnfoldCMS, pricing is here and you can book a demo — we'll show the admin live, no signup wall. We're honest about being early — small ecosystem, headless API on the roadmap not shipped — but the modern stack and one-deployable-artifact story is real.

FAQ

What's the best self-hosted CMS for a non-technical client?

WordPress, by a wide margin. The plugin ecosystem, the cheap hosting, the ability to find a freelancer in any city — these matter more than developer experience when the editor isn't a developer. The downsides (security patching, plugin bloat) are real but manageable on a maintained site.

What's the best self-hosted CMS for developers?

It depends on stack. On Next.js + TypeScript: Payload. On Laravel: Statamic, Craft, or UnfoldCMS. On Node with framework-agnostic frontends: Strapi. The "best for developers" answer is the one that aligns with the framework you already know — fighting an unfamiliar stack is the costliest mistake.

Is WordPress still worth using in 2026?

Yes, for the right project. WordPress runs 43% of the web because it solves a specific problem well: a non-technical client publishing daily with affordable freelance support. It's the wrong choice for custom dev work or anything security-sensitive without active maintenance — but for content-only sites with maintained plugins, it still works.

What's the cheapest self-hosted CMS?

Free + low hosting cost: WordPress (free license, $5/mo shared host), Ghost (free, $10/mo VPS), Strapi (free CE, $20/mo VPS). Paid-license budget options: UnfoldCMS ($99 one-time + $5/mo hosting), Kirby (€99 + $5-20/mo). The lowest absolute TCO over 3 years for a small site is usually WordPress on shared hosting or Kirby on a basic VPS.

What self-hosted CMS has the best editor experience?

Ghost for long-form writing, Statamic and Craft for custom content with rich live previews, UnfoldCMS for a modern shadcn/ui admin. WordPress's Gutenberg editor has improved a lot but still feels chunky compared to Ghost's editor. Strapi and Payload have engineered admins (good for developers, less polished for content editors).

Can I migrate between self-hosted CMS platforms?

Yes — it's annoying but doable. The hard part is preserving URLs and SEO equity, not the data move. We've published migration guides for WordPress, Contentful, Sanity, and Strapi and a general CMS migration guide for developers that covers the framework-agnostic playbook.

Sources & Methodology

This ranking draws on:

• GitHub commit history for each platform (we checked release frequency through May 2026)
• Patchstack 2024-2025 vulnerability data for security claims (WordPress plugin vuln disclosure rate)
• First-hand testing — we set up local installs of all 10 platforms in May 2026 and ran through the editor flow for a basic blog post
• Pricing pages (statamic.com, craftcms.com, getkirby.com) checked May 2026
• Community signals — Reddit r/selfhosted, r/PHP, r/node CMS threads from 2025-2026

Disclosure: UnfoldCMS is our product. We tried to rank it honestly — it's listed at #8 because it's the newest entrant with the smallest ecosystem, even though we use it daily and obviously prefer it. The "skip it if" sections for UnfoldCMS are real limitations, not marketing humility.

The TCO estimates are ranges based on observed deployments, not single data points. Your actual cost depends heavily on traffic, plugin choices, and whether you self-manage hosting or pay for managed services.