Built for Astro content collections

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, and publish merges it. No code, no lock-in, no copy-pasting Markdown.

Start free → See how it works

Open a draft · Preview the PR · Merge to publish

The Periapse CMS visual editor: a post open for editing with its collection sidebar, frontmatter fields, and a draft ready to push to preview.
Features

Everything an Astro content team needs. Nothing it doesn’t.

Periapse 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 Periapse 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.

Built for Cloudflare

We watch your Cloudflare build for each pull request and surface its preview link the moment it goes live, so you can check the real, deployed page before you merge.

Schema-aware fields

Periapse 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 Periapse CMS merges the pull request. Your site rebuilds and deploys itself. No manual git pulls, no waiting on an engineer.

astro-cms.json 
1234567891011121314151617181920212223242526272829303132333435363738394041424344{
  "url": "https://periapselabs.com",
  "collections": {
    "posts": {
      "label": "Posts",
      "content": "src/content/posts",
      "images": "src/assets/images/posts",
      "sidebar": {
        "groupBy": "year",
        "pinDrafts": true,
        "sortBy": "pubDate"
      },
      "fields": {
        "title": {
          "type": "string",
          "label": "Title",
          "required": true
        },
        "pubDate": {
          "type": "date",
          "label": "Publish date",
          "required": true
        },
        "description": {
          "type": "string",
          "label": "Description",
          "required": true,
          "multiline": true
        },
        "cover": {
          "type": "image",
          "label": "Cover image",
          "required": true,
          "basePath": "src/assets/images"
        },
        "tags": {
          "type": "array",
          "label": "Tags",
          "items": { "type": "string" }
        }
      }
    }
  }
}
Configuration

One config file. Your whole CMS.

Drop an astro-cms.json at the root of your repo and Periapse CMS knows exactly what to edit. Point it at your collections, declare your fields, and the editor builds itself to match.

  • content is where the Markdown goes. Every post you write is saved as a .md file straight into this folder, one file per entry. Opinionated by design, so your collection stays flat and predictable.
  • images is the root for uploads. Each post gets its own folder, so an entry’s images land together at /images/post/{slug} and never collide. That layout is the default. Point it anywhere you like.
  • Describes your fields. Types, labels, and required rules drive the form: strings, dates, images, and arrays included.
  • Lives in Git. It is committed alongside your content, versioned and reviewable like everything else in the repo.
Why this way?

Opinionated, on purpose.

Periapse CMS is built around a few hard convictions about what a content tool should, and shouldn’t, make you carry.

Writing comes first

Sanity and most of the others bury you in boilerplate and schema wrangling before you can type a sentence, and the writing surface itself is an afterthought. We flipped it: a clean, focused editor up front, configuration out of the way.

Your content is just files

No proprietary database, no being landlocked to someone’s infrastructure, no inventing a query language to get your own words back. Everything lives as plain Markdown in your repo: portable, greppable, and yours to move anytime.

No dependencies

Every dependency is a future break, a security patch, a thing you didn’t write but now own. We keep the footprint as close to zero as we can, so what runs your content stays small, auditable, and boring, in the best way.

Genuinely cost-effective

Because it’s files and Git, there’s no heavy backend to pay for and nothing exotic to scale. It runs cheap, scales with your repo and your host, and stays simple enough that you never need a specialist to keep the lights on.

How it works

From repo to published in four steps.

Periapse CMS works the way your site already deploys. Git in, Git out, with a friendly editing surface in between.

  1. 01

    Connect your repo

    Sign in and point Periapse CMS at the GitHub repository for your Astro site. It reads your content config to learn your collections and fields.

  2. 02

    Edit in a draft

    Open a draft and write. Periapse CMS opens a pull request behind the scenes and commits your edits to it as you go. No Markdown wrangling.

  3. 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.

  4. 04

    Publish merges the PR

    Hit publish and Periapse CMS merges the pull request. Your site rebuilds, deploys, and the change lands in your main branch. You own all of it.

FAQ

Questions, answered straight.

The short version of what people ask before connecting a repo.

What is Periapse CMS?

Periapse CMS lets you edit your Astro content collections in a Notion-like editor, right in the browser. You write in a clean, familiar surface, and every change is committed straight back to your Git repository, so your content stays in your repo and your site deploys the way it already does. We like to call it Astro’s missing CMS.

Where does my content live?

In your own Git repository, exactly where it does now. Periapse 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. Periapse 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, Periapse CMS merges the pull request and your site rebuilds and deploys automatically.

Can my whole team use it?

Yes. Periapse 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 Periapse CMS?

Periapse CMS is a product of Periapse Labs, a US-based senior development studio. You can reach the team through PeriapseLabs.com.

Is Periapse CMS affiliated with Astro or Cloudflare?

No. Periapse CMS is an independent, unofficial tool built by Periapse Labs. We pitch it as "Astro’s Missing CMS" because it fills the content-editing gap for Astro sites, but the product is named Periapse CMS. We do not call it "Astro CMS" or claim that name. It is not made, endorsed, sponsored, or maintained by the Astro project or Cloudflare. "Astro" is a trademark of its respective owner; we use the name only to describe what our tool works with: Astro content collections.

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.

Start free → Log in