Payload is on your shortlist, or you already run it, and you want to know what else fits before you commit. If your content model and access rules belong in TypeScript code and you want to own the database, Payload stays the strongest pick. If editors need to own the schema, a database already exists, or you want nobody on your team running servers, one of the alternatives fits better.
Every price on this page is as of September 2026.
- Payload CMS alternatives at a glance
- When is Payload the right choice?
- What are the main alternatives to Payload CMS?
- Which other options come up?
- How do you choose between them?
- Payload CMS alternatives: common questions
- Want a second opinion on your shortlist?
Payload CMS alternatives at a glance
Payload, WordPress, Sanity, Strapi and Directus differ most in where they run, where the content model lives, and how the bill grows.
| Payload | WordPress | Sanity | Strapi | Directus | |
|---|---|---|---|---|---|
| Where it runs | Admin and API as a Next.js app, on your servers | Its own PHP app on your server | Content on Sanity’s hosted database; Studio in your codebase | Its own Node.js service, on your servers | Its own Node.js service, on top of your SQL database |
| Where the content model lives | TypeScript config in your repo | Admin screens, themes and plugins | Schema code in your Studio | Files written by the Content-Type Builder, in development only | Your database tables, managed from the admin |
| Databases | MongoDB, Postgres, SQLite | MySQL 8.0+ or MariaDB 10.11+, recommended | Hosted by Sanity | PostgreSQL, MySQL, MariaDB, SQLite | PostgreSQL, MySQL, SQLite, SQL Server, MariaDB, CockroachDB, OracleDB |
| Licence | MIT | GPLv2 or later | Studio MIT; content platform by subscription | MIT core; Enterprise features under a commercial licence | MSCL-1.0-GPL, source-available (each version GPL-3.0 after four years) |
| Entry price (USD, September 2026) | Free to self-host; Enterprise licence for SSO and dedicated support | Free software; you pay for hosting | Free up to 20 seats; Growth $15 per seat per month | Community free; Growth $45 per month with 3 seats; Cloud from $35 per project per month | Core free for 3 seats; Team $499 per month, annual |
| Best for | A backend whose content model, access rules and logic live in TypeScript | A conventional site run by a non-technical team | Editors who want a managed, collaborative workspace | A MySQL or MariaDB stack, or SSO at a published price | An existing SQL database that stays the source of truth |
When is Payload the right choice?
Payload is the right choice when the CMS is part of your product rather than a separate website tool. It’s an application framework and backend with an admin panel, and it installs into a Next.js app, where its admin panel and API run. Your frontend can live in the same app and read content through the Local API, or be a separate app on any stack, mobile included, that calls the REST or GraphQL API. The content model is TypeScript in your repo, so a new field goes through code review like any other change, and the database, whether MongoDB, Postgres or SQLite, is yours.
Access control is where it goes furthest. Rules are functions per operation, and they can return a query constraint instead of a plain yes or no, down to single fields. For example, a franchise app can let each branch’s staff edit only their own branch’s menu while head office edits every branch. Our guide to Payload multi-tenancy shows how that works with the official plugin.
Payload is MIT-licensed and free to self-host, and as of September 2026 it lists two options, free self-hosting and Enterprise, which Payload sells under an Enterprise licence. Enterprise adds dedicated support, SSO, publishing workflows and audit logs, and lists a visual editor and multiplayer editing as still to come. Payload Cloud, the managed hosting, has new projects currently paused, so plan to host it yourself. Every install includes document locking, so while one person edits a document, others see it’s in use and can view it read-only or take it over.
We’ve built on Payload since 2025, and as of September 2026 we manage 27 Payload codebases, all built on Next.js. Before that we looked at Directus, Sanity, Strapi and headless WordPress. What decided it was the config-driven TypeScript. The content model is code, Payload’s official docs sat in the same repo, and the agent setup we built to guide our AI-powered development reads both. We haven’t moved our own work off Payload since, and we’d choose another system only when a project’s requirements call for it. For the platform in full, start with our Payload CMS guide.
What are the main alternatives to Payload CMS?
Payload’s own comparison pages cover WordPress, Sanity, Strapi, Directus and Contentful. The first four each have a full comparison on our blog, and Contentful, KeystoneJS and Storyblok get a short note each after them.
WordPress
WordPress is the familiar publishing dashboard, with themes and plugins for most website jobs. It’s free, GPL-licensed software that runs on PHP, and WordPress recommends MySQL 8.0 or MariaDB 10.11 or later, so what you pay for is hosting and upkeep. It wins when a non-technical team runs a conventional site and wants to publish without a developer. For example, a school that posts news, term dates and admissions pages can run on a standard theme and a few trusted plugins.
Verdict: choose WordPress for a standard website your editors run alone, and Payload when the site is part of a product with its own data and rules. Our Payload CMS vs WordPress comparison covers costs, security and a full migration.
Sanity
Sanity is a hosted content platform. Your team customises Sanity Studio, an MIT-licensed editing app, in code, while the content lives in Sanity’s hosted, real-time database. Paid plans charge per seat, so the bill grows with the editorial team. It wins when several editors work on the same content at once and nobody on your team wants to run a database. For example, two editors can type in the same document and see each other’s changes live, because Studio is a real-time collaborative workbench, and Sanity’s plan comparison lists real-time editing and multiplayer presence on every plan, Free included. Payload handles the same moment with document locking, one editor at a time, and lists multiplayer editing for Enterprise as still to come.
Verdict: choose Sanity for a managed, collaborative editing workspace, and Payload when you need to own the database and the backend logic. Payload CMS vs Sanity covers the trade-offs, including what leaving involves.
Strapi
Strapi is a Node.js headless CMS that runs as its own service, with an admin panel and a visual Content-Type Builder. The builder is available in development only, so once the site is live a new field goes through code and a deploy, as it does in Payload. You can self-host the free Community edition or pay for Strapi Cloud. It wins when the database has to be MySQL or MariaDB, which Strapi supports and Payload’s official adapters don’t, when you want SSO at a published price, or when a plugin from its marketplace already does the job. For example, a team on Strapi’s Growth plan can add SSO for $150 a month plus $50 per seat, straight from the pricing page.
Verdict: choose Strapi when the database must be MySQL or MariaDB or you want SSO priced on the page, and Payload when you want the content model, access rules and backend logic in one TypeScript codebase. Plugins, upgrades and the rest are in Payload CMS vs Strapi.
Directus
Directus is database-first. You point it at a SQL database, new or existing, and it reads the tables and relationships and builds an API and an admin from them. Since version 12.0.0 on 10 June 2026, it’s under its own source-available licence, MSCL-1.0-GPL, which allows any use except offering Directus in competition with its own paid versions, and turns each version into GPL-3.0 after four years. It wins when the database already exists, outlives any one app, and several systems read it. For example, if an order system already writes to a Postgres database, Directus can sit on those tables and give staff an admin and an API without moving the data.
Verdict: choose Directus when the database is the source of truth, and Payload when the application defines the data. Payload CMS vs Directus covers the licence and the database-first model in depth.
Which other options come up?
Contentful, KeystoneJS and Storyblok also come up, and each suits a narrower kind of project.
Contentful is a managed headless CMS for larger organisations, and its Enterprise plan, sold through Contentful’s sales team, adds custom roles, enhanced governance and security features, and an uptime SLA of up to 99.99%. Free is $0 with 10 users and hard usage caps, Lite is $300 per month with 20 users, and each extra Lite Space costs $850 per month on top. It suits a company that wants governance, compliance and support from one vendor under one contract.
KeystoneJS is the closest match to Payload’s code-first model. You describe the schema in TypeScript and get a GraphQL API and an admin UI, with database migrations through Prisma, and it’s MIT-licensed and self-hosted. It suits a team that wants GraphQL and Prisma at the centre of the backend.
Storyblok is a managed CMS built around a visual block editor, so marketers assemble pages from components they can see. Starter is free with one seat and a second at $15 per month, and Growth costs $99 per month billed monthly with five seats. It suits marketing teams that build landing pages every week.
How do you choose between them?
Work through these five questions in order, because each one removes options before the next.
1. Where should the backend run?
The backend runs either on your own infrastructure (Payload, Strapi, Directus, KeystoneJS, WordPress) or on the vendor’s (Sanity, Contentful, Storyblok). Self-hosted, you own the database and the upkeep. Hosted, the database leaves your to-do list and a subscription joins it. Among the self-hosted options, Payload runs as a Next.js app and the others as their own service, and each can serve separate frontends over an API.
2. Who changes the content model after launch?
If developers change it through code review, Payload, Sanity and KeystoneJS keep the schema in code, and Strapi joins them once the site is live, because its Content-Type Builder runs in development only. If people outside engineering need to add fields from an admin, Directus and WordPress let them. For example, a team whose marketing lead adds a product attribute every month will fight a code-first schema, and a team that audits every schema change will want one.
3. Does a database already exist?
If a SQL database already holds your data and has to stay the source of truth, Directus is built for exactly that. Payload can keep existing Postgres tables through its adapter’s beforeSchemaInit hook, though by default it manages the schema itself. Strapi isn’t meant for pre-existing databases.
4. How should the bill grow?
Hosted platforms charge by seats, usage or both, while a self-hosted CMS costs what your hosting costs, however many people log in. For example, 30 editors on Sanity Growth come to $450 a month in seats alone, while the same 30 editors on a self-hosted Payload or KeystoneJS build add no seat fees, because both are MIT-licensed. Self-hosting moves the cost into engineering time instead, and our Payload CMS pricing breakdown puts numbers on that side.
5. Which licence can you live with?
The licence decides the choice only if you’ll distribute the software or offer it as a service. In that case, MIT (Payload, KeystoneJS) carries almost no conditions, while the Directus licence and WordPress’s GPL each add terms worth reading before you build.
Once two options survive, spend a day building one real content type in each and publishing one entry through your actual frontend.