# The best CMSs for Astro 2026, tried and verified. — ZeroCMS

[Resources](/resources) [Comparisons](/resources)

# The best CMSs for Astro 2026, tried and verified.

Choosing a CMS for your Astro project means going through dozens of products and reading their docs. We did that, wrote down what we found, and put it all in one place.

![The best CMSs for Astro 2026, tried and verified.](/_astro/astro-cms-comparison-cover.BurdOZTv_Z4deG7.webp)

We're committed to keeping this comparison fresh and accurate The data on this page is automatically gathered and verified from each product's official documentation, website, and public repositories.

While we use AI for the bulk of the work, we still manually verify the data to ensure accuracy and completeness, as well as test many of the products ourselves. Each data point also mentions its source, and includes links to the relevant documentation that the answer is drawn from.

The data is refreshed, and new products are added roughly every few months. If you find something missing or inaccurate, please report your findings to [support@zerocms.io](mailto:support@zerocms.io) so they can be fixed.

## Products

12 products, 8 of them we ran ourselves. Last verified 1 Sep – 17 Sep 2026.

Each section below is one subject: a table of the answers, then every aspect in turn with its answers grouped, each naming the products that gave it, our note on each, how the answer was established and when it was checked. “Not checked” and “Not tested” mean we did not settle it, not that the product lacks it. On a ranked aspect the answers are listed best first and the best answer is in bold in the table.

| Product | Website | How we checked it | Reviewed |
| --- | --- | --- | --- |
| ZeroCMS | https://www.zerocms.io | We ran it | 1 Sep 2026 |
| CloudCannon | https://cloudcannon.com | We ran it | 4 Sep 2026 |
| Decap CMS | https://decapcms.org | We ran it | 3 Sep 2026 |
| EmDash | https://emdashcms.com | We ran it | 3 Sep 2026 |
| Keystatic | https://keystatic.com | We ran it | 17 Sep 2026 |
| Pages CMS | https://pagescms.org | We ran it | 3 Sep 2026 |
| Payload CMS | https://payloadcms.com | We ran it | 3 Sep 2026 |
| Sanity | https://www.sanity.io | Read, not run | 3 Sep 2026 |
| Storyblok | https://www.storyblok.com | Read, not run | 3 Sep 2026 |
| Strapi | https://strapi.io | Read, not run | 3 Sep 2026 |
| Sveltia CMS | https://sveltiacms.app/en/ | Read, not run | 3 Sep 2026 |
| TinaCMS | https://tina.io | We ran it | 3 Sep 2026 |

### Screenshots

- ZeroCMS: ![The ZeroCMS visual editor with its block menu open, beside a live preview of the Astro site being edited](/_astro/editor-live-preview.Bqtg-cYR_2sx6Wh.webp) ![The ZeroCMS agent panel listing the edits it made after being asked to proofread a page, beside the live preview](/_astro/agent-proofread.BDDMbAbZ_I87W9.webp) ![The ZeroCMS dashboard with an AI prompt, recently edited entries and the site's collections](/_astro/dashboard.BjU_JbWA_Z18IVAs.webp)
- CloudCannon: ![CloudCannon visual editor: the homepage's title, description and page-section list in a sidebar beside a live render of the landing page.](/_astro/img1-b215f10a.CSpij0oL_Z1H4Tyq.webp) ![CloudCannon site dashboard: sync and Astro build both completed, usage counters, a getting-started guide and the repository README.](/_astro/img3-aae767b2.Be6wx4ni_1gvLbB.webp) ![CloudCannon editing a guide: frontmatter fields (dropdowns, date, author picker, toggle) beside the rendered article with a Callout component block inline.](/_astro/guide-editor-callout.BglZoUES_ZxnX7y.webp) ![CloudCannon Save changes dialog listing two edited files, a guide and site settings, each selectable, with Discard selected and Save selected buttons.](/_astro/save-changes-dialog.CuWssioY_Z1RxIzk.webp)
- Decap CMS: ![Decap CMS editor with a Pages entry open: title and description fields, and an MDX body showing component imports and tags as raw text.](/_astro/1.tEXNAkUu_GaY6.webp)
- EmDash: ![EmDash admin editing a guide: rich-text toolbar, prose with Callout and Stat grid blocks, and a publish panel showing draft changes.](/_astro/2.Nj35wnze_1x8hwN.webp) ![EmDash admin editing the home page as schema form fields (hero badge, title, body, button label) beside a publish panel with draft changes.](/_astro/home-page-fields.C7e_Y-b4_ZD9FMA.webp) ![EmDash admin dashboard with quick-create buttons, draft, media and user counts, content per collection and recent activity.](/_astro/dashboard.CzwWU1LG_1XQet1.webp)
- Keystatic: ![Keystatic admin editing the Home page singleton: sidebar with Settings, Pages, Guides and Team, and form fields for the hero badge, title, body and primary CTA.](/_astro/1.Cj-hE1Ad_Z1jzNIe.webp)
- Pages CMS: ![Pages CMS editing a Home page entry: hero fields for badge, title, body and a primary button's label and href, each marked Required.](/_astro/editor-fields.DNUZQ2fA_Z2qgzXC.webp) ![Pages CMS editing an MDX page: title and description fields above a code editor with hand-written component imports and JSX.](/_astro/editor-mdx.7vJbBR70_bOokO.webp)
- Payload CMS: ![Payload admin editing a guide: title, tagline and rich-text content with a Callout block on the left, live preview of the rendered page on the right.](/_astro/shot-1.CsmxA4Pc_qgoxw.webp) ![Payload admin editing a team member: name, role, department, group, bio, initials, avatar colour, avatar image, social links and slug fields.](/_astro/shot-2.DHp7fKZ3_Z1cnGx5.webp)
- TinaCMS: ![TinaCMS editing a Guides article: rich-text toolbar and body on the left with collapsed Callout and Stat grid blocks, the rendered article beside it on the right.](/_astro/1.CXYL9vMC_Z1qahz3.webp) ![TinaCMS editing the home page Hero: Badge, Title, Body, button and Rating fields on the left, the rendered hero section on the right.](/_astro/2.UCr9ndif_Z1uFcHl.webp) ![TinaCMS Media Manager dialog: search box, type filter and Upload button above a grid of two JPEG author portraits, maya-chen.jpg and theo-ellison.jpg.](/_astro/4.BsLKRd2C_Z2raPkr.webp)

## By area

Each cell is the share of the area's ranked aspects on which the product has the best answer. An aspect not yet tested counts as not best. The leader of each area is in bold.

| Area | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Astro fit (6 ranked aspects) | **83%** | 67% | 50% | 40% | 33% | 50% | 60% | 40% (1 not tested) | 60% (1 not tested) | 40% (1 not tested) | 50% (1 not tested) | 67% |
| Codebase fit (5 ranked aspects) | **100%** | 20% | 0% | 0% | 0% | 0% | 0% | 20% | 0% (1 not tested) | 0% | 0% | 0% |
| Editing (19 ranked aspects) | 63% | 63% | 50% | 56% (1 not tested) | 62% | 46% | 57% | 64% (2 not tested) | **71% (1 not tested)** | 43% (3 not tested) | 56% (1 not tested) | 56% (2 not tested) |
| Publishing and review (5 ranked aspects) | 80% | 40% | 60% | 80% | 40% (1 not tested) | 20% | **100%** | **100%** | 80% (1 not tested) | 80% | 60% | 20% |
| Governance and access (8 ranked aspects) | 38% | 63% | 50% | 25% | 25% | 38% | **75%** | 50% (1 not tested) | **75%** | **75%** | 13% | 50% |
| Git and the repository (7 ranked aspects) | 57% | **86%** | 57% | Does not apply | 43% (1 not tested) | 57% | Does not apply | Does not apply | Does not apply | Does not apply | 43% | **86%** |
| APIs and extensibility (7 ranked aspects) | 0% | 43% | 0% (1 not tested) | 43% | 0% | 0% | 43% | **71%** | 57% | 57% | 0% (3 not tested) | 43% |
| AI capabilities (9 ranked aspects) | **100%** | 0% | 0% | 25% | 0% | 0% | 33% | 67% | 44% (1 not tested) | 22% (1 not tested) | 11% | 0% |

## At a glance

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| What it is | AI-native, Git-based CMS driven by your own Astro schemas. | Git-based CMS with a visual editor over your built site. | Open-source, Git-based CMS that edits a static site through a self-hosted admin panel. | Open-source, Astro-only CMS from Cloudflare that stores content in a database and ships an MCP server for AI agents. | Open-source, Git-based CMS for Astro, Next.js and Remix, configured in your repository and editing Markdown, YAML and JSON files. | Open-source, Git-based CMS that edits a GitHub repository's files through a hosted or self-hosted admin app. | Headless CMS whose admin panel runs inside a Next.js app. | Headless CMS whose open-source, code-configured Studio edits content held in a hosted cloud store and delivered through APIs. | Headless CMS delivered as a SaaS, edited through a block-based visual editor over its content API. | Open-core headless CMS that runs as its own Node application. | Open-source, Git-based CMS that edits repository files through a self-hosted admin panel — a modern Svelte rewrite of Netlify/Decap CMS. | Git-based CMS that serves its editor from your own repository. |
| Product category | Git-based CMS, AI CMS, Astro-specific | Git-based CMS, Page builder | Git-based CMS | Coupled CMS, Astro-specific, AI CMS | Git-based CMS | Git-based CMS | Headless CMS | Headless CMS, AI CMS | Headless CMS | Headless CMS | Git-based CMS, Headless CMS | Git-based CMS, Page builder |
| CMS type | Git-based | Git-based | Git-based | Coupled | Git-based | Git-based | Headless | Headless | Headless | Headless | Git-based | Git-based |
| Deployment | SaaS | SaaS | SaaS, Self-hosted | Self-hosted | Self-hosted, SaaS | SaaS, Self-hosted | SaaS, Self-hosted | SaaS | SaaS | SaaS, Self-hosted | Self-hosted | SaaS, Self-hosted |
| Frameworks supported | Astro | Astro, Next.js, Nuxt, SvelteKit, Hugo, Jekyll, Eleventy, Gatsby, Others | Any | Astro | Astro, Next.js, Remix | Any | Any, Next.js | Astro, Next.js, Nuxt, SvelteKit, Remix, Others | Astro, Next.js, Nuxt, Others | Any | Any | Astro, Next.js, SvelteKit, Hugo, Jekyll, Eleventy, Gatsby, Remix, Others |
| First released | Not checked | 2013 | Not checked | 2026 | 2023 | Not checked | 2021 | 2017 | 2017 | 2015 | 2022 | 2019 |
| Release model | Continuous | Continuous | Versioned | Versioned | Versioned | Versioned | Versioned | Continuous | Continuous | Versioned | Versioned | Versioned |
| Status | **Active** | **Active** | **Active** | **Active** | **Active** | **Active** | **Active** | **Active** | **Active** | **Active** | **Active** | **Active** |

### Fit

How well each product matches the filters you switched on: every answer scored, then averaged. A product stays in the table at 50%. Nothing is graded here: the score is computed in the browser from the filters a reader picks.

### What it is

One neutral sentence, written the same way for every product on this page.

- **AI-native, Git-based CMS driven by your own Astro schemas.**
  - ZeroCMS — By design.
- **Git-based CMS that serves its editor from your own repository.**
  - TinaCMS — By design.
- **Git-based CMS with a visual editor over your built site.**
  - CloudCannon — By design.
- **Headless CMS delivered as a SaaS, edited through a block-based visual editor over its content API.**
  - Storyblok — By design.
- **Headless CMS whose admin panel runs inside a Next.js app.**
  - Payload CMS — By design.
- **Headless CMS whose open-source, code-configured Studio edits content held in a hosted cloud store and delivered through APIs.**
  - Sanity — By design.
- **Open-core headless CMS that runs as its own Node application.**
  - Strapi — By design.
- **Open-source, Astro-only CMS from Cloudflare that stores content in a database and ships an MCP server for AI agents.**
  - EmDash — By design.
- **Open-source, Git-based CMS for Astro, Next.js and Remix, configured in your repository and editing Markdown, YAML and JSON files.**
  - Keystatic — By design.
- **Open-source, Git-based CMS that edits a GitHub repository's files through a hosted or self-hosted admin app.**
  - Pages CMS — By design.
- **Open-source, Git-based CMS that edits a static site through a self-hosted admin panel.**
  - Decap CMS — By design.
- **Open-source, Git-based CMS that edits repository files through a self-hosted admin panel — a modern Svelte rewrite of Netlify/Decap CMS.**
  - Sveltia CMS — By design.

### Product category

Main categories where the product fits.

- **Git-based CMS** — Git-based CMS: Content is stored as files in your git repository and published through git commits.
  - Decap CMS, Keystatic, Pages CMS — By design.
- **Headless CMS** — Headless CMS: Content lives in the vendor's store and is fetched over an API.
  - Payload CMS, Storyblok, Strapi — By design.
- **Git-based CMS, Page builder** — Git-based CMS: Content is stored as files in your git repository and published through git commits. Page builder: Pages are assembled from blocks on a canvas.
  - CloudCannon, TinaCMS — By design.
- **Coupled CMS, Astro-specific, AI CMS** — Coupled CMS: The CMS runs inside your site's own app and reads content from a database you host. Astro-specific: Built specifically for Astro, using core Astro functionality. AI CMS: Builds artificial intelligence directly into its core architecture to automate the creation, organization, optimization, and delivery of content.
  - EmDash — By design.
- **Git-based CMS, AI CMS, Astro-specific** — Git-based CMS: Content is stored as files in your git repository and published through git commits. AI CMS: Builds artificial intelligence directly into its core architecture to automate the creation, organization, optimization, and delivery of content. Astro-specific: Built specifically for Astro, using core Astro functionality.
  - ZeroCMS — By design.
- **Headless CMS, AI CMS** — Headless CMS: Content lives in the vendor's store and is fetched over an API. AI CMS: Builds artificial intelligence directly into its core architecture to automate the creation, organization, optimization, and delivery of content.
  - Sanity — By design.
- **Git-based CMS, Headless CMS** — Git-based CMS: Content is stored as files in your git repository and published through git commits. Headless CMS: Content lives in the vendor's store and is fetched over an API.
  - Sveltia CMS — By design.

### CMS type

Your repository, or the vendor's store.

- **Git-based** — Content is stored as files in your git repository and published through git commits.
  - ZeroCMS, CloudCannon, Decap CMS, Keystatic, Pages CMS, Sveltia CMS, TinaCMS — By design.
- **Headless** — Content lives in the vendor's store and is fetched over an API.
  - Payload CMS, Sanity, Storyblok, Strapi — By design.
- **Coupled** — The CMS runs inside your site's own app and reads content from a database you host.
  - EmDash — By design.

### Deployment

Who runs the product, and how it's deployed. Some products are available as both SaaS and self-hosted.

- **SaaS, Self-hosted** — SaaS: The product runs in the cloud and is maintained and updated by the vendor. Self-hosted: You run the product on your own infrastructure and are responsible for maintenance and updates.
  - Decap CMS, Keystatic, Pages CMS, Payload CMS, Strapi, TinaCMS — By design.
- **SaaS** — SaaS: The product runs in the cloud and is maintained and updated by the vendor.
  - ZeroCMS, CloudCannon, Sanity, Storyblok — By design.
- **Self-hosted** — Self-hosted: You run the product on your own infrastructure and are responsible for maintenance and updates.
  - EmDash, Sveltia CMS — By design.

### Frameworks supported

Frameworks that the product targets and supports.

- **Any** — Any: Supports any framework calling the API.
  - Decap CMS, Pages CMS, Strapi, Sveltia CMS — By design.
- **Astro**
  - ZeroCMS, EmDash — By design.
- **Any, Next.js** — Any: Supports any framework calling the API.
  - Payload CMS — By design.
- **Astro, Next.js, Nuxt, SvelteKit, Hugo, Jekyll, Eleventy, Gatsby, Others**
  - CloudCannon — By design.
- **Astro, Next.js, SvelteKit, Hugo, Jekyll, Eleventy, Gatsby, Remix, Others**
  - TinaCMS — By design.
- **Astro, Next.js, Nuxt, Others**
  - Storyblok — By design.
- **Astro, Next.js, Nuxt, SvelteKit, Remix, Others**
  - Sanity — By design.
- **Astro, Next.js, Remix**
  - Keystatic — By design.

### First released

The year the product was first released.

- **2017**
  - Sanity — Vendor claim, checked 3 Sep 2026. Source: [sanity.io/…/sanity-studio-v3-simplified-yet-powerful-customization](https://www.sanity.io/blog/sanity-studio-v3-simplified-yet-powerful-customization)
  - Storyblok — Vendor claim, checked 3 Sep 2026. Source: [storyblok.com/about](https://www.storyblok.com/about)
- **2013**
  - CloudCannon — Vendor claim, checked 31 Aug 2026. Sources: [cloudcannon.com/blog/powerful-templates](https://cloudcannon.com/blog/powerful-templates/), [cloudcannon.com/ai-info](https://cloudcannon.com/ai-info/)
- **2015**
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [handbook.strapi.io/strapi-story](https://handbook.strapi.io/strapi-story), [raw.githubusercontent.com/…/LICENSE](https://raw.githubusercontent.com/strapi/strapi/develop/LICENSE)
- **2019**
  - TinaCMS — Vendor claim, checked 3 Sep 2026. Source: [tina.io/blog/announcing-tinacms](https://tina.io/blog/announcing-tinacms)
- **2021**
  - Payload CMS — Vendor claim, checked 3 Sep 2026. Source: [payloadcms.com/…/introducing-payload-2021s-node-react-headless-cms-for-javascript-developers](https://payloadcms.com/posts/blog/introducing-payload-2021s-node-react-headless-cms-for-javascript-developers)
- **2022**
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/successor-to-netlify-cms](https://sveltiacms.app/en/docs/successor-to-netlify-cms)
- **2023**
  - Keystatic — Vendor claim, checked 17 Sep 2026. Source: [thinkmill.com.au/blog/keystatic-is-now-in-early-access](https://www.thinkmill.com.au/blog/keystatic-is-now-in-early-access)
- **2026**
  - EmDash — The first public release was announced 28 April 2026. Vendor documentation, checked 3 Sep 2026. Source: [emdashcms.com/blog](https://emdashcms.com/blog)
- **Not checked** — We did not settle this. It is not a claim that the product lacks it.
  - Decap CMS
  - ZeroCMS — No launch date is published. The changelog's earliest entry is 14 December 2025, which is a floor rather than a release date.
  - Pages CMS — No launch date is published. The GitHub repository was created in December 2023 and the project launched in early 2024; the LICENSE now reads a 2025 copyright.

### Release model

How the product is released and updated.

- **Versioned** — Each release is versioned, allowing you to upgrade on your own schedule.
  - Decap CMS, EmDash, Keystatic, Pages CMS, Payload CMS, Strapi, Sveltia CMS, TinaCMS — By design.
- **Continuous** — New versions are released continuously as they are developed.
  - ZeroCMS, CloudCannon, Sanity, Storyblok — By design.

### Status

Is the product actively developed and supported. Ranked; best answer first.

- **Active** — No end-of-life notice has been published.
  - ZeroCMS — Vendor documentation, checked 1 Sep 2026. Sources: [zerocms.io/changelog](https://www.zerocms.io/changelog), [zerocms.io/pricing](https://www.zerocms.io/pricing)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/pricing](https://cloudcannon.com/pricing/), [cloudcannon.com/documentation/changelog](https://cloudcannon.com/documentation/changelog/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/about](https://decapcms.org/about/)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/posts/releases](https://payloadcms.com/posts/releases), [github.com/payloadcms/payload/releases](https://github.com/payloadcms/payload/releases)
  - Sanity — Vendor claim, checked 3 Sep 2026. Sources: [github.com/sanity-io/sanity](https://github.com/sanity-io/sanity), [sanity.io](https://www.sanity.io/)
  - Storyblok — Vendor claim, checked 3 Sep 2026. Source: [storyblok.com/changelog](https://www.storyblok.com/changelog)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/release-notes](https://docs.strapi.io/release-notes)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/whats-new/tinacms](https://tina.io/whats-new/tinacms), [tina.io/pricing](https://tina.io/pricing)
  - EmDash — Self-described as beta preview, under active development. Vendor claim, checked 3 Sep 2026. Source: [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash)
  - Keystatic — Self-described as experimental. Vendor claim, checked 17 Sep 2026. Source: [raw.githubusercontent.com/…/README.md](https://raw.githubusercontent.com/Thinkmill/keystatic/main/README.md)
  - Sveltia CMS — In beta, ahead of a stable 1.0 release. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/start](https://sveltiacms.app/en/docs/start), [sveltiacms.app/en/docs/successor-to-netlify-cms](https://sveltiacms.app/en/docs/successor-to-netlify-cms)

## Astro fit

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Content loading | **Content collections** | **Content collections** | **Content collections** | Content Layer loader | **Content collections** | **Content collections** | REST API fetch | Vendor SDK | Vendor SDK | REST API fetch | **Content collections** | Vendor SDK |
| Collection formats | Markdown, MDX, JSON, YAML | **Markdown, MDX, JSON, YAML, TOML** | Markdown, JSON, YAML, TOML | Does not apply | JSON, YAML, Markdoc, MDX | Markdown, JSON, YAML, TOML | Does not apply | Does not apply | Does not apply | Does not apply | Markdown, JSON, YAML, TOML | **Markdown, MDX, JSON, YAML, TOML** |
| Astro versions | Astro 4–7 | Astro 5–7 | Any version | Astro 6 | Astro 5–7 | Any version | Any version | Astro 2–7 | Astro 3–7 | Any version | Any version | Astro 5–7 |
| Starlight support | **Fully** | **Fully** | Partly | **Fully** | Partly | Partly | **Fully** | Not tested | Not tested | Not tested | Not tested | **Fully** |
| Astro build requirements | **Nothing** | **Nothing** | **Nothing** | Adapter required | Adapter required | **Nothing** | **Nothing** | **Nothing** | **Nothing** | **Nothing** | **Nothing** | Adapter required |
| Output modes | **Static, Server-rendered** | Static | **Static, Server-rendered** | **Static, Server-rendered** | **Static, Server-rendered** | **Static, Server-rendered** | **Static, Server-rendered** | **Static, Server-rendered** | **Static, Server-rendered** | **Static, Server-rendered** | **Static, Server-rendered** | **Static, Server-rendered** |
| Preview output modes | **Static, Server-rendered** | Static | None | Server-rendered | None | None | None | Server-rendered | **Static, Server-rendered** | None | None | **Static, Server-rendered** |

### Content loading

How your Astro site loads content from the product. Ranked; best answer first.

- **Content collections** — Your site uses Astro's built-in content collections and loaders to load content from files.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-the-cloudcannon-configuration-file](https://cloudcannon.com/documentation/developer-articles/what-is-the-cloudcannon-configuration-file/), [cloudcannon.com/…/configure-your-collections](https://cloudcannon.com/documentation/developer-articles/configure-your-collections/), [cloudcannon.com/…/configure-your-commit-messages](https://cloudcannon.com/documentation/developer-articles/configure-your-commit-messages/), [cloudcannon.com/…/using-components](https://cloudcannon.com/documentation/developer-guides/bookshop-astro-guide/using-components/)
  - Decap CMS — Decap commits files to the repository. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/intro](https://decapcms.org/docs/intro/)
  - Keystatic — The Astro guide reads content through astro:content; an in-process Reader API is offered as an alternative but the guide steers away from it. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/installation-astro](https://keystatic.com/docs/installation-astro)
  - Pages CMS — Pages CMS commits files to the repository and ships no content API, SDK or loader; the Astro build reads the files itself. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs](https://pagescms.org/docs/), [pagescms.org](https://pagescms.org/)
  - Sveltia CMS — Sveltia stores static content files and ships no content API, SDK or loader; the Astro build reads the files itself. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/data-output](https://sveltiacms.app/en/docs/data-output), [sveltiacms.app/en/docs/architecture](https://sveltiacms.app/en/docs/architecture)
- **Content Layer loader** — Your site uses a custom content loader that fetches content from the product to Astro's content collections.
  - EmDash — Content reaches Astro through a Live Content Collections loader and is queried with getEmDashCollection / getEmDashEntry. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/coming-from/astro](https://docs.emdashcms.com/coming-from/astro/), [docs.emdashcms.com/concepts/architecture](https://docs.emdashcms.com/concepts/architecture/), [docs.emdashcms.com/guides/querying-content](https://docs.emdashcms.com/guides/querying-content/)
- **Vendor SDK** — Your site calls a vendor SDK from code at build or request time to fetch content.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/…/displaying-content-in-an-astro-front-end](https://www.sanity.io/docs/astro-quickstart/displaying-content-in-an-astro-front-end)
  - Storyblok — An official Astro Content Layer loader is also available, so stories can arrive as a content collection. Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/guides/astro](https://www.storyblok.com/docs/guides/astro), [astro.build/blog/storyblok-loader](https://astro.build/blog/storyblok-loader/)
  - TinaCMS — The content sits in your repository as Markdown, but the site reads it through a generated GraphQL client. Vendor documentation, checked 3 Sep 2026. Sources: [github.com/…/data.ts](https://github.com/tinacms/tina-astro-starter/blob/main/src/lib/data.ts), [tina.io/docs/features/data-fetching](https://tina.io/docs/features/data-fetching), [tina.io/docs](https://tina.io/docs)
- **REST API fetch** — Your site makes plain HTTP calls to a REST or GraphQL endpoint and then wires the responses into Astro content.
  - Payload CMS — Payload's Local API can query the database directly from Node instead, without a network call. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/rest-api/overview](https://payloadcms.com/docs/rest-api/overview), [payloadcms.com/docs/graphql/overview](https://payloadcms.com/docs/graphql/overview), [payloadcms.com/docs/local-api/overview](https://payloadcms.com/docs/local-api/overview)
  - Strapi — Strapi's Astro documentation leads with plain HTTP calls, and offers its own client library or a community content loader as the alternatives. Vendor claim, checked 3 Sep 2026. Source: [community.strapi.io/integrations/astro](https://community.strapi.io/integrations/astro)

### Collection formats

For products that use Astro's content collections, the file formats they support. Ranked; best answer first.

- **Markdown, MDX, JSON, YAML, TOML**
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/collections](https://tina.io/docs/reference/collections), [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro)
  - CloudCannon — Astro page files are editable too, through the source editor directly and the visual editor once Editable Regions are configured. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/documentation/user-glossary](https://cloudcannon.com/documentation/user-glossary/), [cloudcannon.com/…/what-are-rich-text-editors](https://cloudcannon.com/documentation/developer-articles/what-are-rich-text-editors/), [cloudcannon.com/…/what-is-the-source-editor](https://cloudcannon.com/documentation/user-articles/what-is-the-source-editor/), [cloudcannon.com/…/configure-image-editable-regions](https://cloudcannon.com/documentation/developer-articles/configure-image-editable-regions/), [cloudcannon.com/…/configure-source-editable-regions](https://cloudcannon.com/documentation/developer-articles/configure-source-editable-regions/)
- **Markdown, JSON, YAML, TOML**
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/data-output](https://sveltiacms.app/en/docs/data-output)
  - Pages CMS — Markdown is edited as frontmatter; JSON, YAML and TOML data files are edited too. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/content](https://pagescms.org/docs/configuration/content/), [pagescms.org/docs/configuration/fields/rich-text](https://pagescms.org/docs/configuration/fields/rich-text/)
- **JSON, YAML, Markdoc, MDX**
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/format-options](https://keystatic.com/docs/format-options)
- **Markdown, MDX, JSON, YAML**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/visual-content-editor](https://www.zerocms.io/features/visual-content-editor), [zerocms.io/features/zero-integration](https://www.zerocms.io/features/zero-integration)
- **Does not apply**
  - EmDash — The content is not files in your repository, so there are no collection formats to open.
  - Payload CMS — The content is not files in your repository, so there are no collection formats to open.
  - Sanity — The content is not files in your repository, so there are no collection formats to open.
  - Storyblok — The content is not files in your repository, so there are no collection formats to open.
  - Strapi — The content is not files in your repository, so there are no collection formats to open.

### Astro versions

The major Astro versions supported by the product.

- **Any version**
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/rest-api/overview](https://payloadcms.com/docs/rest-api/overview), [payloadcms.com/docs/live-preview/client](https://payloadcms.com/docs/live-preview/client)
  - Decap CMS — Decap has no Astro-specific code and states no Astro version, regardless of the framework. Vendor claim, checked 3 Sep 2026. Source: [decapcms.org/docs/intro](https://decapcms.org/docs/intro/)
  - Pages CMS — Pages CMS has no Astro-specific code and states no Astro version; Astro is named once, in a list of compatible generators. Vendor documentation, checked 3 Sep 2026. Source: [github.com/hunvreus/pagescms](https://github.com/hunvreus/pagescms)
  - Strapi — Strapi's own surface is the REST API and an official client SDK; the Astro starter, loader and blocks renderer its page links are community-built, and its listings give no Astro range. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/api/rest](https://docs.strapi.io/cms/api/rest), [docs.strapi.io/cms/api/client](https://docs.strapi.io/cms/api/client), [community.strapi.io/integrations/astro](https://community.strapi.io/integrations/astro)
  - Sveltia CMS — Sveltia is framework-agnostic and names no Astro version; it edits repository files regardless of the framework. Vendor documentation, checked 3 Sep 2026. Sources: [github.com/sveltia/sveltia-cms](https://github.com/sveltia/sveltia-cms), [sveltiacms.app/en/docs/architecture](https://sveltiacms.app/en/docs/architecture)
- **Astro 5–7**
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [registry.npmjs.org/@keystatic/astro/latest](https://registry.npmjs.org/@keystatic/astro/latest)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [raw.githubusercontent.com/…/package.json](https://raw.githubusercontent.com/tinacms/tinacms/main/packages/@tinacms/astro/package.json), [tina.io/docs/frameworks/astro](https://tina.io/docs/frameworks/astro)
  - CloudCannon — The editable-regions integration requires Astro 5+; on Astro 4 it is skipped. Static output only — server and hybrid Astro sites are not covered. Vendor documentation, checked 4 Sep 2026. Sources: [raw.githubusercontent.com/…/visual-editing.md](https://raw.githubusercontent.com/CloudCannon/agent-skills/main/skills/cloudcannon-visual-editing/astro/visual-editing.md), [raw.githubusercontent.com/…/cc-friendly-conventions.md](https://raw.githubusercontent.com/CloudCannon/agent-skills/main/skills/migrate-to-cloudcannon/astro/cc-friendly-conventions.md), [raw.githubusercontent.com/…/package.json](https://raw.githubusercontent.com/CloudCannon/astro-minimal-starter/main/package.json), [raw.githubusercontent.com/…/package.json](https://raw.githubusercontent.com/CloudCannon/editable-regions/main/package.json), [raw.githubusercontent.com/…/overview.md](https://raw.githubusercontent.com/CloudCannon/agent-skills/main/skills/migrate-to-cloudcannon/astro/overview.md)
- **Astro 2–7**
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [raw.githubusercontent.com/…/package.json](https://raw.githubusercontent.com/sanity-io/sanity-astro/main/packages/sanity-astro/package.json)
- **Astro 3–7**
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [raw.githubusercontent.com/…/package.json](https://raw.githubusercontent.com/storyblok/monoblok/main/packages/astro/package.json)
- **Astro 4–7**
  - ZeroCMS — Tested, checked 22 Aug 2026.
- **Astro 6**
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/existing-project](https://docs.emdashcms.com/existing-project/)

### Starlight support

Whether the product supports editing Astro Starlight sites. Ranked; best answer first.

- **Fully** — The docs are editable, Starlight's own components are fully supported, and the preview renders the Starlight site.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon, Payload CMS, TinaCMS — Tested, checked 18 Sep 2026.
  - EmDash — Tested, checked 17 Sep 2026.
- **Partly** — Docs are editable, but something is missing or doesn't fully work.
  - Decap CMS — The docs collection is editable, but there is no preview, and Starlight components can only be typed into a raw MDX code editor rather than inserted with their props as fields. Tested, checked 17 Sep 2026.
  - Keystatic — The docs collection is editable and Starlight components insert with their props as fields, but no preview renders the Starlight site. Tested, checked 16 Sep 2026.
  - Pages CMS — The docs collection is editable only as raw MDX in a code editor, where Starlight components are typed by hand with their imports; no component insertion with props as fields and no preview. Tested, checked 16 Sep 2026.
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Sanity — Sanity publishes no Starlight integration, starter or guide, so there was nothing to grade it against.
  - Storyblok — Storyblok publishes no Starlight guide, starter or example, so there was nothing to grade it against.
  - Strapi — Strapi publishes no Starlight guide, starter or example, so there was nothing to grade it against.
  - Sveltia CMS — Sveltia documents no Astro or Starlight integration; it discovers content by config-declared folder paths and renders no preview of the built site.

### Astro build requirements

What does adopting this product force you to change about your Astro build? Ranked; best answer first.

- **Nothing** — Your build stays untouched.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [community.strapi.io/integrations/astro](https://community.strapi.io/integrations/astro), [docs.strapi.io/cms/api/rest](https://docs.strapi.io/cms/api/rest)
  - CloudCannon — A config using CloudCannon's editable-regions integration has no `adapter` or `output` key; static output is required if CloudCannon builds and hosts, and SSR sites use Headless Mode elsewhere. Vendor documentation, checked 31 Aug 2026. Sources: [raw.githubusercontent.com/…/astro.config.mjs](https://raw.githubusercontent.com/CloudCannon/astro-minimal-starter/main/astro.config.mjs), [raw.githubusercontent.com/…/cc-friendly-conventions.md](https://raw.githubusercontent.com/CloudCannon/agent-skills/main/skills/migrate-to-cloudcannon/astro/cc-friendly-conventions.md), [cloudcannon.com/…/what-is-headless-mode](https://cloudcannon.com/documentation/developer-articles/what-is-headless-mode/)
  - Decap CMS — Decap is a separate static admin app; it adds nothing to the Astro build and demands no adapter. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/install-decap-cms](https://decapcms.org/docs/install-decap-cms/)
  - Pages CMS — Pages CMS is a separate editing app and demands nothing of the Astro build. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs](https://pagescms.org/docs/)
  - Payload CMS — No adapter and output stays static; a custom loader fetches content from Payload at build time, so the CMS must be reachable during the build and a publish needs a rebuild to go live. Tested, checked 18 Sep 2026.
  - Sanity — Only the visual-editing live preview needs an Astro SSR adapter. Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/astro/configure-sanity-astro](https://www.sanity.io/docs/astro/configure-sanity-astro), [sanity.io/docs/visual-editing/astro-visual-editing](https://www.sanity.io/docs/visual-editing/astro-visual-editing)
  - Storyblok — Only the opt-in real-time live preview needs an Astro SSR adapter. Vendor documentation, checked 3 Sep 2026. Sources: [github.com/storyblok/storyblok-astro](https://github.com/storyblok/storyblok-astro), [storyblok.com/docs/guides/astro/visual-preview](https://www.storyblok.com/docs/guides/astro/visual-preview)
  - Sveltia CMS — Sveltia is a separate static admin bundle that adds nothing to the Astro build and demands no adapter. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/start](https://sveltiacms.app/en/docs/start), [sveltiacms.app/en/docs/architecture](https://sveltiacms.app/en/docs/architecture)
- **Adapter required** — An adapter has to be installed before its own surfaces work.
  - EmDash — An SSR adapter is required — @astrojs/node or @astrojs/cloudflare; on Cloudflare it must be Workers, not Pages. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/existing-project](https://docs.emdashcms.com/existing-project/)
  - Keystatic — A Node-capable Astro adapter is required to deploy. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/installation-astro](https://keystatic.com/docs/installation-astro)
  - TinaCMS — The adapter is required either way, because the per-island refresh route runs at request time. `output` can stay static, but only if every editable region is wrapped in a TinaIsland. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro)

### Output modes

The rendering modes the product works with. Ranked; best answer first.

- **Static, Server-rendered**
  - ZeroCMS, Decap CMS, EmDash, Keystatic, Pages CMS, Payload CMS, Sanity, Storyblok, Strapi, Sveltia CMS, TinaCMS — By design.
- **Static**
  - CloudCannon — By design.

### Preview output modes

Output modes supported by the preview. Ranked; best answer first.

- **Static, Server-rendered**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/live-preview](https://www.zerocms.io/features/live-preview)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/guides/astro/visual-preview](https://www.storyblok.com/docs/guides/astro/visual-preview)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro)
- **Server-rendered**
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/coming-from/astro](https://docs.emdashcms.com/coming-from/astro/)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/visual-editing/astro-visual-editing](https://www.sanity.io/docs/visual-editing/astro-visual-editing)
- **Static**
  - CloudCannon — Server-rendered sites can be hosted elsewhere in Headless Mode, which turns off CloudCannon's builds and hosting, and with them the Visual Editor and preview screenshots. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-visual-editing](https://cloudcannon.com/documentation/developer-articles/what-is-visual-editing/), [cloudcannon.com/…/configure-your-initial-site-settings](https://cloudcannon.com/documentation/developer-articles/configure-your-initial-site-settings/), [cloudcannon.com/…/what-is-headless-mode](https://cloudcannon.com/documentation/developer-articles/what-is-headless-mode/), [cloudcannon.com/…/unified-configuration-migration-guide](https://cloudcannon.com/documentation/developer-guides/unified-configuration-migration-guide/)
- **None**
  - Keystatic — Tested, checked 16 Sep 2026.
  - Decap CMS — The preview pane is Decap's own render, so it renders neither the static nor the SSR output of the real Astro site. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/architecture](https://decapcms.org/docs/architecture/)
  - Pages CMS — Pages CMS renders no preview of the built site; the only "preview" is a button that dispatches a GitHub Actions workflow. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/content](https://pagescms.org/docs/configuration/content/), [pagescms.org/docs/configuration/actions](https://pagescms.org/docs/configuration/actions/)
  - Payload CMS — The preview renders in your own front end, so which modes it covers is your code's answer rather than Payload's. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/live-preview/overview](https://payloadcms.com/docs/live-preview/overview), [payloadcms.com/docs/live-preview/client](https://payloadcms.com/docs/live-preview/client)
  - Strapi — The preview renders in your own front end, so which modes it covers is your code's answer rather than Strapi's. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/preview](https://docs.strapi.io/cms/features/preview)
  - Sveltia CMS — The preview pane is not the built Astro site, so it renders neither the static nor the SSR output. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor)

## Codebase fit

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Code in your repository | **Nothing** | Config file, Schema definition, Dependency, Build config | Config file, Admin route, Schema definition | Dependency, Build config, Integration code, Admin route, Generated code | Dependency, Config file, Build config, Schema definition, Credentials | Config file, Schema definition | Dependency, Config file, Build config, Schema definition, Integration code, Generated code, Credentials | Dependency, Config file, Build config, Admin route, Schema definition, Integration code, Credentials | Dependency, Build config, Credentials, Integration code | Integration code, Credentials | Admin route, Config file, Schema definition | Dependency, Config file, Build config, Admin route, Schema definition, Integration code, Generated code, Credentials |
| Infrastructure you run | **Nothing** | **Nothing** | OAuth gateway | App server, Database, Build pipeline | App server | OAuth gateway, App server, Database | App server, Database | **Nothing** | Not tested | App server, Database | OAuth gateway | App server, Database |
| Schema source | **Your Zod schemas** | CMS config file | CMS config file | CMS dashboard | CMS config file | CMS config file | CMS config file | CMS config file | CMS dashboard | CMS config file | CMS config file | CMS config file |
| Component registration | **Your own components** | Declared in config | Declared in config | Mapped in code | Declared in config | No components | Mapped in code | Mapped in code | Mapped in code | Mapped in code | Declared in config | Declared in config |
| Media configuration | **Found in the project** | Declared in config | Declared in config | Declared in config | Declared in config | Declared in config | Declared in config | The vendor's | The vendor's | Declared in config | Declared in config | Declared in config |

### Code in your repository

What adopting the product adds to your repository. Ranked; best answer first.

- **Nothing**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/zero-integration](https://www.zerocms.io/features/zero-integration), [zerocms.io/features/mcp-server](https://www.zerocms.io/features/mcp-server)
- **Config file, Schema definition** — Config file: A config file owned by the CMS. Schema definition: Your content model, declared a second time.
  - Pages CMS — A single .pages.yml is the config file and declares the content model's fields; nothing else is added. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs](https://pagescms.org/docs/), [pagescms.org/docs/configuration](https://pagescms.org/docs/configuration/), [pagescms.org/docs/configuration/content](https://pagescms.org/docs/configuration/content/)
- **Integration code, Credentials** — Integration code: Fetching and rendering code you write and maintain. Credentials: An API key or token the repo and deploy carry.
  - Strapi — Strapi is a separate application, so none of its own files — the model, the admin panel, its configuration — land in the site's repository. Vendor documentation, checked 3 Sep 2026. Sources: [community.strapi.io/integrations/astro](https://community.strapi.io/integrations/astro), [strapi.io/…/lightning-fast-building-with-strapi-and-astro](https://strapi.io/blog/lightning-fast-building-with-strapi-and-astro), [docs.strapi.io/cms/project-structure](https://docs.strapi.io/cms/project-structure), [docs.strapi.io/cms/installation/cli](https://docs.strapi.io/cms/installation/cli)
- **Config file, Admin route, Schema definition** — Config file: A config file owned by the CMS. Admin route: An editor served by your own site. Schema definition: Your content model, declared a second time.
  - Decap CMS — A static /admin folder holds a config.yml that declares the collections; installing as an npm module instead adds a dependency. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/install-decap-cms](https://decapcms.org/docs/install-decap-cms/), [decapcms.org/docs/configure-decap-cms](https://decapcms.org/docs/configure-decap-cms/)
  - Sveltia CMS — A static folder holds an index.html loading the CMS from a CDN and a config.yml that declares the collections; installing via npm instead adds a dependency. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/start](https://sveltiacms.app/en/docs/start), [sveltiacms.app/en/docs/architecture](https://sveltiacms.app/en/docs/architecture)
- **Config file, Schema definition, Dependency, Build config** — Config file: A config file owned by the CMS. Schema definition: Your content model, declared a second time. Dependency: A package in package.json. Build config: An integration or plugin in your Astro config.
  - CloudCannon — A config file in the repo root, one or more schema/template files per collection, and a Bookshop spec file beside each component; Bookshop also adds an npm package and an entry in the Astro config. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-the-cloudcannon-configuration-file](https://cloudcannon.com/documentation/developer-articles/what-is-the-cloudcannon-configuration-file/), [cloudcannon.com/…/what-is-a-schema](https://cloudcannon.com/documentation/developer-articles/what-is-a-schema/), [cloudcannon.com/…/create-a-schema](https://cloudcannon.com/documentation/developer-articles/create-a-schema/), [cloudcannon.com/…/getting-set-up](https://cloudcannon.com/documentation/developer-guides/bookshop-astro-guide/getting-set-up/), [cloudcannon.com/…/using-structures](https://cloudcannon.com/documentation/developer-guides/bookshop-astro-guide/using-structures/)
- **Dependency, Build config, Credentials, Integration code** — Dependency: A package in package.json. Build config: An integration or plugin in your Astro config. Credentials: An API key or token the repo and deploy carry. Integration code: Fetching and rendering code you write and maintain.
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/guides/astro](https://www.storyblok.com/docs/guides/astro)
- **Dependency, Build config, Integration code, Admin route, Generated code** — Dependency: A package in package.json. Build config: An integration or plugin in your Astro config. Integration code: Fetching and rendering code you write and maintain. Admin route: An editor served by your own site. Generated code: Generated types or a client, committed to the repo.
  - EmDash — The content model lives in the database, surfacing in the repo only as generated types. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/existing-project](https://docs.emdashcms.com/existing-project/), [docs.emdashcms.com/coming-from/astro](https://docs.emdashcms.com/coming-from/astro/), [docs.emdashcms.com/getting-started](https://docs.emdashcms.com/getting-started/), [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash)
- **Dependency, Config file, Build config, Schema definition, Credentials** — Dependency: A package in package.json. Config file: A config file owned by the CMS. Build config: An integration or plugin in your Astro config. Schema definition: Your content model, declared a second time. Credentials: An API key or token the repo and deploy carry.
  - Keystatic — keystatic.config.ts holds both the config and the content-model schema; credentials are written into an .env file. Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/installation-astro](https://keystatic.com/docs/installation-astro), [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode)
- **Dependency, Config file, Build config, Admin route, Schema definition, Integration code, Credentials** — Dependency: A package in package.json. Config file: A config file owned by the CMS. Build config: An integration or plugin in your Astro config. Admin route: An editor served by your own site. Schema definition: Your content model, declared a second time. Integration code: Fetching and rendering code you write and maintain. Credentials: An API key or token the repo and deploy carry.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [raw.githubusercontent.com/…/README.md](https://raw.githubusercontent.com/sanity-io/sanity-astro/main/packages/sanity-astro/README.md), [sanity.io/content-lake](https://www.sanity.io/content-lake), [sanity.io/docs/astro/embedding-studio-in-astro](https://www.sanity.io/docs/astro/embedding-studio-in-astro), [sanity.io/docs/astro/configure-sanity-astro](https://www.sanity.io/docs/astro/configure-sanity-astro), [sanity.io/…/displaying-content-in-an-astro-front-end](https://www.sanity.io/docs/astro-quickstart/displaying-content-in-an-astro-front-end)
- **Dependency, Config file, Build config, Schema definition, Integration code, Generated code, Credentials** — Dependency: A package in package.json. Config file: A config file owned by the CMS. Build config: An integration or plugin in your Astro config. Schema definition: Your content model, declared a second time. Integration code: Fetching and rendering code you write and maintain. Generated code: Generated types or a client, committed to the repo. Credentials: An API key or token the repo and deploy carry.
  - Payload CMS — An admin app is committed as a separate Next.js workspace package the Astro site depends on, rather than a route the Astro build serves. Vendor documentation, checked 3 Sep 2026. Sources: [raw.githubusercontent.com/…/package.json](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/website/package.json), [raw.githubusercontent.com/…/payload.config.ts](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/payload/src/payload.config.ts), [raw.githubusercontent.com/…/page.tsx](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/payload/src/app/%28payload%29/admin/%5B%5B...segments%5D%5D/page.tsx), [raw.githubusercontent.com/…/astro.config.mjs](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/website/astro.config.mjs), [raw.githubusercontent.com/…/index.astro](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/website/src/pages/index.astro), [raw.githubusercontent.com/…/.env.example](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/payload/.env.example), [raw.githubusercontent.com/…/pnpm-workspace.yaml](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/pnpm-workspace.yaml), [raw.githubusercontent.com/…/package.json](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/package.json), [raw.githubusercontent.com/…/package.json](https://raw.githubusercontent.com/payloadcms/payload/main/examples/astro/payload/package.json), [payloadcms.com/docs/admin/overview](https://payloadcms.com/docs/admin/overview)
- **Dependency, Config file, Build config, Admin route, Schema definition, Integration code, Generated code, Credentials** — Dependency: A package in package.json. Config file: A config file owned by the CMS. Build config: An integration or plugin in your Astro config. Admin route: An editor served by your own site. Schema definition: Your content model, declared a second time. Integration code: Fetching and rendering code you write and maintain. Generated code: Generated types or a client, committed to the repo. Credentials: An API key or token the repo and deploy carry.
  - TinaCMS — The model, a committed schema lock file and the code marking each editable section live in the repository; the client and admin bundle are built. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/frameworks/astro](https://tina.io/docs/frameworks/astro), [tina.io/docs/tina-folder/overview](https://tina.io/docs/tina-folder/overview), [tina.io/…/cloudflare-workers](https://tina.io/docs/tinacloud/deployment-options/cloudflare-workers), [tina.io/docs/reference/config](https://tina.io/docs/reference/config)

### Infrastructure you run

What you have to run yourself when self-hosting. Ranked; best answer first.

- **Nothing**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-a-site-build](https://cloudcannon.com/documentation/developer-articles/what-is-a-site-build/), [cloudcannon.com/…/configure-your-first-build](https://cloudcannon.com/documentation/developer-articles/configure-your-first-build/), [cloudcannon.com/…/authenticate-your-git-provider](https://cloudcannon.com/documentation/developer-articles/authenticate-your-git-provider/)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/deployment](https://www.sanity.io/docs/studio/deployment)
- **OAuth gateway** — OAuth gateway: A service that exchanges a Git host login for a token.
  - Decap CMS — Self-hosting with a direct GitHub backend needs an OAuth server; Netlify hosts one, or you run your own. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/github-backend](https://decapcms.org/docs/github-backend/), [decapcms.org/docs/external-oauth-clients](https://decapcms.org/docs/external-oauth-clients/)
  - Sveltia CMS — OAuth sign-in needs an OAuth client server the customer deploys (Sveltia's Authenticator, a Netlify/Decap client, or Netlify). Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/backends/github](https://sveltiacms.app/en/docs/backends/github)
- **App server** — App server: The product's own server process.
  - Keystatic — Keystatic's API routes run inside the customer's own Astro app, which must run Node.js. Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/installation-astro](https://keystatic.com/docs/installation-astro), [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode)
- **App server, Database** — App server: The product's own server process. Database: A database and its backups.
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/getting-started/installation](https://payloadcms.com/docs/getting-started/installation)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/deployment](https://docs.strapi.io/cms/deployment), [docs.strapi.io/cms/features/preview](https://docs.strapi.io/cms/features/preview)
  - TinaCMS — Self-hosting replaces TinaCloud with a backend, a database and an auth provider you run, and gives up repo-based media, search and runtime branch switching. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/self-hosted/overview](https://tina.io/docs/self-hosted/overview), [tina.io/…/overview](https://tina.io/docs/reference/self-hosted/database-adapter/overview), [tina.io/docs/faq](https://tina.io/docs/faq)
- **App server, Database, Build pipeline** — App server: The product's own server process. Database: A database and its backups. Build pipeline: A CI job or deploy hook beyond the site's own.
  - EmDash — You run the Astro SSR process, provision the database yourself, and run the build and migrations to deploy. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/existing-project](https://docs.emdashcms.com/existing-project/), [docs.emdashcms.com/deployment/database](https://docs.emdashcms.com/deployment/database/), [docs.emdashcms.com/deployment/nodejs](https://docs.emdashcms.com/deployment/nodejs/), [docs.emdashcms.com/deployment/cloudflare](https://docs.emdashcms.com/deployment/cloudflare/)
- **OAuth gateway, App server, Database** — OAuth gateway: A service that exchanges a Git host login for a token. App server: The product's own server process. Database: A database and its backups.
  - Pages CMS — Self-hosting runs a Node app server, a PostgreSQL database and a GitHub App for auth. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/guides/installing/self-host](https://pagescms.org/docs/guides/installing/self-host/)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Storyblok

### Schema source

Where the content model is defined. Ranked; best answer first.

- **Your Zod schemas** — Read from your Astro collection schemas.
  - ZeroCMS — Tested, checked 22 Aug 2026.
- **CMS config file** — Defined again in a CMS config in your repository.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/configuration-file](https://cloudcannon.com/documentation/developer-reference/configuration-file/), [cloudcannon.com/…/create-your-cloudcannon-configuration-file](https://cloudcannon.com/documentation/developer-guides/getting-started-with-cloudcannon/create-your-cloudcannon-configuration-file/), [cloudcannon.com/…/create-a-schema](https://cloudcannon.com/documentation/developer-articles/create-a-schema/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/install-decap-cms](https://decapcms.org/docs/install-decap-cms/), [decapcms.org/docs/configure-decap-cms](https://decapcms.org/docs/configure-decap-cms/), [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/collections](https://keystatic.com/docs/collections), [keystatic.com/docs/installation-astro](https://keystatic.com/docs/installation-astro)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/content](https://pagescms.org/docs/configuration/content/), [pagescms.org/docs/configuration](https://pagescms.org/docs/configuration/)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/content-lake](https://www.sanity.io/content-lake)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/start](https://sveltiacms.app/en/docs/start), [sveltiacms.app/en/docs/architecture](https://sveltiacms.app/en/docs/architecture)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/schema](https://tina.io/docs/reference/schema), [tina.io/docs/reference/config](https://tina.io/docs/reference/config), [tina.io/docs/content-model-intro](https://tina.io/docs/content-model-intro)
  - Payload CMS — Declared once, but a separate front end is told to get it by copying the generated types across. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/configuration/collections](https://payloadcms.com/docs/configuration/collections), [payloadcms.com/docs/configuration/overview](https://payloadcms.com/docs/configuration/overview), [payloadcms.com/docs/typescript/generating-types](https://payloadcms.com/docs/typescript/generating-types)
  - Strapi — The builder runs only against a development instance, so the model cannot be changed on a live project. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/deployment](https://docs.strapi.io/cms/deployment), [docs.strapi.io/cms/faq](https://docs.strapi.io/cms/faq), [docs.strapi.io/cms/backend-customization/models](https://docs.strapi.io/cms/backend-customization/models), [docs.strapi.io/cms/quick-start](https://docs.strapi.io/cms/quick-start)
- **CMS dashboard** — Defined in the vendor's UI, outside your repository.
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Sources: [github.com/storyblok/storyblok-astro](https://github.com/storyblok/storyblok-astro), [storyblok.com/docs/concepts/blocks](https://www.storyblok.com/docs/concepts/blocks)
  - EmDash — The model is authored in the admin or the CLI, and can be exported as a JSON seed for version control. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/concepts/content-model](https://docs.emdashcms.com/concepts/content-model/), [docs.emdashcms.com/concepts/architecture](https://docs.emdashcms.com/concepts/architecture/)

### Component registration

How the editor learns about your components. Ranked; best answer first.

- **Your own components** — The editor reads the components in your repository.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/zero-integration](https://www.zerocms.io/features/zero-integration), [zerocms.io/features/visual-content-editor](https://www.zerocms.io/features/visual-content-editor)
- **Declared in config** — Each component registered in a CMS config in your repository.
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/custom-widgets](https://decapcms.org/docs/custom-widgets/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/content-components](https://keystatic.com/docs/content-components)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/api/editor-components](https://sveltiacms.app/en/docs/api/editor-components)
  - CloudCannon — A component nobody registered appears in the editor as a block that cannot be edited. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/snippets-using-mdx-components](https://cloudcannon.com/documentation/developer-articles/snippets-using-mdx-components/), [cloudcannon.com/…/using-structures](https://cloudcannon.com/documentation/developer-guides/bookshop-astro-guide/using-structures/)
  - TinaCMS — A component in the body needs a template describing its fields and a renderer registered under a matching name, or it shows as a placeholder. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro)
- **Mapped in code** — Blocks defined in the CMS, each mapped to a component in your code.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/astro/images-and-portable-text-astro](https://www.sanity.io/docs/astro/images-and-portable-text-astro), [sanity.io/…/portable-text-editor-configuration](https://www.sanity.io/docs/studio/portable-text-editor-configuration)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/guides/astro](https://www.storyblok.com/docs/guides/astro)
  - EmDash — Custom block types require a native plugin loaded from npm at build time. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/…/portable-text-components](https://docs.emdashcms.com/plugins/creating-native-plugins/portable-text-components/)
  - Payload CMS — Blocks are defined in the Payload config, and rendering each one is a converter the Astro site has to write. Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/rich-text/blocks](https://payloadcms.com/docs/rich-text/blocks)
  - Strapi — The renderer Strapi ships officially is a React one, covering its rich-text blocks; an Astro site defines its own renderers for those blocks. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/content-type-builder](https://docs.strapi.io/cms/features/content-type-builder), [strapi.io/…/lightning-fast-building-with-strapi-and-astro](https://strapi.io/blog/lightning-fast-building-with-strapi-and-astro), [github.com/strapi/blocks-react-renderer](https://github.com/strapi/blocks-react-renderer)
- **No components** — Nothing can be placed in the body.
  - Pages CMS — Tested, checked 16 Sep 2026.

### Media configuration

How the editor learns where your assets live. Ranked; best answer first.

- **Found in the project** — The editor locates your asset folders itself.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/media-library](https://www.zerocms.io/features/media-library)
- **Declared in config** — Upload and public paths are set in a CMS config.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/adjusting-the-uploads-path](https://cloudcannon.com/documentation/developer-articles/adjusting-the-uploads-path/), [cloudcannon.com/…/what-is-the-cloudcannon-configuration-file](https://cloudcannon.com/documentation/developer-articles/what-is-the-cloudcannon-configuration-file/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/)
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/concepts/architecture](https://docs.emdashcms.com/concepts/architecture/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/fields/image](https://keystatic.com/docs/fields/image)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/media](https://pagescms.org/docs/configuration/media/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/upload/overview](https://payloadcms.com/docs/upload/overview)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/media](https://sveltiacms.app/en/docs/media)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/media/overview](https://tina.io/docs/reference/media/overview), [tina.io/docs/reference/media/repo-based](https://tina.io/docs/reference/media/repo-based)
  - Strapi — Declared in the Strapi application's own configuration, in config/plugins. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/media-library](https://docs.strapi.io/cms/features/media-library), [docs.strapi.io/cms/project-structure](https://docs.strapi.io/cms/project-structure)
- **The vendor's** — Assets live with the vendor, so there is nothing to configure.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/content-lake/assets](https://www.sanity.io/docs/content-lake/assets)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/assets](https://www.storyblok.com/docs/concepts/assets)

## Editing

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Editing surfaces | Rich text, Schema forms, Raw code | On-page inline, Visual blocks, Rich text, Schema forms, Raw code | Schema forms, Rich text, Markdown source | Rich text, Markdown source, Schema forms | Schema forms, Rich text, Visual blocks | Schema forms, Rich text, Markdown source, Raw code | Visual blocks, Rich text, Schema forms | Not tested | Not tested | Visual blocks, Rich text, Markdown source, Schema forms | Schema forms, Rich text, Markdown source | Schema forms, Rich text, Visual blocks, Markdown source |
| Components in rich text | **Fully** | **Fully** | **Fully** | **Fully** | **Fully** | No | **Fully** | **Fully** | **Fully** | Partly | **Fully** | **Fully** |
| Validation | **Before save** | **Before save** | At publish | At publish | **Before save** | **Before save** | **Before save** | At publish | **Before save** | At publish | **Before save** | At publish |
| Entry references | **A picker** | **A picker** | **A picker** | **A picker** | **A picker** | **A picker** | **A picker** | **A picker** | **A picker** | **A picker** | **A picker** | **A picker** |
| Custom field controls | No | No | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** |
| Nested objects and arrays | **As structure** | **As structure** | **As structure** | As raw text | **As structure** | **As structure** | **As structure** | **As structure** | **As structure** | **As structure** | **As structure** | **As structure** |
| Variant blocks | **Choosable** | **Choosable** | **Choosable** | **Choosable** | **Choosable** | **Choosable** | **Choosable** | **Choosable** | **Choosable** | **Choosable** | **Choosable** | **Choosable** |
| Revision history | In git only | In git only | In git only | **Shown and restorable** | In git only | In git only | **Shown and restorable** | **Shown and restorable** | **Shown and restorable** | **Shown and restorable** | Shown, not restorable | In git only |
| Real-time collaboration | **Merged live** | Locked | Last save wins | Warns before overwriting | **Merged live** | Discards unsaved edits | Locked | **Merged live** | Locked | Not tested | Last save wins | Not tested |
| Conflict handling | Flagged | **Blocked** | Overwrites | Not tested | **Blocked** | Discards your edits | Overwrites | Not tested | Flagged | Not tested | Overwrites | Not tested |
| Editorial comments | No | No | No | No | No | No | No | **Threads on fields** | **Threads on fields** | Not tested | Not tested | No |
| Localization | Untracked | Untracked | Linked locales | Linked locales | Untracked | Untracked | Linked locales | Linked locales | **Translation workflow** | Linked locales | Linked locales | Untracked |
| Content checks | **SEO, accessibility, readability, writing style, broken links, broken content, content consistency, GEO** | Nothing | Nothing | Nothing | Nothing | Nothing | Nothing | Nothing | Nothing | Nothing | Nothing | Nothing |
| Check enforcement | **Your choice** | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply |
| Custom checks | **In plain language** | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply |
| Check scope | **The whole site** | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply |

### Editing surfaces

The kinds of editing interface the product offers.

- **Schema forms, Rich text, Markdown source** — Schema forms: A form generated from the content model. Rich text: A formatted-text editor. Markdown source: The raw Markdown.
  - EmDash — Tested, checked 17 Sep 2026.
  - Decap CMS — Fields are generated from the config's widgets, and the markdown widget toggles between a rich-text and a raw markdown mode. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/widgets/markdown](https://decapcms.org/docs/widgets/markdown/), [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/)
  - Sveltia CMS — Fields are generated from the schema, and the rich-text field has a raw Markdown mode. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/fields](https://sveltiacms.app/en/docs/fields), [sveltiacms.app/en/docs/fields/richtext](https://sveltiacms.app/en/docs/fields/richtext)
- **Visual blocks, Rich text, Markdown source, Schema forms** — Visual blocks: Building a page from blocks on a canvas. Rich text: A formatted-text editor. Markdown source: The raw Markdown. Schema forms: A form generated from the content model.
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/content-manager](https://docs.strapi.io/cms/features/content-manager), [docs.strapi.io/cms/features/content-type-builder](https://docs.strapi.io/cms/features/content-type-builder)
  - TinaCMS — Clicking the page selects the matching field, but the typing happens in the sidebar rather than on the page. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacms-lingo](https://tina.io/docs/tinacms-lingo), [tina.io/docs/reference/fields](https://tina.io/docs/reference/fields), [tina.io/docs/reference/types/rich-text](https://tina.io/docs/reference/types/rich-text), [tina.io/docs/editing/blocks](https://tina.io/docs/editing/blocks)
- **Schema forms, Rich text, Visual blocks** — Schema forms: A form generated from the content model. Rich text: A formatted-text editor. Visual blocks: Building a page from blocks on a canvas.
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/fields/image](https://keystatic.com/docs/fields/image), [keystatic.com/docs/fields/document](https://keystatic.com/docs/fields/document), [keystatic.com/docs/fields/blocks](https://keystatic.com/docs/fields/blocks)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/fields/blocks](https://payloadcms.com/docs/fields/blocks), [payloadcms.com/…/how-to-build-flexible-layouts-with-payload-blocks](https://payloadcms.com/posts/guides/how-to-build-flexible-layouts-with-payload-blocks), [payloadcms.com/docs/live-preview/overview](https://payloadcms.com/docs/live-preview/overview), [payloadcms.com/docs/rich-text/overview](https://payloadcms.com/docs/rich-text/overview), [payloadcms.com/docs/fields/overview](https://payloadcms.com/docs/fields/overview), [payloadcms.com/docs/admin/overview](https://payloadcms.com/docs/admin/overview)
- **Schema forms, Rich text, Markdown source, Raw code** — Schema forms: A form generated from the content model. Rich text: A formatted-text editor. Markdown source: The raw Markdown. Raw code: The underlying file, edited as code.
  - Pages CMS — Fields are generated; the rich-text body toggles to a Markdown source view, and files without fields fall back to a raw editor. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/content/editors](https://pagescms.org/docs/configuration/content/editors/), [pagescms.org/docs/configuration/fields/rich-text](https://pagescms.org/docs/configuration/fields/rich-text/)
- **On-page inline, Visual blocks, Rich text, Schema forms, Raw code** — On-page inline: Editing text directly on the rendered page. Visual blocks: Building a page from blocks on a canvas. Rich text: A formatted-text editor. Schema forms: A form generated from the content model. Raw code: The underlying file, edited as code.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/using-cloudcannons-editing-interfaces](https://cloudcannon.com/documentation/user-guides/editing-in-cloudcannon/using-cloudcannons-editing-interfaces/), [cloudcannon.com/…/what-is-an-array-input](https://cloudcannon.com/documentation/user-articles/what-is-an-array-input/), [cloudcannon.com/…/configuring-live-editing](https://cloudcannon.com/documentation/developer-guides/bookshop-astro-guide/configuring-live-editing/)
- **Rich text, Schema forms, Raw code** — Rich text: A formatted-text editor. Schema forms: A form generated from the content model. Raw code: The underlying file, edited as code.
  - ZeroCMS — Tested, checked 1 Sep 2026. [Source](https://www.zerocms.io/features/visual-content-editor)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Sanity, Storyblok

### Components in rich text

Whether components can be placed inside body content. Ranked; best answer first.

- **Fully** — Inserted from a palette with its props as fields, and nothing left to hand-edit.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/visual-content-editor](https://www.zerocms.io/features/visual-content-editor)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/snippets-using-mdx-components](https://cloudcannon.com/documentation/developer-articles/snippets-using-mdx-components/)
  - EmDash — Tested, checked 17 Sep 2026.
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/fields/document](https://keystatic.com/docs/fields/document)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/rich-text/blocks](https://payloadcms.com/docs/rich-text/blocks)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/…/portable-text-editor-configuration](https://www.sanity.io/docs/studio/portable-text-editor-configuration)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/concepts/fields](https://www.storyblok.com/docs/concepts/fields), [storyblok.com/docs/manuals/visual-editor](https://www.storyblok.com/docs/manuals/visual-editor)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro), [tina.io/docs/reference/types/rich-text](https://tina.io/docs/reference/types/rich-text), [tina.io/docs/tinacms-lingo](https://tina.io/docs/tinacms-lingo)
  - Decap CMS — Blocks are Decap editor components declared in code; their props are entered as fields and serialized to Markdown. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/custom-widgets](https://decapcms.org/docs/custom-widgets/)
  - Sveltia CMS — Editor components are inserted from the toolbar's Insert menu with their props entered as fields. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/fields/richtext](https://sveltiacms.app/en/docs/fields/richtext), [sveltiacms.app/en/docs/api/editor-components](https://sveltiacms.app/en/docs/api/editor-components)
- **Partly** — It can be inserted, but something is still hand-work — raw props, or an import line to write. The note says which.
  - Strapi — Custom block types can be registered into the Blocks rich-text editor's toolbar; other components attach through dynamic zones rather than inline in a prose body. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/…/content-manager-apis](https://docs.strapi.io/cms/plugins-development/content-manager-apis), [docs.strapi.io/cms/features/content-type-builder](https://docs.strapi.io/cms/features/content-type-builder)
- **No** — Prose only.
  - Pages CMS — The rich-text body inserts images only. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/fields/rich-text](https://pagescms.org/docs/configuration/fields/rich-text/)

### Validation

When, if at all, are values that break the schema caught? Ranked; best answer first.

- **Before save** — Caught while editing.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/zero-integration](https://www.zerocms.io/features/zero-integration), [zerocms.io/…/content-collections-deep-dive](https://www.zerocms.io/resources/guides/content-collections-deep-dive), [zerocms.io/features/visual-content-editor](https://www.zerocms.io/features/visual-content-editor), [zerocms.io](https://www.zerocms.io/)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-are-inputs](https://cloudcannon.com/documentation/user-articles/what-are-inputs/), [cloudcannon.com/…/what-is-an-array-input](https://cloudcannon.com/documentation/user-articles/what-is-an-array-input/)
  - Keystatic — Tested, checked 16 Sep 2026.
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/content/fields](https://pagescms.org/docs/configuration/content/fields/), [pagescms.org/docs/configuration/fields/number](https://pagescms.org/docs/configuration/fields/number/), [pagescms.org/docs/development/fields](https://pagescms.org/docs/development/fields/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/fields/overview](https://payloadcms.com/docs/fields/overview)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/fields](https://www.storyblok.com/docs/concepts/fields)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/fields](https://sveltiacms.app/en/docs/fields), [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor)
- **At publish** — Caught at publish or at build, not while editing.
  - Decap CMS — Required and a regex pattern with a message are enforced. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/widgets](https://decapcms.org/docs/widgets/)
  - EmDash — The options rule is enforced server-side on save; live in-editor validation is not documented, and json fields are unchecked. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/reference/rest-api](https://docs.emdashcms.com/reference/rest-api/), [docs.emdashcms.com/reference/field-types](https://docs.emdashcms.com/reference/field-types/)
  - Sanity — Validation is enforced as a publish-time gate that blocks publishing, not as you type. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/validation](https://www.sanity.io/docs/studio/validation)
  - Strapi — Required and length rules are enforced at publish: the entry cannot be published and a red warning names the offending field. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/draft-and-publish](https://docs.strapi.io/cms/features/draft-and-publish), [docs.strapi.io/cms/features/content-type-builder](https://docs.strapi.io/cms/features/content-type-builder)
  - TinaCMS — A missing required value blocks save; required and fixed options are declarative, and custom rules are a validation function you write — not on reference, object or rich-text fields. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/reference/fields](https://tina.io/docs/reference/fields)

### Entry references

How a field pointing at another entry is edited. Ranked; best answer first.

- **A picker** — A picker over the target collection.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/zero-integration](https://www.zerocms.io/features/zero-integration), [zerocms.io/features/visual-content-editor](https://www.zerocms.io/features/visual-content-editor)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/populate-a-select-input](https://cloudcannon.com/documentation/developer-articles/populate-a-select-input/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/widgets](https://decapcms.org/docs/widgets/)
  - EmDash — Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/concepts/admin-panel](https://docs.emdashcms.com/concepts/admin-panel/), [docs.emdashcms.com/reference/field-types](https://docs.emdashcms.com/reference/field-types/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/fields/relationship](https://keystatic.com/docs/fields/relationship)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/fields/reference](https://pagescms.org/docs/configuration/fields/reference/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/fields/relationship](https://payloadcms.com/docs/fields/relationship)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/reference-type](https://www.sanity.io/docs/studio/reference-type)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/fields](https://www.storyblok.com/docs/concepts/fields)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/content-manager](https://docs.strapi.io/cms/features/content-manager)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/fields/relation](https://sveltiacms.app/en/docs/fields/relation)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/reference/types/reference](https://tina.io/docs/reference/types/reference)

### Custom field controls

Whether a field's editing control can be replaced with one you write. Ranked; best answer first.

- **Yes**
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/custom-widgets](https://decapcms.org/docs/custom-widgets/)
  - Keystatic — Tested, checked 17 Sep 2026.
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/fields/overview](https://payloadcms.com/docs/fields/overview)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/form-components-reference](https://www.sanity.io/docs/studio/form-components-reference)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/plugins](https://www.storyblok.com/docs/plugins)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/api/field-types](https://sveltiacms.app/en/docs/api/field-types)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/extending-tina/custom-field-components](https://tina.io/docs/extending-tina/custom-field-components)
  - EmDash — A field's default control can be overridden with a named custom widget. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/plugins/field-kit](https://docs.emdashcms.com/plugins/field-kit/)
  - Pages CMS — Arbitrary custom field components are supported, but they compile into the app. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/guides/creating-custom-field](https://pagescms.org/docs/guides/creating-custom-field/)
  - Strapi — A custom field ships any React component as its input, but cannot be registered against a relation, media, component or dynamic-zone field. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/custom-fields](https://docs.strapi.io/cms/features/custom-fields), [docs.strapi.io/cms/plugins-development/admin-panel-api](https://docs.strapi.io/cms/plugins-development/admin-panel-api), [docs.strapi.io/cms/features/content-type-builder](https://docs.strapi.io/cms/features/content-type-builder)
- **No**
  - ZeroCMS — Every schema field gets a purpose-built built-in control; supplying a custom component for a field is not supported. Tested, checked 22 Aug 2026. [Source](https://www.zerocms.io/features/visual-content-editor)
  - CloudCannon — Twelve built-in input types, some with a choice of control (checkbox or switch, text box or range slider). Vendor documentation, checked 3 Sep 2026. Source: [cloudcannon.com/…/what-are-inputs](https://cloudcannon.com/documentation/user-articles/what-are-inputs/)

### Nested objects and arrays

How structures nested inside an entry are edited. Ranked; best answer first.

- **As structure** — Edited as fields, at any depth.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/visual-content-editor](https://www.zerocms.io/features/visual-content-editor), [zerocms.io](https://www.zerocms.io/)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/what-is-an-array-input](https://cloudcannon.com/documentation/user-articles/what-is-an-array-input/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/widgets](https://decapcms.org/docs/widgets/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/fields/object](https://keystatic.com/docs/fields/object)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/fields/block](https://pagescms.org/docs/configuration/fields/block/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/fields/overview](https://payloadcms.com/docs/fields/overview)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/object-type](https://www.sanity.io/docs/studio/object-type)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/blocks](https://www.storyblok.com/docs/concepts/blocks)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/content-type-builder](https://docs.strapi.io/cms/features/content-type-builder), [docs.strapi.io/cms/features/content-manager](https://docs.strapi.io/cms/features/content-manager)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/fields](https://sveltiacms.app/en/docs/fields), [sveltiacms.app/en/docs/fields/list](https://sveltiacms.app/en/docs/fields/list)
  - TinaCMS — Objects nest: an object's fields may hold another object list, worked through three levels in the docs with the innermost items picked from templates. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/types/object](https://tina.io/docs/reference/types/object), [tina.io/docs/editing/blocks](https://tina.io/docs/editing/blocks), [tina.io/docs/reference/fields](https://tina.io/docs/reference/fields)
- **As raw text** — Editable, as raw JSON or YAML.
  - EmDash — Structured fields nest one level (a custom block may hold a repeater of simple inputs); deeper structure is reachable only as raw JSON in a single-line, unvalidated JSON field. Tested, checked 17 Sep 2026.

### Variant blocks

How a field that allows several shapes is edited. Ranked; best answer first.

- **Choosable** — Adding an item offers the shapes the union allows.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/visual-content-editor](https://www.zerocms.io/features/visual-content-editor), [zerocms.io](https://www.zerocms.io/)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-an-array-input](https://cloudcannon.com/documentation/user-articles/what-is-an-array-input/), [cloudcannon.com/…/using-structures](https://cloudcannon.com/documentation/developer-guides/bookshop-astro-guide/using-structures/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/variable-type-widgets](https://decapcms.org/docs/variable-type-widgets/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/fields/conditional](https://keystatic.com/docs/fields/conditional), [keystatic.com/docs/fields/blocks](https://keystatic.com/docs/fields/blocks)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/fields/block](https://pagescms.org/docs/configuration/fields/block/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/fields/blocks](https://payloadcms.com/docs/fields/blocks)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/array-type](https://www.sanity.io/docs/studio/array-type)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/concepts/fields](https://www.storyblok.com/docs/concepts/fields), [storyblok.com/docs/concepts/blocks](https://www.storyblok.com/docs/concepts/blocks)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/content-manager](https://docs.strapi.io/cms/features/content-manager), [docs.strapi.io/cms/features/content-type-builder](https://docs.strapi.io/cms/features/content-type-builder)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/fields/list](https://sveltiacms.app/en/docs/fields/list)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/reference/types/object](https://tina.io/docs/reference/types/object)
  - EmDash — Only in rich-text fields, where the / menu picks a custom block type and each type has its own form; every custom block appears in every rich-text field, and repeater rows have no per-row type. Tested, checked 17 Sep 2026.

### Revision history

Whether earlier versions of an entry can be seen and restored. Ranked; best answer first.

- **Shown and restorable**
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/working-with-content](https://docs.emdashcms.com/guides/working-with-content/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/versions/overview](https://payloadcms.com/docs/versions/overview)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/studio/compare-document-versions](https://www.sanity.io/docs/studio/compare-document-versions), [sanity.io/docs/studio/document-actions-api](https://www.sanity.io/docs/studio/document-actions-api)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/history](https://www.storyblok.com/docs/manuals/history)
  - Strapi — A paid-tier feature that keeps versions for at most ninety days; the free edition keeps no history at all. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/content-history](https://docs.strapi.io/cms/features/content-history), [strapi.io/pricing-cms](https://strapi.io/pricing-cms)
- **Shown, not restorable** — You can see earlier versions but not roll back to one.
  - Sveltia CMS — An in-editor History panel lists an entry's commits; the diff opens on the Git provider. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor)
- **In git only** — The history is in your repository; the product does not show it.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon — Tested, checked 18 Sep 2026.
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/intro](https://decapcms.org/docs/intro/)
  - Keystatic — Tested, checked 16 Sep 2026.
  - Pages CMS — Every save is a git commit, so history lives in git; the app shows no version list, diff or restore of its own. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs](https://pagescms.org/docs/), [pagescms.org/docs/configuration/settings](https://pagescms.org/docs/configuration/settings/)
  - TinaCMS — The history is in Git and the editor only links out to it: a configurable setting says where TinaCMS sends you to view a file's source history — GitHub's commits view in the vendor's own example. Vendor documentation, checked 3 Sep 2026. Sources: [raw.githubusercontent.com/…/config.mdx](https://raw.githubusercontent.com/tinacms/tina.io/main/content/docs/reference/config.mdx), [tina.io/enterprise](https://tina.io/enterprise)

### Real-time collaboration

What happens when two people edit the same entry at once. Ranked; best answer first.

- **Merged live** — Edits from several people merge as they type.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/collaboration](https://www.zerocms.io/features/collaboration)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/content-lake/realtime-updates](https://www.sanity.io/docs/content-lake/realtime-updates), [sanity.io/docs/studio/array-type](https://www.sanity.io/docs/studio/array-type)
  - Keystatic — Real-time multiplayer editing is an experimental, opt-in Keystatic Cloud product. Vendor claim, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
- **Locked** — The entry is locked while someone has it open.
  - CloudCannon — Vendor documentation, checked 4 Sep 2026. Source: [cloudcannon.com/…/edit-your-files](https://cloudcannon.com/documentation/user-articles/edit-your-files/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/admin/locked-documents](https://payloadcms.com/docs/admin/locked-documents)
  - Storyblok — Simultaneous edits raise a conflict warning; a lock feature can hold off a second editor. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/content-authoring](https://www.storyblok.com/docs/manuals/content-authoring)
- **Warns before overwriting** — Both can edit, and the later save is warned before it overwrites the earlier.
  - EmDash — Two editors can work on the same entry; the later save warns that it will overwrite the other's changes and can go ahead. Tested, checked 17 Sep 2026.
- **Last save wins** — Both can edit, and the later save overwrites the earlier.
  - Decap CMS — Tested, checked 17 Sep 2026.
  - Sveltia CMS — Multiple editors can work at once with no locking or merge handling, so a later save overwrites an earlier one. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/workflows/simple](https://sveltiacms.app/en/docs/workflows/simple)
- **Discards unsaved edits** — Both can edit, and the first save wipes the other person's unsaved changes.
  - Pages CMS — Two accounts can edit one entry at once; when the first saves, the second editor's view silently reloads the committed file, discarding their unsaved edits with no notice. Tested, checked 16 Sep 2026.
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Strapi — Nothing in Strapi's documentation describes what happens when two people open the same entry at once.
  - TinaCMS — Nothing describes two editors in one entry; the docs establish only that several people can save to the same repository.

### Conflict handling

What happens when the content changed between you opening and saving it. Ranked; best answer first.

- **Blocked** — The save is refused until you take the change.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/resolve-publishing-conflicts](https://cloudcannon.com/documentation/user-articles/resolve-publishing-conflicts/)
  - Keystatic — When the same entry changed under the editor, the save is refused and a new branch is required. Vendor documentation, checked 17 Sep 2026. Source: [raw.githubusercontent.com/…/updating.tsx](https://raw.githubusercontent.com/Thinkmill/keystatic/main/packages/keystatic/src/app/updating.tsx)
- **Flagged** — You are told the content changed.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/content-authoring](https://www.storyblok.com/docs/manuals/content-authoring)
- **Overwrites** — Your save replaces the newer content without warning.
  - Decap CMS — Tested, checked 17 Sep 2026.
  - Payload CMS — Tested, checked 18 Sep 2026.
  - Sveltia CMS — There is no conflict detection: a baseline that moved under an open editor is neither flagged nor blocked before a save. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/workflows/simple](https://sveltiacms.app/en/docs/workflows/simple)
- **Discards your edits** — Your unsaved changes are replaced by the newer content without warning.
  - Pages CMS — A commit made on GitHub while an entry is open is pulled into the editor, replacing the open content and discarding unsaved edits without notice. Tested, checked 16 Sep 2026.
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - EmDash — Edits save straight to the database with no staging baseline; no stale-change detection is documented.
  - Sanity — Editors share one live draft through merged real-time patches, and no separate stale-baseline warning or block is documented.
  - Strapi — Nothing in Strapi's documentation says what happens when an entry is saved under another editor's open change; releases publish the latest saved draft rather than the version added to them.
  - TinaCMS — Nothing in TinaCMS's documentation describes what happens when the branch has moved under an open editor.

### Editorial comments

Whether reviewers can leave comments on the content. Ranked; best answer first.

- **Threads on fields** — A thread on a field, resolvable.
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/visual-editor](https://www.storyblok.com/docs/manuals/visual-editor)
  - Sanity — Field-level comments, resolvable; a paid feature on the Growth plan. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/comments](https://www.sanity.io/docs/studio/comments)
- **No** — Email.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/review-and-merge-a-pull-request](https://cloudcannon.com/documentation/developer-articles/review-and-merge-a-pull-request/), [cloudcannon.com/…/editing-sessions-and-collaboration](https://cloudcannon.com/documentation/user-guides/editing-in-cloudcannon/editing-sessions-and-collaboration/), [cloudcannon.com/…/save-your-changes](https://cloudcannon.com/documentation/user-articles/save-your-changes/), [cloudcannon.com/…/what-is-the-publishing-page](https://cloudcannon.com/documentation/user-articles/what-is-the-publishing-page/)
  - Decap CMS, EmDash — Tested, checked 17 Sep 2026.
  - Keystatic — Tested, checked 16 Sep 2026.
  - Payload CMS — Tested, checked 18 Sep 2026.
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/editorial-workflow](https://tina.io/editorial-workflow), [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow), [tina.io/docs/tinacloud](https://tina.io/docs/tinacloud), [tina.io/pricing](https://tina.io/pricing)
  - Pages CMS — In-content comments are an announced but unreleased feature. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Sveltia CMS
  - Strapi — Strapi documents review workflows and per-entry assignees, but nothing on its pages says whether an editor can leave a comment on an entry.

### Localization

How translations of the same entry are handled. Ranked; best answer first.

- **Translation workflow** — Linked locales, plus tracking of what still needs translating.
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/internationalization](https://www.storyblok.com/docs/concepts/internationalization)
- **Linked locales** — The product knows one entry is a translation of another.
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/i18n](https://decapcms.org/docs/i18n/)
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/internationalization](https://docs.emdashcms.com/guides/internationalization/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/configuration/localization](https://payloadcms.com/docs/configuration/localization)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/i18n](https://sveltiacms.app/en/docs/i18n), [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor)
  - Sanity — Localization stores a language field; the recommended document-internationalization plugin relates translations as references. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/localization](https://www.sanity.io/docs/studio/localization)
  - Strapi — Each locale publishes on its own, and only one can be edited at a time. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/internationalization](https://docs.strapi.io/cms/features/internationalization)
- **Untracked** — Translations are just separate entries.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Keystatic, Pages CMS — Tested, checked 16 Sep 2026.
  - CloudCannon — The tool their docs pair with CloudCannon translates tagged strings in the finished site as a postbuild step, not entries. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-internationalization](https://cloudcannon.com/documentation/developer-articles/what-is-internationalization/), [cloudcannon.com/…/what-is-rosey](https://cloudcannon.com/documentation/developer-guides/add-internationalization-with-rosey/what-is-rosey/)
  - TinaCMS — Under directory-based localization, a second locale is a separate document whose filename puts it in a locale sub-folder; nothing ties the copies together. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/guides/internationalization](https://tina.io/docs/guides/internationalization), [tina.io/docs/guides/nextjs-internationalization](https://tina.io/docs/guides/nextjs-internationalization)

### Content checks

Automated checks the product runs over content. Ranked; best answer first.

- **SEO, accessibility, readability, writing style, broken links, broken content, content consistency, GEO**
  - ZeroCMS — The audits cover content-level issues an editor can fix, not a WCAG or Lighthouse audit of your templates. Tested and documented, checked 1 Sep 2026. Source: [zerocms.io/features/audits-and-checks](https://www.zerocms.io/features/audits-and-checks)
- **Nothing**
  - CloudCannon, Payload CMS — Tested, checked 18 Sep 2026.
  - Decap CMS — Tested, checked 17 Sep 2026.
  - Keystatic — Tested, checked 16 Sep 2026.
  - EmDash — An SEO panel sets title, description and OG fields but does not score or lint content. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/querying-content](https://docs.emdashcms.com/guides/querying-content/)
  - Pages CMS — Pages CMS validates individual fields but ships no content checks such as SEO, readability or broken links. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/content/fields](https://pagescms.org/docs/configuration/content/fields/)
  - Sanity — Beyond schema field validation, there are no built-in content audits such as SEO, readability or link checks. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/validation](https://www.sanity.io/docs/studio/validation)
  - Storyblok — Beyond schema field validation, there are no built-in content audits; SEO is a separate app. Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/concepts/fields](https://www.storyblok.com/docs/concepts/fields), [storyblok.com/docs/manuals/ai-assistance](https://www.storyblok.com/docs/manuals/ai-assistance)
  - Strapi — Strapi ships no SEO tooling of its own: the original strapi-plugin-seo repository was archived and SEO analysis now comes from a community fork, and Strapi does not generate sitemaps natively. Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/blog/strapi-seo-plugins](https://strapi.io/blog/strapi-seo-plugins), [docs.strapi.io/…/installing-plugins-via-marketplace](https://docs.strapi.io/cms/plugins/installing-plugins-via-marketplace), [docs.strapi.io/cms/features/review-workflows](https://docs.strapi.io/cms/features/review-workflows)
  - Sveltia CMS — Sveltia validates individual fields but ships no content checks such as SEO, readability or broken links. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/fields](https://sveltiacms.app/en/docs/fields)
  - TinaCMS — They publish an AI content-freshness audit, but it runs as a GitHub Action and raises issues rather than holding anything. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/guides/content-auditing-github-actions](https://tina.io/docs/guides/content-auditing-github-actions)

### Check enforcement

Whether a failed check blocks publishing. Ranked; best answer first.

- **Your choice** — You decide which checks block.
  - ZeroCMS — An admin can make checks automatic pre-publish rather than on-demand; warnings can be overridden, errors must be addressed or dismissed. Tested, checked 1 Sep 2026. [Source](https://www.zerocms.io/features/audits-and-checks)
- **Does not apply**
  - CloudCannon, Decap CMS, EmDash, Keystatic, Pages CMS, Payload CMS, Sanity, Storyblok, Strapi, Sveltia CMS, TinaCMS

### Custom checks

Whether you can add checks of your own. Ranked; best answer first.

- **In plain language** — You write your own checks as written instructions.
  - ZeroCMS — Tested and documented, checked 1 Sep 2026. Source: [zerocms.io/features/audits-and-checks](https://www.zerocms.io/features/audits-and-checks)
- **Does not apply**
  - CloudCannon, Decap CMS, EmDash, Keystatic, Pages CMS, Payload CMS, Sanity, Storyblok, Strapi, Sveltia CMS, TinaCMS

### Check scope

How much of the site a single check can look at. Ranked; best answer first.

- **The whole site** — A check sees the whole site.
  - ZeroCMS — Tested and documented, checked 1 Sep 2026. Source: [zerocms.io/features/audits-and-checks](https://www.zerocms.io/features/audits-and-checks)
- **Does not apply**
  - CloudCannon, Decap CMS, EmDash, Keystatic, Pages CMS, Payload CMS, Sanity, Storyblok, Strapi, Sveltia CMS, TinaCMS

## Preview

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Preview renderer | Astro dev server | Astro build output | The CMS renders it | A server you run | No preview | No preview | You implement it | You implement it | You implement it | You implement it | The CMS renders it | A server you run |
| Preview updates | Hot reload | Re-rendered in the browser | Re-rendered in the browser | Not tested | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Re-rendered in the browser | Region re-render |
| Preview trigger | **As you type** | **As you type** | On save | **As you type** | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | **As you type** | **As you type** |
| Preview latency | **Under ten seconds** | **Under ten seconds** | **Under ten seconds** | **Under ten seconds** | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | **Under ten seconds** | **Under ten seconds** |
| Shareable preview links | **Yes** | **Yes** | **Yes** | **Yes** | Does not apply | Does not apply | No | Not tested | Not tested | No | No | **Yes** |

### Preview renderer

What renders the page the editor sees.

- **You implement it** — You build the preview yourself.
  - Payload CMS — Payload ships React and Vue helpers for the live-preview bridge; an Astro site wires up the subscription itself. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/live-preview/overview](https://payloadcms.com/docs/live-preview/overview), [payloadcms.com/docs/live-preview/client](https://payloadcms.com/docs/live-preview/client)
  - Sanity — The Presentation tool loads the customer's own frontend app in an iframe with visual-editing overlays; the customer builds, hosts and sets the preview URL. Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/…/configuring-the-presentation-tool](https://www.sanity.io/docs/visual-editing/configuring-the-presentation-tool), [sanity.io/docs/visual-editing/astro-visual-editing](https://www.sanity.io/docs/visual-editing/astro-visual-editing)
  - Storyblok — The visual editor loads the customer's own site in an iframe with the Storyblok Bridge for live editing; the customer builds, hosts and points at the preview URL. Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/concepts/visual-editor](https://www.storyblok.com/docs/concepts/visual-editor), [storyblok.com/docs/guides/astro/visual-preview](https://www.storyblok.com/docs/guides/astro/visual-preview)
  - Strapi — The preview link points at a route on your own front end, and the documented example implementation is Next.js, with a pointer to Nuxt's own preview docs. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/preview](https://docs.strapi.io/cms/features/preview)
- **The CMS renders it** — The CMS draws the page with its own renderer, not your site's code.
  - Decap CMS — The preview is Decap's own render, not the built Astro site, so Astro components and layouts are not reflected. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/customization](https://decapcms.org/docs/customization/), [decapcms.org/docs/architecture](https://decapcms.org/docs/architecture/)
  - Sveltia CMS — The preview is Sveltia's own render of the entry, not the built Astro site, so Astro components and layouts are not reflected. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/api/field-types](https://sveltiacms.app/en/docs/api/field-types)
- **A server you run** — Your own server renders the page, through a route they supply.
  - EmDash — EmDash supplies the preview middleware; the customer's own Astro SSR deployment renders the draft on each request. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/preview](https://docs.emdashcms.com/guides/preview/)
  - TinaCMS — Your own Astro server re-renders the preview at request time, and only sections wrapped in a TinaIsland refresh as you type. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro)
- **No preview**
  - Keystatic — previewUrl opens draft mode, but a save to main is already live and a branch save ships only by merging in GitHub. Tested, checked 17 Sep 2026.
  - Pages CMS — The editor never shows the rendered site; the flow goes from editing straight to a commit. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs](https://pagescms.org/docs/), [pagescms.org/docs/configuration/fields/rich-text](https://pagescms.org/docs/configuration/fields/rich-text/)
- **Astro build output** — Your real Astro build, served once it finishes.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/confirm-your-output-urls](https://cloudcannon.com/documentation/developer-guides/set-up-visual-editing/confirm-your-output-urls/)
- **Astro dev server** — Your real Astro site, running as it does in development.
  - ZeroCMS — Tested and documented, checked 23 Aug 2026. Source: [zerocms.io/features/live-preview](https://www.zerocms.io/features/live-preview)

### Preview updates

How your changes reach the preview.

- **Re-rendered in the browser** — The changed region renders again in the page, not on a server.
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/customization](https://decapcms.org/docs/customization/)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/api/field-types](https://sveltiacms.app/en/docs/api/field-types)
  - CloudCannon — The changed region renders again, without saving — but in the browser, so components must be registered and must run client-side. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/an-overview-of-editable-regions](https://cloudcannon.com/documentation/developer-guides/set-up-visual-editing/an-overview-of-editable-regions/), [cloudcannon.com/…/visually-edit-components](https://cloudcannon.com/documentation/developer-guides/set-up-visual-editing/visually-edit-components/), [cloudcannon.com/…/component-templating](https://cloudcannon.com/documentation/developer-guides/bookshop-astro-guide/component-templating/), [cloudcannon.com/…/what-is-the-visual-editor](https://cloudcannon.com/documentation/user-articles/what-is-the-visual-editor/)
- **Hot reload** — The framework's own hot module reload.
  - ZeroCMS — Tested, checked 23 Aug 2026.
- **Region re-render** — Only the changed region is rendered again.
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro)
- **Does not apply**
  - Keystatic, Pages CMS, Payload CMS, Sanity, Storyblok, Strapi
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - EmDash

### Preview trigger

What makes the preview update. Ranked; best answer first.

- **As you type**
  - ZeroCMS — Tested, checked 23 Aug 2026.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-the-visual-editor](https://cloudcannon.com/documentation/user-articles/what-is-the-visual-editor/), [cloudcannon.com/…/what-is-visual-editing](https://cloudcannon.com/documentation/developer-guides/set-up-visual-editing/what-is-visual-editing/)
  - EmDash — Tested, checked 17 Sep 2026.
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro)
- **On save**
  - Decap CMS — Tested, checked 17 Sep 2026.
- **Does not apply**
  - Keystatic, Pages CMS, Payload CMS, Sanity, Storyblok, Strapi

### Preview latency

How long a change takes to appear in the preview. Ranked; best answer first.

- **Under ten seconds**
  - ZeroCMS — Tested and documented, checked 23 Aug 2026. Source: [zerocms.io/features/live-preview](https://www.zerocms.io/features/live-preview)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-the-visual-editor](https://cloudcannon.com/documentation/user-articles/what-is-the-visual-editor/), [cloudcannon.com/…/what-is-visual-editing](https://cloudcannon.com/documentation/developer-guides/set-up-visual-editing/what-is-visual-editing/)
  - EmDash — Tested, checked 17 Sep 2026.
  - Decap CMS — No latency figure is published; the preview is described as real-time. Vendor claim, checked 3 Sep 2026. Source: [decapcms.org/docs/intro](https://decapcms.org/docs/intro/)
  - Sveltia CMS — The pane shows a real-time preview as you type; no latency figure is published. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor)
  - TinaCMS — The docs say field changes appear in the preview as you type: each update is POSTed to an endpoint that re-renders the matching Astro component and swaps the HTML into the live DOM. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/…/astro-react-free-visual-editing](https://tina.io/docs/migrations/astro-react-free-visual-editing), [tina.io/docs/contextual-editing/astro](https://tina.io/docs/contextual-editing/astro)
- **Does not apply**
  - Keystatic, Pages CMS, Payload CMS, Sanity, Storyblok, Strapi

### Shareable preview links

Whether a preview can be shared and opened without an account. Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested and documented, checked 23 Aug 2026. Source: [zerocms.io/features/live-preview](https://www.zerocms.io/features/live-preview)
  - Decap CMS — Tested, checked 17 Sep 2026.
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/preview](https://docs.emdashcms.com/guides/preview/)
  - CloudCannon — Every site gets a free .cloudvent.net testing domain, which can be password-protected. Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/what-is-a-testing-domain](https://cloudcannon.com/documentation/user-articles/what-is-a-testing-domain/)
  - TinaCMS — The shared link is a branch deploy on your own host (Netlify, Vercel, AWS), returned by a previewUrl function you add to your config. Vendor claim, checked 3 Sep 2026. Sources: [tina.io/editorial-workflow](https://tina.io/editorial-workflow), [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow)
- **No**
  - Payload CMS — Both preview surfaces are Admin Panel surfaces, and Payload documents no public share link; its draft-preview route authenticates the user. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/live-preview/overview](https://payloadcms.com/docs/live-preview/overview), [payloadcms.com/docs/admin/preview](https://payloadcms.com/docs/admin/preview)
  - Strapi — The "Copy preview link" button copies the admin-panel preview URL, which needs an admin login and content-manager read permission; the front-end route is one you implement yourself. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/preview](https://docs.strapi.io/cms/features/preview), [raw.githubusercontent.com/…/PreviewHeader.tsx](https://raw.githubusercontent.com/strapi/strapi/main/packages/core/content-manager/admin/src/preview/components/PreviewHeader.tsx), [raw.githubusercontent.com/…/routes.tsx](https://raw.githubusercontent.com/strapi/strapi/main/packages/core/content-manager/admin/src/preview/routes.tsx), [raw.githubusercontent.com/…/Preview.tsx](https://raw.githubusercontent.com/strapi/strapi/main/packages/core/content-manager/admin/src/preview/pages/Preview.tsx)
  - Sveltia CMS — The preview is a pane inside the signed-in editor; the only shareable link is a deploy preview built by the Git host's CI on the pull request. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor), [sveltiacms.app/en/docs/workflows/deploy-previews](https://sveltiacms.app/en/docs/workflows/deploy-previews)
- **Does not apply**
  - Keystatic, Pages CMS
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Storyblok
  - Sanity — The previewed page is the customer's own hosted site, so whether it opens without a login depends on their deployment, not on Sanity.

## Media

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Media library | Images, Video | **Images, Documents, Video** | **Images, Video, Documents** | **Images, Video, Documents** | Images, Documents | **Images, Video, Documents** | **Images, Video, Documents** | **Images, Video, Documents** | **Images, Video, Documents** | **Images, Video, Documents** | **Images, Video, Documents** | **Images, Video, Documents** |
| Media storage | Your repository | Your repository, Your bucket, Third-party DAM | Your repository, Third-party DAM | Your bucket | Your repository, Vendor CDN | Your repository | Your bucket | Vendor CDN | Vendor CDN | Vendor CDN, Your bucket, Third-party DAM | Your repository, Your bucket, Third-party DAM | Your repository, Vendor CDN, Your bucket, Third-party DAM |
| Image transformations | Optimized by Astro | Optimized by Astro, Sizes cut on upload | No variants | Transformed on request | Transformed on request | No variants | Sizes cut on upload | Transformed on request | Transformed on request | Sizes cut on upload | No variants | No variants |

### Media library

A media library allows users to upload, browse, and select images and videos. Ranked; best answer first.

- **Images, Documents, Video**
  - EmDash — Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/guides/media-library](https://docs.emdashcms.com/guides/media-library/), [docs.emdashcms.com/deployment/storage](https://docs.emdashcms.com/deployment/storage/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/upload/overview](https://payloadcms.com/docs/upload/overview)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/content-lake/assets](https://www.sanity.io/docs/content-lake/assets)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/assets](https://www.storyblok.com/docs/concepts/assets)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/media-library](https://docs.strapi.io/cms/features/media-library)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/ui/asset-library](https://sveltiacms.app/en/docs/ui/asset-library)
  - CloudCannon — There is no video-specific input or preview: video goes through the generic File input and File Browser, and their docs steer large files to external storage. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/documentation/user-articles/add-a-file](https://cloudcannon.com/documentation/user-articles/add-a-file/), [cloudcannon.com/…/the-file-browser](https://cloudcannon.com/documentation/user-articles/the-file-browser/), [cloudcannon.com/…/what-is-a-file-input](https://cloudcannon.com/documentation/user-articles/what-is-a-file-input/)
  - Decap CMS — The image widget handles images; the file widget uploads any other file type into the same media library. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/widgets](https://decapcms.org/docs/widgets/)
  - Pages CMS — The file field takes any type — documents, video, audio — not images alone. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/media](https://pagescms.org/docs/configuration/media/), [pagescms.org/docs/configuration/fields/file](https://pagescms.org/docs/configuration/fields/file/)
  - TinaCMS — Repo-based media cannot be renamed through the Media Manager or replaced in place, and there is no Git LFS support. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/media/repo-based](https://tina.io/docs/reference/media/repo-based), [tina.io/docs/reference/types/image](https://tina.io/docs/reference/types/image), [tina.io/docs/faq](https://tina.io/docs/faq)
- **Images, Documents**
  - Keystatic — Core has per-field image and file pickers; a browsable image library exists only in Keystatic Cloud. Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/fields/image](https://keystatic.com/docs/fields/image), [keystatic.com/docs/fields/file](https://keystatic.com/docs/fields/file), [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
- **Images, Video**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/media-library](https://www.zerocms.io/features/media-library), [zerocms.io/features/file-browser](https://www.zerocms.io/features/file-browser)

### Media storage

Storage locations for uploaded media files.

- **Your bucket** — Your bucket: Held in object storage you own.
  - EmDash — Uploads go to a storage backend the customer configures, including the local filesystem. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/deployment/storage](https://docs.emdashcms.com/deployment/storage/)
  - Payload CMS — Files land on your own server by default, or in a bucket you own through an official storage adapter. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/upload/storage-adapters](https://payloadcms.com/docs/upload/storage-adapters), [payloadcms.com/docs/upload/overview](https://payloadcms.com/docs/upload/overview)
- **Your repository, Your bucket, Third-party DAM** — Your repository: Committed alongside the content. Your bucket: Held in object storage you own. Third-party DAM: Held in a separate asset manager.
  - CloudCannon — The repository is the default, and their own documentation warns against keeping large assets there. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/documentation/user-articles/add-a-file](https://cloudcannon.com/documentation/user-articles/add-a-file/), [cloudcannon.com/…/what-is-a-file-input](https://cloudcannon.com/documentation/user-articles/what-is-a-file-input/), [cloudcannon.com/…/introduction-to-assets-and-dams](https://cloudcannon.com/documentation/developer-articles/introduction-to-assets-and-dams/)
  - Sveltia CMS — Uploads commit to the repository by default; S3-compatible buckets you own and DAMs like Cloudinary or Uploadcare are alternatives. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/media](https://sveltiacms.app/en/docs/media)
- **Your repository** — Your repository: Committed alongside the content.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/media-library](https://www.zerocms.io/features/media-library), [zerocms.io/features/zero-integration](https://www.zerocms.io/features/zero-integration), [zerocms.io/features/visual-content-editor](https://www.zerocms.io/features/visual-content-editor)
  - Pages CMS — Uploads are committed to the repository; external buckets (S3, R2) are an announced but unreleased feature. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/media](https://pagescms.org/docs/configuration/media/), [pagescms.org](https://pagescms.org/)
- **Vendor CDN** — Vendor CDN: Held and served by the vendor.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/apis-and-sdks/asset-cdn](https://www.sanity.io/docs/apis-and-sdks/asset-cdn)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/assets](https://www.storyblok.com/docs/concepts/assets)
- **Your repository, Vendor CDN, Your bucket, Third-party DAM** — Your repository: Committed alongside the content. Vendor CDN: Held and served by the vendor. Your bucket: Held in object storage you own. Third-party DAM: Held in a separate asset manager.
  - TinaCMS — The repository is the default and its files are mirrored to Tina's own CDN; an external provider replaces that rather than joining it. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/media/overview](https://tina.io/docs/reference/media/overview), [tina.io/docs/reference/media/repo-based](https://tina.io/docs/reference/media/repo-based), [tina.io/docs/reference/media/external/authentication](https://tina.io/docs/reference/media/external/authentication), [tina.io/docs/reference/media/external/s3](https://tina.io/docs/reference/media/external/s3), [tina.io/docs/reference/media/external/do-spaces](https://tina.io/docs/reference/media/external/do-spaces), [tina.io/docs/reference/media/external/cloudinary](https://tina.io/docs/reference/media/external/cloudinary)
- **Vendor CDN, Your bucket, Third-party DAM** — Vendor CDN: Held and served by the vendor. Your bucket: Held in object storage you own. Third-party DAM: Held in a separate asset manager.
  - Strapi — Files land on your own server by default, on Strapi's own storage with the hosted service, or in a bucket or asset library you own. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/media-library](https://docs.strapi.io/cms/features/media-library), [docs.strapi.io/…/media-library-providers](https://docs.strapi.io/cms/configurations/media-library-providers), [docs.strapi.io/cloud/advanced/upload](https://docs.strapi.io/cloud/advanced/upload), [docs.strapi.io/cloud/getting-started/usage-billing](https://docs.strapi.io/cloud/getting-started/usage-billing), [strapi.io/pricing-cloud](https://strapi.io/pricing-cloud)
- **Your repository, Third-party DAM** — Your repository: Committed alongside the content. Third-party DAM: Held in a separate asset manager.
  - Decap CMS — Uploads are committed to the repository by default; Cloudinary is an external media-library option. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/), [decapcms.org/docs/cloudinary](https://decapcms.org/docs/cloudinary/)
- **Your repository, Vendor CDN** — Your repository: Committed alongside the content. Vendor CDN: Held and served by the vendor.
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/fields/image](https://keystatic.com/docs/fields/image), [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)

### Image transformations

How images are resized and optimized for the page.

- **No variants**
  - Decap CMS — Uploads are referenced by a static public path, so they never reach astro:assets. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/)
  - Pages CMS — Pages CMS writes the file and rewrites its path but performs no resizing, format conversion or variant generation. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/media](https://pagescms.org/docs/configuration/media/), [pagescms.org/docs/configuration/fields/image](https://pagescms.org/docs/configuration/fields/image/)
  - Sveltia CMS — Sveltia optimizes an image to WebP but cuts no variants, deferring responsive sizes to the framework's own build. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/media](https://sveltiacms.app/en/docs/media)
  - TinaCMS — Files are committed to the repository but referenced by a Tina CDN URL, so Astro sees a remote image, and no documented path produces variants. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/media/repo-based](https://tina.io/docs/reference/media/repo-based), [tina.io/docs/reference/media/external/authentication](https://tina.io/docs/reference/media/external/authentication)
- **Transformed on request** — Transformed on request: Resized by a service when the page asks for it.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/apis-and-sdks/image-urls](https://www.sanity.io/docs/apis-and-sdks/image-urls)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/assets](https://www.storyblok.com/docs/concepts/assets)
  - EmDash — An image endpoint EmDash installs resizes on request — on Cloudflare Workers through the IMAGES binding, over the media in your own bucket. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/guides/media-library](https://docs.emdashcms.com/guides/media-library/), [docs.emdashcms.com/deployment/cloudflare](https://docs.emdashcms.com/deployment/cloudflare/)
  - Keystatic — Keystatic Cloud Images transforms images via URL query parameters. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
- **Sizes cut on upload** — Sizes cut on upload: Fixed sizes generated when the file is uploaded.
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/upload/overview](https://payloadcms.com/docs/upload/overview)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/media-library](https://docs.strapi.io/cms/features/media-library)
- **Optimized by Astro** — Optimized by Astro: Astro's own astro:assets pipeline, at build time.
  - ZeroCMS — Tested, checked 22 Aug 2026.
- **Optimized by Astro, Sizes cut on upload** — Optimized by Astro: Astro's own astro:assets pipeline, at build time. Sizes cut on upload: Fixed sizes generated when the file is uploaded.
  - CloudCannon — Uploads default to the Git repository rather than a vendor CDN, so an uploaded image is an ordinary project file; a DAM is the opt-in way to store assets outside the repo. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/documentation/user-articles/add-a-file](https://cloudcannon.com/documentation/user-articles/add-a-file/), [cloudcannon.com/…/introduction-to-assets-and-dams](https://cloudcannon.com/documentation/developer-articles/introduction-to-assets-and-dams/), [cloudcannon.com/…/configure-a-file-input](https://cloudcannon.com/documentation/developer-articles/configure-a-file-input/)

## Publishing and review

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Publish target | A commit | A commit, A pull request | A commit, A pull request, A branch | The vendor's store | A commit, A branch, A pull request | A commit | The vendor's store | The vendor's store | Not tested | The vendor's store | A commit, A pull request, A branch | A commit, A branch, A pull request |
| Review before publish | **Line by line** | **Line by line** | Entry level only | No | No | No | **Line by line** | **Line by line** | Not tested | Entry level only | Entry level only | Entry level only |
| Drafts | **Real drafts** | A flag in the content | **Real drafts** | **Real drafts** | **Real drafts** | No | **Real drafts** | **Real drafts** | **Real drafts** | **Real drafts** | **Real drafts** | A flag in the content |
| Selective publish | **Yes** | No | **Yes** | **Yes** | **Yes** | No | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | No |
| Scheduled publishing | No | No | No | **Yes** | No | No | **Yes** | **Yes** | **Yes** | **Yes** | No | No |
| Author attribution | **Yes** | **Yes** | **Yes** | **Yes** | Not tested | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** |

### Publish target

Defines where published content lands.

- **A commit, A pull request, A branch** — A commit: A commit is created and pushed to your repository. A pull request: Opened as a pull request for review. A branch: A branch is created for each change.
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Sources: [raw.githubusercontent.com/…/updating.tsx](https://raw.githubusercontent.com/Thinkmill/keystatic/main/packages/keystatic/src/app/updating.tsx), [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode), [raw.githubusercontent.com/…/en-US.json](https://raw.githubusercontent.com/Thinkmill/keystatic/main/packages/keystatic/src/app/l10n/en-US.json)
  - Decap CMS — Simple mode commits straight to the configured branch; editorial workflow opens a branch and pull request per entry. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/backends-overview](https://decapcms.org/docs/backends-overview/), [decapcms.org/docs/editorial-workflows](https://decapcms.org/docs/editorial-workflows/)
  - Sveltia CMS — Simple workflow commits straight to the configured branch; editorial workflow opens a branch and pull request per entry. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/workflows/simple](https://sveltiacms.app/en/docs/workflows/simple), [sveltiacms.app/en/docs/workflows/editorial](https://sveltiacms.app/en/docs/workflows/editorial)
  - TinaCMS — Saving commits straight to the branch by default; the editorial workflow adds a branch and a draft pull request, on Business and Enterprise only. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/git-co-authoring](https://tina.io/docs/tinacloud/git-co-authoring), [tina.io/docs/faq](https://tina.io/docs/faq), [tina.io/docs/tinacloud/deployment-options/vercel](https://tina.io/docs/tinacloud/deployment-options/vercel), [tina.io/docs/tinacloud/overview](https://tina.io/docs/tinacloud/overview), [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow), [tina.io/editorial-workflow](https://tina.io/editorial-workflow)
- **The vendor's store** — The vendor's store: Saved to the vendor's database.
  - EmDash — Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/why-emdash](https://docs.emdashcms.com/why-emdash/), [docs.emdashcms.com/concepts/content-model](https://docs.emdashcms.com/concepts/content-model/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/versions/drafts](https://payloadcms.com/docs/versions/drafts), [payloadcms.com/docs/versions/overview](https://payloadcms.com/docs/versions/overview), [payloadcms.com/docs/database/overview](https://payloadcms.com/docs/database/overview)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/content-lake/drafts](https://www.sanity.io/docs/content-lake/drafts)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/configurations/database](https://docs.strapi.io/cms/configurations/database), [docs.strapi.io/cms/features/draft-and-publish](https://docs.strapi.io/cms/features/draft-and-publish)
- **A commit** — A commit: A commit is created and pushed to your repository.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Pages CMS — Saves commit straight to the branch you are on. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs](https://pagescms.org/docs/), [pagescms.org/docs/configuration/settings](https://pagescms.org/docs/configuration/settings/)
- **A commit, A pull request** — A commit: A commit is created and pushed to your repository. A pull request: Opened as a pull request for review.
  - CloudCannon — Saving is what commits your changes to your Git repository; publishing is a separate second step that sends those changes to the Site's assigned Publish Branch. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/save-your-changes](https://cloudcannon.com/documentation/user-articles/save-your-changes/), [cloudcannon.com/…/what-are-publishing-methods](https://cloudcannon.com/documentation/user-articles/what-are-publishing-methods/), [cloudcannon.com/…/what-is-publishing](https://cloudcannon.com/documentation/user-articles/what-is-publishing/)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Storyblok

### Review before publish

Can you see what changed before publishing? Ranked; best answer first.

- **Line by line** — A full diff of the changes about to be published.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/review-and-publish](https://www.zerocms.io/features/review-and-publish)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/versions/overview](https://payloadcms.com/docs/versions/overview), [payloadcms.com/docs/versions/drafts](https://payloadcms.com/docs/versions/drafts)
  - CloudCannon — A line-by-line diff per file before saving; at publish time you get a file list and a link out to your Git host. Vendor documentation, checked 3 Sep 2026. Sources: [cloudcannon.com/…/save-your-configuration-file](https://cloudcannon.com/documentation/developer-guides/getting-started-with-cloudcannon/save-your-configuration-file/), [cloudcannon.com/…/publishing-conflict-resolution-domains-rework-and-more](https://cloudcannon.com/documentation/changelog/2025/05/13/publishing-conflict-resolution-domains-rework-and-more/), [cloudcannon.com/…/what-is-the-publishing-page](https://cloudcannon.com/documentation/user-articles/what-is-the-publishing-page/), [cloudcannon.com/…/publishing-your-changes](https://cloudcannon.com/documentation/user-guides/editing-in-cloudcannon/publishing-your-changes/)
  - Sanity — Version comparison highlights changed fields; richer inline diff annotations come from Advanced Version Control. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/compare-document-versions](https://www.sanity.io/docs/studio/compare-document-versions)
- **Entry level only** — You are told an entry changed, without being shown what.
  - Decap CMS — The editorial-workflow interface tracks unpublished entries by status; the change goes through a pull request on the git host. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/editorial-workflows](https://decapcms.org/docs/editorial-workflows/)
  - Strapi — An entry is marked as modified, and the history screen lists a single version's fields rather than a comparison of two. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/draft-and-publish](https://docs.strapi.io/cms/features/draft-and-publish), [docs.strapi.io/cms/features/content-history](https://docs.strapi.io/cms/features/content-history)
  - Sveltia CMS — Status badges and an Unpublished Entries list flag that an entry changed; the line-by-line diff lives on the Git provider, not in the CMS. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/workflows/editorial](https://sveltiacms.app/en/docs/workflows/editorial), [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor)
  - TinaCMS — Tina links out from the branch list modal to a preview of the branch and to the pull request on GitHub, where the change is merged. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow), [tina.io/editorial-workflow](https://tina.io/editorial-workflow), [tina.io/roadmap](https://tina.io/roadmap)
- **No** — There's no way to see exactly what changed.
  - Keystatic — Tested, checked 16 Sep 2026.
  - EmDash — Changes to published content take effect on save; there is no staged changeset to diff before publishing. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/working-with-content](https://docs.emdashcms.com/guides/working-with-content/)
  - Pages CMS — Editing goes straight to a commit, with no in-product diff. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs](https://pagescms.org/docs/)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Storyblok

### Drafts

Whether unfinished work can be saved without publishing. Ranked; best answer first.

- **Real drafts** — An entry can stay unpublished, be previewed, and be found again.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/review-and-publish](https://www.zerocms.io/features/review-and-publish), [zerocms.io/pricing](https://www.zerocms.io/pricing), [zerocms.io](https://www.zerocms.io/), [zerocms.io/features/live-preview](https://www.zerocms.io/features/live-preview), [zerocms.io/changelog](https://www.zerocms.io/changelog), [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent)
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/working-with-content](https://docs.emdashcms.com/guides/working-with-content/)
  - Keystatic — Tested, checked 16 Sep 2026.
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/versions/drafts](https://payloadcms.com/docs/versions/drafts)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/content-lake/drafts](https://www.sanity.io/docs/content-lake/drafts), [sanity.io/…/presenting-and-previewing-content](https://www.sanity.io/docs/content-lake/presenting-and-previewing-content)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/manuals/content-authoring](https://www.storyblok.com/docs/manuals/content-authoring), [storyblok.com/docs/guides/astro](https://www.storyblok.com/docs/guides/astro)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/draft-and-publish](https://docs.strapi.io/cms/features/draft-and-publish), [docs.strapi.io/cms/features/preview](https://docs.strapi.io/cms/features/preview)
  - Decap CMS — Editorial workflow adds unpublished draft states across the content publishing phases. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/), [decapcms.org/docs/editorial-workflows](https://decapcms.org/docs/editorial-workflows/)
  - Sveltia CMS — True unpublished drafts persist and are listed, but only under the editorial workflow on the GitHub and GitLab backends. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/workflows/editorial](https://sveltiacms.app/en/docs/workflows/editorial), [sveltiacms.app/en/docs/backends](https://sveltiacms.app/en/docs/backends)
- **A flag in the content** — A draft flag the site is expected to honour.
  - CloudCannon — Unsaved edits persist across sessions and save file by file, but they are shared and any teammate can commit them. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/save-your-changes](https://cloudcannon.com/documentation/user-articles/save-your-changes/), [cloudcannon.com/…/edit-your-files](https://cloudcannon.com/documentation/user-articles/edit-your-files/)
  - TinaCMS — Either implement a draft field of your own, or use the editorial, pull-request based workflow, which is Business and Enterprise only. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/drafts/overview](https://tina.io/docs/drafts/overview), [tina.io/docs/drafts/drafts-fields](https://tina.io/docs/drafts/drafts-fields), [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow)
- **No** — Every save is a publish.
  - Pages CMS — Every save is an immediate commit; there is no staging layer. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs](https://pagescms.org/docs/), [pagescms.org/docs/configuration/settings](https://pagescms.org/docs/configuration/settings/)

### Selective publish

Is it possible to publish only some of the changes? Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/review-and-publish](https://www.zerocms.io/features/review-and-publish)
  - Keystatic — Tested, checked 16 Sep 2026.
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/versions/drafts](https://payloadcms.com/docs/versions/drafts)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/user-guides/content-releases](https://www.sanity.io/docs/user-guides/content-releases)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/content-authoring](https://www.storyblok.com/docs/manuals/content-authoring)
  - Decap CMS — In editorial workflow each entry is its own branch and pull request, so pending entries can be held while others publish. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/editorial-workflows](https://decapcms.org/docs/editorial-workflows/)
  - EmDash — Publishing is per locale — one locale can go live while another stays draft. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/internationalization](https://docs.emdashcms.com/guides/internationalization/)
  - Strapi — Entry by entry, or several at once from the list view; Releases additionally batch entries across content types and locales, and need the Growth or Enterprise plan. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/releases](https://docs.strapi.io/cms/features/releases), [docs.strapi.io/cms/features/draft-and-publish](https://docs.strapi.io/cms/features/draft-and-publish)
  - Sveltia CMS — In editorial workflow each entry is its own branch and pull request, so pending entries can be held while others publish. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/workflows/editorial](https://sveltiacms.app/en/docs/workflows/editorial)
- **No**
  - CloudCannon — Publishing moves everything saved on the branch; the choosing happens earlier, when you pick which files to save. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/publish-changes-to-a-publish-branch](https://cloudcannon.com/documentation/user-articles/publish-changes-to-a-publish-branch/), [cloudcannon.com/…/publishing-your-changes](https://cloudcannon.com/documentation/user-guides/editing-in-cloudcannon/publishing-your-changes/), [cloudcannon.com/…/saving-your-changes](https://cloudcannon.com/documentation/user-guides/editing-in-cloudcannon/saving-your-changes/)
  - Pages CMS — Each save commits its own entry immediately, so there is no pile of pending changes to hold some of back from. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs](https://pagescms.org/docs/)
  - TinaCMS — Everything saved on a working branch ships together when its pull request is merged. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow), [tina.io/docs/tinacloud/deployment-options/vercel](https://tina.io/docs/tinacloud/deployment-options/vercel)

### Scheduled publishing

Whether a publish can be set to happen later. Ranked; best answer first.

- **Yes**
  - EmDash — On Cloudflare Workers a cron trigger is required to release scheduled content. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/working-with-content](https://docs.emdashcms.com/guides/working-with-content/)
  - Payload CMS — Needs the jobs queue configured, and something running it. Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/versions/drafts](https://payloadcms.com/docs/versions/drafts)
  - Sanity — Scheduled publishing of single documents and grouped Content Releases both hold and release on a clock. Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/studio/scheduled-drafts](https://www.sanity.io/docs/studio/scheduled-drafts), [sanity.io/docs/user-guides/content-releases](https://www.sanity.io/docs/user-guides/content-releases)
  - Storyblok — Scheduling and releases are paid features. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/content-authoring](https://www.storyblok.com/docs/manuals/content-authoring)
  - Strapi — Through releases, which require the Growth or Enterprise plan. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/releases](https://docs.strapi.io/cms/features/releases), [docs.strapi.io/cms/features/draft-and-publish](https://docs.strapi.io/cms/features/draft-and-publish)
- **No**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/), [decapcms.org/docs/editorial-workflows](https://decapcms.org/docs/editorial-workflows/)
  - Keystatic — Tested, checked 16 Sep 2026.
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/drafts/overview](https://tina.io/docs/drafts/overview), [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow), [tina.io/editorial-workflow](https://tina.io/editorial-workflow), [tina.io/docs/tinacloud/deployment-options/vercel](https://tina.io/docs/tinacloud/deployment-options/vercel)
  - CloudCannon — What can be scheduled is a build: a `_schedule.txt` file, which their Jekyll plugin generates from future-dated posts, or a one-off build set in the CloudCannon UI. Vendor documentation, checked 1 Sep 2026. Sources: [cloudcannon.com/…/scheduling-your-next-build-automatically](https://cloudcannon.com/documentation/developer-articles/scheduling-your-next-build-automatically/), [cloudcannon.com/…/scheduling-your-builds-manually](https://cloudcannon.com/documentation/developer-articles/scheduling-your-builds-manually/)
  - Pages CMS — Scheduled publishing is an announced but unreleased feature. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - Sveltia CMS — Publishing is an immediate commit; there is no scheduled or timed publish. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/workflows/simple](https://sveltiacms.app/en/docs/workflows/simple)

### Author attribution

Is published content recorded under the editor's own name? Ranked; best answer first.

- **Yes**
  - CloudCannon — Vendor documentation, checked 4 Sep 2026. Sources: [cloudcannon.com/…/configure-your-commit-messages](https://cloudcannon.com/documentation/developer-articles/configure-your-commit-messages/), [cloudcannon.com/…/configure-the-commit-details-for-clients](https://cloudcannon.com/documentation/developer-articles/configure-the-commit-details-for-clients/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/github-backend](https://decapcms.org/docs/github-backend/), [decapcms.org/docs/open-authoring](https://decapcms.org/docs/open-authoring/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/versions/overview](https://payloadcms.com/docs/versions/overview)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/content-lake/realtime-updates](https://www.sanity.io/docs/content-lake/realtime-updates)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/history](https://www.storyblok.com/docs/manuals/history)
  - ZeroCMS — Changes an external agent makes through the MCP server are attributed to the user who authorized it. Tested, checked 22 Aug 2026.
  - EmDash — Entries record the creating user; EmDash uses real per-user accounts, not a shared bot identity. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/concepts/content-model](https://docs.emdashcms.com/concepts/content-model/), [docs.emdashcms.com/concepts/admin-panel](https://docs.emdashcms.com/concepts/admin-panel/)
  - Pages CMS — A signed-in GitHub user's commits are attributed to them. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/development/authentication](https://pagescms.org/docs/development/authentication/), [pagescms.org/docs/configuration/settings](https://pagescms.org/docs/configuration/settings/)
  - Strapi — The entry records who created and updated it, but REST omits those fields unless populateCreatorFields is activated on the content-type, and that setting is not available to the GraphQL API. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/…/populate-creator-fields](https://docs.strapi.io/cms/api/rest/guides/populate-creator-fields), [docs.strapi.io/cms/features/content-history](https://docs.strapi.io/cms/features/content-history), [docs.strapi.io/cms/features/audit-logs](https://docs.strapi.io/cms/features/audit-logs)
  - Sveltia CMS — Commits made through Sveltia are automatically GPG-signed and marked verified on GitHub. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/backends/github](https://sveltiacms.app/en/docs/backends/github)
  - TinaCMS — Off by default: a GitHub account lets an editor author the commit, or be named co-author of the bot's. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/tinacloud/git-co-authoring](https://tina.io/docs/tinacloud/git-co-authoring)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Keystatic — Keystatic's documentation does not say whose identity its commits carry, in GitHub mode or for Keystatic Cloud editors without a GitHub account.

## Governance and access

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Approval workflow | One review step | One review step | One review step | One review step | No | No | **Stages you define** | No | **Stages you define** | **Stages you define** | One review step | One review step |
| Permission granularity | Per site | Per collection | Per collection | Per organization | Everyone the same | Per site | **Per field** | Per collection | **Per field** | **Per field** | Everyone the same | Per site |
| Multi-site | **Yes** | **Yes** | **Yes** | No | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | No | **Yes** |
| White labelling | No | Some surfaces | Some surfaces | Some surfaces | Some surfaces | No | Some surfaces | Not tested | Some surfaces | **Throughout** | Some surfaces | Some surfaces |
| Audit log | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** | **Published changes only** |
| Sign-in methods | Git host, Email and password, Google, Microsoft, Magic link, Something else | Git host, Email and password, Something else | Git host, Email and password, Google | Git host, Google, Magic link, Something else | Git host | Git host, Something else | Email and password | Google, Git host, Something else | Email and password, Git host | Email and password, Google, Microsoft, Git host, Something else | Git host, Something else | Git host, Email and password |
| Email invitations | **Yes** | **Yes** | **Yes** | **Yes** | No | **Yes** | **Yes** | **Yes** | **Yes** | No | No | **Yes** |
| Single sign-on (SSO) | No | **Yes** | **Yes** | No | No | No | **Yes** | **Yes** | **Yes** | **Yes** | No | **Yes** |
| Multi-factor authentication | Your provider's | **Enforceable** | Your provider's | Your provider's | Your provider's | Your provider's | Your provider's | Your provider's | Optional | Your provider's | Your provider's | Optional |

### Approval workflow

Can someone else approve a change before it's published? Ranked; best answer first.

- **Stages you define** — Stages you define, and who may move an entry between them.
  - Payload CMS — Multi-step approval with field-level stages, advertised in vendor marketing copy. Vendor claim, checked 3 Sep 2026. Source: [payloadcms.com/enterprise/publishing-workflows](https://payloadcms.com/enterprise/publishing-workflows)
  - Storyblok — Custom workflow stages, with the roles that may edit and publish at each, are a premium feature; a fixed default workflow is otherwise available. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/workflows](https://www.storyblok.com/docs/manuals/workflows)
  - Strapi — Stages you define yourself, with the roles that may move an entry into and out of each one. An Enterprise feature. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/review-workflows](https://docs.strapi.io/cms/features/review-workflows)
- **One review step** — Request review, and hold the publish until it is granted.
  - ZeroCMS — Publishing can be gated on approval; a Business-plan feature. Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/pricing](https://www.zerocms.io/pricing)
  - CloudCannon — The diff, the comments and the approval all happen at your Git host. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/review-and-merge-a-pull-request](https://cloudcannon.com/documentation/developer-articles/review-and-merge-a-pull-request/), [cloudcannon.com/…/change-your-publishing-method](https://cloudcannon.com/documentation/developer-articles/change-your-publishing-method/), [cloudcannon.com/…/what-are-publishing-methods](https://cloudcannon.com/documentation/user-articles/what-are-publishing-methods/)
  - Decap CMS — The editorial workflow adds a drafting and review step before publishing. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/editorial-workflows](https://decapcms.org/docs/editorial-workflows/)
  - EmDash — The Contributor role needs approval to publish. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/authentication](https://docs.emdashcms.com/guides/authentication/)
  - Sveltia CMS — The editorial workflow adds a fixed draft-and-review step before publishing; GitHub and GitLab backends only. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/workflows/editorial](https://sveltiacms.app/en/docs/workflows/editorial), [sveltiacms.app/en/docs/backends](https://sveltiacms.app/en/docs/backends)
  - TinaCMS — On the Business and Enterprise plans, edits to a protected branch go through a generated draft pull request; publishing is merging it on GitHub, and Tina links out to the PR rather than showing it. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow)
- **No** — Anyone who can edit can publish.
  - Keystatic — Tested, checked 16 Sep 2026.
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs](https://pagescms.org/docs/)
  - Sanity — No built-in sign-off gate; review workflows are built by overriding the publish action with custom document actions. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/studio/document-actions-api](https://www.sanity.io/docs/studio/document-actions-api)

### Permission granularity

How finely an editor's access can be limited. Ranked; best answer first.

- **Per field**
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/roles](https://www.storyblok.com/docs/concepts/roles)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/rbac](https://docs.strapi.io/cms/features/rbac)
  - Payload CMS — Access rules are boolean-returning functions that receive the authenticated user, and can be written against a role field on users. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/access-control/fields](https://payloadcms.com/docs/access-control/fields), [payloadcms.com/docs/access-control/overview](https://payloadcms.com/docs/access-control/overview)
- **Per collection**
  - CloudCannon — Access can be scoped to collections, folders and file patterns, but custom groups start at the Team plan. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-are-custom-permission-groups](https://cloudcannon.com/documentation/developer-articles/what-are-custom-permission-groups/), [cloudcannon.com/…/permissions](https://cloudcannon.com/documentation/developer-reference/permissions/)
  - Decap CMS — Custom roles scope collections as edit, view-only or no-access; leaving the roles field blank means any logged-in user may access the CMS. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/turbo-roles-and-members](https://decapcms.org/docs/turbo-roles-and-members/), [decapcms.org/docs/choosing-a-backend](https://decapcms.org/docs/choosing-a-backend/)
  - Sanity — Custom roles scope access to GROQ-filtered content resources, an Enterprise feature. Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/…/custom-roles-and-resources](https://www.sanity.io/learn/course/introduction-to-users-and-roles/custom-roles-and-resources), [sanity.io/docs/content-lake/roles-concepts](https://www.sanity.io/docs/content-lake/roles-concepts)
- **Per site**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Pages CMS — More limited collaborators scoped per repository; there are no configurable roles, and finer control is unreleased. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/collaborators](https://pagescms.org/docs/configuration/collaborators/), [pagescms.org](https://pagescms.org/)
  - TinaCMS — Project Admin and Project Editor differ only in managing project configuration and collaborators, and both can edit project content. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/dashboard/users](https://tina.io/docs/tinacloud/dashboard/users), [tina.io/docs/tinacloud/dashboard/organizations](https://tina.io/docs/tinacloud/dashboard/organizations)
- **Per organization**
  - EmDash — Five instance-wide roles from Subscriber to Admin; access cannot differ per collection or field. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/authentication](https://docs.emdashcms.com/guides/authentication/)
- **Everyone the same** — Every editor has the same access.
  - Keystatic — Keystatic Cloud grants team-level access to all projects. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
  - Sveltia CMS — Sveltia has no user or role system; every authorized editor has the same access, and who can reach the repository is the Git host's to control. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro)

### Multi-site

Can a single account manage several sites? Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/multi-site](https://www.zerocms.io/features/multi-site)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/documentation/user-glossary](https://cloudcannon.com/documentation/user-glossary/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org](https://pagescms.org/), [pagescms.org/docs/quick-start](https://pagescms.org/docs/quick-start/)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/…/projects-organizations-and-billing](https://www.sanity.io/docs/platform-management/projects-organizations-and-billing)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/organizations](https://www.storyblok.com/docs/manuals/organizations)
  - Decap CMS — One organization owns many sites; a self-hosted install is one repository and config per site. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/turbo-how-it-works](https://decapcms.org/docs/turbo-how-it-works/)
  - Payload CMS — Through the official multi-tenant plugin, which scopes documents and list views to a tenant. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/plugins/multi-tenant](https://payloadcms.com/docs/plugins/multi-tenant), [payloadcms.com/docs/plugins/overview](https://payloadcms.com/docs/plugins/overview)
  - Strapi — Separate websites are separate projects, each needing its own instance and licence, and on the hosted service its own per-project subscription. Vendor documentation, checked 3 Sep 2026. Sources: [support.strapi.io/…/2990044364-understanding-the-definition-of-a-strapi-project](https://support.strapi.io/articles/2990044364-understanding-the-definition-of-a-strapi-project), [docs.strapi.io/cloud/projects/overview](https://docs.strapi.io/cloud/projects/overview), [strapi.io/pricing-cloud](https://strapi.io/pricing-cloud)
  - TinaCMS — Every plan carries one project, so a second site is a second subscription. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/dashboard/organizations](https://tina.io/docs/tinacloud/dashboard/organizations), [tina.io/docs/tinacloud/dashboard/projects](https://tina.io/docs/tinacloud/dashboard/projects), [tina.io/pricing](https://tina.io/pricing)
- **No**
  - EmDash — EmDash embeds per Astro project as a single deployment; no organization or multi-site management layer is documented. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/concepts/architecture](https://docs.emdashcms.com/concepts/architecture/), [docs.emdashcms.com/why-emdash](https://docs.emdashcms.com/why-emdash/)
  - Sveltia CMS — Each admin instance binds to one repository, and there is no account or dashboard spanning several sites. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro), [sveltiacms.app/en/docs/backends/github](https://sveltiacms.app/en/docs/backends/github)

### White labelling

Can the CMS be branded with your own logo and colors? Ranked; best answer first.

- **Throughout** — Sign-in page and editor, on your own domain.
  - Strapi — The sign-in logo, the menu logo, the favicon and the colours are all replaceable, on your own domain — the logos by upload in the admin panel, the favicon and theme by editing configuration. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/admin-panel-customization/logos](https://docs.strapi.io/cms/admin-panel-customization/logos), [docs.strapi.io/cms/admin-panel-customization/favicon](https://docs.strapi.io/cms/admin-panel-customization/favicon), [docs.strapi.io/…/theme-extension](https://docs.strapi.io/cms/admin-panel-customization/theme-extension), [docs.strapi.io/cms/features/admin-panel](https://docs.strapi.io/cms/features/admin-panel), [docs.strapi.io/cloud/projects/settings](https://docs.strapi.io/cloud/projects/settings)
- **Some surfaces** — Some surfaces carry your branding and some do not.
  - CloudCannon — Badge, logo and accent colour reach inside the app, and the Partner Program brands each client; clients reaching a headless Site by its .cloudvent.net link are forwarded to app.cloudcannon.com/update. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/customize-your-organization-branding](https://cloudcannon.com/documentation/user-articles/customize-your-organization-branding/), [cloudcannon.com/…/what-is-client-sharing](https://cloudcannon.com/documentation/user-articles/what-is-client-sharing/)
  - Decap CMS — The login-page and header logo can be replaced. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/configuration-options](https://decapcms.org/docs/configuration-options/)
  - EmDash — Your logo, name and favicon on sign-in and admin; the /_emdash/admin URL, the sidebar version line and some messages still say EmDash. Tested, checked 17 Sep 2026.
  - Keystatic — The Admin UI's brand name and logo mark are configurable; the GitHub sign-in is not branded. Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/user-interface](https://keystatic.com/docs/user-interface), [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode)
  - Payload CMS — The admin UI's logo is replaceable, including on the login view; a custom domain is not documented. Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/custom-components/root-components](https://payloadcms.com/docs/custom-components/root-components)
  - Storyblok — Enterprise can replace the in-app logo, and organizations can serve the editor on a custom domain; the sign-in page's own branding is not separately documented. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/organizations](https://www.storyblok.com/docs/manuals/organizations)
  - Sveltia CMS — The logo and app title are replaceable, but a “Powered by Sveltia CMS” line stays on the login page. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/customization](https://sveltiacms.app/en/docs/customization)
  - TinaCMS — The editor sits on your own domain and the project name shown at sign-in is yours to set, but editors sign in to TinaCloud. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/using-tina-editor](https://tina.io/docs/using-tina-editor), [tina.io/docs/tinacloud/dashboard/users](https://tina.io/docs/tinacloud/dashboard/users), [tina.io/docs/tinacloud/dashboard/projects](https://tina.io/docs/tinacloud/dashboard/projects)
- **No** — The client sees the vendor's product.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Pages CMS — Tested, checked 16 Sep 2026.
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Sanity

### Audit log

Does the product keep a record of who did what? Ranked; best answer first.

- **Published changes only** — Covers what was published, and nothing else.
  - ZeroCMS — Git covers published changes, not in-product activity such as sign-ins, invites, role changes or discarded edits. Tested, checked 22 Aug 2026.
  - CloudCannon — File changes (with author, date, time and commit message), Site and branch settings changes, and syncing/output errors are logged. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/tour-your-site](https://cloudcannon.com/documentation/developer-guides/getting-started-with-cloudcannon/tour-your-site/), [cloudcannon.com/documentation/user-glossary](https://cloudcannon.com/documentation/user-glossary/), [cloudcannon.com/…/permissions](https://cloudcannon.com/documentation/developer-reference/permissions/), [cloudcannon.com/…/organizations](https://cloudcannon.com/documentation/developer-reference/api/organizations/)
  - Decap CMS — Git commit history covers published content changes. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/turbo-how-it-works](https://decapcms.org/docs/turbo-how-it-works/)
  - EmDash — A first-party audit-log plugin and invocation logging (plugin, tool, route, actor) exist; coverage of sign-ins, invites and role changes is not documented. Vendor documentation, checked 3 Sep 2026. Sources: [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash), [docs.emdashcms.com/reference/mcp-server](https://docs.emdashcms.com/reference/mcp-server/)
  - Keystatic — The Git commit history records who changed content; sign-ins, invites and role or permission changes are not logged. Tested, checked 16 Sep 2026.
  - Pages CMS — Git commit history covers published content changes, not in-product activity such as sign-ins, invites or collaborator changes. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/settings](https://pagescms.org/docs/configuration/settings/)
  - Payload CMS — Version history covers changes to documents, user records included; sign-ins and other authentication events are not documented. Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/versions/overview](https://payloadcms.com/docs/versions/overview)
  - Sanity — The Activity Feed logs project and team management events, exportable as CSV. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/platform-management/activity-feed](https://www.sanity.io/docs/platform-management/activity-feed)
  - Storyblok — Logs create, update and delete of content and configuration; sign-in coverage is not documented and the extended log is an Enterprise feature. Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/api/management/activities](https://www.storyblok.com/docs/api/management/activities), [storyblok.com/faq/what-is-extended-activity-log](https://www.storyblok.com/faq/what-is-extended-activity-log)
  - Strapi — Sign-ins, role and user changes, content and media, searchable, with each event's JSON payload readable in a modal; it needs an Enterprise plan. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/audit-logs](https://docs.strapi.io/cms/features/audit-logs), [docs.strapi.io/cms/configurations/admin-panel](https://docs.strapi.io/cms/configurations/admin-panel)
  - Sveltia CMS — Git commit history covers published content changes, but not in-product activity such as sign-ins or invites — there is no account system to log. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro)
  - TinaCMS — Git tracks every content change and, by default, attributes all of it to one bot; Tina lists audit logs among the features it does not have. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/enterprise](https://tina.io/enterprise), [tina.io/docs/faq](https://tina.io/docs/faq), [tina.io/docs/forestry/missing-forestry-features](https://tina.io/docs/forestry/missing-forestry-features)

### Sign-in methods

How editors can sign in.

- **Email and password, Git host** — Git host: Signing in with the Git host account.
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/dashboard/registration](https://tina.io/docs/tinacloud/dashboard/registration), [tina.io/docs/faq](https://tina.io/docs/faq), [tina.io/blog/two-factor-authentication](https://tina.io/blog/two-factor-authentication), [tina.io/docs/tinacloud/dashboard/projects](https://tina.io/docs/tinacloud/dashboard/projects)
  - Storyblok — Native sign-in is email or GitHub; Google, Microsoft, Okta and others arrive through SSO. Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/manuals/account](https://www.storyblok.com/docs/manuals/account), [storyblok.com/docs/concepts/sso-and-scim](https://www.storyblok.com/docs/concepts/sso-and-scim)
- **Git host, Something else** — Git host: Signing in with the Git host account.
  - Pages CMS — GitHub OAuth for repository owners, and email sign-in for invited collaborators without a GitHub account. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/quick-start](https://pagescms.org/docs/quick-start/), [pagescms.org/docs/configuration/collaborators](https://pagescms.org/docs/configuration/collaborators/), [pagescms.org](https://pagescms.org/)
  - Sveltia CMS — OAuth “Sign in with” the Git host, or a personal access token; no email, Google, Microsoft or magic-link option. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/backends](https://sveltiacms.app/en/docs/backends), [sveltiacms.app/en/docs/backends/github](https://sveltiacms.app/en/docs/backends/github)
- **Email and password**
  - Payload CMS — SAML and OAuth identity providers belong to the quote-only enterprise tier. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/authentication/overview](https://payloadcms.com/docs/authentication/overview), [payloadcms.com/docs/plugins/overview](https://payloadcms.com/docs/plugins/overview), [payloadcms.com/headless-cms-auth](https://payloadcms.com/headless-cms-auth), [payloadcms.com/enterprise/single-sign-on-sso](https://payloadcms.com/enterprise/single-sign-on-sso), [payloadcms.com/get-started](https://payloadcms.com/get-started)
- **Git host, Email and password, Google** — Git host: Signing in with the Git host account.
  - Decap CMS — Direct backends use the git-host account; the hosted sign-in adds email/password and Google. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/github-backend](https://decapcms.org/docs/github-backend/), [decapcms.org/docs/turbo-getting-started](https://decapcms.org/docs/turbo-getting-started/)
- **Git host, Email and password, Google, Microsoft, Magic link, Something else** — Git host: Signing in with the Git host account. Magic link: A sign-in link sent by email.
  - ZeroCMS — The remaining methods include a one-time emailed code, a passkey, and Google One Tap. Vendor documentation, checked 1 Sep 2026. Sources: [clerk.zerocms.io/v1/environment](https://clerk.zerocms.io/v1/environment), [zerocms.io/privacy](https://www.zerocms.io/privacy), [zerocms.io/features/access-management](https://www.zerocms.io/features/access-management)
- **Email and password, Google, Microsoft, Git host, Something else** — Git host: Signing in with the Git host account.
  - Strapi — The rest is Okta, Keycloak, Discord and any valid Passport strategy that needs no additional custom data; every provider beyond a password needs the Enterprise plan or the SSO add-on. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/configurations/guides/configure-sso](https://docs.strapi.io/cms/configurations/guides/configure-sso), [docs.strapi.io/cms/features/sso](https://docs.strapi.io/cms/features/sso), [docs.strapi.io/…/setting-up-admin-panel](https://docs.strapi.io/cms/getting-started/setting-up-admin-panel), [docs.strapi.io/cms/features/rbac](https://docs.strapi.io/cms/features/rbac), [strapi.io/pricing-cms](https://strapi.io/pricing-cms)
- **Git host, Email and password, Something else** — Git host: Signing in with the Git host account.
  - CloudCannon — The rest is SAML on the Enterprise plan, and a shared site password for clients from outside the organization. Vendor documentation, checked 4 Sep 2026. Sources: [app.cloudcannon.com](https://app.cloudcannon.com/), [app.cloudcannon.com/register](https://app.cloudcannon.com/register), [app.cloudcannon.com/users/sign_in](https://app.cloudcannon.com/users/sign_in), [cloudcannon.com/…/what-are-login-sessions](https://cloudcannon.com/documentation/user-articles/what-are-login-sessions/), [cloudcannon.com/…/create-a-cloudcannon-account](https://cloudcannon.com/documentation/user-articles/create-a-cloudcannon-account/), [cloudcannon.com/…/what-is-sso-saml](https://cloudcannon.com/documentation/developer-articles/what-is-sso-saml/), [cloudcannon.com/…/what-is-client-sharing](https://cloudcannon.com/documentation/user-articles/what-is-client-sharing/)
- **Git host** — Git host: Signing in with the Git host account.
  - Keystatic — GitHub OAuth is the documented method; Keystatic Cloud lets team members edit without a GitHub account, but the sign-in it uses is not documented. Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode), [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
- **Git host, Google, Magic link, Something else** — Git host: Signing in with the Git host account. Magic link: A sign-in link sent by email.
  - EmDash — Passkeys are the primary method; GitHub, Google and Atmosphere (AT Protocol) OAuth ship built-in, magic links are the email fallback, and providers are pluggable. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/authentication](https://docs.emdashcms.com/guides/authentication/)
- **Google, Git host, Something else** — Git host: Signing in with the Git host account.
  - Sanity — Beyond Google and GitHub, sign-in offers a native Sanity account and Vercel. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/cli-reference/login](https://www.sanity.io/docs/cli-reference/login)

### Email invitations

Whether an editor can be added by emailing them a link. Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/access-management](https://www.zerocms.io/features/access-management)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/add-a-team-member-to-your-organization](https://cloudcannon.com/documentation/user-articles/add-a-team-member-to-your-organization/)
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/authentication](https://docs.emdashcms.com/guides/authentication/)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/collaborators](https://pagescms.org/docs/configuration/collaborators/), [pagescms.org](https://pagescms.org/)
  - Payload CMS — Tested, checked 18 Sep 2026.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/cli-reference/users](https://www.sanity.io/docs/cli-reference/users)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/manuals/organizations](https://www.storyblok.com/docs/manuals/organizations), [storyblok.com/faq/can-i-whitelabel-storyblok](https://www.storyblok.com/faq/can-i-whitelabel-storyblok)
  - Decap CMS — Email invites come through the hosted Members page or Netlify Identity. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/turbo-roles-and-members](https://decapcms.org/docs/turbo-roles-and-members/), [decapcms.org/docs/choosing-a-backend](https://decapcms.org/docs/choosing-a-backend/)
  - TinaCMS — Invitations go out by email — the changelog documents invitation emails, their subject lines and project-name personalisation. Vendor documentation, checked 3 Sep 2026. Sources: [raw.githubusercontent.com/…/2026.01.3.json](https://raw.githubusercontent.com/tinacms/tina.io/main/content/whats-new-tinacloud/2026.01.3.json), [raw.githubusercontent.com/…/2026.04.3.json](https://raw.githubusercontent.com/tinacms/tina.io/main/content/whats-new-tinacloud/2026.04.3.json), [raw.githubusercontent.com/…/2026.04.4.json](https://raw.githubusercontent.com/tinacms/tina.io/main/content/whats-new-tinacloud/2026.04.4.json)
- **No**
  - Keystatic — Tested, checked 16 Sep 2026.
  - Strapi — Inviting an administrator creates the account and produces a sign-in link, which you then have to deliver to them yourself. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/rbac](https://docs.strapi.io/cms/features/rbac)
  - Sveltia CMS — Every editor must already hold an account on the chosen Git host; there is no email-invite path. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro)

### Single sign-on (SSO)

Whether editors can sign in through your identity provider. Ranked; best answer first.

- **Yes**
  - CloudCannon — Enterprise plan only. Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/what-is-sso-saml](https://cloudcannon.com/documentation/developer-articles/what-is-sso-saml/)
  - Decap CMS — SSO/SAML is an Enterprise-tier feature. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/turbo](https://decapcms.org/turbo/)
  - Payload CMS — Advertised on the enterprise tier and documented nowhere. Vendor claim, checked 3 Sep 2026. Sources: [payloadcms.com/enterprise/single-sign-on-sso](https://payloadcms.com/enterprise/single-sign-on-sso), [payloadcms.com/security](https://payloadcms.com/security), [payloadcms.com/enterprise](https://payloadcms.com/enterprise)
  - Sanity — A SAML SSO feature available on Enterprise plans. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/developer-guides/sso-saml](https://www.sanity.io/docs/developer-guides/sso-saml)
  - Storyblok — SSO with SCIM user provisioning; a Premium and Elite feature. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/sso-and-scim](https://www.storyblok.com/docs/concepts/sso-and-scim)
  - Strapi — Advertised as SAML 2.0 in the SSO add-on's pricing description, though the setup documentation covers only OpenID and OAuth; an Enterprise plan or a paid add-on either way. Vendor claim, checked 3 Sep 2026. Sources: [strapi.io/features/single-sign-on-sso](https://strapi.io/features/single-sign-on-sso), [strapi.io/pricing-cms](https://strapi.io/pricing-cms), [docs.strapi.io/cms/features/sso](https://docs.strapi.io/cms/features/sso), [docs.strapi.io/cms/configurations/guides/configure-sso](https://docs.strapi.io/cms/configurations/guides/configure-sso)
  - TinaCMS — Advertised on the enterprise tier as SAML and OIDC with Okta, Entra ID and Google Workspace. Vendor claim, checked 3 Sep 2026. Sources: [tina.io/enterprise](https://tina.io/enterprise), [tina.io/pricing](https://tina.io/pricing)
- **No**
  - ZeroCMS — Tested, checked 23 Aug 2026.
  - EmDash — No native SAML; SSO can be added by fronting the deployment with Cloudflare Access. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/authentication](https://docs.emdashcms.com/guides/authentication/)
  - Keystatic — The Cloud plans enumerate Free and Pro by users and price only; no SAML or enterprise SSO tier appears anywhere. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
  - Pages CMS — The supported auth is a GitHub App and Better Auth; the environment lists no SAML or SSO option. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/development/environment-variables](https://pagescms.org/docs/development/environment-variables/)
  - Sveltia CMS — The only sign-in methods are Git-host OAuth and access tokens; any SSO would come from the Git host, not Sveltia. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/backends](https://sveltiacms.app/en/docs/backends), [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro)

### Multi-factor authentication

Whether a second factor is offered or required. Ranked; best answer first.

- **Enforceable** — Can be required for everyone.
  - CloudCannon — An authenticator-app second factor of CloudCannon's own; requiring it across a team is a Team-plan feature. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/enforce-multi-factor-authentication](https://cloudcannon.com/documentation/developer-articles/enforce-multi-factor-authentication/), [cloudcannon.com/…/what-is-multi-factor-authentication](https://cloudcannon.com/documentation/user-articles/what-is-multi-factor-authentication/)
- **Optional** — Available, and each editor chooses.
  - Storyblok — Storyblok's own 2FA (authenticator app, SMS or email) is opt-in per user and is not enforced for GitHub sign-in. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/account](https://www.storyblok.com/docs/manuals/account)
  - TinaCMS — Each person turns on their own authenticator app; it is available for email logins, and GitHub logins take their MFA from GitHub. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/blog/two-factor-authentication](https://tina.io/blog/two-factor-authentication)
- **Your provider's** — Whatever the sign-in provider enforces.
  - ZeroCMS — Tested, checked 23 Aug 2026.
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/intro](https://decapcms.org/docs/intro/)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/cli-reference/login](https://www.sanity.io/docs/cli-reference/login), [sanity.io/docs/developer-guides/sso-saml](https://www.sanity.io/docs/developer-guides/sso-saml)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro)
  - EmDash — EmDash ships no native second factor; MFA comes from the identity provider behind Cloudflare Access. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/authentication](https://docs.emdashcms.com/guides/authentication/)
  - Keystatic — Sign-in is delegated to GitHub. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode)
  - Pages CMS — Pages CMS has no second factor of its own; GitHub users get GitHub's MFA. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/quick-start](https://pagescms.org/docs/quick-start/)
  - Payload CMS — The built-in email and password sign-in carries no second factor; one can arrive with an identity provider behind enterprise SSO. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/authentication/operations](https://payloadcms.com/docs/authentication/operations), [payloadcms.com/security](https://payloadcms.com/security), [payloadcms.com/headless-cms-auth](https://payloadcms.com/headless-cms-auth)
  - Strapi — The built-in password sign-in carries no second factor; one can only arrive with an identity provider behind paid single sign-on. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/sso](https://docs.strapi.io/cms/features/sso), [docs.strapi.io/…/setting-up-admin-panel](https://docs.strapi.io/cms/getting-started/setting-up-admin-panel), [docs.strapi.io/cms/features/rbac](https://docs.strapi.io/cms/features/rbac), [strapi.io/pricing-cms](https://strapi.io/pricing-cms), [strapi.io/blog/authentication-and-authorization](https://strapi.io/blog/authentication-and-authorization)

## Git and the repository

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Git hosts | GitHub | GitHub, GitLab, Bitbucket | **GitHub, GitLab, Bitbucket, Gitea, Forgejo, Azure DevOps** | Does not apply | GitHub | GitHub | Does not apply | Does not apply | Does not apply | Does not apply | GitHub, GitLab, Gitea, Forgejo | GitHub |
| Self-hosted Git instances | No | **Yes** | **Yes** | Does not apply | Not tested | No | Does not apply | Does not apply | Does not apply | Does not apply | **Yes** | **Yes** |
| Private repositories | **Yes** | **Yes** | **Yes** | Does not apply | **Yes** | **Yes** | Does not apply | Does not apply | Does not apply | Does not apply | **Yes** | **Yes** |
| Branch switching | **Yes** | **Yes** | No | Does not apply | **Yes** | **Yes** | Does not apply | Does not apply | Does not apply | Does not apply | No | **Yes** |
| Git account required | **No** | **No** | Yes | Does not apply | Yes | **No** | Does not apply | Does not apply | Does not apply | Does not apply | Yes | **No** |
| Write access required | **No** | **No** | Yes | Does not apply | Yes | **No** | Does not apply | Does not apply | Does not apply | Does not apply | Yes | **No** |
| Local development | No | **Yes** | **Yes** | **Yes** | **Yes** | No | **Yes** | No | No | **Yes** | **Yes** | **Yes** |

### Git hosts

Which Git hosts the product works with. Ranked; best answer first.

- **GitHub, GitLab, Bitbucket, Gitea, Forgejo, Azure DevOps**
  - Decap CMS — By design.
- **GitHub, GitLab, Gitea, Forgejo**
  - Sveltia CMS — By design.
- **GitHub, GitLab, Bitbucket**
  - CloudCannon — By design.
- **GitHub**
  - ZeroCMS, Keystatic, Pages CMS, TinaCMS — By design.
- **Does not apply**
  - EmDash — The content lives in the vendor's store, so there is no repository to ask about.
  - Payload CMS — The content lives in the vendor's store, so there is no repository to ask about.
  - Sanity — The content lives in the vendor's store, so there is no repository to ask about.
  - Storyblok — The content lives in the vendor's store, so there is no repository to ask about.
  - Strapi — The content lives in the vendor's store, so there is no repository to ask about.

### Self-hosted Git instances

Does the product work with a Git host you run yourself. Ranked; best answer first.

- **Yes**
  - CloudCannon — Self-hosted GitLab and GitHub Enterprise Server, both on the Enterprise plan. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/connecting-a-self-hosted-gitlab-repository-as-your-source](https://cloudcannon.com/documentation/developer-articles/connecting-a-self-hosted-gitlab-repository-as-your-source/), [cloudcannon.com/…/connecting-a-github-enterprise-server-repository-as-your-source](https://cloudcannon.com/documentation/developer-articles/connecting-a-github-enterprise-server-repository-as-your-source/)
  - Decap CMS — GitHub Enterprise and self-hosted GitLab and Gitea instances are supported. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/backends-overview](https://decapcms.org/docs/backends-overview/), [decapcms.org/docs/gitlab-backend](https://decapcms.org/docs/gitlab-backend/)
  - Sveltia CMS — GitHub Enterprise, self-hosted GitLab, and self-hosted Gitea/Forgejo (including Codeberg) are supported via base_url options. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/backends/github](https://sveltiacms.app/en/docs/backends/github), [sveltiacms.app/en/docs/backends/gitlab](https://sveltiacms.app/en/docs/backends/gitlab), [sveltiacms.app/en/docs/backends/gitea-forgejo](https://sveltiacms.app/en/docs/backends/gitea-forgejo)
  - TinaCMS — GitHub Enterprise Server on the Enterprise plan, and only if TinaCloud can reach it over the network. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/github-enterprise-integration](https://tina.io/docs/tinacloud/github-enterprise-integration), [tina.io/pricing](https://tina.io/pricing), [tina.io/docs/faq](https://tina.io/docs/faq)
- **No**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org](https://pagescms.org), [pagescms.org/docs/development/environment-variables](https://pagescms.org/docs/development/environment-variables/)
- **Does not apply**
  - EmDash — The content lives in the vendor's store, so there is no repository to ask about.
  - Payload CMS — The content lives in the vendor's store, so there is no repository to ask about.
  - Sanity — The content lives in the vendor's store, so there is no repository to ask about.
  - Storyblok — The content lives in the vendor's store, so there is no repository to ask about.
  - Strapi — The content lives in the vendor's store, so there is no repository to ask about.
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Keystatic — Keystatic's documentation explains connecting a GitHub repository but never says whether a self-hosted GitHub Enterprise Server instance can be used.

### Private repositories

Does the product support private repositories? Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon — Vendor claim, checked 31 Aug 2026. Sources: [cloudcannon.com/…/hugo-modules](https://cloudcannon.com/documentation/developer-guides/hugo-modules/), [cloudcannon.com/…/modules-with-site-mounting](https://cloudcannon.com/documentation/developer-guides/hugo-modules/modules-with-site-mounting/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/open-authoring](https://decapcms.org/docs/open-authoring/)
  - Keystatic, Pages CMS — Tested, checked 16 Sep 2026.
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/workflows/open](https://sveltiacms.app/en/docs/workflows/open)
  - TinaCMS — Vendor claim, checked 3 Sep 2026. Source: [tina.io/git-cms](https://tina.io/git-cms)
- **Does not apply**
  - EmDash — The content lives in the vendor's store, so there is no repository to ask about.
  - Payload CMS — The content lives in the vendor's store, so there is no repository to ask about.
  - Sanity — The content lives in the vendor's store, so there is no repository to ask about.
  - Storyblok — The content lives in the vendor's store, so there is no repository to ask about.
  - Strapi — The content lives in the vendor's store, so there is no repository to ask about.

### Branch switching

Can editors work on a branch other than the default. Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/multi-site](https://www.zerocms.io/features/multi-site)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration](https://pagescms.org/docs/configuration/)
  - CloudCannon — A site is tied to one branch, so working on another means opening that branch's own site within the project. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-the-project-browser](https://cloudcannon.com/documentation/user-articles/what-is-the-project-browser/), [cloudcannon.com/…/what-are-the-optional-project-tabs](https://cloudcannon.com/documentation/user-articles/what-are-the-optional-project-tabs/), [cloudcannon.com/…/add-a-site-to-your-project](https://cloudcannon.com/documentation/developer-articles/add-a-site-to-your-project/), [cloudcannon.com/…/create-a-branched-site](https://cloudcannon.com/documentation/user-articles/create-a-branched-site/)
  - TinaCMS — A developer sets a flag in the Tina config; switching at runtime is not available when you host the backend yourself. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/branching](https://tina.io/docs/tinacloud/branching), [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow), [tina.io/docs/faq](https://tina.io/docs/faq)
- **No**
  - Decap CMS — The config pins one branch for published content; editors do not switch working branches in the UI. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/backends-overview](https://decapcms.org/docs/backends-overview/)
  - Sveltia CMS — The working branch is fixed by the config's `branch` option; editors do not switch branches in the UI. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/backends](https://sveltiacms.app/en/docs/backends)
- **Does not apply**
  - EmDash — The content lives in the vendor's store, so there is no repository to ask about.
  - Payload CMS — The content lives in the vendor's store, so there is no repository to ask about.
  - Sanity — The content lives in the vendor's store, so there is no repository to ask about.
  - Storyblok — The content lives in the vendor's store, so there is no repository to ask about.
  - Strapi — The content lives in the vendor's store, so there is no repository to ask about.

### Git account required

Does every editor need an account on your Git host? Ranked; best answer first.

- **No**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/access-management](https://www.zerocms.io/features/access-management)
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/create-a-cloudcannon-account](https://cloudcannon.com/documentation/user-articles/create-a-cloudcannon-account/), [cloudcannon.com/…/what-is-branching](https://cloudcannon.com/documentation/user-articles/what-is-branching/)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/faq](https://tina.io/docs/faq)
  - Pages CMS — Invited collaborators edit by email with no GitHub account. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/configuration/collaborators](https://pagescms.org/docs/configuration/collaborators/), [pagescms.org](https://pagescms.org/)
- **Yes**
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro)
  - Decap CMS — The direct backends need each editor to hold a git-host account; another route removes that requirement. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/github-backend](https://decapcms.org/docs/github-backend/), [decapcms.org/docs/turbo-how-it-works](https://decapcms.org/docs/turbo-how-it-works/)
  - Keystatic — In GitHub mode every editor signs in with GitHub. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode)
- **Does not apply**
  - EmDash — The content lives in the vendor's store, so there is no repository to ask about.
  - Payload CMS — The content lives in the vendor's store, so there is no repository to ask about.
  - Sanity — The content lives in the vendor's store, so there is no repository to ask about.
  - Storyblok — The content lives in the vendor's store, so there is no repository to ask about.
  - Strapi — The content lives in the vendor's store, so there is no repository to ask about.

### Write access required

Does every editor need write access to the repository? Ranked; best answer first.

- **No**
  - ZeroCMS — Zero commits through its GitHub App installation, so editors are never repo collaborators and cost no GitHub seat. Tested, checked 22 Aug 2026.
  - CloudCannon — CloudCannon commits through the CloudCannon GitHub App installed on your account or organization; connecting the Git provider is a one-time step, and editors need no Git-provider access. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/publishing-your-changes](https://cloudcannon.com/documentation/user-guides/editing-in-cloudcannon/publishing-your-changes/), [cloudcannon.com/…/editing-in-cloudcannon](https://cloudcannon.com/documentation/user-guides/editing-in-cloudcannon/), [cloudcannon.com/…/what-is-client-sharing](https://cloudcannon.com/documentation/user-articles/what-is-client-sharing/), [cloudcannon.com/…/authenticate-your-git-provider](https://cloudcannon.com/documentation/developer-articles/authenticate-your-git-provider/), [cloudcannon.com/…/connecting-a-github-repository-as-your-source](https://cloudcannon.com/documentation/developer-articles/connecting-a-github-repository-as-your-source/)
  - Pages CMS — Collaborators write through the GitHub App installation token, so they need no personal repo write access. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/collaborators](https://pagescms.org/docs/configuration/collaborators/)
  - TinaCMS — Tina's bot commits on the repository's behalf — you can be named co-author without a GitHub account, but authoring the commit yourself, or merging the pull request, needs one. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/faq](https://tina.io/docs/faq), [tina.io/docs/tinacloud/git-co-authoring](https://tina.io/docs/tinacloud/git-co-authoring), [tina.io/docs/tinacloud/editorial-workflow](https://tina.io/docs/tinacloud/editorial-workflow)
- **Yes**
  - Decap CMS — Direct backends require repo push access; other routes remove it. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/github-backend](https://decapcms.org/docs/github-backend/), [decapcms.org/docs/git-gateway-backend](https://decapcms.org/docs/git-gateway-backend/), [decapcms.org/docs/open-authoring](https://decapcms.org/docs/open-authoring/)
  - Keystatic — Editors must be repo collaborators with write access. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/github-mode](https://keystatic.com/docs/github-mode)
  - Sveltia CMS — The direct-commit flow needs repo push access; Open Authoring is the fork-based exception. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/workflows/simple](https://sveltiacms.app/en/docs/workflows/simple), [sveltiacms.app/en/docs/workflows/open](https://sveltiacms.app/en/docs/workflows/open)
- **Does not apply**
  - EmDash — The content lives in the vendor's store, so there is no repository to ask about.
  - Payload CMS — The content lives in the vendor's store, so there is no repository to ask about.
  - Sanity — The content lives in the vendor's store, so there is no repository to ask about.
  - Storyblok — The content lives in the vendor's store, so there is no repository to ask about.
  - Strapi — The content lives in the vendor's store, so there is no repository to ask about.

### Local development

Does the product run locally with no account or cloud? Ranked; best answer first.

- **Yes**
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/installation-astro](https://keystatic.com/docs/installation-astro), [keystatic.com/docs/configuration](https://keystatic.com/docs/configuration)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/getting-started/installation](https://payloadcms.com/docs/getting-started/installation)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/installation/cli](https://docs.strapi.io/cms/installation/cli)
  - CloudCannon — A command-line dev server runs the editor against local files with no account, though it is framed as a tool for building the editing setup. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/documentation/developer-reference/cli](https://cloudcannon.com/documentation/developer-reference/cli/), [cloudcannon.com/…/build-your-editing-experience-locally-with-the-cloudcannon-dev-server](https://cloudcannon.com/blog/build-your-editing-experience-locally-with-the-cloudcannon-dev-server/)
  - Decap CMS — A local backend reads a working directory; a test backend runs with no repository at all. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/decap-proxy](https://decapcms.org/docs/decap-proxy/), [decapcms.org/docs/test-backend](https://decapcms.org/docs/test-backend/)
  - EmDash — The default setup uses a local SQLite file and local file storage, so the admin runs at localhost with no cloud service. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/getting-started](https://docs.emdashcms.com/getting-started/)
  - Sveltia CMS — A local Git folder is edited through the File System Access API (Chromium-only), or a repository-less Test backend. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/workflows/local](https://sveltiacms.app/en/docs/workflows/local), [sveltiacms.app/en/docs/backends/test](https://sveltiacms.app/en/docs/backends/test)
  - TinaCMS — Local mode reads your files straight off disk with no sign-in, and is not meant to run in production. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/faq](https://tina.io/docs/faq)
- **No**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Pages CMS — Sign-in and the GitHub App install are required; there is no offline, account-free local-file mode. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/quick-start](https://pagescms.org/docs/quick-start/)
  - Sanity — The Studio runs against a hosted project and dataset and requires a login. Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/astro/configure-sanity-astro](https://www.sanity.io/docs/astro/configure-sanity-astro), [sanity.io/docs/astro-quickstart/setting-up-your-studio](https://www.sanity.io/docs/astro-quickstart/setting-up-your-studio)
  - Storyblok — Even in local development the site fetches content from Storyblok's cloud with an access token; there is no account-free local-files mode. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/guides/astro](https://www.storyblok.com/docs/guides/astro)

## APIs and extensibility

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| REST API | None | **Wide** | None | **Wide** | None | None | **Wide** | **Wide** | **Wide** | **Wide** | None | Narrow |
| GraphQL API | None | None | None | None | None | None | **Wide** | Narrow | Narrow | **Wide** | Not tested | **Wide** |
| Webhooks | None | One corner | None | None | None | None | None | **Content events** | **Content events** | **Content events** | Not tested | **Content events** |
| CLI | None | **Maintenance and content** | Maintenance only | **Maintenance and content** | Maintenance only | None | **Maintenance and content** | **Maintenance and content** | **Maintenance and content** | **Maintenance and content** | Not tested | Maintenance only |
| Extension points | AI skills | Build hooks, Editor plugins | Custom fields, Editor plugins, Fork it | Content hooks, Custom fields, Editor plugins, Fork it | Fork it | Custom fields, Fork it | Content hooks, Custom fields, Editor plugins, Fork it | **Content hooks, Custom fields, Editor plugins, AI skills, Fork it** | Custom fields, Editor plugins | Content hooks, Custom fields, Editor plugins, Fork it | Custom fields, Editor plugins, Fork it | Custom fields, Editor plugins, Fork it |
| Third-party integrations | GitHub | **GitHub, GitLab and Bitbucket as sources, GitHub Enterprise Server and self-hosted GitLab, on the Enterprise plan, Cloudinary and Tenovos as asset libraries, Amazon S3, Cloudflare R2, Google Cloud Storage, Azure and DigitalOcean Spaces, Zapier, Make, IFTTT and Slack, Netlify, if you host the built site yourself** | Not tested | Databases — SQLite, libSQL, Cloudflare D1, PostgreSQL, Media storage — Cloudflare R2, AWS S3 or S3-compatible, local files, Sign-in — GitHub, Google, Atmosphere (AT Protocol) | GitHub, Keystatic Cloud (auth and image hosting) | GitHub, for content, auth and webhook delivery, An email provider (Resend or SMTP) for sign-in and invite mail | MongoDB, Postgres and SQLite as databases, Amazon S3, Cloudflare R2, Google Cloud Storage, Azure and Vercel Blob, Uploadthing, through an official storage adapter, Stripe and Sentry, through official plugins | **Algolia search, Cloudinary, via a plugin, Mux video, Shopify, Vercel deployments, Netlify deployments** | Cloudinary asset manager, via an app, Bynder DAM, via an app, Shopify, via an app, Slack, via an app, Vercel deployments, via an app | Amazon S3 and Cloudinary, through official upload providers, PostgreSQL, MySQL, MariaDB and SQLite as databases, Nodemailer and SendGrid, through official email providers, Sentry, through the official @strapi/plugin-sentry error-tracking plugin, Strapi Cloud, deploying from a Git branch | GitHub, GitLab and Gitea/Forgejo repositories, S3-compatible buckets and Azure Blob for external media, Cloudinary and Uploadcare as external DAMs, Lorem Picsum, Pexels, Pixabay and Unsplash stock photos, Translation via Google NMT and LLM providers | **GitHub is the only Git provider Tina ships; other hosts need your own, GitHub Enterprise Server and Cloud, on the Enterprise plan, Cloudinary, Amazon S3 and DigitalOcean Spaces, through official plugins, TinaCloud Search, the only search backend, Auth.js, the recommended auth provider, Database adapters for Vercel KV and MongoDB** |
| Content import | Nothing | Nothing | Nothing | **WordPress WXR file import, WordPress.com OAuth import, Self-hosted WordPress import by URL** | Nothing | Nothing | Import and export plugin for CSV and JSON | CLI dataset import (NDJSON) | **Storyblok CLI, Management API, Migration guides for Contentful, WordPress, AEM, Sitecore and Drupal** | strapi import (restores strapi export archives) | Netlify/Decap CMS drop-in config compatibility | Forestry migration, from its settings file, WordPress, as a guide around a third-party exporter |

### REST API

Does the product offer a REST API? Ranked; best answer first.

- **Wide** — Broad reach, including writes.
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/reference/rest-api](https://docs.emdashcms.com/reference/rest-api/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/rest-api/overview](https://payloadcms.com/docs/rest-api/overview)
  - CloudCannon — It manages organizations, projects, sites and builds. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/platform](https://cloudcannon.com/documentation/developer-reference/platform/), [cloudcannon.com/…/editing-sessions](https://cloudcannon.com/documentation/developer-reference/api/editing-sessions/), [cloudcannon.com/…/editing-session-files](https://cloudcannon.com/documentation/developer-reference/api/editing-session-files/)
  - Sanity — A query HTTP endpoint for reads and a Mutation API for writes. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/http-reference](https://www.sanity.io/docs/http-reference)
  - Storyblok — A Content Delivery API, plus a Management API that creates, edits and deletes content and configuration. Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/api/management](https://www.storyblok.com/docs/api/management), [storyblok.com/docs/api/content-delivery/v2](https://www.storyblok.com/docs/api/content-delivery/v2)
  - Strapi — A read-and-write endpoint per content type, generated from the model, and a separate token system for the administrative routes. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/api/rest](https://docs.strapi.io/cms/api/rest), [docs.strapi.io/cms/features/admin-tokens](https://docs.strapi.io/cms/features/admin-tokens)
- **Narrow** — Limited reach, or read-only.
  - TinaCMS — APIs exist for content (read-only) and search. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/dashboard/projects](https://tina.io/docs/tinacloud/dashboard/projects), [tina.io/docs/reference/content-api/content-delivery](https://tina.io/docs/reference/content-api/content-delivery)
- **None**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Keystatic — Tested, checked 16 Sep 2026.
  - Decap CMS — Decap is a client-side app that calls the git host's API and exposes no content-management API of its own. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/intro](https://decapcms.org/docs/intro/)
  - Pages CMS — Pages CMS positions itself as backend-less, and no content API of its own is documented. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - Sveltia CMS — A client-side app that calls the Git host's API directly; it exposes no content API of its own. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro), [sveltiacms.app/en/docs/privacy](https://sveltiacms.app/en/docs/privacy)

### GraphQL API

Does the product offer a GraphQL API? Ranked; best answer first.

- **Wide** — Broad reach, including writes.
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/graphql/overview](https://payloadcms.com/docs/graphql/overview)
  - Strapi — A plugin you install rather than part of the core. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/plugins/graphql](https://docs.strapi.io/cms/plugins/graphql)
  - TinaCMS — The content tokens you can issue are read-only, and the only other token type updates just the hosted search index; the contract is pre-1.0, so a minor version may break it. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud/api-versioning](https://tina.io/docs/tinacloud/api-versioning), [tina.io/docs/graphql/queries](https://tina.io/docs/graphql/queries), [tina.io/docs/graphql/queries/update-document](https://tina.io/docs/graphql/queries/update-document), [tina.io/docs/graphql/queries/add-document](https://tina.io/docs/graphql/queries/add-document), [tina.io/docs/reference/content-api/content-delivery](https://tina.io/docs/reference/content-api/content-delivery), [tina.io/docs/tinacloud/dashboard/projects](https://tina.io/docs/tinacloud/dashboard/projects)
- **Narrow** — Limited reach, or read-only.
  - Sanity — A read-only content-delivery endpoint; writes go through the Mutation API. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/content-lake/graphql](https://www.sanity.io/docs/content-lake/graphql)
  - Storyblok — A read-only content-delivery endpoint. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/api/graphql](https://www.storyblok.com/docs/api/graphql)
- **None**
  - ZeroCMS — Tested, checked 23 Aug 2026.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/documentation/developer-reference](https://cloudcannon.com/documentation/developer-reference/), [cloudcannon.com/documentation/developer-reference/api](https://cloudcannon.com/documentation/developer-reference/api/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/intro](https://decapcms.org/docs/intro/)
  - Keystatic — Tested, checked 16 Sep 2026.
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - EmDash — The documented content API is REST; no GraphQL endpoint appears in the API reference. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/reference/rest-api](https://docs.emdashcms.com/reference/rest-api/)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Sveltia CMS

### Webhooks

Can the product send webhooks to a URL you control? Ranked; best answer first.

- **Content events** — Fires when content is saved, published or built.
  - Sanity — Webhooks fire a customized HTTP request on document create, update and delete. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/content-lake/webhooks](https://www.sanity.io/docs/content-lake/webhooks)
  - Storyblok — Fires on content, asset, discussion and space-membership events. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/webhooks](https://www.storyblok.com/docs/concepts/webhooks)
  - Strapi — Entries on create, update, delete, publish and unpublish, and media on create, update and delete, posted to a URL you name. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/backend-customization/webhooks](https://docs.strapi.io/cms/backend-customization/webhooks)
  - TinaCMS — Content added, changed and removed, posted to a server you name, per branch. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/docs/tinacloud/webhooks](https://tina.io/docs/tinacloud/webhooks)
- **One corner** — Fires on part of the product, but not on content events.
  - CloudCannon — Form submissions only. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/what-is-a-form](https://cloudcannon.com/documentation/developer-articles/what-is-a-form/), [cloudcannon.com/documentation/developer-reference/api](https://cloudcannon.com/documentation/developer-reference/api/)
- **None**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Decap CMS — Tested, checked 17 Sep 2026.
  - Keystatic, Pages CMS — Tested, checked 16 Sep 2026.
  - EmDash — Plugin hooks run in-process; no outbound webhooks to customer URLs are documented. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/reference/hooks](https://docs.emdashcms.com/reference/hooks/)
  - Payload CMS — Nothing fires at a URL you register, though a server-side hook can make the outbound call itself — code you write and maintain. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/hooks/overview](https://payloadcms.com/docs/hooks/overview), [payloadcms.com/docs/hooks/collections](https://payloadcms.com/docs/hooks/collections)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Sveltia CMS

### CLI

Does the product offer a CLI? Ranked; best answer first.

- **Maintenance and content** — Reaches the content as well.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/apis-and-sdks/cli](https://www.sanity.io/docs/apis-and-sdks/cli)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/libraries/storyblok-cli](https://www.storyblok.com/docs/libraries/storyblok-cli)
  - CloudCannon — Sites, builds, orgs and inboxes, plus a config generator and local `configure` and `dev` commands that need no authentication. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/platform](https://cloudcannon.com/documentation/developer-reference/platform/), [cloudcannon.com/…/files](https://cloudcannon.com/documentation/developer-reference/cli/sites/files/), [cloudcannon.com/documentation/developer-reference/cli](https://cloudcannon.com/documentation/developer-reference/cli/)
  - EmDash — Reaches content, schema and media, not only the account or builds. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/reference/cli](https://docs.emdashcms.com/reference/cli/)
  - Payload CMS — Scaffolding, migrations and type generation are among the commands. Vendor documentation, checked 3 Sep 2026. Sources: [raw.githubusercontent.com/…/defaults.ts](https://raw.githubusercontent.com/payloadcms/payload/main/packages/payload/src/config/defaults.ts), [payloadcms.com/docs/getting-started/installation](https://payloadcms.com/docs/getting-started/installation)
  - Strapi — Content moves in bulk through export, import and transfer; no command edits a single entry. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/cli](https://docs.strapi.io/cms/cli)
- **Maintenance only** — Reaches the account, its sites and its builds, but not the content.
  - Decap CMS — decap-server is a local development proxy. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/decap-proxy](https://decapcms.org/docs/decap-proxy/)
  - Keystatic — The CLI only scaffolds a new Next.js, Astro or Remix project with Keystatic integrated; it cannot read or write content. Tested, checked 16 Sep 2026.
  - TinaCMS — A build toolchain — start, build, scaffold, index, audit, dependency check. No command authors content, though search-index uploads to TinaCloud. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/cli-overview](https://tina.io/docs/cli-overview), [tina.io/roadmap](https://tina.io/roadmap)
- **None**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - Pages CMS — Tested, checked 16 Sep 2026.
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Sveltia CMS

### Extension points

Where you can add your own code to the product. Ranked; best answer first.

- **Content hooks, Custom fields, Editor plugins, AI skills, Fork it** — Content hooks: Run your own code when content changes. Custom fields: Add your own field types to the editor. Editor plugins: Add your own UI to the editor. AI skills: Add your own instructions for the product's AI. Fork it: Change the product's own source.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/docs/functions/functions-introduction](https://www.sanity.io/docs/functions/functions-introduction), [sanity.io/docs/studio/form-components-reference](https://www.sanity.io/docs/studio/form-components-reference), [sanity.io/docs/studio](https://www.sanity.io/docs/studio), [sanity.io/…/ai-assist-working-with-instructions](https://www.sanity.io/docs/user-guides/ai-assist-working-with-instructions)
- **Content hooks, Custom fields, Editor plugins, Fork it** — Content hooks: Run your own code when content changes. Custom fields: Add your own field types to the editor. Editor plugins: Add your own UI to the editor. Fork it: Change the product's own source.
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/hooks/overview](https://payloadcms.com/docs/hooks/overview), [payloadcms.com/docs/fields/overview](https://payloadcms.com/docs/fields/overview), [payloadcms.com/compare/contentful](https://payloadcms.com/compare/contentful), [payloadcms.com/docs/custom-components/custom-views](https://payloadcms.com/docs/custom-components/custom-views), [payloadcms.com/docs/custom-components/root-components](https://payloadcms.com/docs/custom-components/root-components), [payloadcms.com/get-started](https://payloadcms.com/get-started)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/backend-customization/models](https://docs.strapi.io/cms/backend-customization/models), [docs.strapi.io/cms/features/custom-fields](https://docs.strapi.io/cms/features/custom-fields), [docs.strapi.io/cms/plugins-development/admin-panel-api](https://docs.strapi.io/cms/plugins-development/admin-panel-api), [raw.githubusercontent.com/strapi/strapi/main/LICENSE](https://raw.githubusercontent.com/strapi/strapi/main/LICENSE), [docs.strapi.io/cms/ai/for-content-managers](https://docs.strapi.io/cms/ai/for-content-managers)
  - EmDash — Plugins run in isolated Worker sandboxes with a declared capability manifest. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/reference/hooks](https://docs.emdashcms.com/reference/hooks/), [docs.emdashcms.com/plugins/field-kit](https://docs.emdashcms.com/plugins/field-kit/), [emdashcms.com](https://emdashcms.com/), [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash)
- **Custom fields, Editor plugins, Fork it** — Custom fields: Add your own field types to the editor. Editor plugins: Add your own UI to the editor. Fork it: Change the product's own source.
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/docs/custom-widgets](https://decapcms.org/docs/custom-widgets/), [decapcms.org/docs/customization](https://decapcms.org/docs/customization/), [raw.githubusercontent.com/…/LICENSE](https://raw.githubusercontent.com/decaporg/decap-cms/main/LICENSE)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/extending-tina/custom-field-components](https://tina.io/docs/extending-tina/custom-field-components), [tina.io/docs/extending-tina/overview](https://tina.io/docs/extending-tina/overview), [tina.io/docs](https://tina.io/docs), [tina.io/docs/extending-tina/before-submit](https://tina.io/docs/extending-tina/before-submit)
  - Sveltia CMS — Custom field types, editor components and preview templates in code; the MIT source can be forked. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/customization](https://sveltiacms.app/en/docs/customization)
- **Build hooks, Editor plugins** — Build hooks: Run your own code around a build. Editor plugins: Add your own UI to the editor.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/extending-your-build-process-with-hooks](https://cloudcannon.com/documentation/developer-articles/extending-your-build-process-with-hooks/), [cloudcannon.com/…/what-is-the-visual-editor-api](https://cloudcannon.com/documentation/developer-articles/what-is-the-visual-editor-api/)
- **Custom fields, Editor plugins** — Custom fields: Add your own field types to the editor. Editor plugins: Add your own UI to the editor.
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/plugins](https://www.storyblok.com/docs/plugins)
- **Custom fields, Fork it** — Custom fields: Add your own field types to the editor. Fork it: Change the product's own source.
  - Pages CMS — Custom field types are a designed seam; the whole MIT codebase can also be forked. Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/development/fields](https://pagescms.org/docs/development/fields/), [github.com/hunvreus/pagescms](https://github.com/hunvreus/pagescms)
- **AI skills** — AI skills: Add your own instructions for the product's AI.
  - ZeroCMS — Skills, knowledge and guidelines are authored in the product, in plain language. Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/audits-and-checks](https://www.zerocms.io/features/audits-and-checks), [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent), [zerocms.io/privacy](https://www.zerocms.io/privacy), [zerocms.io/features/zero-integration](https://www.zerocms.io/features/zero-integration)
- **Fork it** — Fork it: Change the product's own source.
  - Keystatic — MIT-licensed, so the whole product can be forked. Vendor documentation, checked 17 Sep 2026. Source: [raw.githubusercontent.com/…/LICENSE](https://raw.githubusercontent.com/Thinkmill/keystatic/main/LICENSE)

### Third-party integrations

Named services the product connects to. Ranked; best answer first.

- **Algolia search, Cloudinary, via a plugin, Mux video, Shopify, Vercel deployments, Netlify deployments**
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/technology-partners/cloudinary](https://www.sanity.io/technology-partners/cloudinary), [sanity.io/technology-partners/vercel](https://www.sanity.io/technology-partners/vercel), [sanity.io/technology-partners/algolia](https://www.sanity.io/technology-partners/algolia), [sanity.io/technology-partners/mux](https://www.sanity.io/technology-partners/mux), [sanity.io/technology-partners/shopify](https://www.sanity.io/technology-partners/shopify), [sanity.io/technology-partners/netlify](https://www.sanity.io/technology-partners/netlify)
- **GitHub, GitLab and Bitbucket as sources, GitHub Enterprise Server and self-hosted GitLab, on the Enterprise plan, Cloudinary and Tenovos as asset libraries, Amazon S3, Cloudflare R2, Google Cloud Storage, Azure and DigitalOcean Spaces, Zapier, Make, IFTTT and Slack, Netlify, if you host the built site yourself**
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/introduction-to-syncing](https://cloudcannon.com/documentation/developer-articles/introduction-to-syncing/), [cloudcannon.com/…/integrating-your-dam-with-cloudcannon](https://cloudcannon.com/documentation/developer-articles/integrating-your-dam-with-cloudcannon/), [cloudcannon.com/…/what-is-a-form](https://cloudcannon.com/documentation/developer-articles/what-is-a-form/), [cloudcannon.com/…/netlify-hosting-with-cloudcannon-editing](https://cloudcannon.com/documentation/developer-articles/netlify-hosting-with-cloudcannon-editing/), [cloudcannon.com/…/connecting-a-github-enterprise-server-repository-as-your-source](https://cloudcannon.com/documentation/developer-articles/connecting-a-github-enterprise-server-repository-as-your-source/), [cloudcannon.com/…/connecting-a-self-hosted-gitlab-repository-as-your-source](https://cloudcannon.com/documentation/developer-articles/connecting-a-self-hosted-gitlab-repository-as-your-source/)
- **GitHub is the only Git provider Tina ships; other hosts need your own, GitHub Enterprise Server and Cloud, on the Enterprise plan, Cloudinary, Amazon S3 and DigitalOcean Spaces, through official plugins, TinaCloud Search, the only search backend, Auth.js, the recommended auth provider, Database adapters for Vercel KV and MongoDB**
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/…/overview](https://tina.io/docs/reference/self-hosted/git-provider/overview), [tina.io/docs/tinacloud/github-enterprise-integration](https://tina.io/docs/tinacloud/github-enterprise-integration), [tina.io/docs/reference/media/external/authentication](https://tina.io/docs/reference/media/external/authentication), [tina.io/docs/reference/search/overview](https://tina.io/docs/reference/search/overview), [tina.io/…/overview](https://tina.io/docs/reference/self-hosted/auth-provider/overview), [tina.io/…/overview](https://tina.io/docs/reference/self-hosted/database-adapter/overview)
- **Amazon S3 and Cloudinary, through official upload providers, PostgreSQL, MySQL, MariaDB and SQLite as databases, Nodemailer and SendGrid, through official email providers, Sentry, through the official @strapi/plugin-sentry error-tracking plugin, Strapi Cloud, deploying from a Git branch**
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/media-library](https://docs.strapi.io/cms/features/media-library), [docs.strapi.io/cms/configurations/database](https://docs.strapi.io/cms/configurations/database), [docs.strapi.io/cms/features/email](https://docs.strapi.io/cms/features/email), [docs.strapi.io/cms/plugins/sentry](https://docs.strapi.io/cms/plugins/sentry), [docs.strapi.io/cloud/projects/settings](https://docs.strapi.io/cloud/projects/settings)
- **Cloudinary asset manager, via an app, Bynder DAM, via an app, Shopify, via an app, Slack, via an app, Vercel deployments, via an app**
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/app-store](https://www.storyblok.com/app-store)
- **GitHub, GitLab and Gitea/Forgejo repositories, S3-compatible buckets and Azure Blob for external media, Cloudinary and Uploadcare as external DAMs, Lorem Picsum, Pexels, Pixabay and Unsplash stock photos, Translation via Google NMT and LLM providers**
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/backends](https://sveltiacms.app/en/docs/backends), [sveltiacms.app/en/docs/media](https://sveltiacms.app/en/docs/media), [sveltiacms.app/en/docs/integrations/stock-photos](https://sveltiacms.app/en/docs/integrations/stock-photos), [sveltiacms.app/en/docs/integrations/translations](https://sveltiacms.app/en/docs/integrations/translations)
- **MongoDB, Postgres and SQLite as databases, Amazon S3, Cloudflare R2, Google Cloud Storage, Azure and Vercel Blob, Uploadthing, through an official storage adapter, Stripe and Sentry, through official plugins**
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/database/overview](https://payloadcms.com/docs/database/overview), [payloadcms.com/docs/upload/storage-adapters](https://payloadcms.com/docs/upload/storage-adapters), [payloadcms.com/docs/plugins/overview](https://payloadcms.com/docs/plugins/overview)
- **Databases — SQLite, libSQL, Cloudflare D1, PostgreSQL, Media storage — Cloudflare R2, AWS S3 or S3-compatible, local files, Sign-in — GitHub, Google, Atmosphere (AT Protocol)**
  - EmDash — Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/concepts/architecture](https://docs.emdashcms.com/concepts/architecture/), [docs.emdashcms.com/coming-from/astro](https://docs.emdashcms.com/coming-from/astro/), [docs.emdashcms.com/guides/authentication](https://docs.emdashcms.com/guides/authentication/)
- **GitHub, for content, auth and webhook delivery, An email provider (Resend or SMTP) for sign-in and invite mail**
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Sources: [pagescms.org/docs/guides/installing/github-app](https://pagescms.org/docs/guides/installing/github-app/), [pagescms.org/docs/development/environment-variables](https://pagescms.org/docs/development/environment-variables/)
- **GitHub, Keystatic Cloud (auth and image hosting)**
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Sources: [keystatic.com/docs/configuration](https://keystatic.com/docs/configuration), [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
- **GitHub**
  - ZeroCMS — Tested, checked 22 Aug 2026.
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Decap CMS

### Content import

Tools for bringing existing content in. Ranked; best answer first.

- **Storyblok CLI, Management API, Migration guides for Contentful, WordPress, AEM, Sitecore and Drupal**
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/cms-migration](https://www.storyblok.com/docs/concepts/cms-migration)
- **WordPress WXR file import, WordPress.com OAuth import, Self-hosted WordPress import by URL**
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/migration/content-import](https://docs.emdashcms.com/migration/content-import/)
- **Forestry migration, from its settings file, WordPress, as a guide around a third-party exporter**
  - TinaCMS — Their own note on the Forestry importer is that the migration will not be perfect. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/forestry/migrate](https://tina.io/docs/forestry/migrate), [tina.io/docs/guides/converting-wordpress-to-tina](https://tina.io/docs/guides/converting-wordpress-to-tina)
- **CLI dataset import (NDJSON)**
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/content-lake/importing-data](https://www.sanity.io/docs/content-lake/importing-data)
- **Import and export plugin for CSV and JSON**
  - Payload CMS — Batch hooks remap a foreign system's field names on the way in; migrating media is a custom script against the Local API. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/plugins/import-export](https://payloadcms.com/docs/plugins/import-export), [payloadcms.com/…/how-to-migrate-from-wordpress-to-payload](https://payloadcms.com/posts/blog/how-to-migrate-from-wordpress-to-payload)
- **Netlify/Decap CMS drop-in config compatibility**
  - Sveltia CMS — Existing Netlify/Decap configs work with a one-line script swap. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/migration/netlify-decap-cms](https://sveltiacms.app/en/docs/migration/netlify-decap-cms), [sveltiacms.app/en/docs/successor-to-netlify-cms](https://sveltiacms.app/en/docs/successor-to-netlify-cms)
- **strapi import (restores strapi export archives)**
  - Strapi — strapi import restores archives produced by strapi export — configuration, entities, relations, assets, schemas — and requires source and target schemas to match. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/features/data-management](https://docs.strapi.io/cms/features/data-management), [docs.strapi.io/cms/features/data-management/import](https://docs.strapi.io/cms/features/data-management/import)
- **Nothing**
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/introduction-to-syncing](https://cloudcannon.com/documentation/developer-articles/introduction-to-syncing/), [cloudcannon.com/…/create-a-site-with-direct-upload](https://cloudcannon.com/documentation/developer-articles/create-a-site-with-direct-upload/), [cloudcannon.com/website-migration](https://cloudcannon.com/website-migration/)
  - Decap CMS — Tested, checked 17 Sep 2026.
  - Keystatic, Pages CMS — Tested, checked 16 Sep 2026.

## AI

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| AI capabilities | **An agent** | None | None | None | None | None | AI-assisted tools | **An agent** | AI-assisted tools | AI-assisted tools | AI-assisted tools | None |
| AI context | **Content and code** | The prompt only | The prompt only | The prompt only | The prompt only | The prompt only | Undisclosed | Your content | Your content | Your content | Undisclosed | The prompt only |
| AI skills | **Yes** | No | No | No | No | No | No | **Yes** | No | No | No | No |
| MCP server | **Reads and writes** | None | None | **Reads and writes** | None | None | **Reads and writes** | **Reads and writes** | **Reads and writes** | **Reads and writes** | None | None |
| MCP transport | **Remote** | None | None | **Remote** | None | None | **Remote** | **Remote** | **Remote** | **Remote** | None | None |
| MCP authentication | OAuth | None | None | OAuth, API key | None | None | API key | OAuth, API key | OAuth, API key | API key | None | None |
| Model choice | **Yes** | No | No | No | No | No | **Yes** | No | **Yes** | Not tested | **Yes** | No |
| AI billing | In the plan, Metered | None | None | None | None | None | Undisclosed | Not tested | In the plan, Metered, Your own key | In the plan, Metered | Your own key | None |
| Trains on your content | **No** | Does not apply | Does not apply | Does not apply | Does not apply | Does not apply | Not prohibited | **No** | **No** | Not prohibited | Not prohibited | Does not apply |
| Image generation | **Yes** | No | No | No | No | No | No | **Yes** | Not tested | No | No | No |
| Other AI features | **Knowledge — brand voice, terminology and strategy the agent loads when relevant, Guidelines — standing rules, site-wide or scoped to one collection, Web search with citations while writing, PDF and image input — a brief, screenshot or mockup the agent works from, Per-user and per-organization AI credit caps, Undo for AI edits, from stored content checkpoints** | Nothing | Nothing | Nothing | Nothing | Nothing | Chunking entries into vector embeddings for RAG | Generate document content from instructions, Transform and rewrite existing content, Generate images from a prompt field | Translation of content into many languages, Alt text generated for images in the asset manager, SEO tag generation, Drafting and improving article content with AI | Building a content model from a natural-language description, Content structure extracted from a design image, a Figma project or code, Alt text, captions and tags generated for uploaded images, Entries translated into every locale when the source is saved | AI field translation via Google NMT and LLM providers | Nothing |

### AI capabilities

What the product's own AI tools or agents can do. Ranked; best answer first.

- **An agent** — A proper agent you can hand tasks to.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent)
  - Sanity — Agent Actions edit a document's fields. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/agent-actions/introduction](https://www.sanity.io/docs/agent-actions/introduction)
- **AI-assisted tools** — For example buttons that rewrite, summarize or translate.
  - Strapi — Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/ai/for-content-managers](https://docs.strapi.io/cms/ai/for-content-managers)
  - Payload CMS — Announced on the quote-only enterprise tier. Vendor claim, checked 3 Sep 2026. Sources: [payloadcms.com/enterprise/enterprise-ai](https://payloadcms.com/enterprise/enterprise-ai), [payloadcms.com/enterprise](https://payloadcms.com/enterprise)
  - Storyblok — Point tools — translation, alt text and SEO. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/ai-assistance](https://www.storyblok.com/docs/manuals/ai-assistance)
  - Sveltia CMS — The in-product AI is field translation. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/integrations/translations](https://sveltiacms.app/en/docs/integrations/translations)
- **None**
  - CloudCannon — Vendor claim, checked 31 Aug 2026. Sources: [cloudcannon.com/ai-info](https://cloudcannon.com/ai-info/), [cloudcannon.com/ai-llm-cms](https://cloudcannon.com/ai-llm-cms/)
  - Decap CMS — Tested, checked 17 Sep 2026.
  - Keystatic, Pages CMS — Tested, checked 16 Sep 2026.
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/pricing](https://tina.io/pricing), [tina.io/roadmap](https://tina.io/roadmap), [tina.io/docs/vibe-coding](https://tina.io/docs/vibe-coding)
  - EmDash — Agent-ready through the MCP server; ships no first-party AI feature of its own. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/ai-tools](https://docs.emdashcms.com/guides/ai-tools/)

### AI context

What is being passed to the AI tools or agents as context. Ranked; best answer first.

- **Content and code** — Your entries and the site's own code.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent), [zerocms.io](https://www.zerocms.io/)
- **Your content** — Your entries.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/agent-actions/introduction](https://www.sanity.io/docs/agent-actions/introduction)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/manuals/ai-assistance](https://www.storyblok.com/docs/manuals/ai-assistance), [storyblok.com/docs/api/management/stories/ai-translate](https://www.storyblok.com/docs/api/management/stories/ai-translate)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/ai/for-content-managers](https://docs.strapi.io/cms/ai/for-content-managers), [docs.strapi.io/cms/features/internationalization](https://docs.strapi.io/cms/features/internationalization)
- **The prompt only** — Only the text you send it.
  - CloudCannon — The product has no built-in AI, so this follows from that. Vendor claim, checked 31 Aug 2026.
  - Decap CMS — The product has no built-in AI, so this follows from that. Tested, checked 17 Sep 2026.
  - EmDash — The product has no built-in AI, so this follows from that. Vendor documentation, checked 3 Sep 2026.
  - Keystatic — The product has no built-in AI, so this follows from that. Tested, checked 16 Sep 2026.
  - Pages CMS — The product has no built-in AI, so this follows from that. Tested, checked 16 Sep 2026.
  - TinaCMS — The product has no built-in AI, so this follows from that. Vendor documentation, checked 3 Sep 2026.
- **Undisclosed** — The vendor does not say what the AI sees.
  - Payload CMS — Vendor claim, checked 3 Sep 2026. Source: [payloadcms.com/enterprise/enterprise-ai](https://payloadcms.com/enterprise/enterprise-ai)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/integrations/translations](https://sveltiacms.app/en/docs/integrations/translations)

### AI skills

Whether you can create custom skills the AI can use. Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/…/ai-assist-working-with-instructions](https://www.sanity.io/docs/user-guides/ai-assist-working-with-instructions)
- **No**
  - CloudCannon — Only an agent can be given skills, so this follows from the level. Vendor claim, checked 31 Aug 2026.
  - Decap CMS — Only an agent can be given skills, so this follows from the level. Tested, checked 17 Sep 2026.
  - EmDash — Only an agent can be given skills, so this follows from the level. Vendor documentation, checked 3 Sep 2026.
  - Keystatic — Only an agent can be given skills, so this follows from the level. Tested, checked 16 Sep 2026.
  - Pages CMS — Only an agent can be given skills, so this follows from the level. Tested, checked 16 Sep 2026.
  - Payload CMS — Only an agent can be given skills, so this follows from the level. Vendor claim, checked 3 Sep 2026.
  - Storyblok — Only an agent can be given skills, so this follows from the level. Vendor documentation, checked 3 Sep 2026.
  - Strapi — Only an agent can be given skills, so this follows from the level. Vendor documentation, checked 3 Sep 2026.
  - Sveltia CMS — Only an agent can be given skills, so this follows from the level. Vendor documentation, checked 3 Sep 2026.
  - TinaCMS — Only an agent can be given skills, so this follows from the level. Vendor documentation, checked 3 Sep 2026.

### MCP server

Does the product offer an MCP server? Ranked; best answer first.

- **Reads and writes** — An agent can read and write content.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/mcp-server](https://www.zerocms.io/features/mcp-server)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/plugins/mcp](https://payloadcms.com/docs/plugins/mcp)
  - EmDash — A server that reads, writes and publishes. Vendor documentation, checked 3 Sep 2026. Sources: [docs.emdashcms.com/guides/ai-tools](https://docs.emdashcms.com/guides/ai-tools/), [docs.emdashcms.com/reference/mcp-server](https://docs.emdashcms.com/reference/mcp-server/)
  - Sanity — The server can write and publish documents, not only read. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/ai/mcp-server](https://www.sanity.io/docs/ai/mcp-server)
  - Storyblok — The hosted server exposes the Management API only, not the read-only Content Delivery API. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/libraries/mcp-server](https://www.storyblok.com/docs/libraries/mcp-server)
  - Strapi — Off until it is enabled in the server configuration file. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/strapi-mcp-server](https://docs.strapi.io/cms/features/strapi-mcp-server)
- **None**
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/ai-info](https://cloudcannon.com/ai-info/), [cloudcannon.com/documentation/developer-reference](https://cloudcannon.com/documentation/developer-reference/)
  - Decap CMS — Tested, checked 17 Sep 2026.
  - Keystatic — Tested, checked 16 Sep 2026.
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/working-with-ai](https://sveltiacms.app/en/docs/working-with-ai)
  - TinaCMS — Vendor claim, checked 3 Sep 2026. Source: [tina.io/roadmap](https://tina.io/roadmap)

### MCP transport

How an agent connects to the MCP server. Ranked; best answer first.

- **Remote** — Remote: You can pass the client an URL to connect to.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Source: [zerocms.io/features/mcp-server](https://www.zerocms.io/features/mcp-server)
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/reference/mcp-server](https://docs.emdashcms.com/reference/mcp-server/)
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/plugins/mcp](https://payloadcms.com/docs/plugins/mcp)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/ai/mcp-server](https://www.sanity.io/docs/ai/mcp-server)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/libraries/mcp-server](https://www.storyblok.com/docs/libraries/mcp-server)
  - Strapi — Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/strapi-mcp-server](https://docs.strapi.io/cms/features/strapi-mcp-server)
- **None**
  - CloudCannon — There is no MCP server, so this follows from that. Vendor documentation, checked 31 Aug 2026.
  - Decap CMS — There is no MCP server, so this follows from that. Tested, checked 17 Sep 2026.
  - Keystatic — There is no MCP server, so this follows from that. Tested, checked 16 Sep 2026.
  - Pages CMS — There is no MCP server, so this follows from that. Vendor documentation, checked 3 Sep 2026.
  - Sveltia CMS — There is no MCP server, so this follows from that. Vendor documentation, checked 3 Sep 2026.
  - TinaCMS — There is no MCP server, so this follows from that. Vendor claim, checked 3 Sep 2026.

### MCP authentication

How an agent authenticates to the MCP server.

- **None**
  - CloudCannon — There is no MCP server, so this follows from that. Vendor documentation, checked 31 Aug 2026.
  - Decap CMS — There is no MCP server, so this follows from that. Tested, checked 17 Sep 2026.
  - Keystatic — There is no MCP server, so this follows from that. Tested, checked 16 Sep 2026.
  - Pages CMS — There is no MCP server, so this follows from that. Vendor documentation, checked 3 Sep 2026.
  - Sveltia CMS — There is no MCP server, so this follows from that. Vendor documentation, checked 3 Sep 2026.
  - TinaCMS — There is no MCP server, so this follows from that. Vendor claim, checked 3 Sep 2026.
- **OAuth, API key** — OAuth: The user can authorize the agent to access their account. Works with most tools such as Claude or Cursor, including their mobile apps. API key: The agent carries a key you issue.
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/ai/mcp-server](https://www.sanity.io/docs/ai/mcp-server)
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/libraries/mcp-server](https://www.storyblok.com/docs/libraries/mcp-server)
  - EmDash — Sign-in is OAuth or a personal access token minted in the admin. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/reference/mcp-server](https://docs.emdashcms.com/reference/mcp-server/)
- **API key** — API key: The agent carries a key you issue.
  - Payload CMS — An administrator mints keys in the admin panel. Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/plugins/mcp](https://payloadcms.com/docs/plugins/mcp)
  - Strapi — Each client connects with an Admin token created in the admin panel and pasted into its config. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/strapi-mcp-server](https://docs.strapi.io/cms/features/strapi-mcp-server)
- **OAuth** — OAuth: The user can authorize the agent to access their account. Works with most tools such as Claude or Cursor, including their mobile apps.
  - ZeroCMS — Each person authorizes the connection with their own account from inside their AI client, and the agent then acts as them. Tested and documented, checked 22 Aug 2026. Sources: [mcp.zerocms.io/.well-known/oauth-authorization-server](https://mcp.zerocms.io/.well-known/oauth-authorization-server), [mcp.zerocms.io/.well-known/oauth-protected-resource](https://mcp.zerocms.io/.well-known/oauth-protected-resource), [zerocms.io/features/mcp-server](https://www.zerocms.io/features/mcp-server)

### Model choice

Whether you choose which model runs. Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent), [zerocms.io/changelog](https://www.zerocms.io/changelog)
  - Payload CMS — Vendor claim, checked 3 Sep 2026. Source: [payloadcms.com/enterprise/enterprise-ai](https://payloadcms.com/enterprise/enterprise-ai)
  - Storyblok — A choice of AI model, or a connected provider of your own. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/ai-assistance](https://www.storyblok.com/docs/manuals/ai-assistance)
  - Sveltia CMS — You choose the translation service. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/integrations/translations](https://sveltiacms.app/en/docs/integrations/translations)
- **No**
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/…/install-and-configure-sanity-ai-assist](https://www.sanity.io/docs/studio/install-and-configure-sanity-ai-assist), [sanity.io/blog/sanity-ai-assist-announcement](https://www.sanity.io/blog/sanity-ai-assist-announcement)
  - CloudCannon — The product has no built-in AI, so this follows from that. Vendor claim, checked 31 Aug 2026.
  - Decap CMS — The product has no built-in AI, so this follows from that. Tested, checked 17 Sep 2026.
  - EmDash — The product has no built-in AI, so this follows from that. Vendor documentation, checked 3 Sep 2026.
  - Keystatic — The product has no built-in AI, so this follows from that. Tested, checked 16 Sep 2026.
  - Pages CMS — The product has no built-in AI, so this follows from that. Tested, checked 16 Sep 2026.
  - TinaCMS — The product has no built-in AI, so this follows from that. Vendor documentation, checked 3 Sep 2026.
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Strapi — No choice of the underlying AI model is documented.

### AI billing

How AI usage is charged.

- **None**
  - CloudCannon — The product has no built-in AI, so this follows from that. Vendor claim, checked 31 Aug 2026.
  - Decap CMS — The product has no built-in AI, so this follows from that. Tested, checked 17 Sep 2026.
  - EmDash — The product has no built-in AI, so this follows from that. Vendor documentation, checked 3 Sep 2026.
  - Keystatic — The product has no built-in AI, so this follows from that. Tested, checked 16 Sep 2026.
  - Pages CMS — The product has no built-in AI, so this follows from that. Tested, checked 16 Sep 2026.
  - TinaCMS — The product has no built-in AI, so this follows from that. Vendor documentation, checked 3 Sep 2026.
- **In the plan, Metered** — In the plan: Covered by the plan price. Metered: Charged by use.
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent), [zerocms.io/pricing](https://www.zerocms.io/pricing)
  - Strapi — Sold with the Growth plan only, and listed as not yet available on Enterprise. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/ai/for-content-managers](https://docs.strapi.io/cms/ai/for-content-managers), [strapi.io/pricing-cms](https://strapi.io/pricing-cms)
- **Your own key** — Your own key: You supply a model provider key and pay them.
  - Sveltia CMS — You supply your own API key. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/integrations/translations](https://sveltiacms.app/en/docs/integrations/translations), [sveltiacms.app/en/docs/privacy](https://sveltiacms.app/en/docs/privacy)
- **In the plan, Metered, Your own key** — In the plan: Covered by the plan price. Metered: Charged by use. Your own key: You supply a model provider key and pay them.
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/docs/manuals/ai-assistance](https://www.storyblok.com/docs/manuals/ai-assistance), [storyblok.com/legal/ai-terms-and-conditions](https://www.storyblok.com/legal/ai-terms-and-conditions)
- **Undisclosed** — Undisclosed: The vendor does not publish what the AI costs.
  - Payload CMS — Vendor claim, checked 3 Sep 2026. Source: [payloadcms.com/enterprise/enterprise-ai](https://payloadcms.com/enterprise/enterprise-ai)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Sanity

### Trains on your content

Whether your content is or can be used to train models. Ranked; best answer first.

- **No** — The terms forbid it, for every provider in the chain.
  - ZeroCMS — Vendor documentation, checked 1 Sep 2026. Source: [zerocms.io/privacy](https://www.zerocms.io/privacy)
  - Sanity — Sanity's AI Terms require every AI integration to be configured not to train on input data. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/legal/tos-ai](https://www.sanity.io/legal/tos-ai)
  - Storyblok — Storyblok's AI Terms forbid it; with a customer-connected AI provider, that provider's own terms govern instead. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/legal/ai-terms-and-conditions](https://www.storyblok.com/legal/ai-terms-and-conditions)
- **Not prohibited** — The terms neither allow training nor forbid it.
  - Payload CMS — The terms let Payload use Submitted Data to improve the Service, and say nothing about training either way. Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/cloud-terms](https://payloadcms.com/cloud-terms)
  - Strapi — The terms grant a licence over customer content and say nothing about training; the AI docs promise only non-retention, describe the processing as Strapi-managed and name no model. Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/enterprise-terms](https://strapi.io/enterprise-terms), [strapi.io/privacy](https://strapi.io/privacy), [docs.strapi.io/cms/usage-information](https://docs.strapi.io/cms/usage-information)
  - Sveltia CMS — Sveltia defers to each provider's policy; the docs warn a free-tier provider may use submitted data. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/privacy](https://sveltiacms.app/en/docs/privacy), [sveltiacms.app/en/docs/integrations/translations](https://sveltiacms.app/en/docs/integrations/translations)
- **Does not apply**
  - CloudCannon — There is no built-in AI, so there is no provider to train on anything.
  - Decap CMS — There is no built-in AI, so there is no provider to train on anything.
  - EmDash — There is no built-in AI, so there is no provider to train on anything.
  - Keystatic — There is no built-in AI, so there is no provider to train on anything.
  - Pages CMS — There is no built-in AI, so there is no provider to train on anything.
  - TinaCMS — There is no built-in AI, so there is no provider to train on anything.

### Image generation

Whether the product can generate images using AI. Ranked; best answer first.

- **Yes**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/image-generation](https://www.zerocms.io/features/image-generation), [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent)
  - Sanity — Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/…/install-and-configure-sanity-ai-assist](https://www.sanity.io/docs/studio/install-and-configure-sanity-ai-assist)
- **No**
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/…/what-is-a-file-input](https://cloudcannon.com/documentation/user-articles/what-is-a-file-input/)
  - Decap CMS — Tested, checked 17 Sep 2026.
  - Keystatic, Pages CMS — Tested, checked 16 Sep 2026.
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/ai/for-content-managers](https://docs.strapi.io/cms/ai/for-content-managers), [docs.strapi.io/cms/features/media-library](https://docs.strapi.io/cms/features/media-library)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/types/image](https://tina.io/docs/reference/types/image), [tina.io/docs/reference/media/overview](https://tina.io/docs/reference/media/overview), [tina.io/pricing](https://tina.io/pricing)
  - EmDash — Images are uploaded through the admin UI, not generated. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/ai-tools](https://docs.emdashcms.com/guides/ai-tools/)
  - Payload CMS — Announced on the enterprise tier and badged coming soon by Payload's own page, so nothing generates an image today. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/enterprise/enterprise-ai](https://payloadcms.com/enterprise/enterprise-ai), [payloadcms.com/enterprise](https://payloadcms.com/enterprise)
  - Sveltia CMS — Image support is search-and-insert of existing stock photos; there is no generative image feature. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/integrations/stock-photos](https://sveltiacms.app/en/docs/integrations/stock-photos)
- **Not tested** — We did not run this. It is not a claim that the product lacks it.
  - Storyblok

### Other AI features

AI features beyond the rows above. Ranked; best answer first.

- **Knowledge — brand voice, terminology and strategy the agent loads when relevant, Guidelines — standing rules, site-wide or scoped to one collection, Web search with citations while writing, PDF and image input — a brief, screenshot or mockup the agent works from, Per-user and per-organization AI credit caps, Undo for AI edits, from stored content checkpoints**
  - ZeroCMS — Tested and documented, checked 22 Aug 2026. Sources: [zerocms.io/features/ai-content-agent](https://www.zerocms.io/features/ai-content-agent), [zerocms.io/features/access-management](https://www.zerocms.io/features/access-management), [zerocms.io/pricing](https://www.zerocms.io/pricing), [zerocms.io/changelog](https://www.zerocms.io/changelog)
- **Translation of content into many languages, Alt text generated for images in the asset manager, SEO tag generation, Drafting and improving article content with AI**
  - Storyblok — Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/manuals/ai-assistance](https://www.storyblok.com/docs/manuals/ai-assistance)
- **Building a content model from a natural-language description, Content structure extracted from a design image, a Figma project or code, Alt text, captions and tags generated for uploaded images, Entries translated into every locale when the source is saved**
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cms/ai/for-content-managers](https://docs.strapi.io/cms/ai/for-content-managers), [docs.strapi.io/cms/features/content-type-builder](https://docs.strapi.io/cms/features/content-type-builder), [strapi.io/ai](https://strapi.io/ai)
- **Generate document content from instructions, Transform and rewrite existing content, Generate images from a prompt field**
  - Sanity — Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/…/install-and-configure-sanity-ai-assist](https://www.sanity.io/docs/studio/install-and-configure-sanity-ai-assist), [sanity.io/docs/agent-actions/introduction](https://www.sanity.io/docs/agent-actions/introduction)
- **AI field translation via Google NMT and LLM providers**
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/ui/content-editor](https://sveltiacms.app/en/docs/ui/content-editor), [sveltiacms.app/en/docs/integrations/translations](https://sveltiacms.app/en/docs/integrations/translations)
- **Chunking entries into vector embeddings for RAG**
  - Payload CMS — Vendor claim, checked 3 Sep 2026. Source: [payloadcms.com/enterprise/ai-framework](https://payloadcms.com/enterprise/ai-framework)
- **Nothing**
  - Decap CMS — Tested, checked 17 Sep 2026.
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/ai-tools](https://docs.emdashcms.com/guides/ai-tools/)
  - Keystatic, Pages CMS — Tested, checked 16 Sep 2026.
  - CloudCannon — They ship open-source agent skills — Astro migration, plus standalone configuration, snippets and visual-editing skills — but these run in your own coding agent, not in CloudCannon. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/ai-llm-cms](https://cloudcannon.com/ai-llm-cms/), [cloudcannon.com/open-source](https://cloudcannon.com/open-source/)
  - TinaCMS — They document working alongside coding agents such as Copilot and Cursor, but those run in your editor, not in TinaCMS. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/vibe-coding](https://tina.io/docs/vibe-coding), [tina.io/pricing](https://tina.io/pricing)

## Pricing

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Published price range | $15–$100/site/month | $49–$300/month | Free, or €19/month | Free | Free, or $10/month | Free | Free | $15/user/month | Free, or $99–$349/month | Free, or $35–$450/site/month | Free | Free, or $29–$299/site/month |
| Pricing model | Per site, Feature tiers, Quoted | Feature tiers, Per seat, Quoted, Per usage | Free, Free tier, Feature tiers, Per seat, Per site, Quoted | Free | Free tier, Per seat | Free | Free, Quoted | Not checked | Free tier, Feature tiers, Per seat, Per usage, Quoted | Free tier, Feature tiers, Per seat, Per site, Per usage, Quoted | Free | Free tier, Feature tiers, Per seat, Per site, Quoted |
| Additional costs | AI credits beyond the monthly quota | Additional editor seats, Bandwidth packages beyond the plan allowance, Extra custom domains, One-off website migration services | Custom/granular roles, Priority support | Your own hosting, database and media storage, A paid Cloudflare plan for sandboxed plugins | Editor seats beyond the Cloud free tier's three users | **Nothing** | Hosting for the Next.js app, A database you provide, File storage and a CDN, An email provider for auth mail | Not checked | Not checked | Editor seats beyond the plan's allowance, Single sign-on, as a paid add-on, Metered API requests, bandwidth and asset storage, Extra environments, charged per environment per month, Strapi AI credits beyond the plan's monthly allowance, Offline licensing, as a paid add-on, Premium support and advisory, Self-hosting requires your own server (CPU, RAM, disk) | Third-party media storage or DAM, if configured | Editor seats beyond the plan's allowance |
| Customer-specific plans | Agencies | Agencies, Enterprise, Non-profits | Agencies, Enterprise | None | None | None | Enterprise | Startups, Non-profits, Enterprise | Enterprise, Education, Non-profits | **Agencies, Enterprise, Non-profits, Open source** | None | Enterprise |

### Published price range

The most recent price range published by the vendor.

- **Free**
  - EmDash — Open source and self-hosted; the cost is your own hosting. Vendor documentation, checked 3 Sep 2026. Sources: [emdashcms.com](https://emdashcms.com/), [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash)
  - Pages CMS — Pages CMS is entirely free — the hosted app, a Vercel deploy and self-hosting alike; there is no paid tier. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - Payload CMS — The hosted service takes new projects from enterprise teams only; everyone else self-hosts. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/get-started](https://payloadcms.com/get-started), [payloadcms.com/new](https://payloadcms.com/new)
  - Sveltia CMS — The CMS is free; the maintainer floats an optional paid cloud version in the future but does not offer one. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro), [sveltiacms.app/en/docs/roadmap](https://sveltiacms.app/en/docs/roadmap)
- **$15/user/month**
  - Sanity — The only published paid tier is per seat; the free plan and the quote-only plan sit outside this range. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/pricing](https://www.sanity.io/pricing)
- **$15–$100/site/month**
  - ZeroCMS — By design.
- **$49–$300/month**
  - CloudCannon — Both plans also show a higher price when billed monthly; a cheaper partner-only plan sits below this range. Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/pricing](https://cloudcannon.com/pricing/)
- **Free, or $10/month**
  - Keystatic — The published figure is the Keystatic Cloud Pro base per team; extra editors are billed per seat above three. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
- **Free, or $29–$299/site/month**
  - TinaCMS — The page opens on annual-billed figures, which are lower than the monthly ones recorded here. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/pricing](https://tina.io/pricing)
- **Free, or $35–$450/site/month**
  - Strapi — The hosted plans, at the monthly prices the page shows; the self-hosted Growth plan is priced separately. Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/pricing-cloud](https://strapi.io/pricing-cloud), [docs.strapi.io/cloud/getting-started/usage-billing](https://docs.strapi.io/cloud/getting-started/usage-billing), [strapi.io/pricing-cms](https://strapi.io/pricing-cms)
- **Free, or $99–$349/month**
  - Storyblok — The monthly-billed rate for the two published paid tiers; the free Starter plan and the quote-only Premium and Elite plans sit outside this range. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/pricing](https://www.storyblok.com/pricing)
- **Free, or €19/month**
  - Decap CMS — Pro, a single-site plan, is a fixed price billed monthly in EUR. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/turbo](https://decapcms.org/turbo/), [decapcms.org](https://decapcms.org/)

### Pricing model

What the price is charged per.

- **Free** — Free: No paid plan.
  - EmDash — Open source and self-hosted; the cost is your own hosting. Vendor documentation, checked 3 Sep 2026. Sources: [emdashcms.com](https://emdashcms.com/), [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash)
  - Pages CMS — Pages CMS is entirely free — the hosted app, a Vercel deploy and self-hosting alike; there is no paid tier. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - Sveltia CMS — The CMS is free; the maintainer floats an optional paid cloud version in the future but does not offer one. Vendor documentation, checked 3 Sep 2026. Sources: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro), [sveltiacms.app/en/docs/roadmap](https://sveltiacms.app/en/docs/roadmap)
- **Free tier, Feature tiers, Per seat, Per site, Per usage, Quoted** — Free tier: A free plan you can keep using. Feature tiers: Price steps that unlock features. Quoted: A tier with no published price.
  - Strapi — The free tier is the self-hosted Community edition; Strapi Cloud's three published plans are all paid, and bill per project with metered usage on top. Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/pricing-cms](https://strapi.io/pricing-cms), [strapi.io/pricing-cloud](https://strapi.io/pricing-cloud), [docs.strapi.io/cloud/getting-started/usage-billing](https://docs.strapi.io/cloud/getting-started/usage-billing)
- **Free tier, Feature tiers, Per seat, Per site, Quoted** — Free tier: A free plan you can keep using. Feature tiers: Price steps that unlock features. Quoted: A tier with no published price.
  - TinaCMS — Every plan carries one project, and the three middle tiers publish a price per extra editor, so the bill multiplies by sites and by people at once. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/pricing](https://tina.io/pricing)
- **Free tier, Feature tiers, Per seat, Per usage, Quoted** — Free tier: A free plan you can keep using. Feature tiers: Price steps that unlock features. Quoted: A tier with no published price.
  - Storyblok — A free Starter plan, published paid plans that bill per seat with metered usage on top, and two quote-only enterprise plans. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/pricing](https://www.storyblok.com/pricing)
- **Free, Free tier, Feature tiers, Per seat, Per site, Quoted** — Free: No paid plan. Free tier: A free plan you can keep using. Feature tiers: Price steps that unlock features. Quoted: A tier with no published price.
  - Decap CMS — The open-source CMS is free; the paid tiers, seats, sites and the quoted Enterprise plan are all Decap Turbo. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org](https://decapcms.org/), [decapcms.org/turbo](https://decapcms.org/turbo/)
- **Feature tiers, Per seat, Quoted, Per usage** — Feature tiers: Price steps that unlock features. Quoted: A tier with no published price.
  - CloudCannon — Unlimited sites and repositories on the Lite, Standard, Team and Enterprise plans; bandwidth is metered against a per-plan allowance, with overages billed in the month they accrue. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/pricing](https://cloudcannon.com/pricing/), [cloudcannon.com/partner-program](https://cloudcannon.com/partner-program/)
- **Per site, Feature tiers, Quoted** — Feature tiers: Price steps that unlock features. Quoted: A tier with no published price.
  - ZeroCMS — Vendor documentation, checked 31 Aug 2026. Source: [zerocms.io/pricing](https://www.zerocms.io/pricing)
- **Free tier, Per seat** — Free tier: A free plan you can keep using.
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
- **Free, Quoted** — Free: No paid plan. Quoted: A tier with no published price.
  - Payload CMS — The hosted service takes new projects from enterprise teams only; everyone else self-hosts. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/get-started](https://payloadcms.com/get-started), [payloadcms.com/new](https://payloadcms.com/new)
- **Not checked** — We did not settle this. It is not a claim that the product lacks it.
  - Sanity

### Additional costs

What costs extra on top of the plan price. Ranked; best answer first.

- **Nothing**
  - Pages CMS — Nothing costs extra: the product is free and email collaborators are not paid GitHub seats. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
- **AI credits beyond the monthly quota**
  - ZeroCMS — Vendor documentation, checked 1 Sep 2026. Source: [zerocms.io/pricing](https://www.zerocms.io/pricing)
- **Editor seats beyond the Cloud free tier's three users**
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
- **Editor seats beyond the plan's allowance**
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Source: [tina.io/pricing](https://tina.io/pricing)
- **Third-party media storage or DAM, if configured**
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/media](https://sveltiacms.app/en/docs/media)
- **Your own hosting, database and media storage, A paid Cloudflare plan for sandboxed plugins**
  - EmDash — Vendor documentation, checked 3 Sep 2026. Source: [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash)
- **Custom/granular roles, Priority support**
  - Decap CMS — Vendor documentation, checked 17 Sep 2026. Source: [decapcms.org/turbo](https://decapcms.org/turbo/)
- **Hosting for the Next.js app, A database you provide, File storage and a CDN, An email provider for auth mail**
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/production/deployment](https://payloadcms.com/docs/production/deployment), [payloadcms.com/docs/email/overview](https://payloadcms.com/docs/email/overview)
- **Additional editor seats, Bandwidth packages beyond the plan allowance, Extra custom domains, One-off website migration services**
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/pricing](https://cloudcannon.com/pricing/)
- **Editor seats beyond the plan's allowance, Single sign-on, as a paid add-on, Metered API requests, bandwidth and asset storage, Extra environments, charged per environment per month, Strapi AI credits beyond the plan's monthly allowance, Offline licensing, as a paid add-on, Premium support and advisory, Self-hosting requires your own server (CPU, RAM, disk)**
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/pricing-cms](https://strapi.io/pricing-cms), [strapi.io/pricing-cloud](https://strapi.io/pricing-cloud), [docs.strapi.io/cms/deployment](https://docs.strapi.io/cms/deployment)
- **Not checked** — We did not settle this. It is not a claim that the product lacks it.
  - Sanity, Storyblok

### Customer-specific plans

Are plans offered for particular kinds of customers? Ranked; best answer first.

- **Agencies, Enterprise, Non-profits, Open source**
  - Strapi — The discounts for open-source and non-profit projects are applied on application rather than published as a plan. Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/pricing-cms](https://strapi.io/pricing-cms), [strapi.io/pricing-cloud](https://strapi.io/pricing-cloud), [strapi.io/discounts](https://strapi.io/discounts), [strapi.io/partner-program](https://strapi.io/partner-program)
- **Agencies, Enterprise, Non-profits**
  - CloudCannon — Vendor documentation, checked 4 Sep 2026. Sources: [cloudcannon.com/partner-program](https://cloudcannon.com/partner-program/), [cloudcannon.com/pricing](https://cloudcannon.com/pricing/), [cloudcannon.com/non-profit](https://cloudcannon.com/non-profit/)
- **Enterprise, Education, Non-profits**
  - Storyblok — Premium and Elite are quote-only; nonprofits and educational institutions get a discount. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/pricing](https://www.storyblok.com/pricing)
- **Startups, Non-profits, Enterprise**
  - Sanity — Startup and non-profit programmes, and a quote-only Enterprise plan. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/pricing](https://www.sanity.io/pricing)
- **Agencies, Enterprise**
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/turbo](https://decapcms.org/turbo/)
- **Enterprise**
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/get-started](https://payloadcms.com/get-started), [payloadcms.com/enterprise](https://payloadcms.com/enterprise), [payloadcms.com/partners](https://payloadcms.com/partners), [payloadcms.com/become-a-partner](https://payloadcms.com/become-a-partner)
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/pricing](https://tina.io/pricing), [tina.io/enterprise](https://tina.io/enterprise), [tina.io/partners](https://tina.io/partners), [tina.io/agencies](https://tina.io/agencies)
- **Agencies**
  - ZeroCMS — Vendor documentation, checked 1 Sep 2026. Sources: [zerocms.io/pricing](https://www.zerocms.io/pricing), [zerocms.io/features/multi-site](https://www.zerocms.io/features/multi-site), [zerocms.io/early-partners](https://www.zerocms.io/early-partners)
- **None**
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/cloud](https://keystatic.com/docs/cloud)
  - EmDash — No agency, enterprise or other named plan — there is no commercial offering. Vendor documentation, checked 3 Sep 2026.
  - Pages CMS — There are no paid plans at all, so none is aimed at agencies, enterprise or any other audience. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - Sveltia CMS — There are no paid plans of any kind, so none is aimed at agencies, enterprise or any other audience. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/intro](https://sveltiacms.app/en/docs/intro)

## Vendor and licence

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Licence | Proprietary | Proprietary | MIT | MIT | MIT | MIT | MIT | MIT | Proprietary | Open core | MIT | Apache 2.0 |
| Hosted service | Hosted product | Hosted product | Hosted product | No hosted product | Hosted product | Hosted product | Hosted product | Hosted product | Hosted product | Hosted product | No hosted product | Hosted product |
| Content export | **Already yours** | **Already yours** | **Already yours** | Structured export | **Already yours** | **Already yours** | Structured export | Structured export | Structured export | Structured export | **Already yours** | **Already yours** |
| Asset export | **Already yours** | **Already yours** | **Already yours** | Your own bucket | **Already yours** | **Already yours** | Your own bucket | Bulk export | Bulk export | Bulk export | **Already yours** | **Already yours** |
| Vendor | Neatbit Oy | CloudCannon Limited | PM, poslovni mediji d.o.o. | Cloudflare, Inc. | Thinkmill Labs Pty Ltd | Ronan Berder | Payload CMS, Inc. | Sanity | Storyblok GmbH | Strapi, Inc. | A community project | SSW |
| Product history | None | None | 1 event | None | None | None | 3 events | Not checked | Not checked | 3 events | 1 event | 5 events |
| Headquarters | Finland | New Zealand | Slovenia | United States | Australia | Singapore | United States | United States | Austria | United States | Does not apply | Australia |
| Support channels | Email | **Email, Live chat, Dedicated contact** | **Email, Dedicated contact, SLA** | Community only | Not checked | Community only | Dedicated contact | Dedicated contact, SLA | Live chat, Dedicated contact | **Email, Dedicated contact, SLA** | Community only | Email, Dedicated contact |
| Data processing regions | EU, US, Elsewhere | US, Elsewhere | EU, Elsewhere | Does not apply | Elsewhere | Elsewhere | US, Elsewhere | EU, US, Your choice | EU, US, Elsewhere, Your choice | Your choice | Does not apply | US |
| GDPR compliance | **Yes** | **Yes** | **Yes** | Does not apply | No | No | **Yes** | **Yes** | **Yes** | **Yes** | Does not apply | No |
| Certifications | None | SOC 2 | None | Does not apply | None | None | None | SOC 2 | **ISO 27001, Another attestation** | SOC 2 | Does not apply | None |

### Licence

The licence on the code you run.

- **MIT** — Use it for anything, including commercially.
  - Decap CMS, EmDash, Keystatic, Pages CMS, Payload CMS, Sanity, Sveltia CMS — By design.
- **Proprietary** — No source to read or run.
  - ZeroCMS, CloudCannon, Storyblok — By design.
- **Apache 2.0** — Permissive, with an explicit patent grant.
  - TinaCMS — By design.
- **Open core** — An open core with proprietary features gated inside it.
  - Strapi — By design.

### Hosted service

Whether the vendor also offers it as a hosted service.

- **Hosted product** — The vendor runs a hosted product alongside whatever code is public.
  - ZeroCMS, CloudCannon, Decap CMS, Keystatic, Pages CMS, Payload CMS, Sanity, Storyblok, Strapi, TinaCMS — By design.
- **No hosted product** — There is no service to sign up for — the code is the whole thing.
  - EmDash, Sveltia CMS — By design.

### Content export

How you get your content out of the product. Ranked; best answer first.

- **Already yours** — The content is already files in your repository.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/introduction-to-syncing](https://cloudcannon.com/documentation/developer-articles/introduction-to-syncing/), [cloudcannon.com/…/what-is-the-cloudcannon-configuration-file](https://cloudcannon.com/documentation/developer-articles/what-is-the-cloudcannon-configuration-file/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/intro](https://decapcms.org/docs/intro/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/installation-astro](https://keystatic.com/docs/installation-astro)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs](https://pagescms.org/docs/)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/data-output](https://sveltiacms.app/en/docs/data-output)
  - TinaCMS — The content files leave with the repository. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/integration/frameworks](https://tina.io/docs/integration/frameworks), [tina.io/docs/faq](https://tina.io/docs/faq), [tina.io/docs/frameworks/astro](https://tina.io/docs/frameworks/astro)
- **Structured export** — A dump of the content with its model.
  - EmDash — A backup downloads all content and the model as one JSON file. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/backups](https://docs.emdashcms.com/guides/backups/)
  - Payload CMS — You hold the database outright; the official plugin exports documents as CSV or JSON. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/docs/plugins/import-export](https://payloadcms.com/docs/plugins/import-export), [payloadcms.com/docs/getting-started/what-is-payload](https://payloadcms.com/docs/getting-started/what-is-payload), [payloadcms.com/docs/plugins/overview](https://payloadcms.com/docs/plugins/overview)
  - Sanity — A dataset exports as a gzipped tarball. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/cli-reference/cli-datasets](https://www.sanity.io/docs/cli-reference/cli-datasets)
  - Storyblok — Stories and components back up to your own S3. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/backups](https://www.storyblok.com/docs/concepts/backups)
  - Strapi — One command exports the entries, the uploads and the schemas together. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/data-management/export](https://docs.strapi.io/cms/features/data-management/export)

### Asset export

How you get your images and files out of the product. Ranked; best answer first.

- **Already yours** — Committed beside the content.
  - ZeroCMS — Tested, checked 22 Aug 2026.
  - CloudCannon — Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/…/adjusting-the-uploads-path](https://cloudcannon.com/documentation/developer-articles/adjusting-the-uploads-path/), [cloudcannon.com/…/what-is-the-cloudcannon-configuration-file](https://cloudcannon.com/documentation/developer-articles/what-is-the-cloudcannon-configuration-file/), [cloudcannon.com/…/introduction-to-assets-and-dams](https://cloudcannon.com/documentation/developer-articles/introduction-to-assets-and-dams/)
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/docs/configure-decap-cms](https://decapcms.org/docs/configure-decap-cms/)
  - Keystatic — Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/docs/fields/image](https://keystatic.com/docs/fields/image)
  - Pages CMS — Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/docs/configuration/media](https://pagescms.org/docs/configuration/media/)
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/media](https://sveltiacms.app/en/docs/media)
  - TinaCMS — Assets live in the repo, but their references can carry Tina's own CDN host. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/reference/media/repo-based](https://tina.io/docs/reference/media/repo-based), [tina.io/docs/reference/media/external/authentication](https://tina.io/docs/reference/media/external/authentication)
- **Your own bucket** — Stored in storage you own, so the URLs keep working.
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/docs/upload/storage-adapters](https://payloadcms.com/docs/upload/storage-adapters)
  - EmDash — The media binaries stay in the bucket you hold and the backup carries only metadata. Vendor documentation, checked 3 Sep 2026. Source: [docs.emdashcms.com/guides/backups](https://docs.emdashcms.com/guides/backups/)
- **Bulk export** — Downloadable as a set, and the URLs break when you leave.
  - Sanity — The dataset export includes the asset binaries as a set. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/docs/cli-reference/cli-datasets](https://www.sanity.io/docs/cli-reference/cli-datasets)
  - Storyblok — Built-in backups store only asset references; the files themselves come out as a set via a Management API script or the Storyblok Assets Backup tool. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/docs/concepts/backups](https://www.storyblok.com/docs/concepts/backups)
  - Strapi — Assets kept on the instance leave broken URLs behind. Vendor documentation, checked 3 Sep 2026. Source: [docs.strapi.io/cms/features/data-management/export](https://docs.strapi.io/cms/features/data-management/export)

### Vendor

The company behind the product.

- **A community project**
  - Sveltia CMS — By design.
- **CloudCannon Limited**
  - CloudCannon — By design.
- **Cloudflare, Inc.**
  - EmDash — By design.
- **Neatbit Oy**
  - ZeroCMS — By design.
- **PM, poslovni mediji d.o.o.**
  - Decap CMS — By design.
- **Payload CMS, Inc.**
  - Payload CMS — By design.
- **Ronan Berder**
  - Pages CMS — By design.
- **SSW**
  - TinaCMS — By design.
- **Sanity**
  - Sanity — By design.
- **Storyblok GmbH**
  - Storyblok — By design.
- **Strapi, Inc.**
  - Strapi — By design.
- **Thinkmill Labs Pty Ltd**
  - Keystatic — By design.

### Product history

Significant events in the product's history such as changes of ownership or renames.

- **None**
  - ZeroCMS — Vendor documentation, checked 1 Sep 2026. Sources: [zerocms.io](https://www.zerocms.io), [zerocms.io/changelog](https://www.zerocms.io/changelog), [zerocms.io/privacy](https://www.zerocms.io/privacy)
  - EmDash — Vendor documentation, checked 3 Sep 2026. Sources: [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash), [emdashcms.com](https://emdashcms.com)
  - Keystatic, Pages CMS — Vendor documentation, checked 3 Sep 2026.
  - CloudCannon — Founded in 2013 in New Zealand by Mike Neumegen and George Phillips; the CMS was built as an original product. Vendor documentation, checked 4 Sep 2026. Sources: [cloudcannon.com/company](https://cloudcannon.com/company/), [cloudcannon.com/ai-info](https://cloudcannon.com/ai-info/)
- **5 events**
  - TinaCMS — Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/blog/announcing-tinacms](https://tina.io/blog/announcing-tinacms), [tina.io/about](https://tina.io/about), [api.github.com/repos/tinacms/tinacms/commits/efd56e76](https://api.github.com/repos/tinacms/tinacms/commits/efd56e76), [raw.githubusercontent.com/…/LICENSE](https://raw.githubusercontent.com/tinacms/tinacms/efd56e769c36fbcfe569ffc1ae25a35e2e508258/LICENSE), [raw.githubusercontent.com/…/LICENSE](https://raw.githubusercontent.com/tinacms/tinacms/efd56e769c36fbcfe569ffc1ae25a35e2e508258/packages/%40tinacms/datalayer/LICENSE), [api.github.com/repos/tinacms/tinacms/commits/35177e82](https://api.github.com/repos/tinacms/tinacms/commits/35177e82), [github.com/tinacms/tinacms/commit/35177e82](https://github.com/tinacms/tinacms/commit/35177e82), [tina.io/blog/Tinacms-is-now-fully-open-source](https://tina.io/blog/Tinacms-is-now-fully-open-source), [tina.io/blog/Tina-Joins-SSW](https://tina.io/blog/Tina-Joins-SSW)
    - 2019-10-16: TinaCMS was launched by Forestry.io as an open-source site editing toolkit for React sites, on Gatsby and Next.js. ([source](https://tina.io/blog/announcing-tinacms/))
    - 2023-02-07: A licence based on Fair Source v0.9 shipped in the repository, limiting use to five users, two roles and 500 documents per website. ([source](https://github.com/tinacms/tinacms/commit/efd56e76))
    - 2023-09-07: The carve-out was removed from the root LICENSE. ([source](https://github.com/tinacms/tinacms/commit/35177e82))
    - 2023-11-20: The move to full open source under Apache-2.0 was announced. ([source](https://tina.io/blog/Tinacms-is-now-fully-open-source))
    - 2024-05-14: TinaCMS was acquired by SSW, an Australian software development company and long-time customer, from a team of four developers. ([source](https://tina.io/blog/Tina-Joins-SSW))
- **3 events**
  - Strapi — Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/…/announcing-changes-to-the-strapi-enterprise-plans](https://strapi.io/blog/announcing-changes-to-the-strapi-enterprise-plans), [raw.githubusercontent.com/strapi/strapi/main/LICENSE](https://raw.githubusercontent.com/strapi/strapi/main/LICENSE), [github.com/strapi/strapi/commits/v5.0.0](https://github.com/strapi/strapi/commits/v5.0.0), [github.com/strapi/strapi/releases/tag/v5.0.0](https://github.com/strapi/strapi/releases/tag/v5.0.0), [docs.strapi.io/cms/api/document-service](https://docs.strapi.io/cms/api/document-service), [strapi.io/…/developer-experience-improvements-strapi-5](https://strapi.io/blog/developer-experience-improvements-strapi-5), [strapi.io/blog/bye-2024-hello-2025-a-year-in-review](https://strapi.io/blog/bye-2024-hello-2025-a-year-in-review), [strapi.io/…/we-re-removing-the-free-plan-from-strapi-cloud](https://strapi.io/blog/we-re-removing-the-free-plan-from-strapi-cloud)
    - 2020-07-01: In July 2020 — no day is stated — the Enterprise Edition put paid features in an ee/ directory under a separate non-MIT licence, making the project open core. ([source](https://strapi.io/blog/announcing-changes-to-the-strapi-enterprise-plans))
    - 2024-09-18: Strapi 5 re-architected the content layer around a new document API. ([source](https://github.com/strapi/strapi/releases/tag/v5.0.0))
    - 2026-07-01: Strapi Cloud, the hosted service, withdrew its free plan for new signups, and gave the remaining free projects until that September to upgrade or go. ([source](https://strapi.io/blog/we-re-removing-the-free-plan-from-strapi-cloud))
- **3 events**
  - Payload CMS — Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/posts/blog/open-source](https://payloadcms.com/posts/blog/open-source), [github.com/payloadcms/payload/releases/tag/v3.0.0](https://github.com/payloadcms/payload/releases/tag/v3.0.0), [payloadcms.com/…/payload-30-the-first-cms-that-installs-directly-into-any-nextjs-app](https://payloadcms.com/posts/blog/payload-30-the-first-cms-that-installs-directly-into-any-nextjs-app), [payloadcms.com/posts/blog/payload-is-joining-figma](https://payloadcms.com/posts/blog/payload-is-joining-figma)
    - 2022-05-24: Relicensed from a paid proprietary licence to MIT, and made free. ([source](https://payloadcms.com/posts/blog/open-source))
    - 2024-11-19: Payload 3.0 re-architected the product from an Express and React single-page app onto the Next.js App Router. ([source](https://github.com/payloadcms/payload/releases/tag/v3.0.0))
    - 2025-06-17: Payload joined Figma, which committed to keeping the open-source core. ([source](https://payloadcms.com/posts/blog/payload-is-joining-figma))
- **1 event**
  - Sveltia CMS — Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/docs/successor-to-netlify-cms](https://sveltiacms.app/en/docs/successor-to-netlify-cms)
    - 2022-11-01: Released in November 2022 as a successor to the then-stalled Netlify CMS. ([source](https://sveltiacms.app/en/docs/successor-to-netlify-cms))
- **1 event**
  - Decap CMS — Vendor documentation, checked 3 Sep 2026. Sources: [netlify.com/blog/netlify-cms-to-become-decap-cms](https://www.netlify.com/blog/netlify-cms-to-become-decap-cms/), [decapcms.org/privacy](https://decapcms.org/privacy/)
    - 2023-02-23: Netlify CMS was renamed Decap CMS and its ownership transferred from Netlify to its agency partner PM, poslovni mediji d.o.o. ([source](https://www.netlify.com/blog/netlify-cms-to-become-decap-cms/))
- **Not checked** — We did not settle this. It is not a claim that the product lacks it.
  - Sanity — Sanity has not been renamed; the Studio was rewritten for v3 in 2022 and is now on v6, but the platform's major transitions are not dated on one page.
  - Storyblok — A "Storyblok V2" generation shipped after the original release, but no single vendor page dates the platform's rewrites, so the timeline is unconfirmed.

### Headquarters

Where the company is based.

- **United States**
  - EmDash, Payload CMS, Sanity, Strapi — By design.
- **Australia**
  - Keystatic, TinaCMS — By design.
- **Austria**
  - Storyblok — By design.
- **Finland**
  - ZeroCMS — By design.
- **New Zealand**
  - CloudCannon — By design.
- **Singapore**
  - Pages CMS — By design.
- **Slovenia**
  - Decap CMS — By design.
- **Does not apply**
  - Sveltia CMS — There is no company behind it.

### Support channels

How you reach support. Ranked; best answer first.

- **Email, Dedicated contact, SLA** — Dedicated contact: A named contact or a shared channel. SLA: A response time written into the contract.
  - Decap CMS — Email, dedicated and SLA support come with higher tiers; the entry tier (1 site, 1 seat) gets community support only. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/turbo](https://decapcms.org/turbo/)
  - Strapi — The self-hosted Community edition gets no official support, only volunteers on Discord and GitHub Discussions; email starts at Basic Support, and response-time commitments with the Premium add-on. Vendor documentation, checked 3 Sep 2026. Source: [support.strapi.io/…/6650214304-understanding-strapi-support-coverage](https://support.strapi.io/articles/6650214304-understanding-strapi-support-coverage)
- **Email, Live chat, Dedicated contact** — Dedicated contact: A named contact or a shared channel.
  - CloudCannon — Support is by in-app chat or email, at standard and priority levels. Vendor documentation, checked 31 Aug 2026. Sources: [cloudcannon.com/pricing](https://cloudcannon.com/pricing/), [cloudcannon.com/enterprise](https://cloudcannon.com/enterprise/)
- **Live chat, Dedicated contact** — Dedicated contact: A named contact or a shared channel.
  - Storyblok — Support rises by tier — Core, then Advanced, then Priority — with the top tiers adding a dedicated Customer Success Manager. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/pricing](https://www.storyblok.com/pricing)
- **Email, Dedicated contact** — Dedicated contact: A named contact or a shared channel.
  - TinaCMS — support@tina.io takes account inquiries; Discord is the named channel below Enterprise. The 99.9% figure is an uptime SLA, not a response-time commitment. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/pricing](https://tina.io/pricing), [tina.io/docs/support](https://tina.io/docs/support), [tina.io/enterprise](https://tina.io/enterprise)
- **Dedicated contact, SLA** — Dedicated contact: A named contact or a shared channel. SLA: A response time written into the contract.
  - Sanity — Free and lower tiers get community support; named support with an SLA comes as a paid upgrade, and dedicated support is a paid add-on. Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/pricing](https://www.sanity.io/pricing), [sanity.io/enterprise](https://www.sanity.io/enterprise)
- **Dedicated contact** — Dedicated contact: A named contact or a shared channel.
  - Payload CMS — Dedicated engineering support belongs to the enterprise offering, which is reached by talking to sales. Vendor claim, checked 3 Sep 2026. Sources: [payloadcms.com/get-started](https://payloadcms.com/get-started), [payloadcms.com/talk-to-us](https://payloadcms.com/talk-to-us)
- **Email**
  - ZeroCMS — Vendor documentation, checked 1 Sep 2026. Source: [zerocms.io/pricing](https://www.zerocms.io/pricing)
- **Community only**
  - EmDash — Vendor documentation, checked 3 Sep 2026. Sources: [emdashcms.com](https://emdashcms.com/), [github.com/emdash-cms/emdash](https://github.com/emdash-cms/emdash)
  - Pages CMS — Community help only — documentation, a Discord channel and GitHub issues; there is no paid support tier. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org](https://pagescms.org/)
  - Sveltia CMS — Community help only — GitHub Discussions; the maintainer offers paid consulting, but there is no product support tier. Vendor documentation, checked 3 Sep 2026. Source: [sveltiacms.app/en/support](https://sveltiacms.app/en/support)
- **Not checked** — We did not settle this. It is not a claim that the product lacks it.
  - Keystatic — Keystatic's documentation and Keystatic Cloud plan pages do not describe any support channel or response commitment, free or paid.

### Data processing regions

Where the vendor's own service processes data.

- **Elsewhere**
  - Keystatic — Governed by Australian privacy law; the policy commits to no specific region. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/privacy-policy](https://keystatic.com/privacy-policy)
  - Pages CMS — The hosted app's privacy policy names only Singapore, the operator's location. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/privacy](https://pagescms.org/privacy/)
- **US, Elsewhere**
  - CloudCannon — CloudCannon's own servers are in California, with access from New Zealand. Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/terms](https://cloudcannon.com/terms/)
  - Payload CMS — Content sits in a database you run; the company is in the United States and reserves the right to use service providers in other countries. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/privacy](https://payloadcms.com/privacy), [payloadcms.com/docs/production/deployment](https://payloadcms.com/docs/production/deployment), [payloadcms.com/docs/database/overview](https://payloadcms.com/docs/database/overview)
- **Your choice** — Your choice: You pick the region.
  - Strapi — A hosted project is pinned to a region chosen when it is created and cannot be moved afterwards. Vendor documentation, checked 3 Sep 2026. Sources: [docs.strapi.io/cloud/getting-started/deployment](https://docs.strapi.io/cloud/getting-started/deployment), [docs.strapi.io/cloud/projects/settings](https://docs.strapi.io/cloud/projects/settings)
- **EU, US, Elsewhere, Your choice** — Your choice: You pick the region.
  - Storyblok — Hosted on AWS, with selectable data residency in the EU (Germany), the US and Canada, or Australia. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/trust-center](https://www.storyblok.com/trust-center)
- **EU, US, Your choice** — Your choice: You pick the region.
  - Sanity — The backend runs in an EU region (Belgium); content may be stored in the EU/EEA, the US, or a customer-specified region. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/security](https://www.sanity.io/security)
- **EU, Elsewhere**
  - Decap CMS — Decap Turbo's controller is in Slovenia (EU); its sub-processors Supabase and Paddle may process data in other jurisdictions. Vendor documentation, checked 3 Sep 2026. Sources: [decapcms.org/turbo/privacy](https://decapcms.org/turbo/privacy/), [decapcms.org/turbo/terms](https://decapcms.org/turbo/terms/)
- **EU, US, Elsewhere**
  - ZeroCMS — Servers in the Netherlands. Data may also be transferred to and processed in third-party facilities in the US and other countries, under Standard Contractual Clauses. Vendor documentation, checked 1 Sep 2026. Source: [zerocms.io/privacy](https://www.zerocms.io/privacy)
- **US**
  - TinaCMS — Content lives in your GitHub repository, which stays the source of truth; TinaCloud keeps indexes of it on servers in the United States, and reserves any other country where they maintain facilities. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/docs/tinacloud](https://tina.io/docs/tinacloud), [tina.io/docs/tinacloud/overview](https://tina.io/docs/tinacloud/overview), [tina.io/privacy-notice](https://tina.io/privacy-notice)
- **Does not apply**
  - EmDash — Nobody hosts it, so there is no service processing anything.
  - Sveltia CMS — Nobody hosts it, so there is no service processing anything.

### GDPR compliance

Whether the vendor documents GDPR compliance. Ranked; best answer first.

- **Yes**
  - ZeroCMS — Data controller for EEA residents, with an appointed EEA representative (Neatbit Oy, Helsinki) and Standard Contractual Clauses for transfers. Vendor documentation, checked 1 Sep 2026. Source: [zerocms.io/privacy](https://www.zerocms.io/privacy)
  - CloudCannon — A processor for your personal data, with EU Standard Contractual Clauses and a UK addendum — though the clauses are opt-in: CloudCannon pre-signs them and you countersign and return a copy. Vendor documentation, checked 31 Aug 2026. Source: [cloudcannon.com/gdpr](https://cloudcannon.com/gdpr/)
  - Decap CMS — Decap Turbo acts as GDPR controller, states data-subject rights, and relies on Standard Contractual Clauses for transfers. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/turbo/privacy](https://decapcms.org/turbo/privacy/)
  - Payload CMS — Stated legal bases, appointed EU and UK representatives, and standard-form contracts for transfers out of Europe. Vendor documentation, checked 3 Sep 2026. Source: [payloadcms.com/privacy](https://payloadcms.com/privacy)
  - Sanity — Sanity acts as a data processor on the customer's behalf, relying on Standard Contractual Clauses for transfers. Vendor documentation, checked 3 Sep 2026. Sources: [sanity.io/security](https://www.sanity.io/security), [sanity.io/legal/privacy](https://www.sanity.io/legal/privacy)
  - Storyblok — A processor under a Data Processing Agreement; also self-certified under the EU-US Data Privacy Framework. Vendor documentation, checked 3 Sep 2026. Sources: [storyblok.com/trust-center](https://www.storyblok.com/trust-center), [storyblok.com/legal/dpa](https://www.storyblok.com/legal/dpa)
  - Strapi — A processor for the content you put into Strapi, with a GDPR representative in Paris. Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/privacy](https://strapi.io/privacy), [strapi.io/cloud-legal](https://strapi.io/cloud-legal), [strapi.io/pricing-cloud](https://strapi.io/pricing-cloud)
- **No**
  - Keystatic — The policy invokes the Australian Privacy Principles and consent. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/privacy-policy](https://keystatic.com/privacy-policy)
  - Pages CMS — The hosted app's privacy policy is a generic template with no transfer safeguards; transfers rest on consent. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/privacy](https://pagescms.org/privacy/)
  - TinaCMS — The April 2021 privacy notice names no legal basis, transfer mechanism or EEA representative, while a Chinese-language enterprise page claims full GDPR compliance. Vendor documentation, checked 3 Sep 2026. Sources: [tina.io/privacy-notice](https://tina.io/privacy-notice), [tina.io/terms-of-service](https://tina.io/terms-of-service), [tina.io/security](https://tina.io/security), [tina.io/zh/enterprise](https://tina.io/zh/enterprise)
- **Does not apply**
  - EmDash — Nobody hosts it, so there is no service processing anything.
  - Sveltia CMS — Nobody hosts it, so there is no service processing anything.

### Certifications

Named security and compliance attestations. Ranked; best answer first.

- **ISO 27001, Another attestation**
  - Storyblok — ISO 27001 and TISAX; also self-certified under the EU-US Data Privacy Framework. Vendor documentation, checked 3 Sep 2026. Source: [storyblok.com/trust-center](https://www.storyblok.com/trust-center)
- **SOC 2**
  - CloudCannon — SOC 2 Type 2; the report is released through their trust centre on request. Vendor documentation, checked 4 Sep 2026. Sources: [cloudcannon.com/security](https://cloudcannon.com/security/), [cloudcannon.com/terms](https://cloudcannon.com/terms/)
  - Sanity — SOC 2 Type 2, covering the security principle. Vendor documentation, checked 3 Sep 2026. Source: [sanity.io/security](https://www.sanity.io/security)
  - Strapi — SOC 2 Type 2, audited by a third party with no noted exceptions; the report is available on request through their trust centre. Vendor documentation, checked 3 Sep 2026. Sources: [strapi.io/security](https://strapi.io/security), [strapi.io/…/introducing-faster-deployments-and-soc-2-certification](https://strapi.io/blog/introducing-faster-deployments-and-soc-2-certification)
- **None**
  - ZeroCMS — Vendor documentation, checked 1 Sep 2026. Sources: [zerocms.io/privacy](https://www.zerocms.io/privacy), [zerocms.io/pricing](https://www.zerocms.io/pricing)
  - Decap CMS — Decap Turbo's privacy policy describes security measures but claims no ISO 27001, SOC 2 or other audited certification. Vendor documentation, checked 3 Sep 2026. Source: [decapcms.org/turbo/privacy](https://decapcms.org/turbo/privacy/)
  - Keystatic — The privacy policy's security section names no certification. Vendor documentation, checked 17 Sep 2026. Source: [keystatic.com/privacy-policy](https://keystatic.com/privacy-policy)
  - Pages CMS — No SOC 2, ISO 27001 or other audited certification is named in the privacy policy. Vendor documentation, checked 3 Sep 2026. Source: [pagescms.org/privacy](https://pagescms.org/privacy)
  - Payload CMS — The security page names no audit or attestation. Vendor documentation, checked 3 Sep 2026. Sources: [payloadcms.com/security](https://payloadcms.com/security), [payloadcms.com/enterprise/audit-logs](https://payloadcms.com/enterprise/audit-logs)
  - TinaCMS — The security page says the programme follows SOC 2 criteria, which is not the same as holding an audited report. Vendor documentation, checked 3 Sep 2026. Source: [tina.io/security](https://tina.io/security)
- **Does not apply**
  - EmDash — Nobody hosts it, so there is no service processing anything.
  - Sveltia CMS — Nobody hosts it, so there is no service processing anything.

## Project health

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Commits (90 days) | No public repository | No public repository | 56 | 1,087 | 48 | 0 | 407 | 1,265 | No public repository | 492 | 968 | 164 |
| Latest release | No public repository | No public repository | 2026-09-22 | 2026-09-28 | 2026-08-26 | 2026-06-08 | 2026-09-23 | 2026-09-29 | No public repository | 2026-09-30 | 2026-09-30 | 2026-09-23 |
| GitHub stars | No public repository | No public repository | 19,412 | 13,223 | 2,429 | 4,052 | 45,038 | 6,346 | No public repository | 73,266 | 2,892 | 13,820 |
| Open issues | No public repository | No public repository | 604 | 327 | 192 | 75 | 1,240 | 277 | No public repository | 577 | 41 | 450 |
| npm downloads (weekly) | No public repository | No public repository | 21,202 | 47,364 | 164,793 | Does not apply | 1,060,642 | 1,133,868 | No public repository | 233,848 | 26,429 | 53,464 |
| Maintenance signal | Does not apply | Does not apply | Moving | Moving | Moving | Maintenance mode | Moving | Moving | Does not apply | Moving | Moving | Moving |

### Commits (90 days)

Commits to the default branch in the last 90 days.

- **No public repository**
  - ZeroCMS, CloudCannon, Storyblok — By design.
- **0**
  - Pages CMS — Read from GitHub, checked 1 Oct 2026.
- **1,087**
  - EmDash — Read from GitHub, checked 1 Oct 2026.
- **1,265**
  - Sanity — Read from GitHub, checked 1 Oct 2026.
- **164**
  - TinaCMS — Read from GitHub, checked 1 Oct 2026.
- **407**
  - Payload CMS — Read from GitHub, checked 1 Oct 2026.
- **48**
  - Keystatic — Read from GitHub, checked 1 Oct 2026.
- **492**
  - Strapi — Read from GitHub, checked 1 Oct 2026.
- **56**
  - Decap CMS — Read from GitHub, checked 1 Oct 2026.
- **968**
  - Sveltia CMS — Read from GitHub, checked 1 Oct 2026.

### Latest release

When the npm package last published a stable version, or the latest GitHub release where there is no package.

- **No public repository**
  - ZeroCMS, CloudCannon, Storyblok — By design.
- **2026-09-23**
  - Payload CMS, TinaCMS — Read from GitHub, checked 1 Oct 2026.
- **2026-09-30**
  - Strapi, Sveltia CMS — Read from GitHub, checked 1 Oct 2026.
- **2026-06-08**
  - Pages CMS — Read from GitHub, checked 1 Oct 2026.
- **2026-08-26**
  - Keystatic — Read from GitHub, checked 1 Oct 2026.
- **2026-09-22**
  - Decap CMS — Read from GitHub, checked 1 Oct 2026.
- **2026-09-28**
  - EmDash — Read from GitHub, checked 1 Oct 2026.
- **2026-09-29**
  - Sanity — Read from GitHub, checked 1 Oct 2026.

### GitHub stars

Stars on the public repository.

- **No public repository**
  - ZeroCMS, CloudCannon, Storyblok — By design.
- **13,223**
  - EmDash — Read from GitHub, checked 1 Oct 2026.
- **13,820**
  - TinaCMS — Read from GitHub, checked 1 Oct 2026.
- **19,412**
  - Decap CMS — Read from GitHub, checked 1 Oct 2026.
- **2,429**
  - Keystatic — Read from GitHub, checked 1 Oct 2026.
- **2,892**
  - Sveltia CMS — Read from GitHub, checked 1 Oct 2026.
- **4,052**
  - Pages CMS — Read from GitHub, checked 1 Oct 2026.
- **45,038**
  - Payload CMS — Read from GitHub, checked 1 Oct 2026.
- **6,346**
  - Sanity — Read from GitHub, checked 1 Oct 2026.
- **73,266**
  - Strapi — Read from GitHub, checked 1 Oct 2026.

### Open issues

Open issues on the public repository.

- **No public repository**
  - ZeroCMS, CloudCannon, Storyblok — By design.
- **1,240**
  - Payload CMS — Read from GitHub, checked 1 Oct 2026.
- **192**
  - Keystatic — Read from GitHub, checked 1 Oct 2026.
- **277**
  - Sanity — Read from GitHub, checked 1 Oct 2026.
- **327**
  - EmDash — Read from GitHub, checked 1 Oct 2026.
- **41**
  - Sveltia CMS — Read from GitHub, checked 1 Oct 2026.
- **450**
  - TinaCMS — Read from GitHub, checked 1 Oct 2026.
- **577**
  - Strapi — Read from GitHub, checked 1 Oct 2026.
- **604**
  - Decap CMS — Read from GitHub, checked 1 Oct 2026.
- **75**
  - Pages CMS — Read from GitHub, checked 1 Oct 2026.

### npm downloads (weekly)

Weekly downloads of the product's npm package.

- **No public repository**
  - ZeroCMS, CloudCannon, Storyblok — By design.
- **1,060,642**
  - Payload CMS — Read from GitHub, checked 1 Oct 2026.
- **1,133,868**
  - Sanity — Read from GitHub, checked 1 Oct 2026.
- **164,793**
  - Keystatic — Read from GitHub, checked 1 Oct 2026.
- **21,202**
  - Decap CMS — Read from GitHub, checked 1 Oct 2026.
- **233,848**
  - Strapi — Read from GitHub, checked 1 Oct 2026.
- **26,429**
  - Sveltia CMS — Read from GitHub, checked 1 Oct 2026.
- **47,364**
  - EmDash — Read from GitHub, checked 1 Oct 2026.
- **53,464**
  - TinaCMS — Read from GitHub, checked 1 Oct 2026.
- **Does not apply**
  - Pages CMS

### Maintenance signal

Available for products with a public repository. A product is considered active when it has at least 10 commits in 90 days and has gotten a new release within the last 12 months.

- **Moving** — Above both thresholds.
  - Decap CMS, EmDash, Keystatic, Payload CMS, Sanity, Strapi, Sveltia CMS, TinaCMS — Our judgement.
- **Maintenance mode** — Alive, but not moving by either measure.
  - Pages CMS — Our judgement.
- **Does not apply**
  - ZeroCMS — There is no public repository, so there are no numbers to read.
  - CloudCannon — There is no public repository, so there are no numbers to read.
  - Storyblok — There is no public repository, so there are no numbers to read.

## Our judgement

| Aspect | ZeroCMS | CloudCannon | Decap CMS | EmDash | Keystatic | Pages CMS | Payload CMS | Sanity | Storyblok | Strapi | Sveltia CMS | TinaCMS |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Suited to | Documentation, Marketing sites, Blogs, Agency multi-site | Marketing sites, Blogs, Agency multi-site | Blogs, Marketing sites, Documentation | Marketing sites, Blogs | Marketing sites, Blogs, Documentation | Blogs, Marketing sites, Documentation | Marketing sites, Agency multi-site, Ecommerce | Marketing sites, Ecommerce, Agency multi-site | Marketing sites, Ecommerce, Agency multi-site | Marketing sites, Ecommerce, Agency multi-site | Blogs, Marketing sites, Documentation | Marketing sites, Blogs, Documentation |
| Best for | Astro sites already on GitHub using content collections, Docs and marketing sites built from MDX components, Writers who publish without touching Git, Agencies running several Astro client sites, Teams that want AI agents in their content | Agencies running many client sites, Marketing teams who edit on the page, Teams using Astro alongside Hugo, Jekyll or Eleventy, Organizations that need SOC 2 or SAML SSO, Teams with developers wanting to own the CMS config | Static sites that want a free Git-based editor, Teams committed to open source and self-hosting, Projects already on GitHub, GitLab or Bitbucket, Editors who tolerate a separate preview pane | Astro sites that want a database-backed CMS, Teams migrating a WordPress site to Astro, Developers who drive content with AI agents, Sites needing instant SSR updates, no rebuild, Self-hosters on Cloudflare Workers or Node | Astro sites whose content stays in the repo, Developers comfortable configuring the CMS in code, Solo owners and small content teams, Sites that read content through astro:content, Teams wanting an MIT, self-hostable CMS | Static GitHub sites that want a free editor, Solo owners and small content teams, Editors invited without a GitHub account, Projects happy to review on GitHub | Teams with TypeScript developers on hand, Teams with developer time but limited budget, Projects mixing site content and application data, Organizations that must own the database, Astro sites already fetching from an API | Structured-content teams publishing to many channels, Developers who model content in code, Marketers who edit on a live preview of the page, Enterprises needing SAML SSO and custom roles, Astro sites already fetching content from an API | Enterprise teams wanting visual editing on a headless API, Marketers who edit on a live preview of the page, Multi-market sites needing strong localization, Astro sites already fetching content from an API, Teams that need SAML SSO and ISO 27001 | Teams that need a content API more than a site editor, Organizations that must self-host and own the database, Projects mixing site content and application data, Content teams needing staged review and an audit trail, Astro sites already fetching from a REST or GraphQL API | Sites migrating off Netlify or Decap CMS, Multilingual static sites needing real i18n, Static blogs and marketing sites on Git, Developers wanting a no-build, drop-in editor, Small teams comfortable with Git-host accounts | Astro sites wanting visual editing today, Developers who want the CMS in their repo, Teams whose editors have no GitHub account, Small teams on one site at a time |
| Strengths | Preview is your real Astro site, Nothing added to your repository, Eight built-in content checks, custom ones in prose, Your Zod schemas are the schema, AI agent with custom skills, Editors need no GitHub account or seat, MCP server for external agents | On-page visual editing for marketers, SOC 2 Type 2, SAML SSO and enforced MFA, Client access with no account at all, Per-collection and per-folder permissions, Free staging and branch sites, GitHub, GitLab and Bitbucket, self-hosted included, Thirteen years in market | Backends for six git hosts, self-hosted included, Drafts, review and a pull request per entry, Custom widgets and editor components, Content stays as plain files in your repo, Free and MIT-licensed, with no vendor lock-in, Hosted Decap Turbo tier, priced per seat and site | Edits appear instantly via SSR, no rebuild, Real-site draft preview, updated as you type, Content served through Astro Live Collections, WordPress import built in, REST API and a full content CLI, MCP server reads, writes and publishes, MIT licensed and self-hostable | Content flows through astro:content, Reads Markdoc, MDX, YAML and JSON, Branch and pull-request workflow on GitHub, Stale edits are blocked, not overwritten, Local mode edits files with no account, Reference, object and block fields in forms, MIT licensed and self-hostable | Email editors need no GitHub seat, Free and MIT-licensed, hosted or self-hosted, no paid tier, Only a .pages.yml is added to the repo, Schema-driven forms with block and union fields, Content and media stay as files in your repo | Content model is TypeScript you own, REST, GraphQL and a direct Node API, Versions with diffs and one-click restore, Field-level access control on the free tier, Document locking warns the second editor, Official MCP server that reads and writes, MIT licensed and self-hostable | Real-time collaborative editing, Official Astro integration with visual editing, Agent Actions and a remote MCP server, Forms honor references, unions and nested blocks, GROQ querying, full HTTP API and webhooks, AI terms forbid training on your content, Version history with one-click restore | Official Astro SDK and Content Layer loader, Strong multi-locale translation workflow, On-page visual editing via the Storyblok Bridge, ISO 27001, SAML SSO with SCIM, EU data residency, Field-level roles and staged approval workflows, Management API, webhooks and a remote MCP server, Field-level comments with reply and resolve | Review stages you define, with per-stage role gates, Field-level permissions, free in the Community edition, Audit log covering sign-ins, roles and content changes, First-party MCP server that writes and publishes, REST and GraphQL that both read and write content, Version history with restore, and scheduled releases, Open core, self-hostable, with an MIT-licensed core | Drop-in replacement for Netlify/Decap config, Linked-locale i18n with in-editor machine translation, No build step, adapter or dependency, GitHub, GitLab, Gitea and Forgejo, self-hosted included, In-editor commit history and signed commits on GitHub, Custom fields, editor components and preview templates, Free and MIT-licensed, no vendor lock-in | On-page visual editing of your real Astro site, Blocks with a visual template picker, Editors need no GitHub account, Local editing with no account at all, Editor is served from your own site, Typed GraphQL API over your content, Apache-2.0, with a self-hostable backend |
| Limitations | Only file-backed content collections are editable, GitHub only, No free tier or self-hosted option, No SOC 2, SAML SSO or in-product audit log, Young product with early access, No HTTP API, webhooks or custom field widgets, Astro only | No visual editing or preview for server-rendered Astro, Server-only components do not redraw in the preview, Visual editing needs per-component setup, Every field has to be described twice, No in-product version history, No AI in the product, No content checks | No Astro integration; MDX is raw text only, GitHub login needs access to your whole org, Preview is Decap's own render, not your site, Direct backends need a repo seat per editor, Concurrent edits silently overwrite, Collection roles, SSO and multi-site are paid Turbo tiers, No AI, HTTP API, webhooks or in-editor history | Content lives in a database, not your repo, Whole site goes SSR, on Astro 6 or later, You run the app, database and storage, Beta preview, and a young project, Roles are instance-wide, not per collection, No review diff, comments or content checks, Ships no AI of its own | No rendered live preview for Astro, Reshapes your content and reformats files on save, Needs a Node host, an adapter and React in your repo, Editors need GitHub write access unless you use Cloud, The content model is declared twice, GitHub is the only Git host, Experimental by its own description | Every save commits; no drafts or review diff, No preview of the rendered site, Concurrent or upstream edits discard unsaved work, No Astro integration; MDX is raw-only, No configurable roles, SSO or approvals, GitHub only; no AI, API or webhooks, Content model is declared again in config | You run a second Next.js app, database and storage, Nothing renders an Astro preview for you, You map Payload's model to Astro, blocks and types, No webhooks; you write the hook that triggers a rebuild, A custom loader you write replaces your collections, Astro gets a repo example, not docs or a preview helper, SSO, AI and workflows are enterprise-only | Content lives in Sanity's cloud, not your repo, Visual editing needs SSR on a preview site you host, SaaS only, with no self-hosted or local mode, Adds SDK, config, routes and schema to your repo, You map Portable Text blocks to Astro components, SSO and custom roles are Enterprise, No built-in approval workflow or content checks | Content lives in Storyblok, not your repo, You map Storyblok blocks to Astro components, You build and host the preview site yourself, Published plans include one space; more is quote-only, SSO, scheduling, workflows and extended audit log are paid, SaaS only, with no self-hosted option, No built-in content checks | Astro support is community-maintained, not first-party, Review, audit, history, releases and SSO are paid tiers, Nothing renders an Astro preview for you, No first-party Astro loader; the community one is an RC, Self-hosting means a Node app, database and storage, Schema changes need a redeploy, never on a live instance, No diff of what changed before you publish | Preview is Sveltia's own render, not your site, Concurrent edits can silently overwrite, No Astro integration; MDX and Markdoc unsupported, Beta, no hosted option; you run the OAuth gateway, Every editor needs a Git-host account and seat, No roles, SSO, SAML or multi-site management, Content model is declared again in config.yml | Your Astro content collections go unused, Visual editing needs an adapter and per-page setup, One project per subscription, plus per-seat fees, Drafts and review are paid; otherwise every save deploys, Commits are bot-authored until each editor opts in, No diff or comments in the product; review happens on GitHub, GitHub is the only shipped Git host |

### Suited to

The kinds of site the product suits, in our opinion.

- **ZeroCMS**
  - Documentation
  - Marketing sites
  - Blogs
  - Agency multi-site
- **CloudCannon**
  - Marketing sites
  - Blogs
  - Agency multi-site
- **Decap CMS**
  - Blogs
  - Marketing sites
  - Documentation
- **EmDash**
  - Marketing sites
  - Blogs
- **Keystatic**
  - Marketing sites
  - Blogs
  - Documentation
- **Pages CMS**
  - Blogs
  - Marketing sites
  - Documentation
- **Payload CMS**
  - Marketing sites
  - Agency multi-site
  - Ecommerce
- **Sanity**
  - Marketing sites
  - Ecommerce
  - Agency multi-site
- **Storyblok**
  - Marketing sites
  - Ecommerce
  - Agency multi-site
- **Strapi**
  - Marketing sites
  - Ecommerce
  - Agency multi-site
- **Sveltia CMS**
  - Blogs
  - Marketing sites
  - Documentation
- **TinaCMS**
  - Marketing sites
  - Blogs
  - Documentation

### Best for

Who should pick it, in our opinion.

- **ZeroCMS**
  - Astro sites already on GitHub using content collections
  - Docs and marketing sites built from MDX components
  - Writers who publish without touching Git
  - Agencies running several Astro client sites
  - Teams that want AI agents in their content
- **CloudCannon**
  - Agencies running many client sites
  - Marketing teams who edit on the page
  - Teams using Astro alongside Hugo, Jekyll or Eleventy
  - Organizations that need SOC 2 or SAML SSO
  - Teams with developers wanting to own the CMS config
- **Decap CMS**
  - Static sites that want a free Git-based editor
  - Teams committed to open source and self-hosting
  - Projects already on GitHub, GitLab or Bitbucket
  - Editors who tolerate a separate preview pane
- **EmDash**
  - Astro sites that want a database-backed CMS
  - Teams migrating a WordPress site to Astro
  - Developers who drive content with AI agents
  - Sites needing instant SSR updates, no rebuild
  - Self-hosters on Cloudflare Workers or Node
- **Keystatic**
  - Astro sites whose content stays in the repo
  - Developers comfortable configuring the CMS in code
  - Solo owners and small content teams
  - Sites that read content through astro:content
  - Teams wanting an MIT, self-hostable CMS
- **Pages CMS**
  - Static GitHub sites that want a free editor
  - Solo owners and small content teams
  - Editors invited without a GitHub account
  - Projects happy to review on GitHub
- **Payload CMS**
  - Teams with TypeScript developers on hand
  - Teams with developer time but limited budget
  - Projects mixing site content and application data
  - Organizations that must own the database
  - Astro sites already fetching from an API
- **Sanity**
  - Structured-content teams publishing to many channels
  - Developers who model content in code
  - Marketers who edit on a live preview of the page
  - Enterprises needing SAML SSO and custom roles
  - Astro sites already fetching content from an API
- **Storyblok**
  - Enterprise teams wanting visual editing on a headless API
  - Marketers who edit on a live preview of the page
  - Multi-market sites needing strong localization
  - Astro sites already fetching content from an API
  - Teams that need SAML SSO and ISO 27001
- **Strapi**
  - Teams that need a content API more than a site editor
  - Organizations that must self-host and own the database
  - Projects mixing site content and application data
  - Content teams needing staged review and an audit trail
  - Astro sites already fetching from a REST or GraphQL API
- **Sveltia CMS**
  - Sites migrating off Netlify or Decap CMS
  - Multilingual static sites needing real i18n
  - Static blogs and marketing sites on Git
  - Developers wanting a no-build, drop-in editor
  - Small teams comfortable with Git-host accounts
- **TinaCMS**
  - Astro sites wanting visual editing today
  - Developers who want the CMS in their repo
  - Teams whose editors have no GitHub account
  - Small teams on one site at a time

### Strengths

What the product does well, in our opinion.

- **ZeroCMS**
  - Preview is your real Astro site
  - Nothing added to your repository
  - Eight built-in content checks, custom ones in prose
  - Your Zod schemas are the schema
  - AI agent with custom skills
  - Editors need no GitHub account or seat
  - MCP server for external agents
- **CloudCannon**
  - On-page visual editing for marketers
  - SOC 2 Type 2, SAML SSO and enforced MFA
  - Client access with no account at all
  - Per-collection and per-folder permissions
  - Free staging and branch sites
  - GitHub, GitLab and Bitbucket, self-hosted included
  - Thirteen years in market
- **Decap CMS**
  - Backends for six git hosts, self-hosted included
  - Drafts, review and a pull request per entry
  - Custom widgets and editor components
  - Content stays as plain files in your repo
  - Free and MIT-licensed, with no vendor lock-in
  - Hosted Decap Turbo tier, priced per seat and site
- **EmDash**
  - Edits appear instantly via SSR, no rebuild
  - Real-site draft preview, updated as you type
  - Content served through Astro Live Collections
  - WordPress import built in
  - REST API and a full content CLI
  - MCP server reads, writes and publishes
  - MIT licensed and self-hostable
- **Keystatic**
  - Content flows through astro:content
  - Reads Markdoc, MDX, YAML and JSON
  - Branch and pull-request workflow on GitHub
  - Stale edits are blocked, not overwritten
  - Local mode edits files with no account
  - Reference, object and block fields in forms
  - MIT licensed and self-hostable
- **Pages CMS**
  - Email editors need no GitHub seat
  - Free and MIT-licensed, hosted or self-hosted, no paid tier
  - Only a .pages.yml is added to the repo
  - Schema-driven forms with block and union fields
  - Content and media stay as files in your repo
- **Payload CMS**
  - Content model is TypeScript you own
  - REST, GraphQL and a direct Node API
  - Versions with diffs and one-click restore
  - Field-level access control on the free tier
  - Document locking warns the second editor
  - Official MCP server that reads and writes
  - MIT licensed and self-hostable
- **Sanity**
  - Real-time collaborative editing
  - Official Astro integration with visual editing
  - Agent Actions and a remote MCP server
  - Forms honor references, unions and nested blocks
  - GROQ querying, full HTTP API and webhooks
  - AI terms forbid training on your content
  - Version history with one-click restore
- **Storyblok**
  - Official Astro SDK and Content Layer loader
  - Strong multi-locale translation workflow
  - On-page visual editing via the Storyblok Bridge
  - ISO 27001, SAML SSO with SCIM, EU data residency
  - Field-level roles and staged approval workflows
  - Management API, webhooks and a remote MCP server
  - Field-level comments with reply and resolve
- **Strapi**
  - Review stages you define, with per-stage role gates
  - Field-level permissions, free in the Community edition
  - Audit log covering sign-ins, roles and content changes
  - First-party MCP server that writes and publishes
  - REST and GraphQL that both read and write content
  - Version history with restore, and scheduled releases
  - Open core, self-hostable, with an MIT-licensed core
- **Sveltia CMS**
  - Drop-in replacement for Netlify/Decap config
  - Linked-locale i18n with in-editor machine translation
  - No build step, adapter or dependency
  - GitHub, GitLab, Gitea and Forgejo, self-hosted included
  - In-editor commit history and signed commits on GitHub
  - Custom fields, editor components and preview templates
  - Free and MIT-licensed, no vendor lock-in
- **TinaCMS**
  - On-page visual editing of your real Astro site
  - Blocks with a visual template picker
  - Editors need no GitHub account
  - Local editing with no account at all
  - Editor is served from your own site
  - Typed GraphQL API over your content
  - Apache-2.0, with a self-hostable backend

### Limitations

Where the product falls short, in our opinion.

- **ZeroCMS**
  - Only file-backed content collections are editable
  - GitHub only
  - No free tier or self-hosted option
  - No SOC 2, SAML SSO or in-product audit log
  - Young product with early access
  - No HTTP API, webhooks or custom field widgets
  - Astro only
- **CloudCannon**
  - No visual editing or preview for server-rendered Astro
  - Server-only components do not redraw in the preview
  - Visual editing needs per-component setup
  - Every field has to be described twice
  - No in-product version history
  - No AI in the product
  - No content checks
- **Decap CMS**
  - No Astro integration; MDX is raw text only
  - GitHub login needs access to your whole org
  - Preview is Decap's own render, not your site
  - Direct backends need a repo seat per editor
  - Concurrent edits silently overwrite
  - Collection roles, SSO and multi-site are paid Turbo tiers
  - No AI, HTTP API, webhooks or in-editor history
- **EmDash**
  - Content lives in a database, not your repo
  - Whole site goes SSR, on Astro 6 or later
  - You run the app, database and storage
  - Beta preview, and a young project
  - Roles are instance-wide, not per collection
  - No review diff, comments or content checks
  - Ships no AI of its own
- **Keystatic**
  - No rendered live preview for Astro
  - Reshapes your content and reformats files on save
  - Needs a Node host, an adapter and React in your repo
  - Editors need GitHub write access unless you use Cloud
  - The content model is declared twice
  - GitHub is the only Git host
  - Experimental by its own description
- **Pages CMS**
  - Every save commits; no drafts or review diff
  - No preview of the rendered site
  - Concurrent or upstream edits discard unsaved work
  - No Astro integration; MDX is raw-only
  - No configurable roles, SSO or approvals
  - GitHub only; no AI, API or webhooks
  - Content model is declared again in config
- **Payload CMS**
  - You run a second Next.js app, database and storage
  - Nothing renders an Astro preview for you
  - You map Payload's model to Astro, blocks and types
  - No webhooks; you write the hook that triggers a rebuild
  - A custom loader you write replaces your collections
  - Astro gets a repo example, not docs or a preview helper
  - SSO, AI and workflows are enterprise-only
- **Sanity**
  - Content lives in Sanity's cloud, not your repo
  - Visual editing needs SSR on a preview site you host
  - SaaS only, with no self-hosted or local mode
  - Adds SDK, config, routes and schema to your repo
  - You map Portable Text blocks to Astro components
  - SSO and custom roles are Enterprise
  - No built-in approval workflow or content checks
- **Storyblok**
  - Content lives in Storyblok, not your repo
  - You map Storyblok blocks to Astro components
  - You build and host the preview site yourself
  - Published plans include one space; more is quote-only
  - SSO, scheduling, workflows and extended audit log are paid
  - SaaS only, with no self-hosted option
  - No built-in content checks
- **Strapi**
  - Astro support is community-maintained, not first-party
  - Review, audit, history, releases and SSO are paid tiers
  - Nothing renders an Astro preview for you
  - No first-party Astro loader; the community one is an RC
  - Self-hosting means a Node app, database and storage
  - Schema changes need a redeploy, never on a live instance
  - No diff of what changed before you publish
- **Sveltia CMS**
  - Preview is Sveltia's own render, not your site
  - Concurrent edits can silently overwrite
  - No Astro integration; MDX and Markdoc unsupported
  - Beta, no hosted option; you run the OAuth gateway
  - Every editor needs a Git-host account and seat
  - No roles, SSO, SAML or multi-site management
  - Content model is declared again in config.yml
- **TinaCMS**
  - Your Astro content collections go unused
  - Visual editing needs an adapter and per-page setup
  - One project per subscription, plus per-seat fees
  - Drafts and review are paid; otherwise every save deploys
  - Commits are bot-authored until each editor opts in
  - No diff or comments in the product; review happens on GitHub
  - GitHub is the only shipped Git host

The table above can contain mistakes. If you find something missing or inaccurate, please report your findings to [support@zerocms.io](mailto:support@zerocms.io) so they can be fixed.

## Related resources

[Guide How to design Astro content collections that scale A practical guide to choosing collection boundaries, formats, loaders, and schemas as an Astro site grows.](/resources/guides/content-collections-deep-dive)

Done reading?

## Now give your collections an editor.

Connect your Astro repo and Zero turns every collection into a form your team can edit. 14-day free trial.

[Connect your site](/signup) [Try the live demo](https://go.zerocms.io/demo)
