Workspace, API, CLI — every connection option routes through the same Orchestra pipeline. Same tenant isolation, same policy gates, same proof on every output.
Connection options
A human-facing AI workspace with proof-backed answers. Desktop client for teams who want governed AI without writing code.
OpenAI-compatible and native endpoints for applications. Every response includes a proof ID, status and route metadata.
Sandbox surface live internally; public endpoint pending production verification. Quickstart →
For operators and developers. Feature-flagged spine access with the same envelopes and the same proof discipline as the API.
Outbound event delivery — task completed, proof attached, approval requested. Designed so external sends stay approval-gated.
Approval-gated coordination surfaces for conversational teams. Same tenant scoping; sensitive actions still stop at approval gates.
For sensitive customers: tenant-isolated deployment with private routing, audit log retention and a security review. Scoped per engagement.
A pilot starts with one workflow and the simplest connection that serves it — usually Workspace or the API.