← All posts
· Facts checked

Open-source alternatives to popular CMSs

How Colophon, an open-source headless CMS you host yourself, compares with Strapi, Payload, Directus, Contentful, Sanity and git-based CMSs, dated.

Status. Colophon is pre-release (0.1.0-alpha.1) and has no users yet. I build it in public, on my own. See what’s built and the build log.

I build Colophon, so read this with that in mind. Each comparison below says who Colophon is for, puts the facts side by side with a link to the other vendor’s own page and the date they were checked, and ends with what to know before choosing Colophon.

Who Colophon is for

Colophon is an open-source headless CMS, under the MIT licence, that you run on your own servers with PostgreSQL. It is built for a team that wants every publish to leave a record it can check: a numbered release of the whole site, a receipt that says whether readers can see it, a rollback that is reviewed like any other change, roles down to a single field, and AI agents that can draft but never approve. It is pre-release, as the status line above says.

The comparisons

Comparison How the other one runs Licence
Colophon vs Strapi Self-hosted, or Strapi Cloud MIT, with enterprise code under a separate licence
Colophon vs Payload Installs into a Next.js app MIT
Colophon vs Directus Self-hosted, or Directus Cloud Its own source-available licence
Colophon vs Contentful A hosted platform Commercial service
Colophon vs Sanity Studio anywhere; content in its hosted Content Lake Studio MIT; hosted store
Colophon vs Storyblok Hosted spaces, with a visual editor Commercial service
Colophon vs Decap, Keystatic and TinaCMS Content as files in your git repository MIT (Decap, Keystatic); Apache-2.0 (TinaCMS)

The Strapi, Payload and Directus facts were checked on 16 November 2026, and the Contentful, Sanity, Storyblok, Decap, Keystatic and TinaCMS facts on 19 November 2026. Every row’s sources are listed in its comparison.

What sets Colophon apart

What to know before choosing Colophon

  • It’s pre-release. The first version, 0.1.0-alpha.1, is tagged, and its npm packages aren’t published yet. Nobody runs it in production.
  • There’s no hosted option, no plugin system that runs your code, and PostgreSQL is the only database.
  • The public delivery API has no language parameter yet, webhooks aren’t signed yet, and there’s no adapter for a real CDN.
  • The 24-hour soak test hasn’t passed yet. The load results that exist are laptop numbers, labelled as such.

FAQ

Is Colophon ready to replace my current CMS?

Not for production yet. It is pre-release, run by one maintainer, with no users so far. It is ready to try with Docker, to read, and to judge against the comparisons on this page.

Why do these comparisons only describe competitors neutrally?

Each comparison says what Colophon does and why it matters, states every competitor fact with a link to that vendor's own page and the date it was checked, and ends with what to know before choosing Colophon. If a fact is wrong or out of date, open an issue and it gets corrected with a dated note.