# 26 Netlify CMS Alternatives for Developers & Agencies

*Updated 2026-09-03.*

> Netlify CMS became Decap CMS, and its Git Gateway login is deprecated. If your site still runs it, here are 26 realistic destinations, compared honestly.

## TL;DR

Quick answer: Least change is Decap CMS, the same project renamed, plus an OAuth app for sign-in. Want a modern panel on the same config? Sveltia CMS. Free and hosted, no auth to wire? Pages CMS or Sitepins. Handing the site to a client? CMS Brew ($39/mo for 5 sites). Visual editing? CloudCannon. The rest depends on who edits the site and how often, keep reading.

## At a glance

| Tool | Editing model | Setup | Review before publish | Price |
| --- | --- | --- | --- | --- |
| CMS Brew | Hosted, chat-based | Connect repo, automatic mapping | Included, per-field guards | $39/mo, 5 sites |
| Decap CMS | Self-hosted panel | Keep config, fix auth | Drafts via editorial workflow | Free |
| Sveltia CMS | Self-hosted panel | Keep config, fix auth | PR drafts on GitHub/GitLab | Free (MIT) |
| Pages CMS | Hosted or self-hosted panel | New config file, email invites | No | Free (MIT) |
| Sitepins | Hosted or self-hosted panel | Connect repo, fields auto-detected | Branch + PR flow on Pro | Free tier; $12 to $49/mo |
| CloudCannon | Hosted, visual editing | Editable regions per site | On Team tier | From $55/mo + $10/user |
| TinaCMS | In-site visual editor | Schema rewrite | Team Plus tier, $49/mo | OSS core; cloud from $29/mo |
| Keystatic | Self-hosted admin UI | Schema rewrite | No | Free; Cloud from $10/mo |
| Netlify Visual Editor | Hosted visual layer | Netlify site + content source | Builder and Publisher roles; PR mode | Netlify Pro $20/mo |
| GitCMS | Hosted Markdown editor | GitHub App, collections | Editorial workflow, on by default | $49 one-time per site |
| Outstatic | Panel in a Next.js app, or hosted | Next.js install or hosted dashboard | Draft or published only | Free; PRO $9.99/user/mo |
| Siteleaf | Hosted panel for Jekyll | GitHub sync, Jekyll only | Writer drafts on Team plan | Unpublished; per site |
| Front Matter CMS | VS Code extension | Local clone, frontmatter.json | No | Free (MIT) |
| Spinal | Hosted Markdown CMS | Connect GitHub, pick folders | Roles only, no approval | $39/mo |
| Unfreez | Hosted, click-to-edit | Developer unlocks fields per site | No; undo per publish | €90 per site per year |
| CMS Chat | Hosted, chat-based | GitHub App, zones per site | Escalations open a PR | From €99/mo, 1 site |
| Nuxt Studio | Editor module inside a Nuxt site | Install module, connect repo | No; PRs on the roadmap | Free (MIT) |
| Payload | Self-hosted app CMS | Code-first, database-backed | Drafts; workflows on Enterprise | Free (MIT); Enterprise custom |
| Strapi | Self-hosted headless CMS | Content types, database, hosting | Review Workflows on Enterprise | Free; Growth $45/mo |
| Directus | Database-backed headless CMS | Connect a database, model collections | Versioning, no approval gate | Free Core; Team $499/mo |
| Sanity | Hosted content platform | Schema, Studio deploy, content migration | None built in; releases on Enterprise | Free; Growth $15/seat/mo |
| Contentful | Hosted content platform | Content model, SDK, content migration | Scheduling; workflows on Enterprise | Free; Lite $300/mo |
| Storyblok | Hosted headless + visual editor | Component schema, API integration | Standard workflow on all tiers | Free; Growth $99/mo |
| DatoCMS | Hosted headless CMS | Content model, GraphQL integration | Scheduling; workflows on Enterprise | Free; Professional €149/mo |
| Prismic | Hosted headless CMS | Slices, Slice Machine, API | Releases and scheduling on all tiers | Free; from $10/mo |
| Hygraph | Hosted GraphQL CMS | Schema, GraphQL integration | Draft/published; scheduling on Enterprise | Free; Growth $199/mo |

## The Netlify CMS alternatives, one by one

### CMS Brew

*Best for agencies handing finished sites to non-technical clients.* </>

Tags: Chat editing, Client handoff, Review included, Hosted, Framework-neutral.

If the site belongs to a client and Netlify CMS was your way of letting them edit it, CMS Brew replaces the whole arrangement rather than patching it. Connect the GitHub or GitLab repository and it maps the editable content automatically: the config.yml, the /admin page, and the auth problem all stop existing. The client describes changes in chat and sees them in a live preview; every publish is one Git commit with one-click revert.

It also adds what the old setup never had: per-field guard levels that hold risky changes for your review, and escalation of out-of-scope requests to you with the client's original words. Sign-in is built in, Google or an emailed 6-digit code.

**Pros**
- Client edits by chat, nothing to relearn between rare visits
- Review-before-publish and per-field guards included
- The deprecated-auth problem disappears entirely, sign-in is built in
- No config.yml and no /admin page to maintain ever again

**Cons**
- Paid, while the panel family is free
- Clients cannot create new pages or change layout; those escalate to you
- Hosted service, not self-hostable

**Pricing:** $39/mo for 5 sites, unlimited editors, 7-day free trial.

[Read the full CMS Brew vs Decap CMS comparison](https://cmsbrew.com/compare/decap-cms)

### Decap CMS

*Least change: the same project under its new name.* <https://decapcms.org>

Tags: Git-based panel, Free, Open source, Framework-neutral, PR drafts.

Decap CMS is Netlify CMS: same project, renamed, now community-maintained, and releasing regularly again in 2026. Updating from the old netlify-cms package to decap-cms is the smallest possible move, your config.yml and content work as they are.

It does not solve the real problem yet, though. The rename did not bring a login path with it: with Git Gateway deprecated, you still need to wire an OAuth app or a third-party auth bridge, and you keep the form admin and per-site config that made you search for alternatives in the first place. Decap Turbo, a hosted layer with hosted auth, is in closed beta; if it ships, the least-change option gets a lot stronger.

**Pros**
- Minimal migration: rename the package, keep config and content
- Free, open source, maintained by the community with 2026 releases
- Editorial workflow (drafts via pull requests) available on GitHub

**Cons**
- The auth problem remains until Decap Turbo leaves closed beta
- Same form admin your rare editors never learned
- config.yml still maintained per site

**Pricing:** Free and open source.

[Read the full CMS Brew vs Decap CMS comparison](https://cmsbrew.com/compare/decap-cms)

### Sveltia CMS

*Best modern drop-in for the same config.* <https://sveltiacms.app>

Tags: Git-based panel, Free, Open source, Framework-neutral, Beta.

Sveltia CMS is a from-scratch, actively developed successor to Netlify/Decap CMS, built to work with an existing configuration and documented with migration guides. It fixes years of accumulated Netlify CMS issues and adds what the original never got: a modern UI, first-class i18n, real asset management, mobile support, and an editorial workflow that turns each draft into a branch and pull request on GitHub or GitLab.

You keep the model, so you keep its obligations: the config file stays yours to maintain, and sign-in is an OAuth flow you set up, since Sveltia backs GitHub, GitLab, and Gitea directly rather than Git Gateway or the Netlify Identity widget. It is also a 0.x beta from one maintainer, with 1.0 planned for late 2026. For a technical team that liked Netlify CMS, this is the best version of that idea available today.

**Pros**
- Works with an existing Netlify/Decap config, migration guides provided
- Free, MIT-licensed, and actively developed
- Substantially better editor UX than the original, with PR-based drafts

**Cons**
- You still maintain the content-model config per site
- OAuth-based sign-in is yours to set up
- Still 0.x beta from one maintainer; 1.0 due late 2026

**Pricing:** Free and open source (MIT).

### Pages CMS

*Best free option with hosting and sign-in handled.* <https://pagescms.org>

Tags: Git-based panel, Free, Open source, Hosted, GitHub only.

Pages CMS keeps the Git-based panel idea but moves it off your site: a free, MIT-licensed CMS for GitHub repos with a hosted version, so there is no /admin page to ship and no OAuth app to wire. You describe content types in one config file, and editors join by email invite.

It is younger than the rest of the family: granular permissions and scheduling are still on the roadmap, and it is GitHub-only. As a free landing spot for a small stranded Netlify CMS site, it is hard to argue with.

**Pros**
- Free, with a hosted version, so auth and hosting are handled
- Editors join by email invite
- Single config file, familiar model for Netlify CMS veterans

**Cons**
- Config file still maintained per site
- GitHub-only
- Team features like granular permissions are roadmap items

**Pricing:** Free and open source (MIT); hosted version free, or self-deploy.

### Sitepins

*Best free hosted panel for agencies, GitLab on paid tiers.* <https://sitepins.com>

Tags: Git-based panel, Free tier, Open source, Hosted, Agency orgs.

Sitepins is the closest thing to a direct rival on this list: a Git-based panel aimed at handing Astro, Next.js, Hugo, and other framework sites to non-technical teammates and clients. It auto-detects fields from existing Markdown and front matter, invites editors by email so nobody needs a GitHub account, and organizes sites into per-client organizations. Open-sourced under AGPL in July 2026, with a free hosted Hobby tier.

It is a form-based admin, not chat: editing a post means a Frontmatter tab of fields and a Content tab with a rich-text toolbar. Review is a branch-and-pull-request workflow on the Pro plan, coarser than a per-field policy, and the free tier is one user and three sites.

**Pros**
- Free hosted tier, cheap paid tiers, unlimited AGPL self-hosting
- Editors join by email, sites grouped in per-client organizations
- Fields auto-detected from Markdown and front matter

**Cons**
- Form-based panel a rare editor must relearn
- Review is a Pro-plan branch and PR flow, not per edit
- GitLab only from the $29 Team plan; one user on the free tier

**Pricing:** Hobby free (3 sites, 1 user); Pro $12/mo, Team $29/mo, Agency $49/mo, less on annual billing; lifetime licenses from $249; self-hosting free under AGPL.

### CloudCannon

*Best visual editing upgrade.* <https://cloudcannon.com>

Tags: Visual editor, Visual editing, Hosted, Per-seat, GitHub, GitLab, Bitbucket.

CloudCannon turns the Git repo into a visually editable site: editors click on the page, changes sync to GitHub, GitLab, or Bitbucket, and the CMS itself is hosted and supported. Teams leaving Netlify CMS for something clients actually enjoy using often land here.

It is a commercial product priced per user: from $55 per month with 3 users included and $10 for each additional one, with branching workflows and advanced scheduling on the larger Team tier. You also configure what is editable per site.

**Pros**
- Real visual, in-context editing
- Hosted and supported, multi-Git-provider
- Mature, agency-friendly product

**Cons**
- Per-user pricing that grows with client editors
- Workflow features gated to the $300+/mo Team tier
- Per-site setup of editable regions

**Pricing:** From $55/mo (3 users, unlimited sites), extra users $10/mo; 21-day trial.

### TinaCMS

*Best for React sites wanting in-place editing.* <https://tina.io>

Tags: Visual editor, Visual editing, Open source core, React-first, Paid review tier.

TinaCMS keeps content in the repo but replaces the form admin with visual editing on the page, strongest on React sites. For a content team that edits daily, it is a genuine upgrade over the Netlify CMS experience.

The move is bigger than a panel swap: you rewrite config.yml as a Tina schema, adopt Tina's client and data layer inside the site, and the editorial workflow that makes edits reviewable starts at TinaCloud's $49 per month Team Plus tier.

**Pros**
- Visual editing daily editors prefer
- Open-source core, content stays in the repo
- Hosted backend available when you want it

**Cons**
- Schema rewrite and a data layer added to the site
- React-first; other frameworks get less
- Review-before-publish starts at the $49/mo tier

**Pricing:** Open-source core (Apache-2.0); TinaCloud free for 2 users, Team $29/mo, editorial workflow from Team Plus at $49/mo.

[Read the full CMS Brew vs TinaCMS comparison](https://cmsbrew.com/compare/tinacms)

### Keystatic

*Best for technical editors who want clean files.* <https://keystatic.com>

Tags: Git-based panel, Free, Open source, Next.js, Astro.

Keystatic, from Thinkmill, is a well-crafted Git-based CMS with a schema defined in code and files clean enough to keep editing by hand. Developer-adjacent teams moving off Netlify CMS often like it a lot.

For non-technical editors it is a harder sell: GitHub mode requires each editor to have a GitHub account with write access to the repo, Keystatic Cloud (free for 3 users, then $10 a month plus $5 per user) is the way around that, and publishes land in the repo with no review step.

**Pros**
- Free, open source, actively developed
- Clean two-way editing of Markdown, JSON, and YAML
- Solid fit for Next.js, Astro, and Remix

**Cons**
- Editors need GitHub write access or Keystatic Cloud seats
- Schema maintained per site
- No approval step before publish

**Pricing:** Free and open source (MIT); Keystatic Cloud free for 3 users, Pro from $10/mo plus $5 per extra user.

[Read the full CMS Brew vs Keystatic comparison](https://cmsbrew.com/compare/keystatic)

### Netlify Visual Editor

*Best if you want to stay inside Netlify.* <https://docs.netlify.com/manage/visual-editor/overview/>

Tags: Visual editor, Visual editing, Netlify teams, Docs only, GitHub, Bitbucket.

Netlify Visual Editor is the other editing product Netlify kept: the Stackbit editor it acquired, now a visual, in-context editing layer over either the files in your Git repository or a headless CMS like Contentful, Sanity, or DatoCMS, for Next.js, Astro, Nuxt, SvelteKit, Eleventy, Gatsby, and any custom dev server. Editors are Netlify team members, with Internal Builders who save work for review and Publishers who ship it.

It is a quiet corner of Netlify now: the marketing pages are gone and only the docs remain, updated through 2026. It accepts GitHub and Bitbucket repositories, not GitLab, and inviting a client editor needs a Pro team at $20 per month, since Free and Personal plans cannot add members.

**Pros**
- Visual editing over repo files or a headless CMS
- Reviewer and Publisher roles; Git publishes can open a PR
- Unlimited team seats on the $20/mo Pro plan

**Cons**
- No marketing page; the product lives in the docs
- GitHub and Bitbucket only, no GitLab
- Editors must be Netlify team members on a Pro team

**Pricing:** Netlify Pro from $20/mo with unlimited team members; which plans include Visual Editor is not stated on the pricing page.

### GitCMS

*Best one-time price for a Markdown content layer.* <https://gitcms.dev>

Tags: Git-based panel, One-time price, Markdown, Review workflow, GitHub only.

GitCMS is a hosted, Notion-like editor for the Markdown and MDX in a GitHub repository: slash commands, a kanban content board, front-matter forms, and MCP access so ChatGPT or Claude can draft into it. It supports a long list of generators, from Astro and Hugo to Docusaurus and Zola.

Review before publish is built in and on by default, with Owner, Admin, Editor, Reviewer, and Viewer roles, and collaborators sign in with Google or GitHub. It stops at the Markdown layer: copy hardcoded in components is out of scope, and it is GitHub-only and proprietary. The price is the unusual part, a one-time license per site.

**Pros**
- One-time $49 per site during launch, no subscription
- Review-before-publish on by default, with reviewer roles
- Block editor plus MCP access for AI drafting

**Cons**
- Markdown and MDX only; component copy is out of reach
- GitHub only, no self-hosting
- One seat included, extra seats cost extra

**Pricing:** $49 one-time per site during launch ($79 regular), 1 seat included, extra seats $9 each; free preview mode, no self-serve free plan.

### Outstatic

*Best free dashboard for Markdown in a Next.js app.* <https://outstatic.com>

Tags: Git-based panel, Free self-hosted, Next.js, Markdown, Source-available.

Outstatic is a Git-based dashboard for Markdown and MDX that installs inside a Next.js app, or runs as a hosted PRO dashboard over any GitHub repository. Collections, custom fields, singletons, and a metadata index cover most content sites, and the free self-hosted version is unlimited.

It is source-available under the Functional Source License rather than open source, GitHub-only, and its statuses stop at draft or published: there is no approval step, and team roles are a PRO feature. Free-tier editors sign in with GitHub; PRO adds email magic links and Google.

**Pros**
- Free self-hosted version with the full feature set
- Hosted PRO dashboard with email and Google sign-in
- Actively maintained, frequent releases

**Cons**
- Self-hosted install is Next.js only; GitHub only
- Draft or published, no review step; roles are PRO-only
- Source-available (FSL), not open source

**Pricing:** Free self-hosted; Outstatic PRO $9.99 per user per month hosted, 14-day trial. Source-available (FSL-1.1).

### Siteleaf

*Best hosted panel if the site is Jekyll.* <https://www.siteleaf.com>

Tags: Git-based panel, Hosted, Jekyll only, GitHub sync, Prices unpublished.

Siteleaf is a hosted CMS for Jekyll sites with two-way GitHub sync: editors work in Siteleaf, changes commit to the repository, and publishing goes to GitHub Pages, S3, or FTP. It has run for over a decade, editors are invited by email, and the Team plan's Writer role defaults new content to draft until a Publisher approves it.

It is Jekyll-only, the blog has been quiet since 2023 while a new version is promised, and the plans page prints no prices. Fine for a Jekyll site that needs a familiar hosted panel; not a destination for anything else.

**Pros**
- Two-way GitHub sync, editors invited by email
- Writer drafts wait for a Publisher on the Team plan
- Unlimited users on every plan

**Cons**
- Jekyll only
- Prices not published; billed monthly per site
- Quiet since 2023, new version still promised

**Pricing:** Prices not printed on the plans page; free Developer plan for public repos, 14-day trial on Personal, billed monthly per site.

### Front Matter CMS

*Best for developers who edit content in VS Code.* <https://frontmatter.codes>

Tags: Developer tool, Free, Open source, VS Code, Local only.

Front Matter CMS is a CMS that lives inside VS Code: a dashboard for the Markdown and MDX in your repository, front-matter forms, data files, and media, with no server or hosted service involved. It works with Astro, Hugo, Jekyll, Eleventy, Next.js, and most generators, and it is free and MIT-licensed.

That makes it a developer's tool, not a client handoff. Every editor needs the repository cloned and VS Code installed, changes go out as their own commits with no review step, and the maintainer's 2026 note says feature work now depends on sponsorship.

**Pros**
- Free and open source, no server to run
- Works with almost any static site generator
- Front matter, data files, and media in one dashboard

**Cons**
- Editors need VS Code and a clone of the repository
- No review step, no hosted sign-in
- Feature development throttled without sponsorship

**Pricing:** Free and open source (MIT).

### Spinal

*Best scheduled publishing for a Markdown marketing blog.* <https://spinalcms.com>

Tags: Git-based panel, Hosted, Markdown, Scheduling, EU-hosted.

Spinal is a hosted CMS for the Markdown in a GitHub repository, built around written marketing content: a WYSIWYG editor, draft and scheduled statuses, and optional kanban and calendar power-ups. Team members sign up with email and password, and it lists Eleventy, Astro, Hugo, Jekyll, Docusaurus, and a dozen other generators.

It is one $39 per month plan with a five-member minimum, GitHub-only, and while Authors cannot publish, there is no approval flow beyond that role split. Copy outside Markdown is out of scope.

**Pros**
- Scheduling and a content calendar for a blog team
- Editors sign in with email, no GitHub accounts
- Hosted in the EU, no CMS code in your site

**Cons**
- $39/mo with a 5-member minimum, card required for the trial
- Markdown content only, GitHub only
- Role split, but no per-edit review

**Pricing:** Pro $39/mo (5 members minimum, $4 per extra member; 1,000 entries, 10 collections); power-ups $9/mo each; 7-day trial, card required.

### Unfreez

*Best client-billed click-to-edit layer for component copy.* <https://unfreez.app>

Tags: Visual editor, Click-to-edit, Client-billed, Component copy, GitHub only.

Unfreez makes a hand-coded Next.js, Astro, Vue, or Svelte site editable without a CMS: it parses the source, pins each human-facing value to a path in the syntax tree, and the client edits on a live copy of the page. Every publish is one signed Git commit with one-tap undo, and, unusually, the bill goes to the client: €90 per site per year through an activation link the developer sends.

The developer curates which values the client may touch, per site, and everything else stays locked. Its pitch is deterministic, no model in the loop and a refusal to write on any ambiguity. There is no review queue and no escalation path; an out-of-scope request is simply a field that was never unlocked. GitHub is the connected provider, and the product is a few months old.

**Pros**
- Edits copy inside components, not only Markdown
- Client-billed at €90 per site per year, unlimited editors
- One atomic commit per publish, one-tap undo

**Cons**
- Developer unlocks every editable value per site by hand
- No review queue or escalation for out-of-scope asks
- GitHub only; young product with no public changelog

**Pricing:** €90 per site per year excl. VAT, billed to the client; unlimited editors; 14-day free trial, no card.

### CMS Chat

*Closest chat-based rival, for teams that can wait out a private beta.* <https://www.cmschat.ai>

Tags: Chat editing, Client handoff, Escalates to PR, Private beta, GitHub only.

CMS Chat is the other chat-to-edit product on this list: clients change text, images, prices, and links by chatting, and every edit lands as a plain Git commit on a branch you control. Its zone model is a real review story. Editable zones commit straight away, Warn zones ask for confirmation, Escalate zones open a GitHub pull request for your team, and Locked zones refuse.

It is in private beta behind a waitlist, GitHub-only, and priced for agencies: Starter is €99 per month for one site and Agency €249 for three, billed by invoice with no free tier or trial. Self-hosting is explicitly not offered.

**Pros**
- Chat editing with a zone-based review model
- Edits copy inside TSX and MDX components, not only Markdown
- Unlimited client users on every tier

**Cons**
- Private beta behind a waitlist, no trial and no free tier
- From €99/mo for a single site
- GitHub only, no self-hosting

**Pricing:** Starter €99/mo (1 site), Agency €249/mo (3 sites), Studio €499/mo (10 sites); private beta, invoiced, no free tier.

### Nuxt Studio

*Best free option if the site is Nuxt.* <https://nuxt.studio>

Tags: Visual editor, Free, Open source, Nuxt only, GitHub, GitLab.

Nuxt Studio went open source and free in 2026: a Nuxt module that mounts an editor at /_studio on your own production site, edits the Nuxt Content files in the repository with a live preview, and commits to GitHub or GitLab. Editors sign in with GitHub, GitLab, or Google, and there are no seats to buy. The former hosted subscription was cancelled for everyone.

It is Nuxt with Nuxt Content only, the site has to be deployed with server-side rendering, and publishing commits straight to the configured branch: pull-request generation is still an open roadmap item, so there is no review step yet.

**Pros**
- Free and MIT, no seats, self-hosted inside your Nuxt site
- GitHub and GitLab, with Google sign-in for editors
- Live preview of the real site while editing

**Cons**
- Nuxt with Nuxt Content only, SSR deployment required
- No review step; commits go straight to the branch
- Young as an open-source module, roadmap still open

**Pricing:** Free and open source (MIT); the hosted subscription was discontinued.

### Payload

*Best when the project is really an application.* <https://payloadcms.com>

Tags: Headless platform, Open source, Self-hosted, Next.js, Database.

Payload is a code-first, open-source CMS that runs inside a Next.js application, with a real database behind it (MongoDB, Postgres, or SQLite) and auth, access control, drafts, versions, and an admin UI generated from your TypeScript config. Owned by Figma since June 2025, and still MIT.

It solves a different problem than a Git panel does. Content moves out of the repository into a database, you host and operate the whole thing, since Payload Cloud is not taking new projects, and the setup is application-scale. Multi-stage publishing workflows are an Enterprise feature. For a brochure site handed to a client, it is far more machine than the job needs.

**Pros**
- Full application CMS: database, auth, access control, hooks
- MIT-licensed and code-first, deeply customizable
- First-class Next.js integration, very active development

**Cons**
- Content leaves the repo for a database
- You build, host, and operate it; Cloud is paused for new projects
- Heavy for small content sites; review workflows are Enterprise-only

**Pricing:** Free and open source (MIT), self-hosted anywhere; Payload Cloud is not accepting new projects; Enterprise plans are custom.

### Strapi

*Best self-hosted open-source headless CMS.* <https://strapi.io>

Tags: Headless platform, Open source, Self-hosted, Database, Cloud option.

Strapi is the established open-source Node.js headless CMS: a self-hosted admin panel over your own SQL database, REST and GraphQL APIs, and a plugin ecosystem, with Strapi Cloud if you would rather not run it. The Community edition is free and MIT-licensed with unlimited usage.

It is an application to operate, not a layer over your repository: content lives in the database, and the governance features are tiered. Releases and content history start on the $45 per month Growth plan, and multi-stage Review Workflows are Enterprise-only.

**Pros**
- Free, MIT-licensed Community edition with unlimited usage
- Your database, your hosting, REST and GraphQL out of the box
- Large plugin ecosystem and active development

**Cons**
- Content leaves your repo; you operate a server and a database
- Review Workflows are Enterprise-only
- Cloud hosting from $35 per project per month

**Pricing:** Community free (MIT); Growth $45/mo (3 seats, $15 per extra seat); Enterprise custom. Strapi Cloud from $35 per project per month.

### Directus

*Best when the content is really a database.* <https://directus.com>

Tags: Headless platform, Source-available, Self-hosted, SQL database, Free Core.

Directus wraps any SQL database in REST and GraphQL APIs and a no-code Data Studio, so it fits teams whose content is really relational data. Self-hosting is free under its grant for organizations under $5M in revenue with fewer than 50 employees, with content versioning, flows, and role-based access included.

It is source-available under the Monospace Sustainable Core License, not open source, and the pricing has a cliff: Core is free with a hard limit of 3 seats, and the next tier is Team at $499 per month on an annual commitment. There is no approval gate; publishing a version makes it current.

**Pros**
- Free Core tier and free self-hosting under the grant
- Any SQL database, REST and GraphQL, no-code Data Studio
- Content versioning, flows, granular roles

**Cons**
- Content leaves your repo; a database to operate
- Nothing between 3 free seats and $499/mo
- Source-available license, no approval step

**Pricing:** Core free (3 seats); Team $499/mo billed annually or $599 monthly (10 SSO seats); Enterprise custom. Self-hosting free under the Open Innovation Grant.

### Sanity

*Best structured-content platform, with a free tier that goes far.* <https://www.sanity.io>

Tags: Headless platform, Hosted, Free tier, Structured content, Per-seat.

Sanity is the most recommended headless CMS in the framework world: content lives in its hosted Content Lake, the open-source Studio is yours to shape, and Next.js, Astro, Nuxt, and SvelteKit are all first-class. The free plan is generous, up to 20 seats with two roles.

Coming from a Git-based panel it is more of everything: a schema you write and deploy, GROQ queries, and a migration of the content itself out of the repository. The permissions story surprises people. On Free, a client is either Administrator or Viewer; Editor and Contributor roles start on Growth at $15 per seat per month, and there is no approve-before-publish gate out of the box.

**Pros**
- Free plan with 20 seats; the Studio is open source
- Best-in-class structured content and real-time collaboration
- First-class SDKs for every major framework

**Cons**
- Content leaves your repo for the Content Lake
- Two roles on Free; an Editor role costs $15 per seat per month
- No approval step out of the box; content releases are Enterprise

**Pricing:** Free up to 20 seats; Growth $15 per seat per month with pay-as-you-go usage; Enterprise custom. Self-serve plans are monthly only.

[Read the full CMS Brew vs Sanity comparison](https://cmsbrew.com/compare/sanity)

### Contentful

*Best-known enterprise headless CMS.* <https://www.contentful.com>

Tags: Headless platform, Hosted, Enterprise, Free tier, Per-seat.

Contentful is the enterprise standard for hosted headless content, now part of Salesforce: spaces, content types, a mature API, and a large integration ecosystem. The free plan covers 10 users and 100K API calls a month, enough for a small site.

The step after free is steep. Lite is $300 per month for 20 users, workflows are not available on the Starter space that Free and Lite include, and the product is built for content operations teams, not for a client who changes a phone number twice a year.

**Pros**
- Mature platform with a deep integration ecosystem
- Free plan with 10 users and scheduled publishing
- Enterprise-grade governance when you need it

**Cons**
- Content leaves your repo
- The next tier is $300/mo, and an extra space $850/mo
- Workflows unavailable below Enterprise spaces

**Pricing:** Free (10 users, 100K API calls/mo); Lite $300/mo (20 users); Enterprise custom.

### Storyblok

*Best hosted headless CMS with visual editing and a workflow on every tier.* <https://www.storyblok.com>

Tags: Headless platform, Hosted, Visual editor, Workflow on free, Per-seat.

Storyblok is a hosted headless CMS with a visual preview editor: editors click on components in a live preview of the site, and content is delivered by API to Next.js, Astro, Nuxt, SvelteKit, and Angular sites. Unusually for this category, its standard workflow (Drafting, Reviewing, Ready to Publish) is on every tier, including the free Starter.

It is priced per seat beyond the first: the free tier is one seat, Growth is $99 a month for five with $15 per extra seat, and scheduling, releases, and custom workflows sit on higher tiers. The content lives in Storyblok's database, so the migration is real.

**Pros**
- Visual editor with a live preview of your site
- Three-stage review workflow on every tier, free included
- Free Starter tier with generous API limits

**Cons**
- Content leaves your repo
- One seat on Free; $15 per extra seat
- Releases and custom workflows on Premium

**Pricing:** Starter free (1 seat); Growth $99/mo (5 seats, $15 per extra); Growth Plus $349/mo (15 seats); Premium and Elite custom. 45-day Growth Plus trial.

### DatoCMS

*Best structured headless CMS for European teams.* <https://www.datocms.com>

Tags: Headless platform, Hosted, EUR pricing, GraphQL, Scheduling.

DatoCMS is a hosted headless CMS with a GraphQL delivery API, an image and video pipeline, and structured text, well documented for Next.js, Nuxt, SvelteKit, and Astro. Priced in euros, with content versioning, rollbacks, custom roles, and scheduled publishing on the Professional plan.

The free plan is small, 300 records and a couple of editors, and Professional is €149 a month billed annually with 10 collaborators and €9 for each extra. Approval workflows, the custom state machine between draft and published, are Enterprise-only.

**Pros**
- Scheduled publishing, versioning, and custom roles on Professional
- Strong media pipeline and structured text
- Well-documented framework integrations

**Cons**
- Content leaves your repo
- Free plan capped at 300 records
- Approval workflows are Enterprise-only

**Pricing:** Free (300 records); Professional €149/mo billed annually or €199 monthly (10 collaborators, €9 per extra); Enterprise custom.

### Prismic

*Best cheap hosted headless CMS with releases on every tier.* <https://prismic.io>

Tags: Headless platform, Hosted, Cheap entry, Releases on free, Slices.

Prismic is a hosted headless CMS built around slices, reusable page sections, with a page builder for editors and Slice Machine for developers on Next.js, Nuxt, and SvelteKit. Releases, scheduling, previews, and unlimited documents are included on every tier, the free one too.

Users are what you pay for: one on Free, three on the $10 per month Starter, seven on Small at $25, and the custom roles that gate publishing arrive on Medium at $150. Prices are per repository, paid annually, and the content lives in Prismic.

**Pros**
- Releases and scheduled publishing on every tier
- Cheap entry: $10/mo for 3 users
- Slice-based page building editors understand

**Cons**
- Content leaves your repo
- Custom roles only from the $150/mo Medium tier
- Per-repository pricing, paid annually

**Pricing:** Free (1 user); Starter $10/mo (3 users); Small $25/mo (7 users); Medium $150/mo (25 users, custom roles); Platinum $675/mo; per repository, paid annually.

### Hygraph

*Best GraphQL-native headless CMS.* <https://hygraph.com>

Tags: Headless platform, Hosted, GraphQL, Free tier, Federation.

Hygraph is a GraphQL-native headless CMS with content federation, meant for teams that stitch several content sources into one API. It documents integrations for more than forty frameworks and runtimes, from Next.js and Astro to Hugo and Eleventy.

The free Hobby plan gives three seats and 1,000 entries; Growth starts at $199 a month for 10 seats and 10,000 entries. Draft and published stages come standard, but scheduled publishing and custom workflows are Enterprise-only.

**Pros**
- GraphQL-first with content federation across sources
- Free Hobby plan with 3 seats
- Integrations documented for dozens of frameworks

**Cons**
- Content leaves your repo
- Growth is $199/mo for 10,000 entries
- Scheduling and workflows are Enterprise-only

**Pricing:** Hobby free (3 seats, 1,000 entries); Growth from $199/mo (10 seats, 10,000 entries); Enterprise custom. 30-day Enterprise trial.

## When updating in place is enough

Not every Netlify CMS site needs a new tool. Renaming the package to Decap and wiring a small OAuth app is a fine answer when:

- The site's editors are technical and already comfortable in the admin.
- Someone on the team is happy to own the OAuth app and config going forward.
- The site edits so rarely that any migration would cost more than it saves.

## FAQ

### Is Netlify CMS the same as Decap CMS?

Yes. Netlify CMS was renamed Decap CMS in early 2023 when Netlify transferred the project to the community. The decap-cms package is the continuation; the old netlify-cms package is not where development happens.

### Does Netlify Identity still work for my CMS login?

Identity does: Netlify reversed that deprecation in February 2026. What is deprecated is Git Gateway, the piece that let the panel write to your repository. It keeps working where it is already enabled, but new configurations are not recommended and bugs are no longer fixed. Sites leaning on it should plan a migration: either wire your own OAuth app or auth bridge to keep a Decap-family panel, or move to a tool with sign-in built in.

### Can I keep my config.yml?

With Decap CMS, yes, unchanged. Sveltia CMS is designed to work with an existing Netlify/Decap configuration too. Pages CMS and Sitepins use their own config formats, Tina and Keystatic use code-defined schemas, and CMS Brew uses no config at all: it maps the repository automatically.

### Do I have to migrate my content off Netlify CMS?

For every Git-based option here, no: your content is files in your repository, and Decap, Sveltia, Pages CMS, Sitepins, CloudCannon, Tina, Keystatic, GitCMS, Outstatic, and CMS Brew all work from those files. Content migration only enters the picture if you move to a headless platform such as Sanity, Contentful, Storyblok, or Payload.

### What is the fastest way off the deprecated Netlify CMS setup?

If you want to keep the panel: switch the package to Decap or Sveltia and wire an OAuth app, an afternoon of work for a technical team. If you want the problem gone rather than patched: a hosted tool with built-in sign-in, like Pages CMS or Sitepins (free, config-based) or CMS Brew (paid, automatic mapping and review included).

### Which Netlify CMS alternative is best for a client-owned site?

CMS Brew is built specifically for that case: the client edits by chat with no admin UI to learn, sign-in is Google or an emailed code, and anything risky waits for the developer's approval instead of publishing straight to production.

---

- [Home](https://cmsbrew.com/)
- [Features](https://cmsbrew.com/features)
- [Full product details](https://cmsbrew.com/llms-full.txt)
