Sitepins or Webamend, for the same client
Sitepins and Webamend are aimed at the same person, the builder handing a static site to a client. They solve it differently, and the cheaper one is not always the right one.
Amit Malul Lev
Software engineer
Sitepins and Webamend are built for the same moment: a static site is done, the client wants to change things, and the builder would like to not be in that loop. If you are choosing between them, it is worth being clear about what each one actually edits, because that decides the rest.
What Sitepins does
Sitepins is a Git-based CMS with a visual editor. You connect a repository, it reads the content files, and it works out the structure on its own. Their words: it "automatically detects your content structure", so there is no config file to write, which is a real improvement over the older Git-based CMSs. The client sees a clean editor for Markdown, MDX, JSON and YAML, with drag-and-drop images and, on the paid plans, a sandbox preview and rollback. Every save is a Git commit. Clients are invited by email and need no GitHub account. It supports Astro, Next.js, Hugo, Svelte, Eleventy and Jekyll, and the homepage makes a point of sites "shipped with Claude, Lovable, or v0".
The pricing is generous. A free Hobby plan covers three sites for one user. Pro is $12 a month for six sites, Team is $29 for fifteen, Agency is $49 for thirty, and each has a lifetime option. The homepage also says you can self-host it for free.
For a site whose content is in those file formats, this is a very good deal, and for a blog or a docs site it is the tool I would point a builder at.
What it edits, and what it does not
Sitepins edits content files. That is the design, and it is the right design for a CMS. Markdown, MDX, JSON, YAML. The prose, the front matter, the data files.
What it does not edit is the rest of the site. The template that decides where the testimonials go. The stylesheet with the green in it. The hand-written HTML page where the prose lives in the markup rather than in a .md file. When the client's request is about one of those, and a lot of them are, the CMS has nothing to show them, and the request comes back to the builder as a message. That is not a criticism of Sitepins. It is what a CMS is.
What Webamend edits
Webamend edits files. Any of them the policy allows. The client writes the request in words, a coding agent makes the change in a sealed copy of the repository, a gate checks the diff against the fences you set once, and what passes becomes a pull request with a Netlify preview. The client publishes from the preview and undo reverts the merge.
So the request that a CMS cannot represent, move that section, change that colour, add a photo here, is exactly the one Webamend is for. And the site that a CMS cannot read at all, the plain HTML one, is where Webamend started. The first site it ran on has no Markdown in it.
It also has no schema to detect, because it never reads the content as content. It reads the repository as a developer would.
Where Sitepins is the better choice
Price, if the client's edits are content. Six sites on Sitepins Pro is $12 a month; six on Webamend is $23. Sitepins is a form over files, which costs nothing per save and never surprises anyone. Webamend runs a model, which costs a few cents per change on your own OpenRouter key and is occasionally wrong in a way the client has to catch on the preview. If every request you get is "change the text in this paragraph", you would be paying Webamend for a capability you do not use.
Where Webamend is
Everything that is not content. Layout, style, new sections, images placed rather than swapped, and any site that was not built with a CMS in mind. If your clients are the kind who send screenshots with arrows on them, the form was never going to cover it.
The two are not exclusive. Both commit to the same repository, both leave Git as the record, and a builder could run Sitepins for a client's blog and Webamend for their homepage without either noticing the other. If you only take one, look at the last ten requests you got and count how many were about words in a Markdown file.
Sitepins' site explains itself well. Webamend's technology post explains what the agent may and may not touch, which is the part that should decide it.