The flagship

The autonomous stack.

Connect Datis to what you already run and the loop runs itself: it observes your services, triages the failure, plans the fix, executes it and ships it — nobody in the chain unless your policy asks for somebody.

Your agent cites the live system it read — not a copy prepared in advance.

4m 13sfrom the first bad signal to the merged fix — the run the landing replays, measured end to end.

The loop

From alert to merged.

From the first bad signal to the merged fix — the same seven steps, every time. The landing shows them run; this is what each one does.

  1. Detect

    Failures have to agree before anything moves: when monitors and error rates breach together, the incident opens itself and the clock starts.

  2. Triage

    The agent reads what a person would — the errors, the recent releases, the code in the path, your runbook — and names the change that did it.

  3. Plan

    Before touching a file it writes down what it will change and what it ruled out. The plan is part of the record, not a formality.

  4. Patch

    The fix arrives as an ordinary pull request on its own branch — same review, same protections, as small as the hypothesis allows.

  5. Try to break it

    Green tests are the floor, not the argument. Reviewers are briefed to break the patch from different angles before it goes anywhere.

  6. Pull request

    Everything the run knows travels in the description — the hypothesis, the evidence, every verdict. The pull request is the argument.

  7. Merge

    A change merges itself only where its track record has earned it. Everything else waits for a person, and the ledger records which of the two happened.

No one in the chain

Autonomous is a policy, not a mood.

Every move above ran because a rule you can read allowed it — and stops the moment one does not.

Policies

What it may read, what it may change, what merges without a signature — written per repository and per class of change, enforced on every run.

The ladder

Watch, propose, execute. Each rung is dialled up as the track record earns it — and down the moment it stops clearing the bar.

The record

Every run keeps its plan, its diff, its tests and its verification. The evidence an auditor asks for, assembled as a side effect of working.

Connect what you run. Watch it close the loop.

The beta is where this runs against your stack. Every request is read by a person. The business model is simple: a B2B subscription per workspace plus usage-based agent runs — the plans are on the pricing page and activate at general availability.