Publish and revert
Publishing is a normal Git commit to the branch you already deploy from. There is no content database, nothing added to your site, and every publish comes back out in a single click.
No credit card, cancel anytime.
Benefits
Everything the client has pending ships together as one labelled commit, not one commit per keystroke.
Your host rebuilds exactly as if you had pushed it yourself. No new build step and no new service.
Your host keeps serving the last good deployment, so the live site does not change until a build succeeds.
The repository stays the only source of truth. If you stop using CMS Brew tomorrow, the content is already where it lives.
How it works
The client can make ten changes across a page before anything is committed.
It goes to the branch your site deploys from, labelled with what changed.
The same pipeline that has always built your site builds it again.
Any publish comes back out in one click, and the history keeps the record either way.
Use cases
You do not need to open a terminal. One click takes the publish back out and the site rebuilds.
Example
A price typo goes live at four in the afternoon. Revert takes it back out before you have finished reading the message about it.
Every publish is a labelled commit in your own history, so the tools you already use work on it.
There is nothing to unwind. The content is already committed to the repository you deliver.
Version history keeps the person and the time on every published state.
Pricing
Everything included. $39 a month for 5 sites, then $10 each.
50% off for 12 months
with code BREW50 for the first 20 customers (11 left)
Billed monthly.
Billed $312 yearly. Save 33%.
FAQ
Give your client the keys to the content. Keep the keys to the code.
Prefer to talk first? Book a 30-minute call