Norcube CMS vs Decap CMS — when paid earns its keep

• Pick Decap if budget is the hard constraint and you don't mind writing the schema yourself; if you're already on Netlify and want the simplest possible integration; if you prefer the long-term certainty of an open-source project that can't be shut down by a vendor.

• Pick Norcube CMS if AI scaffolding saves you a day of schema authoring; if you need solid UX on deeply-nested blocks (think content_blocks → buttons → icon); if you want field- level discussions, drafts per author, and email support.

Both are git-based, both commit to your branch, both keep your content in your repo. The difference is how much editor surface you get and who's on the hook when something breaks.

Schema authoring. Decap requires you to write config.yml by hand — every collection, every field, every widget. Norcube CMS runs an AI agent against your existing markdown and produces a starter schema in one commit. For a 20-block site, that's typically a day of work the agent absorbs.

Visual editor depth. Decap's editor is solid for flat frontmatter and moderate nesting. Norcube CMS handles deeply-nested multi-shape arrays (content blocks with their own buttons with their own icons) with first-class array-item previews, $ref-routed cog buttons, and per-field history.

Field-level collaboration. Norcube CMS has per-page discussions and per-user drafts so concurrent edits don't stomp each other. Decap's collaboration story is lighter; check their docs for the current state.

AI assistance. Norcube CMS includes an AI assistant for rewriting copy in-editor and an AI agent that scaffolds the schema from your existing markdown.

Support. Norcube CMS — email [email protected]. Decap — community-driven on GitHub.

Pricing. Decap is free forever. Norcube CMS is free during beta; paid tiers land at GA with no per-seat fees.