Isolation bar
Soft quotas (illustrative)
Exact numbers come from your workspace contract and live usage meters. Soft quotas throttle and queue; they do not silently share capacity across orgs.
Defaults
- Public surface: Eval API (
agi.akhara.ai), Control plane PDP (api.akhara.dev), and documented consoles only. Orchestrators, workers, and device pools stay on the private network. - Auth: Org-scoped API keys (and SSO/SAML for enterprise). Keys never authorize cross-tenant reads.
- Episode isolation: Each Environments run gets an isolated backend session and device assignment for that episode; teardown drops state.
- Control plane: Fail-closed PEP; PDP never executes customer tools; evidence feed is org-partitioned.
- Expert Review: Experts see only assigned packs; briefs and fixtures stay in-org; no export of other customers’ content.
- Egress: Environment and sandbox egress follow an allowlist on enterprise plans; trial may be open for bring-up.
- Residency: Enterprise can pin region (for example US or EU). Trial defaults to the primary US region.
- Audit: Admin and policy decisions are attributable to an org + principal; retention follows the table above.
What we do not do
- Share device pools or catalogs across orgs in a way that exposes another tenant’s state
- Return another org’s trajectories, permits, or expert labels from any public API
- Let agents or experts choose their own tenant id in a request body
Related
- Environments architecture: private orchestrator and workers
- Control plane architecture: PDP / PEP boundary
- Control plane fail-closed: unreachable means blocked
- Expert Review policies: expert confidentiality