Product

A sentence in, a pull request out.

Here's the whole trip — real screenshots from the demo org, nothing staged.

How people come in

The demo walkthrough's Slack thread: Maya asks for a CSV export, the Coordinator files it as a ticket — Someone asks. The Coordinator turns it into a ticket.

The same walkthrough's build run: repo cloned, files edited, typecheck running, with the cost ticking beside it — The Engineer builds it — every step and every cent recorded.

The Console replaying a finished run: pull request opened, cost $0.42, item moved to review — A pull request lands, with evidence you can read in a minute.

The engine

Named tasks, not a black box.

Triage

Reads the ask, files the ticket, routes it.

fast model

Build

Writes the change in a sandbox, opens the PR.

frontier model

Verify

Runs your spec in a real browser, keeps the evidence.

no tokens

Narrate

Tells the thread what happened, in plain words.

fast model

Designsoon

Brief, render, adversarial critique — then built in code.

frontier + image

Every model call lands on the ticket's cost line — you see the bill per ticket, not per month. New capabilities arrive like plugins; soon experts will publish their own.

The demo org's board: items across Intake, Ready, In Review and Done, each with its source, ticket, pull request and cost

Who decides

You do.

It opens pull requests; it doesn't merge them. Each repo earns more autonomy only when you grant it. How control works

Hosted

Connect and go.

Your own servers

One runner binary inside your network. Code and credentials never leave.

Watch one go through.

See a ticket go through Sign in