Comparison

ZeroCMS vs Keystatic for Astro 2026.

Both keep your content in the repository. ZeroCMS leads on codebase footprint, AI and Astro fit. Keystatic leads on API reach.

ZeroCMS

Git-based · Cloud · From $15 / month, editors need no seat

Connect a GitHub repository and Zero reads your Astro Zod schemas and .astro components to generate the editor — no plugins, no config, nothing added to your repository. Editors work against a live preview of the real site, and every publish lands as a clean commit. An AI agent works in the editor, and eight content checks run on demand or as a pre-publish gate.

Overview

  • Astro fit 5 of 5
  • Codebase fit 5 of 5
  • Editing 4 of 5
  • Publishing and review 5 of 5
  • Governance and access 4 of 5
  • Git and the repository 4 of 5
  • APIs and extensibility 4 of 5
  • AI capabilities 5 of 5

Reviewed 1 Sep 2026 Full CMS comparison →

Keystatic

Git-based · Cloud or self-hosted · Free tier · from $10 / month

Keystatic is configured in a TypeScript file in your repository and edits the Markdown, YAML and JSON already sitting there. A local mode runs the editor against those files with no account at all; Keystatic Cloud adds hosted GitHub auth and image storage. Astro reads the content back through astro:content, but the content model is declared twice.

Overview

  • Astro fit 3 of 5
  • Codebase fit 0 of 5
  • Editing 5 of 5
  • Publishing and review 4 of 5
  • Governance and access 3 of 5
  • Git and the repository 3 of 5
  • APIs and extensibility 5 of 5
  • AI capabilities 0 of 5

Reviewed 17 Sep 2026 Full CMS comparison →

Pick ZeroCMS when

You want a CMS that adds nothing to the repository and runs content checks before anything publishes.

  • You want the CMS to leave your codebase alone
  • AI should do the routine work
  • AI agents edit the content

Pick Keystatic when

You want a CMS that runs locally with no account.

  • The budget is zero
  • Other systems read and write the content

What actually differs.

Codebase fit

Code in your repository

ZeroCMS

Nothing. The editor is generated from the schemas and components already in the repository.

Keystatic

A dependency, a config file owned by the CMS, an integration in your Astro config, the content model declared a second time, and credentials the repo and deploy carry.

AI capabilities

AI capabilities

ZeroCMS

A built-in agent you hand tasks to, with custom skills.

Keystatic

No built-in AI.

Cost, licence and compliance

GDPR compliance

ZeroCMS

States GDPR compliance.

Keystatic

Makes no GDPR statement.

Publishing and review

Review before publish

ZeroCMS

Every change is shown as a diff before it goes live.

Keystatic

There is no way to see exactly what changed.

Governance and access

Email invitations

ZeroCMS

Editors are invited by email.

Keystatic

No email invitations.

Git and the repository

Git account required

ZeroCMS

Anyone you invite by email. Editors need no Git account or seat.

Keystatic

Git-host collaborators with write access to the repository.

Astro fit

Preview output modes

ZeroCMS

Previews static and server-rendered.

Keystatic

No preview for any output mode.

APIs and extensibility

CLI

ZeroCMS

No CLI.

Keystatic

A CLI for the account, its sites and its builds, but not the content.

Every aspect, side by side, in the full Astro CMS comparison →
Still not sure?

Zero adds nothing to the repository.

Keystatic adds five things to your repository, the content model declared a second time among them. That matters if you want the repo left alone. Connect an Astro repo and see the difference in ten minutes.

14 days free · no credit card