When it is ready. It runs our own client work first, and we will not ship it half built. The waitlist hears the launch date before anyone else.

Teams that want to deliver software the way we do: AI agents doing bounded work between human approvals, with a record of every decision. Founders and small product teams first.

Will we be able to self-host it?

Hosting and licensing details come at launch. If self-hosting matters to you, say so when you join. It shapes what we build first.

Can we use it before launch?

Not as a product. If you want work delivered this way now, hire us. Your project runs through the same stages, gates and record, by hand.

What does joining commit me to?

Nothing. One email when there is news worth sending. Reply to it and you are off the list.

The process, as software.

We deliver client work through fixed stages, two human gates and a written record. We are building the platform that runs that process for your own team. It is not launched yet.

Join the waitlist

backlog feature_request
design prd
design approval design_package
development implementation_package
automated qa qa_report
manual review review_report
ready release_candidate
released

A feature request enters backlog, moves through design, design approval, development, automated QA, manual review and ready, and leaves as a release.

How it runs

A request becomes an artifact.

backlog

A feature request is written down as the first artifact of a run. Nothing moves until it exists.
Agents design. A person approves.

designdesign_approval

Research, PRD and design package are produced by agents. Design approval is a human gate; the run waits for it.
It is built and checked twice.

developmentautomated_qamanual_reviewescalated

Development runs as jobs on runners. Automated QA runs first, manual review second. Failures escalate instead of slipping through.
It ships as a release candidate.

readyreleased

Ready means every gate passed and the record says so. Released is the last state, and the start of the next request.

Halftone illustration of the loop: a feature request raised in the app, an artifact written, a release checked, and a green line feeding back to the start. — Production is where the next request comes from.

What it will do

Workflow engine

Nine governed states and explicit transitions. One run per feature request.
Artifacts

Eleven artifact types, from feature request to release candidate, as the system of record.
Agents

Research, plan, design and build jobs bounded by skill files and policy definitions.
Runners

Self-hosted or managed execution, with the runner state visible: online, busy, offline, disabled.
Gates

Design approval and manual review stop the run until a person acts.
Audit log

Every transition, job and artifact, with its actor: user, agent, system or runner.
Project memory

Context that persists across runs, so the next request starts where the last one ended.

The platform · In development

Join the waitlist.

The platform is in development. Leave an email and we write once, when there is something to show. If you want to be among the first to run it, say what you would run through it.

Questions

When does it launch?: When it is ready. It runs our own client work first, and we will not ship it half built. The waitlist hears the launch date before anyone else.
Who is it for?: Teams that want to deliver software the way we do: AI agents doing bounded work between human approvals, with a record of every decision. Founders and small product teams first.
Will we be able to self-host it?: Hosting and licensing details come at launch. If self-hosting matters to you, say so when you join. It shapes what we build first.
Can we use it before launch?: Not as a product. If you want work delivered this way now, hire us. Your project runs through the same stages, gates and record, by hand.
What does joining commit me to?: Nothing. One email when there is news worth sending. Reply to it and you are off the list.

Need it built now?

The platform is coming. The people who designed the process are available today. Tell us the feature and we run it through the stages by hand.

Start a project