Keystatic
Git-based headless CMS with a local editing UI that stores content as files (Markdown, YAML, JSON) in your repository. No database required — content lives in git alongside code. Works with Astro, Next.js, and Remix. Includes a local editing admin UI accessible in development and a cloud UI for non-developers via Keystatic Cloud. Positioned as the developer-friendly CMS where content is code and editors get a polished UI.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Content stored in git — full audit trail. GitHub OAuth for access control. No proprietary database holding sensitive content. MIT open source and auditable.
⚡ Reliability
Best When
You want content editing for a git-deployed static/SSG site (Astro, Next.js) where content living in git as files is the right architectural choice.
Avoid When
You have many concurrent editors, complex content relationships, or high content volume — use Contentful, Sanity, or Payload CMS for database-backed content management.
Use Cases
- • Add content editing UI to Astro, Next.js, or Remix sites where content is stored as Markdown/YAML in git — no database setup
- • Enable non-developer content editors to update website content via Keystatic's admin UI without touching code
- • Build documentation sites where content lives in git and editors use a polished UI instead of raw Markdown
- • Create blog/marketing sites where all content is version-controlled in git with full history and rollback capability
- • Deploy JAMstack sites with content editing that doesn't require a separate CMS database or Contentful/Sanity subscription
Not For
- • High-volume content with many concurrent editors — git-based storage has merge conflicts at scale; use Contentful or Sanity for CMS at scale
- • Non-git workflows — Keystatic requires git integration for content versioning
- • Complex content relationships requiring database-style queries — file-based content has limited relational query capabilities
Interface
Authentication
Local mode: no auth (local dev). Keystatic Cloud: GitHub OAuth for editor access. Cloud mode requires Keystatic Cloud account for non-developer content editing.
Pricing
MIT licensed. Local mode is fully free. Keystatic Cloud adds hosted admin UI for non-developers; free tier available. Open source project from Thinkmill.
Agent Metadata
Known Gotchas
- ⚠ Keystatic stores content as files — concurrent edits by multiple users cause git merge conflicts that require manual resolution
- ⚠ Schema changes require updating both the Keystatic config AND migrating existing content files — no automatic migration
- ⚠ Keystatic Cloud (for non-developer editors) requires GitHub OAuth and separate cloud account — local mode only works in development
- ⚠ Content is read from the filesystem at build time — dynamic runtime content editing is not supported without rebuild
- ⚠ YAML/Markdown content parsing must match Keystatic's field schema exactly — schema mismatches cause runtime errors
- ⚠ GitHub API rate limits apply when using Keystatic Cloud — heavy concurrent editing can hit GitHub's API limits
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Keystatic.
Scores are editorial opinions as of 2026-03-06.