Public alpha

Bring one real workflow, not a slide deck.

The public alpha is self-serve: install from PyPI and run it on your own repos today. The pilot track is for teams using agent tools across multiple repos, services or review paths — bring one concrete workflow, we run it through the protocol together and learn where the control plane helps or gets in the way.

PILOT INTAKE

Email [email protected] Install the public alpha

typed plan cross_plan.md

gate findings review_changes.json

run diff diff.patch

event spine events.jsonl

cost split metrics.json

handoff decision phase_handoff.json

Good fit

You have cross-system agent work today.

A good alpha workflow touches more than one repo, uses more than one worker or has a review/handoff step that is painful enough to name.

Your team is roughly 5–50 engineers shipping across more than one repo, service or review path.
You already use two or more agent tools day to day — and their work has to land as one delivery.
You can share a representative workflow under NDA.
You care about review, evidence or handoff more than novelty.
You can give direct feedback after a run.

Not fit

This is not general self-serve access.

If the need is autocomplete or a finished hosted product, this is too early. Self-serve install is open to everyone; the pilot track is for validating the delivery protocol with real team workflows.

Know the ceiling

Today it is a per-machine, single-operator control plane.

Orcho runs on one machine per operator: no central RBAC, tenant-wide audit, or team budget enforcement yet. The delivery record is the run directories on that machine. That is the honest scope of the alpha — and because every run is plain local files you own, nothing is trapped if you walk away.