shapioreadme
Shapio logo

shapio

a headless cms whose models change live · self-hosted · Node.js · PostgreSQL, SQLite or MySQL

Most headless CMSs turn a content model into code: change a field and you rebuild, migrate and redeploy. Shapio keeps models as data. Add a field in production and REST and GraphQL serve it on the next request, with no rebuild or restart. The schema lives in git too: pull it, review it, apply it, and Shapio refuses an apply when production has moved on, like a rejected push. Schema and content ship together in reviewed change sets, every save is a revision you can restore, and editors get rich text, media, relations and visual editing that are finished. Self-hosted on Node.js with PostgreSQL, SQLite or MySQL; Apache-2.0, with no hosted account and no telemetry.

in the box

live models
Add or change a field in production. REST and GraphQL serve it on the next request: no code generation, no rebuild, no restart.
schema in git
Pull the models to JSON files, review them, apply them live. An apply is refused when production has moved on, and shows the diff.
change sets
Schema and content ship together as one reviewed snapshot, now or at a set time, and every snapshot can be restored.
editors that are finished
Rich text, media, relations, components and localization, with preview and visual editing on your real site.
many sites, one login
Each site keeps its own content, media, tokens, snapshots and deployments under one shared schema.
roles and audit log
Permissions per model, action and field, and a record of who changed what, agents included.
deployments
Cloudflare Pages, Vercel, Netlify or a signed build hook, with real build status and retry.
yours to run
Apache-2.0 with every feature in the core, no hosted account and no telemetry. Nothing leaves your server unless you configure it.

docs and source

Shapio has its own site at shapio.dev, with the documentation and the source code on GitHub. Questions and bug reports go to the GitHub issues.