The CMS your Astro site has been missing.
Edit your content collections in a real visual editor. Every draft opens a pull request with its own preview — publish merges it. No code, no lock-in, no copy-pasting Markdown.
Open a draft · Preview the PR · Merge to publish
Today we shipped.
Everything an Astro content team needs. Nothing it doesn’t.
Astro CMS sits on top of the repo you already have. It adds the editing layer your site was missing without asking you to give up Git, ownership, or speed.
Edit content, not code
A real editor for your content collections — title, dates, tags, and body, laid out from your schema. Writers never touch Markdown or YAML.
Every draft is a pull request
Open a draft and Astro CMS opens a PR against your repo. Real branches, real diffs, full history — reviewed and merged with the Git tools you already use.
Preview before you merge
Each pull request gets its own preview deploy. See the rendered page and share the link, then merge once it looks right.
Schema-aware fields
Astro CMS reads your content config, so fields, required rules, and select options match your collections exactly. No drift between code and CMS.
Publish merges the PR
Hit publish and Astro CMS merges the pull request. Your site rebuilds and deploys itself — no manual git pulls, no waiting on an engineer.
Built for teams
Workspaces, roles, and a shared queue of drafts. Editors write, owners review and merge — everyone sees who changed what.
From repo to published in four steps.
Astro CMS works the way your site already deploys. Git in, Git out — with a friendly editing surface in between.
- 01
Connect your repo
Sign in and point Astro CMS at the GitHub repository for your Astro site. It reads your content config to learn your collections and fields.
- 02
Edit in a draft
Open a draft and write. Astro CMS opens a pull request behind the scenes and commits your edits to it as you go — no Markdown wrangling.
- 03
Preview the pull request
Every PR gets its own preview deploy. Check the real, rendered page and share the link, so the team can review before anything ships.
- 04
Publish merges the PR
Hit publish and Astro CMS merges the pull request. Your site rebuilds, deploys, and the change lands in your main branch. You own all of it.
Questions, answered straight.
The short version of what people ask before connecting a repo.
What is Astro CMS?
Astro CMS is a visual content editor for sites built with Astro. It edits your content collections in the browser and writes every change back to your Git repository as a commit, so your content stays in your repo and your site deploys the way it already does.
Where does my content live?
In your own Git repository, exactly where it does now. Astro CMS never copies your content into a separate database you have to sync or export. Every edit is a normal commit you can read, diff, and revert with standard Git tools.
Do I have to change how my site is built?
No. Astro CMS sits on top of your existing Astro project and content collections. Point it at your repo, and it reads your content config to learn your collections and fields. Your build and deploy pipeline keeps working as-is.
How do previews and publishing work?
Every draft is a pull request against your repository, and each pull request gets its own preview deploy — so you can see the rendered page and review the diff before anything goes live. When you publish, Astro CMS merges the pull request and your site rebuilds and deploys automatically.
Can my whole team use it?
Yes. Astro CMS supports workspaces with role-based access, so editors can write and owners can review and publish. Everyone shares a queue of drafts and can see who changed what.
Who makes Astro CMS?
Astro CMS is a product of Periapse Labs, a US-based senior development studio. You can reach the team through PeriapseLabs.com.
Give your Astro site a CMS in minutes.
Connect a repository, invite your team, and start editing. Free to start, and your content never leaves your Git history.