CMS for Remix sites, content, not just data.
Remix is built for data, not content. CMS Brew adds the missing piece: your client edits the copy by chat, and every publish is a plain commit your host rebuilds from.
No credit card, cancel anytime.
The Remix handoff problem
Remix is built around loaders and actions: it is superb at moving data, and it says nothing about where a marketing site's content should live. So on a delivered client site the copy usually ends up hardcoded in route modules, or fetched by a loader from a store you now maintain. Either way, when the client wants to change a headline, there is no seam for them to reach.
CMS Brew adds that seam without a data layer. It maps the editable text and images in your route modules and components automatically, the client edits in chat, and each publish is one commit that triggers your normal build. No loader to write, nothing added to the app.
No loader plumbing
You do not wire a content source, write a loader, or model a schema to make the site editable. CMS Brew reads the repository and commits to it from outside; the app stays a plain Remix project.
Edits the copy where it lives
CMS Brew maps the editable text and images inside your route modules and components, 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, model a schema, and load content through a loader. |
| Where content lives | In your repository, in the route modules and components Remix 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 the site is genuinely data-driven, a catalog, a dashboard, thousands of entries, that content belongs in a database or a headless CMS, and Remix loaders are the right way to fetch it. CMS Brew is for the marketing copy around it: the pages, the headlines, the images a client wants to change without calling you.
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