Standard PostgreSQL
No proprietary content store. Query it with any Postgres client, ORM, or BI tool you already use.
SolutionsFOR ENGINEERING TEAMS
Content you own. Not content you rent.
Most CMSs ask you to trust a black-box hosted store with your content and hand over the keys. CMSHub keeps your content in standard PostgreSQL with forward-only migrations and a deny-by-default public API — so nothing about your content pipeline is locked behind a proprietary store.
01 / YOUR DATABASE, ALWAYS QUERYABLE
Full control over data residency
Content lives in a schema you can inspect, query directly, and export at any time. Build internal tools straight against it, run your own backups, or migrate off entirely — nothing is locked behind a proprietary API.
Forward-only, dry-run validated
Schema migrations run with dry-run impact checks and apply forward-only — production data is never reset.
Export anytime
There's no lock-in tax on leaving: your content is already in a database you own.
02 / SAFE, PREDICTABLE, OPERABLE
Built to run in production, not just a demo
A deterministic template engine, a deny-by-default public API, and a hosted service we operate for you keep the operational surface small and predictable.
No executable templates
The template engine rejects executable HTML and never evaluates JavaScript — generated pages can't become an XSS surface.
Deny-by-default public API
Public content APIs stay closed until you explicitly configure what a site exposes.
Operated for you
CMSHub runs as a hosted service today. A licensed self-hosted edition is not available yet, and we will announce it when it is.
KEEP YOUR DATA PORTABLE
Keep your content in Postgres you can leave with.
Read the data ownership guide and open a workspace to inspect the schema.