You
“Change the phone number to (555) 123-4567”
Updated 3 places, committed in 2 seconds.
Built for agencies tired of being the human CMSYour clients edit their own site.
Your clients edit their own site.
You stay in control.
CMS Chat lets your clients edit their website just by chatting: text, images, prices, links. Every edit lands as a plain Git commit in your repo. Anything bigger escalates to your team.
Get a beta invite
Free to join the list. We onboard a few agencies per wave.
- Chat to edit
- SEO Guardrails
- Safe Zones
- Team Escalation
Works with any Git framework
Next.js
Astro
Hugo
Nuxt
Remix
SvelteKit
Gatsby
HTML
The case
Stop being your clients’ human CMS.
Your client wants a phone number changed. It sits in the queue for three days, takes thirty seconds to do, and invoicing it costs more goodwill than it earns. Multiply by every client on your roster.
What if routine content changes never reached your inbox, and your team only got pinged for the work worth billing?
Self-serve editing
Your AI partner for every edit
CMS Chat reads your site, understands your stack, and commits safe changes the moment you describe them — no developer in the loop.
AI meets your workflow
From chat to commit in seconds
Connect any GitHub repo. Your AI editor scans the file structure, detects the framework, and applies safe edits as plain Git commits with full history.
Learn morecomponents/Hero.tsx
Apply suggestion
export function Hero() {return (<section>- <h1>Welcome to Acme Dental</h1>- <p>Call us at (555) 123-4567</p>+ <h1>Welcome to Acme Family Dental</h1>+ <p>Call us at (555) 987-6543</p></section>);}
SEO Guardrails
Warnings powered by Google rankings
Before changing a headline, title tag, or meta description, CMS Chat checks Google Search Console. If an element ranks well, you get a warning with the keyword, position, and traffic it drives.
How it worksSEO Warning
Heading ranks #3 for “best dentist NYC”
Position
#3
Clicks/mo
1,247
Impressions
42K
Safe Zones
Define what clients can change
Mark editable regions in your repo. Text and images stay open. Layout, code, and SEO-critical elements stay locked or escalate to your team automatically.
See zone configSearch zones
- 📝Hero textEditable
- 🖼️Hero imageEditable
- 📞Phone numberEditable
- 🔍Page titleWarn
- 🛡️Pricing layoutEscalate
- 🔒Footer codeLocked
Tier 2
Edit through chat — or commit straight to Git
Clients and your team chat with CMS Chat to edit content. Your team can also commit directly to GitHub when they want full control. Either path, the website and database stay perfectly in sync.
See full flowEditors
👤Client
👥Your team
Orchestrator
✨CMS Chat
Storage
🐙GitHub
🗄️Database
Output
🌐Website
60-second setup
Setup. Connect. Start editing.
Connect your site to CMS Chat. We scan it, detect the stack, map the editable parts, and hand you a chat box. That’s the whole onboarding.
~/agency/projects
$ npx cmschat connect
Connect your site and start editing
Sign in with GitHub or clone any repository. CMS Chat scans your code, detects the framework, and maps editable content automatically. Zero configuration.
- Works with Next.js, Astro, Hugo, Nuxt, Eleventy, plain HTML
- Detects safe-to-edit content automatically
- Optional client portal on your subdomain
Any Git repo
Built for the entire web
Wherever there’s a Git repo, CMS Chat can run the content — any stack, any language, clients anywhere in the world.
Example edits
Things you used to email your developer about
Illustrative examples, not customer quotes — this is the kind of request CMS Chat is built to handle without a ticket.
You
“Swap the hero image to the one I uploaded yesterday”
Image replaced + alt text refreshed.
You
“Bump the Pro plan from $29 to $39”
Updated pricing page + structured data + 3 mentions.
You
“Translate the About page to German”
/de/about created, navigation updated.
You
“Hide the holiday banner — we're past New Year”
Banner removed, layout recalculated.
You
“Update the LinkedIn link in the footer to my new company page”
1 link updated, sitemap unchanged.
Pricing
Priced by the sites you run
Three tiers, one difference between them: how many sites you connect. Every tier gets unlimited client edits and unlimited escalations. CMS Chat is in private beta — cancel whenever.
If your team spends two hours a month on content tickets for a site, the Starter plan already pays for itself. And that's before the client-relationship win of “done in two minutes” instead of “in next week's sprint.”
Starter
One site, the whole product. For the first client you hand over.
€99/month
- 1 connected site
- Unlimited client edits
- Unlimited escalations to your team
- Safe editing zones
- Image uploads & optimization
- Works with any Git repo
- Email support
Private beta
Agency
Design partner rateEverything the product does, for the sites you run.
€249/month
Design partners joining now pay €99/month for their first 3 months, then the standard rate.
- 3 connected sites
- Unlimited client edits
- Unlimited escalations to your team
- Safe editing zones
- Image uploads & optimization
- Works with any Git repo
- Email support
- Hands-on onboarding
Studio
Ten sites on one subscription: under €50 per client site.
€499/month
- 10 connected sites
- Unlimited client edits
- Unlimited escalations to your team
- Safe editing zones
- Image uploads & optimization
- Works with any Git repo
- Email support
- Hands-on onboarding
What is CMS Chat?
CMS Chat is an AI-powered editor for the website you already own. Connect your site, define what's safe to change, and edit content by chatting in plain language. Routine edits commit instantly. Anything bigger gets routed to your developer or team.
Who is CMS Chat for?
Web agencies and freelancers who build custom-code sites (Next.js, Astro, Hugo, anything in Git) and are tired of doing content edits by ticket. Your clients get the chat editor; you get the commits, the escalations, and the final say. If you run sites for clients, you're who we onboard first.
How does CMS Chat protect my SEO?
Built-in SEO guardrails warn before any change to title tags, meta descriptions, H1s, or other ranking-critical elements. If you try to edit a heading that performs well in Google search, CMS Chat shows you the keyword, position, and traffic at risk before it commits.
Can I break my website?
The guardrails are built so you can't: clients only edit text, images, prices and content inside zones your developer marked safe. Layout, code and SEO-critical elements stay locked or escalate. And because every change is a real commit, your developer can always see and reverse anything in their normal Git workflow.
What happens when the AI gets an edit wrong?
Every edit is a visible Git commit in your repo, so nothing changes silently: your team sees exactly what changed, where, and can revert it in Git like any other commit. Ambiguous or risky requests don't commit at all: they escalate to your team as a pull request instead.
Why not just add a headless CMS?
Retrofitting a CMS onto a finished site means restructuring content into fields, wiring every component, and training your client on yet another dashboard. CMS Chat sits on the repo you already shipped: no migration, no content modelling, no new admin UI for the client to learn. They type what they want changed; you keep Git as the source of truth.
Does CMS Chat work with WordPress?
CMS Chat works with Git-based stacks today (Next.js, Astro, Hugo, Nuxt, Eleventy, plain HTML, anything in a Git repo). Native WordPress support is on the roadmap. If your WordPress theme is in Git, it already works.
Who pays for the AI tokens?
We do. Client edits are unlimited on the plan — there is no metered token bill and no overage rate to watch.
What if I cancel — am I locked in?
No. CMS Chat works on top of your Git repo, which you own. Every edit is a real commit in that repo, so cancelling leaves your site running with its history intact.
Is my code safe?
CMS Chat connects via a GitHub App with granular, per-repo permissions. We only see the repos you explicitly install on. Every change is a real Git commit in the repository you own — it shows up in your normal history and review tools, no magic.
Stop taking tickets for typos.
Tell us about the first client site you’d hand over. We onboard agencies in small batches, and your team keeps the real work, plus the final say on everything else.