Marble

Marble hits a sweet spot for indie hackers and small teams who are tired of wrestling with heavyweight CMSs. If you're building a personal blog or a product changelog with Next.js or Astro, the API is clean and the setup is quick. The free tier is generous enough to get started, and the $5 Hobby plan is cheap enough to justify upgrading for a bit more storage and AI insights. Where it shines: the writing experience is distraction-free, drag-and-drop images just work, and webhooks via Cloudflare Queues are real-time. The MCP server is a nice touch for AI agent workflows, and the Framer plugin makes it easy to sync content into a Framer site. For a small team, the 5-author limit on Hobby is workable, and the 10GB storage on Pro is plenty for most blogs. But Marble isn't for everyone. It's a headless CMS, so you need to build a frontend—there's no hosting or theming. If you're non-technical, this is a non-starter. Also, there's no SSO, no multi-language support, and no advanced role-based permissions, so enterprise teams will hit a wall. Revision history is missing too, which can be painful if you need to roll back changes. Compared to Strapi or Contentful, Marble is far simpler. Strapi gives you more flexibility with content modeling and roles, but it's heavier to run. Contentful is powerful but can be overkill and pricey. Marble deliberately stays minimal, which is its strength—but also its ceiling. In practice, we'd reach for Marble when you want a CMS you can set up in an hour and forget about. The API responses are straightforward, and the docs are clear. The subscription is per workspace, so if you run multiple projects, each needs its own plan. Watch the API request limits—5k on Free might be tight if you're fetching content frequently, but typical blogs won't