Sagenta

The easiest way to update a website.

Tap what you want changed. The dev pipeline changes it. Then approve the preview. Done.

Request early access Read the API
Example · a customer’s site

From tap to live in five steps.

  1. 01

    Tap

    Point at anything on your site and say what you want.

  2. 02

    Sent

    Sagenta packages the screenshot, the exact element and the source file, and sends it to whoever makes the change.

  3. 03

    Changed

    A developer, an AI coding agent, or your build pipeline makes the change and creates a preview.

  4. 04

    Approved

    See before and after. Tap Approve.

  5. 05

    Live

    It ships. Everyone is notified.

Update your site without learning a CMS.

Tap, type, approve. From your phone.

Example · owner’s phone
The Sagenta widget on a dental practice’s site, on a phone. The heading “Whitening” is picked, and the owner has typed “Teeth whitening” as the words it should say instead.

Every request, every site, one queue.

For agencies, freelancers and in-house teams: review with the checks you already run, approve in one click.

Example · reviewer’s queue
The reviewer’s queue in Sagenta: requests for Harborview Dental with their status, priority, who has them and how long they have waited, with filters and an urgent-first sort above. The reviewer’s queue in Sagenta: requests for Harborview Dental with their status, priority, who has them and how long they have waited, with filters and an urgent-first sort above.

Status, priority, who has it, how long it has waited. Filters and an urgent-first sort for the busy weeks; duplicates fold into one.

Works with what you already use.

Requests arrive by API, webhook, or GitHub issue, with the screenshot and source file attached. Previews and approvals go back the same way. Any developer, any AI coding agent, any CI.

The GitHub app files issues and posts approvals, and never touches your code.

Example · webhook
POST https://your-pipeline.example/hooks/sagenta
Sagenta-Event-Id: evt_01J9...
Sagenta-Signature: t=1756800000,v1=9f2a...

{
  "type": "request.created",
  "siteId": "site_harborview",
  "data": {
    "status": "published",
    "annotation": {
      "comment": "We're open Saturdays now, 10 to 2.",
      "elementPath": "footer > .hours",
      "sagenta": {
        "sourceHint": {
          "file": "src/content/site.yaml",
          "line": 14
        },
        "classification": "content"
      }
    }
  }
}

The owner’s words, kept whole.

Every request keeps what the owner saw and what they meant: the page as it was, the element outlined, and when they changed the words, what it says now beside what it should say. No ticket to write, nothing lost on the way.

Example · a request, as the team sees it
A request page in Sagenta: the owner’s screenshot with the tapped heading outlined, the words it says now beside the words it should say, where on the page it is, and the reviewer’s triage panel. A request page in Sagenta: the owner’s screenshot with the tapped heading outlined, the words it says now beside the words it should say, where on the page it is, and the reviewer’s triage panel.

Everyone else stops one step short.

Feedback tools

End at a ticket.

Coding agents

End at a pull request.

Site builders

Hand the owner the keys.

Sagenta

Closes the loop, with a person in charge.

Get in early.

Solo builders, agencies, in-house teams. Tell us about your sites and a person replies.

We store what you type here and nothing else.