CMS for the Gatsby sites you still maintain.
No new source plugin, no GraphQL layer to wire, no admin panel. Your client edits the Gatsby site by chat, and every publish is a plain commit your host rebuilds from.
No credit card, cancel anytime.
The Gatsby handoff problem
Gatsby's whole design points at a CMS: content comes in through a source plugin and gets queried from the GraphQL data layer. That is powerful, and it is also the tax. Making a delivered site client-editable the Gatsby way means running a headless CMS behind gatsby-source-something, keeping the schema and queries in sync, and still handing the client an editor to learn. For a site you are simply keeping alive, that is a lot of moving parts for a headline change.
CMS Brew skips the data layer. It maps the editable text and images already in your repository, the Markdown, MDX, JSON, and component copy your site sources locally, the client edits in chat, and each publish is one commit that triggers your normal build.
No source plugin, no GraphQL
You do not add a source plugin, extend the schema, or touch a GraphQL query to make the site editable. CMS Brew reads the repository and commits to it from outside; the build stays exactly as it is.
Edits the content Gatsby sources locally
Markdown, MDX, JSON, frontmatter, images, and component copy. CMS Brew maps your existing files, handles dynamic pages like blog/[slug], and scopes edits per page, so the client edits the page they mean.
Safe enough for clients
Per-field guard levels decide what publishes freely and what waits for review, and requests for new pages, layout, or code are refused in the chat and escalated to you with the client's words attached.
Side by side
CMS Brew vs Headless CMS
| CMS Brew | Headless CMS | |
|---|---|---|
| Integration work | Connect the GitHub repository. That is the setup. | Add a source plugin, model a schema, and query content through GraphQL. |
| Where content lives | In your repository, in the files Gatsby sources at build time. | In the vendor's database, behind their API and a source plugin. |
| What the client learns | Nothing. They type what they want changed. | The studio UI and your content model. |
| Publishing | One commit; Vercel, Netlify, or Cloudflare rebuilds as usual. | A webhook from the CMS triggers your builds. |
| Review before publish | Per-field guards and a review queue, included. | Roles and approval workflows, usually on higher tiers. |
| Cost model | $39/mo for 5 sites, unlimited editors. | Per-seat pricing that grows with every editor you invite. |
The honest trade-off
If a site needs thousands of structured entries, localization pipelines, or content shared across several apps, the source-plugin model earns its keep and a real headless CMS behind it is the right call. For the brochure site or the legacy build you are keeping online, adding that machinery just so a client can edit a headline is cost without payoff.
How it works
Three steps, then it's live.
- 01Connect
Point it at the site you built
CMS Brew turns it into a simple list of things your client can edit. No rebuild, no plugin.
- 02Edit
Clients edit in plain words
Your client opens a chat and says what to change: a phone number, a headline, a photo. They see it live before it ships.
- 03Publish
Safe changes go live
Safe edits publish in one click. Bigger requests, like a new page or code, come straight to you.
FAQ
What people ask before switching.
Stop being the person who updates the phone number.
Give your client the keys to the content. Keep the keys to the code.
Prefer to talk first? Book a 30-minute call