What TerminusCMS is in October 2026
TerminusCMS is the old name of TerminusDB, an open source graph and document database with Git-like version control. The TerminusDB site says the product was formerly DFRNT Hub and TerminusCMS and now goes by one name. It is not a classic headless CMS with an editor-first admin panel. It is a database you can model content in, with branches, commits, diffs and merges for the data itself.
The project is alive. The core is licensed Apache 2.0, the current line is TerminusDB 12 with a 12.1 release candidate on GitHub, and the site says the Gettier team has maintained and offered it since 2025. Managed hosting is in early access, with an Azure Marketplace listing slated for autumn 2026. We found no public pricing, so treat any older “$19 per month” figure you see as unverified.
When TerminusDB works as a content backend
It fits when the hard part of your content is the relationships and the history, not the page layout:
- Knowledge bases and documentation where documents link to each other in many ways.
- Regulated or audit-heavy data where you must show who changed what and roll back to an earlier state.
- Product catalogs and reference data that need review branches before changes go live.
- Datasets that several teams edit in parallel and merge, the way developers merge code.
You model schemas as typed documents and query them through a REST API and WOQL, the project’s query language, with JSON-LD documents. A Next.js or Astro front end reads that API like any other.
Where it does not fit
Editors are the weak point. TerminusDB ships no page builder, no media library and no scheduling, and the admin experience is built for data people, not for a marketing team. The community is small next to Strapi or Payload, and fewer developers know WOQL.
If your need is a marketing site with a blog and landing pages, pick another platform. We would reach for Strapi for a self-hosted API CMS, Payload for a code-first TypeScript setup, or Sanity for structured content with a strong editing studio. The headless CMS pillar compares them, and our guide on what a headless CMS is covers the basics.
What we build with TerminusDB
- Schema design: document types, subdocuments, links and constraints that match your domain.
- A thin API layer that hides WOQL behind typed endpoints for the front end.
- Review workflows on top of branches: propose, diff, approve, merge.
- Import jobs from relational databases or older CMS exports, plus the editor tooling around them. For the general method, see our CMS migration checklist.
- Hosting on your own infrastructure with Docker, or on the vendor’s managed cloud once it suits you.
We write the front end in React or Next.js, so the stack stays one TypeScript codebase. If you are weighing platforms before committing, we run a short audit and tell you plainly whether TerminusDB is the right tool. See our headless CMS agency page for how we work.
