01 / TRUST BY DESIGN

Security built into the core

CMSHub was designed data-first: tenant-isolated, auditable, and always keeping your content in a database you can export.

Your content, standard PostgreSQL

All content lives in standard PostgreSQL — a schema you can inspect through backups and exports at any time. No lock-in.

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

Keep your content portable.

Model content and deliver through controlled APIs while your data stays in standard PostgreSQL you can export and back up. A self-hosted edition is not offered yet.