GitCMS is a hosted editor that sits on top of a website repository. Editors change Markdown, MDX or data files in a visual interface, and each change is saved to your Git repository. It is a young commercial product from Wyom Labs with no long track record.
We checked gitcms.dev on 27 October 2026. The product is active, and the site shows a blog post from 10 October. We found no independent reviews, so treat maturity claims as the vendor’s own. Our Git-based CMS comparison lists it next to thirteen other tools.
What does GitCMS actually do?
You connect a site repository, and GitCMS reads the content files and shows them as forms and a visual editor. Teammates and clients are invited by email, so they do not need a GitHub account. Drafts go through a review step before they publish, and AI agents can connect over MCP and propose edits.
The vendor says it works with Astro, Next.js, Nuxt, SvelteKit, Hugo, Eleventy, Jekyll, Gatsby, Docusaurus and Zola. In practice that means any generator that builds from files in Git.
What does it cost?
The vendor currently sells a one-time founding licence per site, with extra editor seats priced separately. Monthly plans are announced as coming later, and the pricing differs between pages of the vendor’s own site. Confirm the figure on gitcms.dev before you commit.
Where are the limits?
- Maturity: The product is new, and the changelog and documentation are thin compared with Tina or Decap.
- Roles: Team roles exist on paid plans, but the vendor does not describe them in detail. Check them against your approval process.
- Previews: It finds the preview deployment your host builds for each draft. The change-request feature is marked beta.
- Licence of the code. The vendor does not state one, so you cannot self-host or audit it the way you can with Decap.
- Lock-in is low. Content stays in your repository, so leaving costs you the editor, not the content.
When would we pick something else?
If you want an open-source editor you host yourself, we would use Decap or Sveltia CMS. For visual editing on a React site, Tina has the longer history. For agencies that hand sites to non-technical clients with their own logins, CloudCannon is the established choice. If content is relational or feeds more than one website, move to a full headless CMS.
What can we do for a team using GitCMS?
- Connect the repository, define which folders editors see, and agree the review flow before launch.
- Set up preview deployments so each draft has a URL the editor can open.
- Validate frontmatter in CI, so an AI agent or a tired editor cannot break a build.
- Build or tidy the site itself, for example on Hugo or in a wider Jamstack setup.
- Move you to Decap, Tina or an API-based CMS if the product does not hold up. Because content is already files, that move is mostly schema mapping.