DevelopersDATA OWNERSHIP

Your content, in a database you can leave with.

CMSHub is offered as a hosted service today, and a licensed self-hosted edition is not available yet. What you get now is data ownership: content, media metadata, and schema live in standard PostgreSQL that you can inspect, query, export, and back up with the tools you already run — nothing is locked behind a proprietary store.

01 / YOUR DATABASE

PostgreSQL, forward-only, dry-run validated

There's no proprietary content store to migrate off later. Schema changes run through a dry-run impact check before they apply, and migrations are strictly forward-only, so production data is never at risk of a reset.

Standard PostgreSQL

The data model is plain Postgres tables and JSONB — nothing about the data layer is CMSHub-specific.

Dry-run migration checks

Preview what a schema change would impact before applying it, across every content type and dependent page.

Forward-only by policy

Migrations never roll back destructively — user data is never reset as the schema evolves.

02 / SELF-HOSTING STATUS

Not offered yet — here is what that means

CMSHub runs on infrastructure we operate. We do not sell a self-hosted license today, so there is no installer, container image, or support contract to buy. When a self-hosted edition ships, we will announce it here and on the pricing page.

Hosted on every plan

Free, Team, Business, and Enterprise all run on CMSHub-managed hosting. Enterprise adds dedicated infrastructure isolation, not a self-hosted install.

Export anytime

Verified PostgreSQL and media backups from the Operations screen, CSV export, and the public content API keep your content portable.

On the roadmap

A packaged self-hosted edition is planned. If it matters to your decision, tell us about your requirements through the Enterprise contact form.

KEEP YOUR DATA PORTABLE

See the data model before you commit.

Open a workspace to inspect the schema, or talk to us if a self-hosted edition matters to your decision.