Sagenta Product 3 min read
Introducing Sagenta: point at the website, approve the fix
Website owners want to scribble on a printout and hand it to someone. Sagenta is that, on the live site, with an approval at the end. Here is what it does, what it deliberately does not do, and how to get in early.
Most small websites are maintained by someone other than their owner. An agency, a freelancer, a developer friend. The owner’s only ways to ask for a change are to learn a CMS they do not want to learn, or to send an email and wait. Meanwhile the tools that make changes have become very good and very fast, and the bottleneck has moved: it is no longer doing the change, it is getting the request in, and getting the approval out.
Sagenta is a feedback-and-approval layer for websites. It owns exactly those two ends.
What the owner sees
The owner opens their site, or a preview of it, taps the thing they mean, and types what they want. “We’re open Saturdays now.” “This photo is the old shop.” “Make the phone number bigger.” On a phone, usually. Sagenta attaches a screenshot with the element outlined, where it is on the page, and, when the site was built with our Astro integration, the file the content came from.
Then the owner waits, and the waiting is honest: Received. Being worked on. Ready for your review. Live. When it is ready they see before and after and tap Approve, or Not quite, which reopens the conversation. They never see a repository, a ticket, or the word “deploy”.
What the pipeline sees
Everything in the middle is yours. The request is available through a versioned API and pushed to your endpoint as a signed webhook, as a standard annotation document. If you turn on the GitHub integration it is filed as an issue too. Your developer, your coding agent, your CI does the work and builds a preview, then posts the preview URL back with one call. When the owner approves, the approval goes out the same way, and as a pull-request review and commit status if GitHub is on. You ship it and tell us it is live.
Sagenta does not make the change. That is a deliberate boundary, not a gap. The tools for making changes are moving too fast for us to pick one for you, and the people we are building for already have opinions about theirs. A Sagenta-run option will exist later, as an option.
Who it is for
Agencies and freelancers who look after many sites and would like their clients to stop emailing them screenshots. Solo developers and small businesses who run their own pipeline and want a review step that a non-technical person can actually use. And developers who already have an agent-driven workflow and want a feedback layer their tooling can drive.
Where it is
Being built, with a handful of agencies, now. The developers page has the API and webhook contract we are building to. If you look after sites and want in early, the form on the home page reaches a person.