Orcher early access opens to a first cohort of regulated operators

Dipp AI Technologies is opening **Orcher**, our Agentic Control Plane, to a first cohort of regulated operators. Access is invitation-only. We review each request, then take a small number of teams at a time so every deployment gets founding-team attention.

Why a cohort, not a signup button

An agent that touches a prior authorisation, a claim, a trade file or a maintenance directive is not a demo. It needs a named authority for each directive, a verification step before anything commits, and a record that survives an external review. Those are deployment decisions, not settings. Working with a small cohort lets us make them with you rather than hand you a console and wish you luck.

What a cohort deployment includes

- **Authority per directive.** Each class of directive is bound to the role that answers for it, before an agent ever runs. - **Pre-commit verification.** Nothing writes to a system of record until the check passes; failures stop, they do not proceed with a warning. - **Dynamic model routing.** Each step goes to the model that satisfies its cost, latency and assurance requirement — the strategy the whole control plane is built around. - **Enterprise data boundary.** Your data is not used to train anyone's model, and the boundary is enforced at the gateway, not promised in a contract. - **Immutable ledger.** Every directive, decision and override lands in a record you can hand to an auditor.

How to take part

Request access and tell us the workflow, the systems of record involved and the obligation you are working against. We reply with a decision and, where it is a fit, an invitation that opens an account and a self-serve workspace showing your status, your invitation and any scheduled briefing.

Prefer to talk first? Book a briefing and we will walk the mechanism against one of your own workflows.