CMS for the Vue sites you hand to clients.
No SDK, no schema, no content layer to bolt on. Your client edits the Vue site by chat, and every publish is a plain commit your host rebuilds from.
No credit card, cancel anytime.
The Vue handoff problem
A Vue site built with Vite has no content layer by default. The copy lives inside .vue single-file components, which is clean for you and untouchable for a client. The moment you want them to change a headline, you are choosing between three chores: bolt on a headless CMS with a schema and fetch calls, wire up a Git-based admin panel with a config file to maintain, or just do every edit yourself.
There is a fourth option. CMS Brew reads the repository directly, maps the editable text and images inside your components automatically, and lets the client edit them in chat. Nothing is added to the app, and each publish is one commit that triggers your normal build.
Nothing added to your app
No SDK, no plugin, no provider to wrap the app in, no content fetching to write. The repo stays a plain Vue project; CMS Brew reads it and commits to it from outside.
Editing built for .vue files
CMS Brew maps the editable text and images inside your single-file components and templates, 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 components to fetch from an API. |
| Vue support | Not a feature, a non-issue: CMS Brew edits the repo, not the runtime. | Often secondary: SDKs and visual editors are React-first. |
| Where content lives | In your repository, in the components Vue 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. |
| 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 portfolio, the small-business 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