Keystatic

What Is Keystatic?

Keystatic is a Git-native content management system built by Thinkmill, the Sydney-based agency behind KeystoneJS. Released in 2023, it takes a fundamentally different approach to content management than API-first platforms like Sanity or Contentful: instead of storing content in a cloud database and serving it via API, Keystatic stores everything as Markdown, YAML, or JSON files directly in your Git repository. The admin UI sits inside your application and reads from and writes to those files. There is no separate CMS server, no third-party database, and no content delivery API to configure or pay for.

The design philosophy is code-first and version-control-native. Content changes are Git commits. Your schema lives in a TypeScript config file that ships with the project. Every field, collection, and singleton is defined in code, which means content models are versioned, reviewable, and consistent across environments. If you already understand your frontend codebase, you understand your content model, because they live in the same repository.

Keystatic ships in two operational modes: local mode, where the admin UI reads and writes directly to disk during development, and GitHub mode, where changes are committed to a GitHub repository via the GitHub API. The latter is production mode for real teams, and Keystatic Cloud provides the OAuth and authentication layer that makes this work without needing to manage GitHub Apps manually. The system is explicitly designed for modern JavaScript frameworks, with first-class support for Astro, Next.js, and Remix.

Key Features

• File-based storage: Content is Markdown, YAML, and JSON in your Git repo, no external database required
• TypeScript config with 30+ field types: Text, slug, date, image, rich text (Markdoc or MDX), arrays, blocks, conditionals, relationships, and more, all fully type-safe
• Collections and singletons: Collections manage repeating entries (blog posts, case studies), singletons manage global content (site settings, homepage hero)
• Local and GitHub modes: Local mode for development, GitHub mode for production team editing with commits made via GitHub API
• Keystatic Cloud: Handles authentication for editors without GitHub accounts, up to 3 users free, Pro plan adds Cloud Images and experimental multi-player editing
• Reader API: Type-safe content querying that integrates cleanly with Astro content collections and Next.js data fetching patterns
• Official Astro and Next.js integrations: First-party integrations with starter templates and documented setup paths
• Zero CMS infrastructure: No CMS servers to deploy, no databases to manage, no separate hosting bill

Pricing

Keystatic itself is MIT-licensed open source and free to self-host. Running it in local mode costs nothing. Running it in GitHub mode requires either manual GitHub OAuth App configuration (free but technical) or Keystatic Cloud.

Keystatic Cloud Free: Unlimited projects and teams, up to 3 users per team, basic GitHub authentication handled for you. This covers most small agency projects and personal sites.

Keystatic Cloud Pro: $10/month per team, plus $5/month per user beyond the first 3. This unlocks two features: Cloud Images (asset upload, optimization, and CDN delivery without storing binaries in Git) and multi-player editing (currently listed as experimental). Pro is the tier you need once a team grows beyond 3 editors or once images at scale become a problem.

Cloud Images on Pro is a genuine value add for content-heavy sites where managing image assets via Git is impractical.

Our Experience

We have used Keystatic on Astro projects and found the developer experience genuinely excellent. The TypeScript config is well-designed, the Reader API is ergonomic, and the Astro integration sets up cleanly. The admin UI is polished relative to what you would expect from a project at this stage. When we evaluate Git-based CMS tools, Keystatic is the one we reach for first in the Astro ecosystem specifically, because the integration is first-party and the schema system is the most expressive available.

The honest limitations show up as soon as you move beyond a small developer-adjacent team. A content team that needs to schedule posts, run approval workflows, manage translations, or publish without any Git awareness will run into walls quickly. There is no scheduling, no workflow engine, no localization layer, and the draft model is a browser localStorage workaround rather than a true staging system. These are not Keystatic-specific failures so much as fundamental characteristics of the Git-based CMS category, but they matter when scoping projects for clients with active editorial teams.

Our typical use case for Keystatic is a marketing site or blog where the client has one to three people editing content, they are comfortable with the concept of changes becoming commits, and the site is built on Astro. In those conditions, Keystatic delivers the full editorial autonomy the client needs without any of the infrastructure overhead of a hosted CMS. When the client profile shifts toward editorial independence, content scheduling, or multi-locale publishing, we move toward Statamic for Laravel-backed projects or Sanity for pure headless work.

When Lucky Media Recommends Keystatic

We reach for Keystatic when:

• The project is built on Astro or Next.js and the team is developer-led
• Content editors are comfortable with a Git-adjacent workflow (or don't need true editorial independence)
• The site is content-light to content-medium: a blog, documentation site, or marketing site with under a few hundred entries
• Infrastructure simplicity matters: no CMS hosting, no additional database, no separate deployment pipeline
• Budget is a real constraint and a $0 CMS with a polished admin UI is a genuine requirement
• The team wants full control over the content schema in TypeScript, with changes tracked in version control

We would suggest alternatives when:

• Editors need to schedule content, run approval workflows, or publish independently without any Git involvement
• The project requires multi-locale content management with translation status tracking
• Asset volume is high and storing images in Git is not an option (unless upgrading to Cloud Pro)
• The client is enterprise-scale with complex permissions, audit trails, or compliance requirements
• Real-time collaboration between simultaneous editors is a core workflow requirement
• The project needs a management API to ingest content programmatically from external systems

faq

How much does Keystatic cost?

Keystatic is open source and free to self-host. Running it in local mode during development costs nothing. For production team use, Keystatic Cloud handles authentication and GitHub access for editors. The Free tier covers up to 3 users per team at no cost. The Pro plan is $10/month per team plus $5/month per user beyond the first 3. Pro unlocks Cloud Images (assets stored on a CDN instead of in Git) and experimental multi-player editing. For most small projects, the free tier is sufficient.

Can non-developers use Keystatic to publish content?

Yes, but with caveats. The admin UI is clean and generally intuitive for basic tasks like writing a post, editing metadata, and uploading images. The challenge is the underlying model: saving content creates a GitHub commit, and editors need a Keystatic Cloud account or GitHub access. There are no approval queues or staging areas separate from the repository. A non-developer editor can publish independently once someone sets up the project, but they need to be comfortable with the concept of their saves being code commits.

How does Keystatic handle images and media?

In local and basic GitHub mode, images are stored directly in your Git repository alongside your code. This works fine for small sites but becomes a problem as your repo grows because binary assets bloat the Git history. The Keystatic Cloud Pro plan ($10/mo per team) adds Cloud Images, which uploads assets to a CDN and keeps them out of your repository. For any site with a meaningful volume of images, Cloud Images or an external asset host (like Cloudinary connected at the framework level) is the recommended approach.

Does Keystatic support content scheduling or draft workflows?

No. There is no native content scheduling, no review-and-approve workflow, and no draft state that exists independently of Git. Unsaved changes are stored in the browser's local storage, but a "draft" in the CMS sense requires either an unpublished Git branch or a manual convention in your content model (a boolean published field filtered at the framework layer). If your team needs editorial workflows with scheduled publication, Keystatic is not the right tool without significant custom work.

How does Keystatic compare to TinaCMS?

Both are Git-based and TypeScript-first. TinaCMS has a longer track record (~9k GitHub stars vs ~2k for Keystatic) and offers visual in-context editing, which Keystatic does not. Keystatic has a substantially cleaner integration with Astro specifically, and its admin UI is more polished for pure content editing tasks. TinaCMS offers branch-based workflows in its paid cloud tier. Keystatic's free tier is more generous. The choice usually comes down to whether visual editing matters for your team (TinaCMS) or whether a clean Astro integration and developer experience is the priority (Keystatic).

How does Keystatic compare to TinaCMS and Decap CMS?

All three are Git-based, but they differ in maturity and focus. TinaCMS (~9k GitHub stars) offers visual in-context editing that Keystatic does not have, and branch-based workflows on its paid cloud tier. Decap CMS (formerly Netlify CMS, ~18k stars) is the most established and integrates with many backends beyond GitHub. Keystatic has the cleanest Astro integration of the three and the most polished content editing UI, but the smallest community. If visual editing is a requirement, TinaCMS has the edge. If you are building with Astro and want a developer-first experience, Keystatic is the strongest option.