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.
No credit card, cancel anytime.
The Next.js handoff problem
Next.js is the default for agency work and still awkward to hand over. A headless CMS means modeling a schema, installing an SDK, and rewriting pages to fetch content from an API, real work for a brochure site with a dozen pages. Keeping content in the components is clean for you and unusable for the client. So every phone-number change becomes an email to you.
CMS Brew takes a different path. Content stays in the repository, in the components and files where it already lives. CMS Brew maps the editable text and images automatically, your client edits in chat, and each publish is one commit that triggers your normal build.
Nothing added to your app
No SDK, no provider, no script tag, no content fetching to rewrite. The repo stays a plain Next.js project; CMS Brew reads it and commits to it from outside.
Made for how Next.js stores content
Pages, components, MDX, JSON, frontmatter, images. CMS Brew maps your existing files, handles dynamic routes 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. | 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. |
The honest trade-off
If a site needs thousands of structured entries, localization pipelines, or content shared across several apps, a real 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.
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