Question 1

Does CMS Brew work with content hardcoded in my Remix routes?

Accepted Answer

Yes. That is the common case, and it is exactly what CMS Brew maps: the editable text and images inside your route modules and components. It handles dynamic routes like /blog/[slug] per page, and a brand-new page or section is an out-of-scope request that gets escalated to you.

Question 2

What about content my loaders fetch from a database?

Accepted Answer

CMS Brew edits the content that lives in your repository, the copy in your routes and components. Data your loaders pull from a database or an external API is owned by that source, not the repo, so CMS Brew leaves it untouched. Most delivered marketing sites keep their copy in the repo, which is what it edits.

Question 3

Which hosts does CMS Brew support?

Accepted Answer

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.

Question 4

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

Accepted Answer

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.

Question 5

Does CMS Brew also work for my non-Remix sites?

Accepted Answer

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

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

CMS for Remix sites, content, not just data.

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

CMS Brew vs Traditional headless CMS

Three steps, then it's live.

Point it at the site you built

Clients edit in plain words

Safe changes go live

What people ask before switching.

Stop being the person who updates the phone number.