Skip to content

Open source headless CMS, compared on license and hosting cost

An open source headless CMS gives you the code, but the license decides what you can do with it. Of the 26 here, 16 ship under a permissive license with nothing held back, and 5 are open core, with SSO, roles or workflows sold separately. Read the license, then price the hosting.

Reviewed by Eugene SuslovFacts read November 2026No affiliate links

26
open source platforms compared
16
under a permissive license
16
hold no feature back for a paid plan
7
store content in Git, no database

What makes a headless CMS open source

The badge on the homepage is not the test. A headless CMS counts as open source when its LICENSE file grants you the right to read, change, run and share the code, and that file often says more than the marketing does. We read every license on this page from the repository itself, including the folders that sit under a second license.

Two things separate the platforms here. The first is how much the license asks of you, which ranges from keeping a copyright notice to publishing your own changes. The second is open core: an MIT or Apache core with the features larger teams need, such as single sign-on and roles, kept in a paid edition.

Every open source headless CMS we review

26 platforms whose core is under an open source license. Each card links to a full review with pricing, hosting and limits. Source-available platforms such as Directus and Statamic are compared further down, not listed here.

Showing 8 of 26 platforms

Payload

Featured

Best for Next.js teams who want to own the database

A MIT-licensed CMS that installs into your Next.js app rather than sitting beside it. Config is TypeScript, the admin panel is generated from it, and the database is yours.

  • Runs inside your Next.js app, same repo and same deploy
  • Postgres, MongoDB or SQLite, your instance
  • Admin UI generated from a TypeScript config
  • Next.js
  • React
  • Vue / Nuxt
  • TypeScript / Next.js
FreeCloud or self-hosted · Open source

Best known open source option

The best-known open-source headless CMS, self-hostable and Node-based. The MIT grant is narrower than everyone assumes: having a Strapi Cloud account is one of the things that voids it.

  • Self-hostable Node.js CMS with an admin panel non-developers can use
  • Auto-generated REST and GraphQL APIs from your content types
  • Role-based permissions and a plugin ecosystem
  • Next.js
  • React
  • Vue / Nuxt
  • JavaScript / Node.js
FreeManaged SaaS · Open source

Best for publishing and newsletters

A publishing platform with memberships and newsletters built in, MIT licensed and genuinely self-hostable. Excellent at articles, deliberately narrow at everything else.

  • Content API and Admin API over a real publishing model
  • Memberships, paid subscriptions and email newsletters in core
  • MIT licensed, self-host with no vendor limits
  • Next.js
  • React
  • Vue / Nuxt
  • JavaScript / Node.js
FreeManaged SaaS · Open source

Best git-backed visual editing

Visual editing on top of Markdown and JSON in your own Git repository, Apache-2.0 licensed. The content stays in your repo whether or not you keep paying.

  • Content lives as Markdown or JSON in your Git repo
  • Visual editing against your live front end
  • Apache-2.0, with a self-hostable backend
  • Next.js
  • React
  • Astro
  • TypeScript / Node.js
$0Managed SaaS · Git-based · Open source

Free git-based editing

A free, MIT-licensed admin panel that commits Markdown to your Git repository. Abandoned as Netlify CMS, handed to new maintainers, and shipping releases again.

  • Content committed as Markdown to your own Git repo
  • MIT licensed; paid hosted backend (Decap Turbo) optional
  • A single-page admin app you host yourself
  • React
  • Next.js
  • Vue / Nuxt
  • JavaScript / React
FreeSelf-hosted · Git-based · Open source

Code-first GraphQL backend

A code-first headless CMS and GraphQL backend. You define the schema in TypeScript and get a Prisma-backed database, a typed GraphQL API and an admin UI generated from it.

  • Schema defined in TypeScript, admin UI generated from it
  • Typed GraphQL API with fine-grained access control
  • Prisma under the hood, Postgres, MySQL or SQLite
  • React
  • Next.js
  • Astro
  • TypeScript / Node.js
FreeSelf-hosted · Open source

Familiar editor, existing content

GPL software your client already knows how to use, with a REST API in core and GraphQL via a plugin. Nobody can reprice it, and nobody is maintaining it for you either.

  • REST API in core since 4.7, GraphQL via WPGraphQL
  • GPLv2 or later, so no vendor can change the terms
  • An editor most clients have already been trained on
  • Next.js
  • React
  • Vue / Nuxt
  • PHP
FreeSelf-hosted · Open source

Best for your own AWS account

An open-source CMS that deploys into your own AWS account as serverless infrastructure. The MIT Community edition is free; multi-tenancy, roles and publishing workflows need a paid license.

  • Deploys into your own AWS account, serverless
  • Multi-locale built in; multi-tenancy on the paid Business tier
  • Headless CMS plus a page builder and form builder
  • React
  • Next.js
  • GraphQL API
  • TypeScript / Node.js on AWS Lambda
FreeSelf-hosted · Open source

Which license each platform ships under

Read from each repository's LICENSE file, with any second license in the same repo.

16 of the 26 use a permissive license such as MIT, Apache-2.0 or BSD, which asks for little more than keeping the notice. 5 are copyleft, so shipping a modified copy to someone means shipping your changes too. 5 are open core, where the second license covers the parts you would pay for.

26 platforms
PlatformLicenseTypeWhat it asks of you
StrapiMIT + EnterpriseOpen coreThe core is MIT only while you use no ee/ code; the paid features run under Strapi's enterprise terms.
GhostMITPermissiveKeep the copyright notice; modify, host or sell it with no duty to share changes.
PayloadMITPermissiveKeep the copyright notice; nothing else. Every first-party package in the repo is MIT.
WordPress (headless)GPL-2.0-or-laterCopyleftRunning it carries no duty; distributing WordPress or a plugin derived from it means GPL source.
WagtailBSD-3-ClausePermissiveKeep the notice, and do not use Torchbox's name to endorse what you build.
Decap CMSMITPermissiveKeep the copyright notice; nothing else.
TinaCMSApache-2.0PermissiveKeep the license and NOTICE and mark the files you changed; no duty to publish changes.
KeystoneMITPermissiveKeep the copyright notice; nothing else.
Orchard CoreBSD-3-ClausePermissiveKeep the notice; no endorsement use of contributors' names.
WebinyMIT + EnterpriseOpen coreThe MIT core is yours; paid features are unlocked by a Webiny license, and enterprise/ code is not MIT.
PubliiGPL-3.0CopyleftBuilding sites with it carries no duty; redistributing a modified app means GPL-3.0 source.
PlasmicMIT + AGPL-3.0Open coreThe loaders are MIT; a modified Studio that users reach over a network must offer them its source.
ApostropheCMSMITPermissiveKeep the copyright notice; Pro and Assembly are separate commercial products.
Pages CMSMITPermissiveKeep the copyright notice; nothing else.
Sveltia CMSMITPermissiveKeep the copyright notice; nothing else.
Front Matter CMSMITPermissiveKeep the copyright notice; nothing else.
SquidexMITPermissiveKeep the copyright notice; nothing else.
AlineaMITPermissiveKeep the copyright notice; nothing else.
CockpitMITPermissiveThe core is MIT; Pro add-ons are licensed per live site.
Gentics MeshApache-2.0 + BUSL-1.1Open coreThe core is Apache-2.0; production use of any ee/ module, such as the PostgreSQL connector, needs a commercial license.
GraphweaverApache-2.0PermissiveKeep the license and NOTICE and mark the files you changed; no duty to publish changes.
Enonic XPGPL-3.0CopyleftDistributing a modified platform means GPL-3.0 source; the README claims a linking exception that LICENSE.txt does not carry.
ContemberApache-2.0PermissiveKeep the license and NOTICE and mark the files you changed; no duty to publish changes.
sensenetGPL-2.0CopyleftDistributing it means GPL-2.0 source, though the README routes on-premises licensing through sales.
ContentrainMIT + AGPL-3.0Open coreThe packages are MIT; a modified Studio that users reach over a network must offer its source and keep the attribution.
MagnoliaGPL-3.0 or commercialCopyleftUnder GPL-3.0, distributing a modified Community Edition means releasing your changes; DX modules need a paid key.

Licenses read from each repository's LICENSE file through the GitHub API, 2026-11-20.

starsGitHub stars, the ten most-starred

Stars measure attention, not quality or maintenance. Check the latest release date in each review.

Stars cluster at the top, around Strapi, Ghost and Payload. A license is a better filter than popularity, because it is the one thing you cannot change after you build on it.

Will the license fit how you ship?

Answer three questions about your project; every platform is sorted by what its license does with the answers.

Where will it run?

Will you change the CMS itself and keep it private?

Need SSO or roles without paying?

Fits · 21

Read the terms first · 5

  • Strapi MIT + EnterpriseThe core is MIT only while you use no ee/ code; the paid features run under Strapi's enterprise terms.
  • Webiny MIT + EnterpriseThe MIT core is yours; paid features are unlocked by a Webiny license, and enterprise/ code is not MIT.
  • Plasmic MIT + AGPL-3.0The loaders are MIT; a modified Studio that users reach over a network must offer them its source.
  • Gentics Mesh Apache-2.0 + BUSL-1.1The core is Apache-2.0; production use of any ee/ module, such as the PostgreSQL connector, needs a commercial license.
  • Contentrain MIT + AGPL-3.0The packages are MIT; a modified Studio that users reach over a network must offer its source and keep the attribution.

Rules it out · 0

    Licenses read from each repository's LICENSE file in November 2026. A reading aid, not legal advice: if a product depends on the answer, have counsel read the license.

    Most projects land in the first column, because serving your own site triggers almost nothing. What moves platforms is handing modified builds to clients (copyleft) or needing single sign-on without paying (open core).

    What the free edition holds back

    Open core is a business model, not a flaw, but it changes the real price.

    16 of the 26 gate nothing: the code in the repository is the whole product. That is the strict meaning of a free open source CMS. The other 10 keep some features in a paid edition, and the list is consistent across them: single sign-on, roles beyond a few presets, audit logs and publishing workflows.

    10 platforms
    PlatformHeld back for a paid planCheapest managed hosting
    PayloadSSO, Publishing workflows, A/B testing, Enterprise AINone from the vendor
    StrapiLive Preview, Releases, Content History, SSO, Review Workflows, Audit Logs$35/mo
    TinaCMSSSO, More than 3 roles$29/mo
    WebinyRole-based access control, Multi-tenancy, Publishing workflows, SSO, Audit logsNone from the vendor
    PlasmicContent creator mode, Roles, SSO$49/mo
    MagnoliaGraphQL, Multisite, SSO, More than one public instance$6,000/mo
    Gentics MeshPostgreSQL, SQL Server and Oracle connectors, Keycloak SSO, SearchNone from the vendor
    ApostropheCMSAdvanced permissions, AI translation, Multitenant dashboardQuote
    ContentrainSelf-hosted Studio$9/mo
    CockpitPro add-ons (AI, search, sync, webhooks, localization)None from the vendor

    Read from each vendor's pricing page, US view, 2026-11-20.

    If the client is a company, expect to need SSO. Price the edition that includes it first.

    What it costs to run one

    The license is free; the server, the database and the hours are not.

    A headless open source CMS needs somewhere to run and somewhere to keep its content. 7 of the platforms here, TinaCMS, Decap CMS, Alinea, Sveltia CMS, Pages CMS, Front Matter CMS and Contentrain, store content as files in your Git repository, so there is no database to host, back up or upgrade. The Git-based CMS page covers where that stops working.

    The rest need a database, and 13 of them support PostgreSQL, which most hosts sell as a managed service. Budget for that database, a small server, and the hours someone spends on upgrades and security patches. 8 of the 26 also sell a managed cloud with a published price, which trades that work for a monthly bill.

    Source-available is not open source

    Some popular platforms publish their code under licenses that stop short of open source.

    Search for a headless CMS open source alternative to Contentful and these turn up next to the platforms above. You can read the code of every one of them, but each license limits who may use it for free, usually by company revenue, or what you may build with it. They are good products with honest licenses, and they belong in a different comparison.

    5 platforms
    PlatformLicenseThe catch
    DirectusMSCL-1.0 (each version also becomes GPL-3.0 four years after its release)Use, modify and host it for anything except selling Directus itself, and never bypass the license key.
    StatamicStatamic licenseOne production install per license; the headless API needs Pro.
    Craft CMSCraft licenseOne production install per license, and pay when the software prompts you.
    dotCMSBUSL-1.1 (converts to GPL-3.0 four years from 1 August 2025)Free in production only while your total finances stay at or under $5 million.
    PimcorePOCLFree in production only at or under EUR 5 million group revenue.

    Read from each repository's LICENSE file, 2026-11-20.

    How to choose the best open source headless CMS

    Four checks, in the order they usually rule platforms out.

    1. 01Match the runtime to your teamA Node.js team should not inherit a Java platform. Each review names the runtime and database.
    2. 02Read the license against how you shipUse the checker above. Copyleft and open core rule out more projects than features do.
    3. 03Price the edition you will needIf SSO, roles or workflows are on the roadmap, price the plan that has them now.
    4. 04Check the release historyA platform with no release in a year is a platform you will maintain yourself.

    The best open source headless CMS for a team with developers is usually the permissive one whose runtime they already know. Without developers, a managed cloud from the same project, or a hosted SaaS, removes the work that makes self-hosting cheap only on paper.

    Open source headless CMS, answered

    • What is the most popular open source headless CMS?
      By GitHub stars, Strapi, followed by Ghost and Payload. Popularity is not fit, though: the license, the runtime and what the free edition holds back decide more than stars do.
    • Is there a free open source CMS with no paid edition at all?
      Yes. Decap CMS, Keystone, Wagtail, sensenet, Orchard Core, Alinea, Contember, Sveltia CMS, Pages CMS, Graphweaver, Front Matter CMS and Publii gate no features and sell no paid tier, so the repository is the whole product. You still pay for hosting a headless open source CMS, and for the hours to maintain it.
    • Can I use an open source CMS in a commercial product?
      Yes with a permissive license such as MIT, Apache-2.0 or BSD: keep the notice and build what you like. With a copyleft license, running it as a website is fine, but handing a modified copy to a customer means handing over your changes as well. Read the license before you build a product on it.
    • Which of these headless CMS platforms need no database?
      The Git-based ones: TinaCMS, Decap CMS, Alinea, Sveltia CMS, Pages CMS, Front Matter CMS and Contentrain. They save content as files in your repository and commit each edit, so your site's hosting is the only hosting.
    • Does Directus's MSCL license count as open source?
      Not by its license. Directus is source-available under its own MSCL license: free for almost any use except selling Directus itself, and each version becomes GPL-3.0 four years after release. It is compared with the other source-available platforms above.

    Picking the provider is the easy half.

    busyless runs content and search as a system: we choose the data sources and tools, build the pipelines on top, and measure what they feed. If that is the part you are missing, talk to us.

    Ask an assistant about this page

    ChatGPTClaudePerplexity

    For scripts and agents

    Markdownllms.txt

    MCP server: https://busyless.space/api/mcp

    An independent comparison. No provider pays to be listed or to rank higher, outbound links carry nofollow, and we earn nothing if you sign up. Prices and terms were read from each vendor's own pages in November 2026 and change without notice.

    Missing, or out of date?

    Every entry here was read off the company's own website and dated, so some of it will have moved since. Corrections are free and so is being added. There is no fee, no sponsored position, and nothing that money moves up this page.