Your content, your database
All content lives in your own PostgreSQL database — a schema you can inspect, query directly, and export any time. No lock-in.
01 / TRUST BY DESIGN
Security built into the core
CMSHub was designed data-first: tenant-isolated, auditable, and always running against a database you control.
Hardened authentication
Argon2id-derived credentials, revocable server-side sessions, and JWT-wrapped session tokens with auditable auth events.
Tenant isolation
Workspace-scoped queries throughout — every request is bound to the caller's workspace membership.
Deny-by-default APIs
Machine credentials carry explicit per-collection action permissions. Public content APIs stay closed until you open them.
Safe templates
The template engine rejects executable HTML and never evaluates JavaScript — generated pages can't become an XSS surface.
Forward-only migrations
Schema evolution is validated with dry-run impact checks and applied forward-only. User data is never reset.
START WITH ONE WORKSPACE
Run CMSHub on infrastructure you own.
No third-party SaaS dependency — model content and deliver through controlled APIs without handing over your database.