Boring CMS: Headless CMS in one Node process. Zero dependencies.

Hi Product Hunt, I'm Amit, maker of Boring CMS. I run many small sites and apps. Each needed the same thing: a place to edit content, an API to read it, and no operational overhead. Hosted CMS pricing scales with projects and seats. Self-hosted ones scale with moving parts. So I built one process, one folder, and no runtime dependencies to patch. What you get: - Multi-project from day one, each project with its own SQLite database, API keys and content model - Draft and publish, field-level revisions, webhooks, media library (local disk or S3-compatible) - REST API with ETag caching, so clients get cheap 304s until the next publish - A per-project MCP server, so Claude, Cursor or any MCP client can create and edit entries while you review and publish - 59 ms cold start, 65 MB idle, 533 KB unpacked, zero runtime dependencies Try it: npx boring-cms (needs Node 24). MIT licensed. I would love feedback on the content API and the MCP tools. What would make you switch from your current CMS?