Netlify CMS alternatives: where to go in 2026.
Netlify CMS became Decap CMS, and the Netlify Identity login path it leaned on is deprecated. If your site still runs it, you owe it a decision. Here are the realistic destinations, compared honestly.
No credit card, cancel anytime.
The short answer
A stranded Netlify CMS site has three exits: stay in the family and fix auth (Decap or Sveltia), keep a free panel but stop hosting it (Pages CMS), or drop the panel model entirely (CloudCannon for visual editing, CMS Brew for client handoffs). Which is right depends on who edits the site and how often.
- Least change: Decap CMS (the rename)
- Modern drop-in: Sveltia CMS
- Best for client sites: CMS Brew
- Best visual editing: CloudCannon
What happened to Netlify CMS
Netlify CMS was renamed Decap CMS in early 2023 when Netlify handed the project to the community. The code lives on, but the batteries it shipped with did not: Netlify deprecated Identity and Git Gateway, the sign-in path that made the classic setup one-click. A site running the old netlify-cms package today is on an unmaintained package name and, most likely, a deprecated login flow.
So the question is not only which CMS to use, but how much of the old setup to keep. The options below run from keep everything and update the packages, to keep the content files but change the tool, to change the model entirely.
The alternatives
7 Netlify CMS alternatives worth considering.
Best for agencies handing finished sites to non-technical clients
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 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
- The deprecated-auth problem disappears entirely, sign-in is built in
- No config.yml and no /admin page to maintain ever again
- Review-before-publish and per-field guards included
- Client edits by chat, nothing to relearn between rare visits
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.
Least change: the same project under its new name
Decap CMS is Netlify CMS: same project, renamed, now community-maintained. 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, though. The rename did not bring a login path with it: with Identity and 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.
Pros
- Minimal migration: rename the package, keep config and content
- Free, open source, still maintained by the community
- Editorial workflow (drafts via pull requests) available on GitHub
Cons
- The auth problem remains: you bring your own OAuth
- Development is slower than in the Netlify years
- Same form admin your rare editors never learned
Pricing Free and open source.
Best modern drop-in for the same config
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, and mobile support.
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 Netlify Identity is not part of the picture. 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
Cons
- You still maintain the content-model config per site
- OAuth-based sign-in is yours to set up
- No review step before publish
Pricing Free and open source (MIT).
Best free option with hosting and sign-in handled
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.
Best visual editing upgrade
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.
Best for React sites wanting in-place editing
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 sits in paid TinaCloud tiers.
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 is a paid feature
Pricing Open-source core; TinaCloud has a free starter tier, editorial workflow on paid plans.
Best for technical editors who want clean files
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 (with its own per-user pricing beyond the free tier) 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; Keystatic Cloud free for 3 users, then paid.
At a glance
Every Netlify CMS alternative, side by side.
| 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 | No | Free (MIT) |
| Pages CMS | Hosted or self-hosted panel | New config file, email invites | No | Free (MIT) |
| CloudCannon | Hosted, visual editing | Editable regions per site | On Team tier | From $55/mo + $10/user |
| TinaCMS | In-site visual editor | Schema rewrite | Paid TinaCloud tier | OSS core; cloud tiers |
| Keystatic | Self-hosted admin UI | Schema rewrite | No | Free; Cloud for teams |
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
What people ask about Netlify CMS alternatives.
Stop being the person who updates the phone number.
Give your client the keys to the content. Keep the keys to the code.
Prefer to talk first? Book a 30-minute call