What is Webamend, and what it is not
A plain answer for anyone who looks after somebody else's website and is tired of being the person who changes the headline.
Amit Malul Lev
Software engineer
Over the last year I built several static websites for clients: hand-written HTML or a small framework, one stylesheet, no database. They were fast and cheap to run, and the clients liked them. Then the requests started arriving. A shorter headline, a different photo on the about page. Each one was a minute of work, and each one was mine, because there was no content system.
I could have given them a CMS. But a CMS only changes what its fields were built for, and what my clients asked for was a new section, a different colour, a photo where there was none, a block moved to the top of the page. What I wanted was a way for them to edit the site the way I do when I build it, without being able to break it.
Webamend is what I built for that.
The short answer
Webamend gives your client a chat box. They write what they want changed, in their own words, the way they would say it to you. A coding agent makes the change in a copy of the site's files. Your host builds a private preview. The client looks at it and presses Publish, or doesn't. That is the entire experience on their side.
On your side, what arrives is a pull request in the repository you already have. The branch has the change, the description has the request, and the merge is the publish. Nothing about the site moves: same repository, same host, same domain, same build. Webamend edits the repository behind the site and then gets out of the way.
So the shortest true description is this: a chat box on one end, a pull request on the other, and a set of rules in between that you write once.
What happened the first time
The first real change went through on the 14th of September. The client asked for a line of text to change on one page. The agent found the page, changed the line, and left everything else alone. Netlify built a preview. They opened it on their phone, saw the new wording, and published. The pull request, number fifteen in that repository, was merged by them, not by me. I read it on Sunday.
The whole thing was unremarkable, which was the point. A change to a website went from a sentence to a commit without a developer in the loop, and the developer could still read every character of it afterwards.
What Webamend is not
It is not a CMS. There is no admin panel with fields for the title and the body and the hero image. Webamend does not know what a hero image is until it reads your site. It has no schema and no database. If that sounds like a weakness, read Why an agent instead of a CMS, where I argue it is the opposite for a certain kind of site.
It is not a page builder. Your client does not drag anything. They cannot restyle the site, add a plugin or move the navigation, unless you decide they can and write that into the rules.
It is not autopilot. Nothing publishes because the agent thought it was done. Every change waits behind a preview until a person presses a button, and that person can be your client or you. If nobody presses it, nothing happens, and the branch sits there until you delete it.
And it is not magic. The agent sometimes does the wrong thing. It changes the wrong line, or too much, or it misreads a request. When that happens your client sees it on the preview, says no, and asks again. A few cents were spent. The site was never touched.
Who it is for
Webamend is for people who maintain other people's websites: agencies, studios, freelance builders. The sites it works on live in a GitHub repository and build on Netlify, which covers most static sites built in the last few years, whether they are Astro, Next.js, Hugo, Eleventy or, like the first one, plain HTML with a stylesheet.
It is not for a WordPress site, or a site with no repository, or a site where the content lives in a database somewhere. Webamend edits files. If the words on the page are not in a file it can read, there is nothing for it to do.
What you keep control of
Three things, all of them in the repository and none of them visible to your client.
Which paths may be edited. A policy file in the repository lists the folders the agent may touch and the ones it may never touch. The payments code, the config, the build scripts: fence them off once and they stay fenced.
How big a change may be. The same file caps how many files a change can span and how many lines it can add or remove. A request for a new headline that somehow turns into a rewrite of forty files is thrown away before it is committed, and you get an email saying so.
Who may ask. Each site has a list of email addresses allowed to sign in. Everyone else gets a closed door. Every request is recorded against the person who made it, so when a client asks why the phone number changed, you can tell them who changed it.
What it costs
It is priced per website, and the price per website falls as you add more. Studio covers three to eight sites for a freelancer or a small studio; Agency covers nine to twenty. The plan does not include the model's tokens. You add your own OpenRouter key, and OpenRouter charges the tokens each change burns to your credit there. That part is small: a wording tweak goes through the free or cheapest tier and comes to fractions of a cent, and a new section is a few cents. Both plans are billed monthly or yearly, and both can be cancelled from a billing portal without writing to anyone. The numbers are on the pricing page, along with what I promise in return.
If you would rather run it yourself, you can. Webamend is open source under the AGPL, and the same code that runs the hosted version runs on your own server for nothing. The same OpenRouter key covers the tokens, and you do your own updates.
Where it stands
I want to be honest about how new this is. As I write, Webamend runs on a handful of client sites and on my own. It has merged a small number of pull requests. The architecture has been the same since the start, and I am not aware of a change it has made that a person did not approve, but the number of people who have tried it is small and you should weigh that.
What I can say is that every part of it is readable. The code is public, the changes it makes are pull requests, and the rules it follows are a text file in your repository. If you want to know what it will do to your client's site, you can read exactly that before you let it near one.
If you have questions the page did not answer, write to me. I read everything.