⚡How to choose: start with the operating model, not the feature list
Every headless CMS comparison you will read ranks features — rich text fields, image pipelines, localisation, webhooks. Here is the uncomfortable truth: at the top of the market those features have converged. All five tools in this article can model structured content, expose it over an API, handle media and manage roles. Choosing on feature grids is choosing on the dimension where they are most alike.
What has not converged is the operating model — who runs it, who edits in it, and who pays for what. A self-hosted open-source CMS is free software running on payroll and servers you fund. A managed SaaS CMS is an invoice that scales with seats and usage but requires no operations work. Those are different cost shapes, and picking the wrong shape costs more than picking the wrong feature set.
So the ranking below is by use-case fit, deliberately. Read the one-paragraph map, find the row that describes your team, and start your evaluation there instead of at the top of a ranking written for a different team.
| CMS | Hosting model | License | Best fit |
|---|---|---|---|
| Strapi | Self-hosted or Strapi Cloud | Open source (MIT), paid enterprise tier | Teams that must own the database and infrastructure |
| Sanity | Fully managed SaaS | Proprietary, free tier available | Editorial and marketing teams, real-time collaboration |
| Payload | Self-hosted, runs inside your Next.js app | Open source (MIT) | TypeScript teams wanting code-first, in-repo content |
| Directus | Self-hosted or Directus Cloud | Open source core, commercial tier above a revenue threshold | Organisations with an existing SQL database |
| Storyblok | Fully managed SaaS | Proprietary, free tier available | Marketing teams who want a visual, component-based editor |
The license fee is not the cost — the operating model is. A free CMS run badly costs more than an expensive CMS run by somebody else. Price the engineer-hours before you price the subscription.
🔧Strapi: the self-hosting default
Strapi is the most-deployed open-source headless CMS and the default answer when a team says they want to own their content infrastructure. It is a Node.js application with a relational mental model — content types, fields, relations — that backend developers understand immediately, backed by your own Postgres (or other SQL) database, exposing REST and GraphQL APIs. The admin panel is functional and customisable through a plugin system.
Strengths: genuine data ownership, because the content lives in a normal database you can query, back up and migrate without asking anyone. No per-seat pricing on the self-hosted community edition, which makes it unusually economical for large editorial teams. A mature plugin ecosystem and a large community. Strapi 5, the current major version, modernised the internals and the document model.
Weaknesses: you are operating a production Node service and a database, with all the patching, scaling and backup discipline that implies — budget real operations time, not just hosting fees. The editor experience is competent rather than delightful; non-technical editors coming from WordPress or a visual tool will notice. Major version upgrades have historically required real migration work. And enterprise features — SSO, audit logs, review workflows — sit behind the paid tiers.
Pricing model: the community edition is free to self-host. Strapi Cloud and enterprise licences are paid, with tiers that change periodically — as of writing, verify current pricing on the vendor site before committing. The honest cost line for self-hosting is infrastructure plus roughly 0.1 to 0.3 of an engineer for a serious deployment, which at market rates dwarfs most SaaS subscription fees.
🗂️Sanity: the editor experience benchmark
Sanity is a fully managed SaaS built around two ideas: a hosted content store (the Content Lake) and an editor (Sanity Studio) that is a React application you own and customise in your own repository. Content is queried with GROQ, a powerful query language, with GraphQL also available. Real-time collaboration — multiple editors in the same document, Google Docs style — is native rather than bolted on.
Strengths: the best day-to-day editing experience in this list, which matters enormously if editors outnumber developers on your project. The Studio being your own code means the editing interface can be shaped to the exact workflow instead of the other way around. Zero infrastructure to run. The free tier is generous enough for real projects, and the developer experience — TypeScript throughout, instant API, strong preview tooling — is excellent.
Weaknesses: your content lives in a vendor-hosted store. Export is real and well-supported, but you are trusting an external service with availability, and data residency requirements can push you toward enterprise tiers. Costs scale with seats and usage, so a growing editorial team plus heavy API traffic turns into a growing invoice. GROQ is one more language your team maintains expertise in, however good it is.
Pricing model: a free tier, then paid plans historically starting around the hundred-dollar per month mark with per-seat charges beyond included seats — as of writing, verify current tiers before committing. Model three years of seats and usage, not the entry price.
🧱Payload: the code-first insurgent
Payload is the newest serious contender and the one engineering teams get attached to fastest. It is TypeScript-native and code-first: content models are TypeScript config in your repository, versioned and reviewed like any other code. Since version 3, Payload installs directly inside your Next.js application — same repo, same deployment, one framework — which collapses the usual two-service architecture (CMS plus frontend) into one. It is open source under the MIT license.
Context worth knowing: Payload joined Figma in 2025, with a public commitment to keeping the project open source and actively developed. As of writing that commitment has held, but any acquisition changes a project risk profile — verify the current state of the repository, release cadence and community before betting a platform on it.
Strengths: the cleanest developer experience in this list for a TypeScript shop — end-to-end types from database to frontend, no separate service to deploy, auth and access control built in. Self-host anywhere Node runs. Weaknesses: it is a developer tool first; the admin UI is good and improving but not the polished editorial environment of Sanity or Storyblok. The ecosystem of plugins and integrations is younger and smaller. And the in-your-app architecture means your CMS scales with your web app, which is either a simplification or a coupling problem depending on your traffic shape.
Pricing model: free and open source to self-host; Payload Cloud is a paid managed option. The dominant cost is the same as Strapi — your own infrastructure and operations time — with a smaller operations surface if it lives inside an app you already run.
🗄️Directus: the database-first option
Directus takes a different architectural bet: instead of owning your content, it wraps your existing SQL database. Point it at Postgres, MySQL or several other engines and it layers a data studio, permissions system and auto-generated REST and GraphQL APIs over whatever schema is already there — including schemas built by other applications years ago. Your data stays yours in the most literal sense of any tool on this list.
Strengths: unmatched for organisations sitting on an existing database — internal tools, legacy modernisation, data platforms where the CMS is one consumer among many. Because it mirrors rather than owns the schema, removing Directus later leaves your data completely intact. The data studio doubles as a competent internal admin panel, which can retire two tools at once.
Weaknesses: it is a data platform that does CMS work rather than a purpose-built editorial CMS, and content teams feel the difference — content modelling, preview workflows and editorial niceties are less refined than in Sanity or Storyblok. The wrapper architecture also means your API surface inherits whatever shape the underlying database has, which is honest but not always elegant.
Pricing model: the core is open source, with a commercial license required for self-hosted production use by organisations above a published revenue threshold, plus managed Directus Cloud tiers. License terms here have specific conditions — read the current license text yourself before committing, because this is exactly the kind of term that changes.
🎨Storyblok: the visual editor for marketing teams
Storyblok is a managed SaaS headless CMS organised around components — content is assembled from nestable blocks that map directly to frontend components — and around a visual editor that lets editors click on a live preview of the actual website and edit what they see. For marketing teams, that visual loop is the product.
Strengths: the shortest distance between a content change and a published page for non-technical editors. The component model maps naturally onto modern component-based frontends (Next.js, Nuxt and friends), which keeps developers and editors talking about the same objects. Strong asset management, workflows and localisation aimed squarely at marketing organisations.
Weaknesses: proprietary SaaS with content in the vendor cloud — the same availability and residency considerations as Sanity. The block-based model suits pages and marketing content better than deep, relational content graphs; complex interconnected content models are not its home turf. And per-seat SaaS pricing on a large marketing organisation adds up the same way it does anywhere else.
Pricing model: a free entry tier for a single seat, then paid plans that scale with seats and features — as of writing, verify current tiers before committing. The buyer question is not the entry price but the invoice at your real seat count in year two.
💰Self-host vs cloud: the honest pricing comparison
Vendor pricing pages change often enough that any number printed in an article is a liability, so instead of figures that may be stale next quarter, here is the shape of each cost model — the part that does not change — and how to model it. Verify current prices on vendor sites before committing; that advice applies to every row.
The comparison that actually matters is total cost at your real shape: number of editors, API traffic, content volume and — most importantly — available operations capacity. Self-hosted open source wins the license line every time and loses the labour line almost as often. Managed SaaS is the reverse. Neither is universally cheaper, which is exactly why the decision belongs to your operating model rather than your procurement spreadsheet.
One line that surprises buyers in both directions is exit cost. Self-hosted tools that keep content in a standard SQL database — Strapi, Directus, WordPress — let you walk away with your data in place. Managed platforms provide real export tooling, but you are still rebuilding the editorial workflow and integrations elsewhere. Price the exit before you sign the entry.
| Cost element | Self-hosted (Strapi, Payload, Directus) | Managed SaaS (Sanity, Storyblok) |
|---|---|---|
| Software license | $0 for community/open tiers; enterprise features paid | Included in subscription |
| Infrastructure | $50 – $500+/month depending on scale and redundancy | Included — usage limits apply |
| Operations labour | 0.1 – 0.3 engineer ongoing (the real cost) | Near zero |
| Per-seat cost | None on open tiers | Scales with editors — model year two, not month one |
| Upgrade burden | Yours — plan migration days per major version | Theirs |
| Exit cost | Low — your database, your backups | Export supported, but you rebuild the editorial workflow |
📰When headless WordPress still wins
Here is the recommendation the headless-CMS industry does not want in an article like this: for a large class of projects, headless WordPress beats every tool above, and it is not close. WordPress runs an enormous share of the public web for boring reasons that remain true — the editor is familiar to hundreds of millions of people, the talent pool is the deepest in content management, and the software plus its REST API and the WPGraphQL plugin are free.
Choose headless WordPress when the project is a content-heavy marketing site or publication, when the editors already know WordPress (retraining a thirty-person editorial team costs more than any CMS license), when budget discipline matters, and when the plugin ecosystem — SEO tooling, custom fields, media handling — covers requirements that would be custom builds elsewhere. Pair it with a Next.js frontend and you get the performance and developer experience of the modern stack with an editorial operation that needs no new hiring or training.
Be honest about the costs too: you are operating a PHP application with a plugin surface that demands security discipline; preview workflows need real engineering; and the API ergonomics are less elegant than purpose-built headless tools. It is the pragmatic choice more often than the fashionable one — which, for a business, is usually the same thing.
🧭The decision matrix: if X, choose A
Run your situation down the first table and take the first row that clearly applies. The second list is for the constraints that override everything else.
WordPress and CMS development servicesTalk through your CMS decision with us
Hard self-hosting requirement
Eliminates Sanity and Storyblok immediately. Choose among Strapi, Payload, Directus and WordPress on the remaining criteria.
No operations capacity at all
Eliminates the self-hosted options regardless of license cost. A free CMS you cannot operate is the most expensive option on the list.
Large editorial team
Per-seat SaaS pricing becomes the dominant cost — model it at your real headcount before ruling out self-hosted options with free unlimited seats.
Existing Next.js investment
Payload and headless WordPress both integrate cleanly; Payload goes further by living inside the same application.
| Your situation | Best fit | Why |
|---|---|---|
| Compliance or residency requires owning the database | Strapi | Self-hosted, your Postgres, enterprise controls available |
| Editors outnumber developers; collaboration is daily | Sanity | Best-in-class editor, real-time co-editing, zero ops |
| TypeScript team, Next.js frontend, code-first culture | Payload | CMS lives in your repo and your app, fully typed |
| An existing SQL database is the source of truth | Directus | Wraps the database instead of replacing it |
| Marketing team edits a visual website daily | Storyblok | Click-the-page visual editing, component model |
| Budget-sensitive publishing, WP-fluent editors | Headless WordPress | Free software, deepest talent pool, familiar editor |
