For agencies and freelance builders
Webamend lets your clients change their website by asking in plain words. It works on the site as it is, whatever it is built with. You add one policy file that says what may be touched. A coding agent makes the change, your client previews and publishes it, and it lands in your repository as a commit you can revert.
Open source under AGPL 3.0. Running on real client sites since September 2026.
Who it’s for
Agencies
A client wants a headline shortened, so a one-word change becomes a ticket and a deploy. With Webamend they change it themselves, as often as they like, and every change is a commit in your repository that you can revert.
Freelance builders
Small edits are the work you least want and can least justify billing for. Hand them over without handing over repository access, and keep the site exactly as you built it.
Studios shipping fast
A static site with no CMS is faster to build and cheaper to host, right up to the first content request. Webamend handles that request without touching the stack you shipped.
How it works
What you get
What the agent changed, on a branch, with the client who asked for it. Revert it any time.
Your host builds a Deploy Preview first. Your client looks before they publish.
A policy file you own sets the paths and size the agent may ever touch.
Publishing merges a pull request. Undo reverts that merge.
GitHub is the record, your host serves it. Nothing new to back up.
Run it on your own infrastructure, forever, for nothing. AGPL 3.0.
Under the hood
The agent runs on a model sized to the request. A wording tweak gets a cheap one and a new section gets a strong one, so most client edits cost pennies. The tokens are charged to your own OpenRouter key, so you see exactly what each change cost.
The agent works in a fresh, locked room that is destroyed the moment it finishes. It holds a copy of the files and no credentials, so it cannot publish and cannot reach the live site or your other clients.
You set which paths may ever be edited and how large a change may be, per website, in a file your clients cannot see. Webamend reads what the agent produced and checks it against those rules before anything is committed. Work that breaks one is thrown away and reported to you.
We connect each client repository and host by hand so it is right the first time. Expect to be handing sites over within one business day of signing up. Running it on your own infrastructure instead is instant and free.
The long version, stage by stage: the technology behind Webamend.
Live today
Pricing
Pick the plan that fits how many sites you look after. Cancel any time.
Most popular
$12/mo
billed monthly
For a freelance builder looking after a handful of client sites.
$32/mo
billed monthly
For a studio or agency shipping client work every day.
Let’s talk
priced per engagement
20+ websites
For more client sites than the sliders go, or a stack that is not GitHub and Netlify.
Prefer to run it yourself? Webamend is open source. Run it on your own machines ↗.
Who builds it
I am Amit Malul Lev. I spent ten years building production systems at Salesforce and Datorama. I developed Webamend for people who build websites for others and want their clients to edit them safely. I set up every site by hand and answer every email myself.
FAQ
An AI coding agent. It reads the repository and edits the files on its own, the way a developer would on a branch. Webamend is what stands around it: the rules it must obey and the preview before anything ships. Every change it makes is recorded.
No. Webamend edits the repository as it is, whatever it is built with: Astro, Next.js, Hugo, Eleventy, Jekyll or hand-written HTML. There is no CMS to install and no schema to define. You add one policy file that says what may be touched, and the site keeps its repository and its build.
No. They see a chat box and a publish button. They never see a repository or a build log, and there is nothing to install. They write what they want changed the way they would say it to you, and the agent does the rest.
Usually one business day per website. We connect the repository and the host by hand rather than making you work through a wizard, so it is right the first time. You get an email when it is ready.
The GitHub repository and the Netlify site for each website, an OpenRouter key for the model, and the email addresses of the clients allowed to request changes on each one. One short form after checkout covers it.
OpenRouter is the service that routes each request to whichever model the agent runs on. Yes, you need an account there. You add your OpenRouter key when we connect your sites, and OpenRouter charges the tokens each change uses to your credit, on top of the plan. Most changes come to fractions of a cent.
Each request carries a budget rather than a model name, and we map budgets to models: free for a wording tweak, stronger for a new section. If your client work needs a specific model or provider, we can pin it on a custom plan.
No. Your client keeps their domain and their host. Webamend only edits the repository behind it. The editor your client signs in to is a separate address: a Webamend domain on Studio, or a domain you control on Agency. Choosing a domain per site inside Webamend is on the roadmap.
On Agency, yes: the editor runs on your own domain, so a client never sees a third-party product in the address bar. Deeper white-labelling, including your own mark and palette, is a custom plan.
Only the addresses you name, per website. Everyone signs in with a code sent to their email, and every request is recorded against the person who made it, so there is an audit trail when a client asks why something changed.
All of it, and you set it once rather than approving each change. A policy file in the repository fixes which paths may ever be edited and how large a change may be. Your clients cannot see it or change it, and work that breaks a rule is blocked before anything is committed.
Nothing publishes on its own. Your client sees a preview first and decides; if they do not publish, nothing happens. A published change was a merged pull request, so Undo reverts the merge, and you can revert it yourself from Git like any other commit.
Neither. Webamend edits the repository you already have and waits for the preview your host already builds. Your stack and your review process stay exactly as they are.
Move the slider and your subscription follows, because you are billed per website. Studio covers 3 to 8 websites, Agency 9 to 20. Past that, or for a setup we do not list, talk to us about a custom plan.
Any time, from the billing portal linked in the footer. Client repositories and sites are untouched: cancelling stops Webamend editing them and removes nothing.
Yes. Webamend is open source under AGPL 3.0. Run it on your own machines, on as many client sites as you like, for nothing. You supply your own OpenRouter key and do your own setup and updates.
Something else? Ask a person.
Run it on your own infrastructure for nothing, or let Webamend host it for you.
Get started
