Decap CMS

Decap CMS is an open-source editor for publishing content through Git-backed static sites. It is best suited to publishers and developers who want contributors to edit in a browser while keeping content and its history in a repository. Choose it for that control and workflow flexibility; look elsewhere if you need hosting, authentication, and a backend supplied as part of a managed service.

Overview

The editor gives non-technical contributors structured fields, rich text, and live preview, with a path from draft through review to publication. Meanwhile, content remains in the user's repository, where teams can use version history, branches, and deployment checks. This division works well when developers can shape and maintain the publishing setup, but puts infrastructure responsibility on the team rather than the product.

Decap CMS targets Git-backed static and Jamstack sites, including Hugo, Next.js, Gatsby, and Jekyll workflows. Collections, nested structures, relation fields, and slug rules let developers fit the content model to a site; custom widgets, editor components, and plugins allow further extension. That flexibility is useful for tailored publishing, though it makes the product a less direct fit for organizations seeking a turnkey CMS.

Key features

Editorial workflow in Git

Draft, review, and publish statuses provide a straightforward editorial sequence. Repository history and branch workflows preserve a familiar development process, and deployment checks connect content changes to delivery. Teams that already work in Git gain a coherent publishing path; teams without that practice may find the repository-centered approach more demanding than a hosted editor.

Backends and media

Supported backends include GitHub, GitLab, Gitea, Bitbucket, Azure, Git Gateway, proxy, and test backends. The range gives developers options for connecting the editor to their Git environment, but they still need to supply authentication and a backend. A media library is included, with integrations for Cloudinary, Uploadcare, or custom services. Decap Turbo encrypts site variables marked as secrets at rest.

One limitation matters for teams choosing a Git host: Decap Turbo deploy notifications currently work for GitHub-hosted sites, while GitLab support is on the roadmap. Teams relying on GitLab should account for that constraint before choosing this workflow.

Pricing

The CMS is MIT-licensed, free, and self-hosted. Decap Turbo adds paid plans, with a 14-day trial and monthly billing for its paid offering.

The free Turbo tier is suitable for a single-site, single-seat setup, but its seat and site caps make it restrictive for a growing team. Pro raises the allowance to five seats and adds variables, secrets, and S3-compatible media; the per-site and per-seat charges apply beyond those included limits. Enterprise is the better fit for organizations needing SSO/SAML, broader role controls, and dedicated support, though its price is custom. The self-hosted CMS remains free, but users must still provide their own authentication and backend.

Platforms

Decap CMS is a self-hosted web application. Its Git-based design supports static and Jamstack publishing workflows rather than removing the need to operate the surrounding site and services.

Who it's for

Publishers, editors, and developers who want browser-based contribution without moving content out of their repository are the clearest audience. It is particularly suitable for teams already building with Git-backed static sites and able to manage the backend and authentication. Teams looking for an all-in-one hosted CMS with infrastructure handled for them should choose a different approach.

Pros and cons

• Repository ownership: Content and version history stay in Git, which suits teams that want repository-based control over publishing.
• Contributor-facing editor: Structured fields, rich text, live preview, and editorial statuses give non-technical contributors a defined way to prepare and review content.
• Adaptable setup: Multiple backends, configurable content structures, and extension points suit varied Git-backed static-site workflows.
• Self-hosting burden: Users must bring authentication and a backend, so teams seeking managed infrastructure will need another product.
• GitHub-only deploy notifications: The current limitation leaves GitLab-hosted teams without that notification support in Decap Turbo.
• Turbo plan limits: Free covers one site and one seat; Pro includes five seats and one site, with extra usage charged per seat and site.

Alternatives

• Quiqr is a free, open-source alternative for readers who want a free option across Linux, macOS, Windows, self-hosted, or web platforms.
• deco CMS may suit readers looking for an open-source, self-hostable CMS with a free core.
• Mattrbld is another free option, with web, mobile, and self-hosted platforms.
• Dhub is worth considering for a web-based GitHub workflow; its free Hobby plan is limited to one user, personal GitHub accounts, public repositories, and editing the default branch.
• HugoCMS may be a better fit for readers seeking a free, open-source option per domain with multilingual support and unlimited updates.
• Keystatic is an alternative for teams looking for a free plan that supports up to three users per team.
• Kiln offers a free, open-source self-hosted option, but its users run the worker and GitHub App and provide the site host.
• Netlify is an alternative for readers comparing a broader web platform with a free tier that includes 300 credits per month, one concurrent build, and one team owner.

Readers comparing categories can also browse Git-Based CMS and Content Management Systems.

Verdict

Decap CMS is a strong choice for publishers and development teams that want an editorial interface while keeping content, history, and workflow in Git. Its core is free and extensible, and Decap Turbo adds defined team plans. The decisive trade-off is operational: you supply the backend and authentication, and GitLab-hosted teams currently miss Turbo deploy notifications. Choose it when repository ownership matters more than a managed setup; look elsewhere when you want the CMS to handle that infrastructure.