# CMS for Hugo sites clients actually use.

> Hugo already keeps content in Markdown, in Git. CMS Brew adds the missing piece: your client edits 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 Markdown and front matter, 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 admin panel to host, update, or secure
- Markdown, front matter, and images, scoped per page
- New pages, layout, and code go to you, in the client's words

## CMS Brew vs Git-based admin panel, side by side

| | CMS Brew | Git-based admin panel |
| --- | --- | --- |
| Setup per site | Connect the GitHub or GitLab repository. Content is mapped automatically. | Write and maintain a config file describing collections and fields. |
| What the client sees | A chat. They describe the change in plain words and watch a live preview. | A form admin at /admin with collections and widgets to learn. |
| Client sign-in | Built in: Google or an emailed 6-digit code. | Bring your own OAuth app or auth bridge. |
| Review before publish | Per-field guards and a review queue, included. | Editorial workflow adds drafts, not per-field rules. |
| Out-of-scope requests | Refused in the editor and escalated to you with the client's original words. | Not a concept. The request reaches you as an email or a phone call. |
| Publishing | One commit; your host rebuilds Hugo as usual. One-click revert. | Also Git commits. Both tools keep content in your repo. |
| Price | $39/mo for 5 sites, unlimited editors, 7-day free trial. | Usually free and open source, plus your time for config and auth upkeep. |

## Where the other option wins

If you already have Decap or another panel wired, with auth working and a client who knows the forms, there is no urgency to move. CMS Brew earns its fee when the panel is the problem: rare editors who forget the UI between visits, config and OAuth you would rather not maintain, and changes you want to review before they publish.

## FAQ

### Does CMS Brew work with my Hugo front matter and shortcodes?

It edits the content of your existing pages: the Markdown body, front matter fields, and images. Shortcodes and layouts are treated as structure, the editor does not rewrite them, and a request to change how the site works is escalated to you rather than guessed at.

### Do I need to change how my site is built?

No. Nothing is installed and no admin page is added to the site. CMS Brew reads the repository, and publishes arrive as normal commits, so your existing Hugo build keeps working exactly as it does 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-Hugo sites?

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