# CMS for the Next.js sites you hand to clients.

> No SDK, no schema, no provider to wrap your app in. Your client edits the Next.js site by chat, and every publish is a plain commit.

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

CMS Brew maps the text and images in your pages, components, MDX, and JSON, 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 SDK, provider, or script tag in the app
- MDX, JSON, frontmatter, and dynamic routes 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. | Install an SDK, define a schema, rewrite pages to fetch from an API. |
| Where content lives | In your repository, in the components and files Next.js already renders. | In the vendor's database, behind their API. |
| 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, a traditional headless CMS earns its schema. For the marketing site, the brochure site, the 20-page client build, moving content out of the repo is cost without payoff.

## FAQ

### Does CMS Brew work with the App Router and the Pages Router?

Yes. CMS Brew edits the files in your repository rather than plugging into the framework at runtime, so the router, rendering mode, and Next.js version do not matter. If the site builds from the repo, its content can be edited.

### Do I need to move content into a CMS or database?

No. Content stays where it already is: in your components, MDX, and JSON. CMS Brew maps the editable text and images automatically when you connect the repository, and every edit arrives as a normal Git commit.

### 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-Next.js sites?

Yes. The same account covers Astro, Vue, SvelteKit, Nuxt, Remix, Gatsby, 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)