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

## Your client edits the page, not a form. Risky changes wait for you.

CMS Brew maps the text and images your site sources locally, the Markdown, MDX, JSON, and component copy, and the client edits them on the page or in chat. Per-field guards decide what publishes on its own and what waits for you.

- No source plugin, schema extension, or GraphQL query to touch
- Markdown, MDX, JSON, frontmatter, and dynamic pages like blog/[slug]
- New pages, layout, and code go to you, in the client's words

## CMS Brew vs Traditional headless CMS, side by side

| | CMS Brew | Traditional headless CMS |
| --- | --- | --- |
| Integration work | Connect the GitHub or GitLab 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. |

## Where the other option wins

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

## FAQ

### Does CMS Brew work with my Markdown and MDX Gatsby content?

Yes. CMS Brew maps the editable text and images in the files your site sources locally, including Markdown, MDX, JSON, and frontmatter, plus copy in your components. It handles dynamic pages like /blog/[slug] per page, and a brand-new page or section is an out-of-scope request that gets escalated to you.

### Do I need to add a source plugin or change my GraphQL queries?

No. Nothing is installed and no query changes. CMS Brew reads the files in your repository directly and publishes plain commits, so your existing source plugins, GraphQL layer, and build keep working exactly as they do today.

### Which hosts does CMS Brew support?

Vercel, Netlify, and Cloudflare, with live previews built into the editor. Because every publish is a plain commit, publishing works with any host that rebuilds your site from Git.

### What happens when the client asks for a new page or a redesign?

The editor refuses it and routes it to you with the client's original message attached, by email or Slack if you have escalations configured. The client gets a clear answer, and you get the work request instead of a surprise on the live site.

### Does CMS Brew also work for my non-Gatsby sites?

Yes. The same account covers Next.js, Vue, SvelteKit, Astro, Nuxt, Remix, and Hugo sites, so one tool can carry your whole client portfolio. Pricing is per connected site: $39 per month includes 5.

---

- [Home](https://cmsbrew.com/)
- [Features](https://cmsbrew.com/features)
- [Full product details](https://cmsbrew.com/llms-full.txt)