Git-based CMS: Markdown in your repo, an editor on top
A Git-based CMS gives non-developers a form over the Markdown and JSON in your repository and saves each edit as a commit. There is no content database to host. The setup work is sign-in: 5 of the 8 here need nothing from you for editors to log in, and the rest need an OAuth service or a backend you run.
Reviewed by Eugene SuslovFacts read November 2026No affiliate links

- 8
- Git-based editors compared
- 5
- need nothing hosted for editor sign-in
- 4
- work with GitLab, not only GitHub
- 7
- are open source
How a Git-based CMS works
Your site generator already reads content from files: Markdown posts, JSON data, YAML settings. A git cms puts an editing interface on those files. An editor fills a form, the tool commits the change to your repository, and your host rebuilds the site. The repository stays the single source of truth, with full history and nothing to export.
That is why these tools are often called a jamstack cms, and why they remain a common static site cms for docs, blogs and marketing sites. They differ in three things that decide the setup: which Git hosts they talk to, where the editor runs, and what must be hosted so someone without a Git account can sign in.
Every Git-based CMS we review
8 tools that store content as files in your repository. Each card links to a full review with pricing, setup and limits.
Showing 8 platforms
Best git-backed visual editing
Visual editing on top of Markdown and JSON in your own Git repository, Apache-2.0 licensed. The content stays in your repo whether or not you keep paying.
- Content lives as Markdown or JSON in your Git repo
- Visual editing against your live front end
- Apache-2.0, with a self-hostable backend
- Next.js
- React
- Astro
- TypeScript / Node.js

Free git-based editing
A free, MIT-licensed admin panel that commits Markdown to your Git repository. Abandoned as Netlify CMS, handed to new maintainers, and shipping releases again.
- Content committed as Markdown to your own Git repo
- MIT licensed; paid hosted backend (Decap Turbo) optional
- A single-page admin app you host yourself
- React
- Next.js
- Vue / Nuxt
- JavaScript / React

Best for portfolios of static sites
A git-based visual editor and static host billed per organisation, not per site. In-place editing needs CloudCannon to run the build, and there is no content delivery API.
- Visual editing on the built page via Editable Regions
- Hosting, builds, forms and CDN on every plan
- Unlimited sites; users are the meter at $10/mo
- Astro
- Svelte / SvelteKit
- React
- Hosted SaaS over Git

Open source, self-hosted
A TypeScript-first CMS for Next.js that keeps content in your repository as JSON and generates fully typed queries. Publishing from a live site needs a backend: Alinea Cloud, free in beta, or your own.
- Content stored in your git repository
- Fully typed schema and queries in TypeScript
- Production backend: Alinea Cloud or self-hosted on your database
- Next.js
- React
- TypeScript

Open source, self-hosted
A free, MIT-licensed Git-based CMS written as a successor to Decap. Most Decap configs switch with one script tag, but Bitbucket, Azure DevOps and Git Gateway sites cannot. Still a pre-1.0 beta with one maintainer.
- Reads Decap and Netlify CMS config: swap one script tag
- GitHub, GitLab and Gitea or Forgejo backends only
- First-class i18n with built-in AI translation on your own key
- Astro
- Next.js
- Svelte / SvelteKit
- JavaScript / Svelte, runs entirely in the browser

Open source, self-hosted
An open-source CMS for GitHub-hosted static sites that needs no install at all: authorise the hosted app against your repo and start editing.
- No install: authorise the hosted app against a GitHub repo
- Content committed directly to your repository
- Configured with a single YAML file
- Astro
- Next.js
- React
- TypeScript / Next.js

Open source, self-hosted
A CMS that lives inside VS Code. Content stays as Markdown in your repo and the editing interface is an editor panel, which suits developer-authored sites.
- Runs as a VS Code extension, no separate app
- Markdown and front matter in your own repo
- Content dashboard, media library and SEO checks
- Astro
- Next.js
- React
- TypeScript / VS Code

Open source, self-hosted
A git-based CMS with MIT-licensed packages, an AGPL-3.0 Studio, an official MCP server and cloud tiers starting at $9 a month. Content stays in your repository as JSON and Markdown.
- Git-based: content as JSON and Markdown in your repo
- MIT-licensed CLI, SDK and MCP packages; AGPL-3.0 Studio
- Official MCP server for AI clients
- Next.js
- React
- Vue / Nuxt
- TypeScript / Node.js
Check hosts, sign-in and workflow
Tick what your team needs; each tool shows the detail where it has it.
What does your repository and your team need?
5of 8 have it
| Platform | GitHub8 | GitLab4 | Bitbucket3 | Nothing to host for sign-in5 | Drafts as pull requests5 | Visual editing2 | Open source7 |
|---|---|---|---|---|---|---|---|
| TinaCMS | |||||||
| CloudCannon | |||||||
| Pages CMS | |||||||
| Front Matter CMS | |||||||
| Contentrain | |||||||
| Decap CMS | |||||||
| Alinea | |||||||
| Sveltia CMS |
Read from each tool's own docs, pricing page and repository, 2026-11-20.
Sign-in is the real setup work
The editor is easy to install. Letting a non-developer log in is not.
| Tool | Git hosts | What you run for sign-in |
|---|---|---|
| TinaCMS | GitHub | Nothing on TinaCloud; self-hosted needs a backend function, a database and an auth provider |
| Decap CMS | GitHubGitLabBitbucketGiteaForgejoAzure DevOps | An OAuth service on GitHub and Bitbucket (or Netlify, or paid Decap Turbo); nothing on GitLab, Gitea and Forgejo |
| CloudCannon | GitHubGitLabBitbucket | Nothing: a hosted app, with guest access for clients |
| Alinea | GitHub | Alinea Cloud (free in beta), or a database and an auth method behind your Next.js app |
| Sveltia CMS | GitHubGitLabGiteaForgejo | An OAuth client on GitHub (a Cloudflare Worker, for example); nothing on GitLab, Gitea and Forgejo |
| Pages CMS | GitHub | Nothing on the hosted app (install its GitHub App); self-hosted needs PostgreSQL and your own GitHub App |
| Front Matter CMS | Any Git remote | Nothing: editors work on a local clone in VS Code |
| Contentrain | GitHub | Nothing on the managed Studio; self-hosted needs PostgreSQL or Supabase and your own GitHub App |
From each tool's authentication and backend docs, 2026-11-20.
GitHub is the common case and the awkward one: its sign-in needs a server-side step, so a browser-only editor needs a small OAuth service somewhere. On GitLab, Gitea and Forgejo, Decap and Sveltia use a browser sign-in flow (PKCE) that needs no server. 4 tools work with GitHub alone, TinaCMS, Alinea, Pages CMS and Contentrain, so if your code lives elsewhere, a github cms is not an option.
A CMS for static sites, by generator
Any of these can edit Markdown; a documented starter saves the configuration.
| Tool | Generators with a vendor guide or starter | Editor runs | Formats |
|---|---|---|---|
| TinaCMS | Next.jsAstroHugoJekyllEleventyGatsbySvelteKit | A browser app served from your site | MarkdownMDXJSONYAMLTOML |
| Decap CMS | HugoJekyllEleventyNext.jsGatsbyNuxtDocusaurusVitePressSvelteKit | A browser app served from your site | MarkdownYAMLJSONTOML |
| CloudCannon | HugoJekyllEleventyAstroNext.jsGatsbyDocusaurusNuxtSvelteKitMkDocs | A hosted web app | MarkdownMDXHTMLYAMLTOMLJSONCSV |
| Alinea | Next.js | Inside your Next.js app | JSON |
| Sveltia CMS | HugoJekyllEleventyAstroNext.jsNuxtSvelteKitDocusaurusVitePressMkDocsZola | A browser app served from your site | MarkdownYAMLJSONTOML |
| Pages CMS | None named; works with any | A hosted web app, or self-hosted | MarkdownYAMLJSONTOML |
| Front Matter CMS | AstroHugoNext.js | A VS Code extension | MarkdownMDX |
| Contentrain | AstroNext.jsNuxtSvelteKitVitePress | A hosted web app, or self-hosted Studio | JSONMarkdown |
Only generators with a page or official starter in the vendor's docs, 2026-11-20.
As a jekyll cms, TinaCMS, Decap CMS, CloudCannon and Sveltia CMS document a setup; as an eleventy cms, TinaCMS, Decap CMS, CloudCannon and Sveltia CMS. Pages CMS names no generator and edit whatever files you point it at, which works for any static site cms setup.
Drafts as pull requests
Review happens in Git, where developers already review code.
In an editorial workflow, saving a draft creates a branch and opens a pull request; publishing merges it. TinaCMS, Decap CMS, CloudCannon, Sveltia CMS and Contentrain document one. The upside is that every change gets a reviewable diff and a preview build on hosts that build pull requests. The catch is that the reviewer works in the Git host or the tool's own queue, so a non-technical approver needs an account there too.
Without a workflow, every save is a commit to the main branch and goes live on the next build. For a solo blogger that is the point. For a team, it means anyone with access can publish, and Git history is the only audit trail.
Who maintains each tool
Most of these are small projects, which matters more than any feature.
| Tool | License | GitHub stars | Maintained by |
|---|---|---|---|
| TinaCMS | Apache-2.0 | 13,883 | SSW, an Australian consultancy |
| Decap CMS | MIT | 19,497 | PM d.o.o., a software company of about 30 |
| CloudCannon | Proprietary | Closed source | CloudCannon, the company |
| Alinea | MIT | 855 | The alineacms organization |
| Sveltia CMS | MIT | 3,103 | Kohei Yoshino, a single maintainer |
| Pages CMS | MIT | 4,245 | Ronan Berder, sponsor-funded |
| Front Matter CMS | MIT | 2,550 | Elio Struyf, a single maintainer |
| Contentrain | MIT packages, AGPL-3.0 Studio | 7 | Contentrain, the company |
Stars from the GitHub API, 2026-11-20; maintainers from each project's own site or repository.
Sveltia CMS and Front Matter CMS depend on one person. That is not a reason to avoid a tool, since your content stays as plain files in your repository whatever happens to the editor. It is a reason to keep your content model simple enough to move.
Where Git stops being a good database
Each tool's docs name the limit that bites first.
- TinaCMS: No Git LFS, and reference fields on large collections can time out.
- Decap CMS: Fetches one file per request, so large collections and search strain the Git host's rate limits.
- CloudCannon: Seats are the meter: 3 users on Standard, then $10 a month each.
- Alinea: Next.js only, on a Node.js 24 server runtime: no Edge runtime and no static export.
- Sveltia CMS: Bound by the Git host's API; the project steers sites with thousands of entries elsewhere.
- Pages CMS: Email collaborators commit under the app's identity, not their own name, by default.
- Front Matter CMS: Every editor needs VS Code and a local clone of the repository.
- Contentrain: 80 unmerged review branches block new writes until some are merged.
The pattern is the same everywhere. A markdown cms reads and writes through the Git host's API, so thousands of entries, frequent edits by many people and large media files all strain it. Relations between entries are also weak, since a file can only point at another file by name. Past that point, a database-backed headless CMS is the better tool.
Media is the other slow leak. Every image an editor uploads is committed to the repository by default, and the repository never forgets it. Decap, Sveltia, TinaCMS and CloudCannon can send uploads to an external store such as Cloudinary or S3 instead, and Contentrain keeps media on its own CDN. Set that up before the first hundred images, not after.
What it costs
The software is often free; the hosted backend is what you pay for.
| Tool | Free | Cheapest paid |
|---|---|---|
| TinaCMS | Free for 2 users | Team $24/mo per project, billed yearly |
| Decap CMS | Free, MIT; Turbo free for 1 site and 1 seat | Decap Turbo Pro €19/mo (EUR only) |
| CloudCannon | No free plan; 21-day trial | Standard $49/mo billed yearly |
| Alinea | Free, MIT; Alinea Cloud free while in beta | No paid tier |
| Sveltia CMS | Free, MIT, no paid tier | No paid tier |
| Pages CMS | Free, MIT; the hosted app is free | No paid tier |
| Front Matter CMS | Free, MIT, no paid tier | No paid tier |
| Contentrain | MIT packages free; no free Studio plan | Studio Starter $9/mo |
From each pricing page, US view, 2026-11-20. Decap Turbo is sold in euros only.
4 of the 8 sell something. What the money buys is the part you would otherwise host: sign-in, a backend for search and media, seats and support. If you can run a small OAuth service, the open source tools cost nothing but the hours.
How to choose
Four checks, in the order they usually rule tools out.
- 01Start from your Git hostSeveral tools are GitHub-only. The checklist shows which work with GitLab or Bitbucket.
- 02Decide who hosts sign-inA vendor app, an OAuth service you run, or VS Code on each editor's machine.
- 03Check your generatorA documented starter saves the configuration, though any tool can edit Markdown.
- 04Count the entriesPast a few thousand, or with many daily editors, a database-backed CMS fits better.
For a docs site or a blog edited by a few people, a free tool on a GitHub repository is usually enough. An agency handing a site to a client may prefer a hosted editor, since nobody at the client will maintain an OAuth service; the cms for static sites is then a seat price, not a setup project.
Where to go from here
- Headless CMS for Next.js46 platforms, 8 of them also on this page.
- Headless CMS for Astro36 platforms, 7 of them also on this page.
- Open source headless CMS26 platforms, 7 of them also on this page.
- Content engineeringWhat a headless CMS makes possible once content is structured.
- Content automationPipelines that publish into a CMS without copy and paste.
Git-based CMS, answered
Which Git-based CMS needs no server for editors to sign in?
TinaCMS, CloudCannon, Pages CMS, Front Matter CMS and Contentrain. Each either hosts the sign-in for you or runs where no sign-in is needed. The open source browser editors need an OAuth service on GitHub.What is the difference between a git cms and a headless CMS?
A headless CMS stores content in its own database and serves it through an API. A Git-based tool stores content as files in your repository and serves nothing: your site generator reads the files at build time.Is Decap CMS still free now that Decap Turbo exists?
Yes. The CMS is MIT-licensed with no paid tier. Decap Turbo is an optional hosted backend from the same maintainer that handles editor sign-in, with a free plan and a paid Pro plan.Which Git-based CMS works with GitLab?
Decap CMS, CloudCannon, Sveltia CMS and Front Matter CMS. The others here work with GitHub only, so check your Git host before anything else.Is Pages CMS free?
Yes. Pages CMS is MIT-licensed and its hosted app is free: you install its GitHub App on your repository and invite editors by email. You can also self-host it, which needs PostgreSQL and your own GitHub App.Does TinaCMS store content in Git?
Yes. TinaCMS commits Markdown, MDX or JSON to your GitHub repository. TinaCloud handles editor sign-in and indexes the content for its GraphQL layer, but the files stay in your repository, and the backend can be self-hosted instead.Which github cms tools document a Jekyll setup?
TinaCMS, Decap CMS, CloudCannon and Sveltia CMS work with GitHub and document Jekyll, which is what GitHub Pages builds by default. Any of them can serve as a jekyll cms for a Pages site.Can a Git-based content editor handle thousands of entries?
It can store them, but it slows down. Every read and write goes through the Git host's API; Decap's docs say its search loads every entry, and Sveltia's steer projects with thousands of entries to a database-backed CMS.
Picking the provider is the easy half.
busyless runs content and search as a system: we choose the data sources and tools, build the pipelines on top, and measure what they feed. If that is the part you are missing, talk to us.
Ask an assistant about this page
An independent comparison. No provider pays to be listed or to rank higher, outbound links carry nofollow, and we earn nothing if you sign up. Prices and terms were read from each vendor's own pages in November 2026 and change without notice.
Missing, or out of date?
Every entry here was read off the company's own website and dated, so some of it will have moved since. Corrections are free and so is being added. There is no fee, no sponsored position, and nothing that money moves up this page.