Product features

Connect to GitHub, GitLab, Gitea, Bitbucket, Azure, Git Gateway (Netlify), proxy, and test backends.

Use backend-specific auth flows such as OAuth, implicit, and PKCE login.

Find entries using titles, slugs, nested fields, and configured summary fields.

Localize the UI and edit content in multiple locales with multiple options for the i18n content structure.

Surface backend-generated preview URLs for entries before they are published.

Generate unique slugs and support configurable file paths for entries.

Folder collections: Organize repeatable content in directory-based collections. File collections: model singleton pages and other fixed content files as editable entries.

Write structured rich text content with CMS-friendly editing controls. Switch between rich text and markdown editing modes.

Use built-in inputs for common content types like strings, text, numbers, booleans, dates, selects, and colors. Capture specialized data with code, map, and other structured widget controls. Attach images and files directly to entry fields and content blocks.

Build complex content with nested objects and repeatable list fields.

You can set up instant previews so editors can see in real-time how their changes will look on the frontend. You can write them in React and CSS.

Invite editors by email and they sign in with a Turbo account — no GitHub or GitLab account, OAuth app, auth server or Git Gateway to run. Admin URLs can include a wildcard, so the same login works on deploy previews and branch deploys.

Organizations have owners and members. Owners invite people by email, decide which sites each member can open, and remove access in one place. Every site has a built-in Full access role.

Large collections load from Turbo’s database instead of one Git API call per file, so they open quickly and don’t burn your Git host’s rate limits. Search runs on the server and covers entry bodies, not just titles.

Saving tells an editor the change was committed, not that the site has rebuilt. Decap watches the deploy and tells them when their change is live — wherever they are in the CMS — with a Deploys page showing what shipped, where it went, and why a build failed. Deploy previews of entries in the editorial workflow are listed too, so you can see whether an entry in review has a working preview. Available for GitHub-hosted sites today; GitLab support is on the roadmap.

Each site gets a key/value store for the settings and credentials it needs, kept out of config.yml and out of your repository. Values marked secret are encrypted at rest and can be replaced, never read back. Today they hold the media library’s storage credentials.

Owners see who saved which entry, in which collection, on which site, and when — along with invitations, new members and new sites — without digging through commit history.

Use the turbo-github or turbo-gitlab backend. Connect your Git provider once per organization — the Decap Turbo GitHub App or a GitLab.com authorization — and limit it to selected repositories or projects. Content stays in your repository, and every save is still a commit.

Editors upload and browse assets in your own bucket: AWS S3, Cloudflare R2, Bunny Storage, or any other S3-compatible storage. The CMS goes through Turbo, which holds the storage keys server-side, so they never reach the browser.