Boring CMS

Boring CMS is a headless CMS that runs as a single Node process on SQLite. One deploy serves many projects, each with its own database, API keys and content model. It starts in 59 ms, idles at 65 MB and ships with zero runtime dependencies, so there is nothing to audit and nothing to update weekly.

Features:

• Multi-project from day one, each project with its own collections, API keys and content model
• Content modeling in the admin: text, markdown, number, boolean, date, json, image, relation and counter fields
• Draft and publish, with field-level revisions and atomic revert
• REST API with Bearer keys (read and write scopes) and ETag caching
• Per-project MCP server, so AI agents such as Claude or Cursor can list, create, edit and publish entries
• Media library on local disk or any S3-compatible store, with optional resized variants
• Webhooks on publish, unpublish and delete
• Full JSON and CSV export and import
• Passkeys (WebAuthn), Google OAuth and email/password sign-in
• Schema-as-code per project, so content models live in version control

Run it with npx boring-cms (needs Node 24). Data lives in one folder as plain SQLite files, so backup and moving servers is a copy. MIT licensed.