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
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.