Keystatic

Keystatic is a codebase-oriented CMS for editing Markdown, YAML and JSON through a visual admin interface or directly in project files. It fits developers and content teams whose publishing process already uses Git, especially with Astro, Next.js or Remix. The central trade-off is a database-free, file-based workflow against an experimental project and extra Cloud charges for larger teams.

Overview

Keystatic stores content in a project directory instead of a separate database. You can keep changes local, commit them to GitHub, or use both storage modes. That makes it a practical match for repositories where content changes move through commits, branches and existing deployment automation. It is less suitable when editors expect a conventional hosted CMS with database administration separate from the codebase.

Markdown and YAML/JSON are supported, including Markdoc and MDX. The Reader API retrieves data from a project directory, allowing an application to consume the same files that editors maintain. Keystatic is developed by Thinkmill as part of Thinkmill Labs Research and Development, and its GitHub project describes it as experimental. Production teams that require a mature, stability-first foundation should treat that status as a serious qualification.

Key features

File editing and Git storage

The visual editor gives non-developers a structured way to change repository content while developers retain direct file editing. Local storage is useful for an entirely self-hosted workflow; GitHub storage suits teams that want edits represented in the repository. Supporting both lets a project accommodate different publishing arrangements, but it also keeps content operations tied to Git concepts rather than a standalone editorial system.

Formats, preview and integrations

Markdown, YAML and JSON support covers common documentation and structured-content models, with Markdoc and MDX for projects using those formats. Visual editing and live preview help editors work through an interface rather than raw syntax. Integration guides for Astro, Next.js and Remix make Keystatic most compelling for teams already using one of those frameworks. Branching is part of its content workflow, and Git-commit deployment aligns publishing with repository changes.

Cloud collaboration and media

Keystatic Cloud connects to GitHub and lets team members edit without their own GitHub account. A Cloud team can contain multiple projects, and every user on that team can access all of them, so the access model is broad rather than project-specific. Cloud Images is an opt-in service for storing, optimizing and delivering web images. Cloud Pro adds experimental real-time multi-player editing on the same document; that may help simultaneous editorial work, but its experimental label makes it a feature to adopt cautiously.

Pricing

The Free plan is the sensible starting point for an individual or small team that can stay within three users per team. Unlimited teams and projects avoid a project-count ceiling, but the per-team user cap limits larger editorial groups. Cloud Pro is aimed at teams needing hosted GitHub authentication, image services or simultaneous editing; the $10 monthly base rises by $5 for every user beyond three, so collaboration costs scale with headcount. No trial term or annual billing option is stated.

Platforms

Keystatic is offered through web and API access, with self-hosting supported. That combination suits teams wanting a browser editor while retaining control of the runtime and repository. GitHub is the supported Git provider. Hosting can be self-managed or use Keystatic Cloud, depending on how much infrastructure the team wants to operate.

Who it's for

Choose Keystatic if your site keeps content in Git, your developers are comfortable with Markdown or structured data files, and your stack is Astro, Next.js or Remix. It is also a fit for small teams that need a visual editor without introducing a database, or for Cloud teams that value GitHub-connected access for non-GitHub users. Look elsewhere if you need a stability-proven platform, granular project-level access within one team, or a database-first editorial model.

Pros and cons

• Pro: Markdown, YAML and JSON stay in the codebase, preserving a Git-native source of truth.
• Pro: Local, GitHub or combined storage supports both self-hosted and cloud-oriented workflows.
• Pro: Astro, Next.js and Remix guides reduce friction for those framework communities.
• Pro: The Free plan allows unlimited teams and projects, subject to three users per team.
• Con: The project is experimental, which raises adoption risk for teams demanding mature stability.
• Con: Cloud teams give every user access to every project in that team, limiting separation between projects.
• Con: Cloud Pro adds $5 monthly for each user beyond three, making larger teams progressively more expensive.

Alternatives

For a broader comparison, see Git-Based CMS. Choose Quiqr instead if you want a free, open-source option that runs across desktop platforms, web and self-hosting. deco CMS suits readers seeking an open-source, self-hostable core that the company says is free. Mattrbld is worth considering for mobile access alongside web and self-hosting, with a free hosted instance aimed at small private projects. Decap CMS offers a free-forever plan for one site and one seat. Dhub is a fit for a single user editing public repositories through GitHub, while its Pro plan costs $41 a month. HugoCMS targets Hugo users with a free per-domain plan and a €139 a month paid-once Pro option. Kiln is the alternative for teams wanting a free, AGPL-3.0 self-hosted setup. Netlify is better when the priority is a broader web platform, with a Free plan at $0/month and 300 credits per month.

Verdict

Keystatic is a strong choice for Git-oriented developers and small content teams that want visual editing over repository files without a database. Its flexible storage, framework integrations and generous project allowance are the main reasons to choose it. Look elsewhere when experimental software, broad team access or rising per-user Cloud pricing conflicts with your operational requirements.