“Hosted-first products such as Contentful, Sanity, and Storyblok are less suitable because the CMS infrastructure remains vendor-controlled.”
“Hosted-first products such as Contentful, Sanity, and Storyblok are less suitable because the CMS infrastructure remains vendor-controlled.”
“Hosted-first products such as Contentful, Sanity, and Storyblok are less suitable because the CMS infrastructure remains vendor-controlled.”
“Hosted-first products such as Contentful, Sanity, and Storyblok are less suitable because the CMS infrastructure remains vendor-controlled.”
“Strapi | General-purpose CMS | UI + code | MIT Community, self-hostable | ⭐ Best all-rounder”
“Strapi is probably the best default if you want a traditional CMS editing experience plus APIs.”
“Its Community Edition is MIT-licensed and can run entirely on your own infrastructure, including on-premises or isolated networks.”
“Choose it when: you have several editors, lots of conventional content types, and want a mature ecosystem and customizable admin UI.”
“Watch out: some advanced enterprise capabilities are separately licensed, so check the exact features you need before assuming the entire Strapi experience is under MIT.”
“Hosted-first products such as Contentful, Sanity, and Storyblok are less suitable because the CMS infrastructure remains vendor-controlled.”
“Hosted-first products such as Contentful, Sanity, and Storyblok are less suitable because the CMS infrastructure remains vendor-controlled.”
“Directus | Existing SQL data | Database-first | Source-available license | ⭐ Best if your database is the source of truth”
“Directus is architecturally different: instead of having the CMS define and own your data model, it sits on top of an SQL database and turns your existing tables into an API and admin interface.”
“You can potentially remove Directus later and still have your underlying PostgreSQL/MySQL/etc. data.”
“Important caveat: Directus changed its licensing in 2026 to a source-available model, so if "fully open-source/permissive licensing" is itself a requirement, I'd favor Payload or Strapi instead.”
“Payload | TypeScript/Next.js teams | Code-first | MIT, fully self-hostable | ⭐ Best for developer-controlled systems”
“Payload is particularly compelling if you're already using Next.js/TypeScript.”
“Your schemas, access control and CMS configuration live in code, while the content itself lives in your database.”
“It's MIT-licensed and can be deployed anywhere you can run Node.js.”
“Downside: its code-first approach is less appealing if you want marketers/content editors to design content structures independently of developers.”
“KeystoneJS | GraphQL-heavy applications | Code-first | MIT | Powerful, but more developer-centric”
“Keystone is a good fit for a GraphQL-first, TypeScript/Node application.”
“It's more of a developer framework than a marketer-oriented CMS, so I'd choose it when the CMS is really part of an application rather than primarily a publishing platform.”
“Wagtail | Python/Django teams | Code + admin | BSD-3-Clause | Excellent for Python organizations”
“It's open source, self-hostable, and gives you a mature editorial experience while remaining deeply customizable.”
“I'd pick it over Node-based alternatives when the rest of the organization's backend is already Django.”
