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.
No credit card, cancel anytime.
Built for Hugo
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
Side by side
CMS Brew vs Git-based admin panel
| 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. |
The honest trade-off
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.
How it works
Three steps, then it's live.
- 01Connect
Point it at the site you built
CMS Brew turns every page, blog post and language into a simple list of things your client can edit. No rebuild, no plugin.
- 02Edit
Clients edit in plain words
Your client says what to change in chat, or clicks the words on the page and retypes them. 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