for platform and SRE

Put agent work through the same governance as production work.

0dai gives platform owners a repo-owned control plane for agent changes: authority rules in ai/, receipts for review, audit trails for merge decisions, and clear boundaries for what needs Enterprise review.

operating controls

Let agents move faster without moving outside review.

Authority rules are diffable

0dai init scaffolds agent-authority.yaml so review boundaries live beside code instead of inside a private chat thread.

Receipts before approval

Agent work can leave a task receipt, proof link, issue reference, and quality artifact before it reaches the merge queue.

Admin controls stay explicit

Team rollout copy is grounded in RBAC, audit logs, and admin controls; SSO/SAML and custom security terms stay Enterprise.

live vs enterprise

Security review gets a boundary, not a vague promise.

Platform teams can start with Team for governed shared workflows. Larger rollouts, SSO/SAML, audit export, dedicated success, and custom security terms stay in the Enterprise path.

Local first

Session roaming starts as ai/sessions/active.json. Cross-machine sync and shared graph history remain planned unless the status page says otherwise.

Enterprise security

SSO/SAML and custom terms are not self-serve Team claims. They belong to Enterprise and contact-sales review.

Change evidence

The operating model is governed-merge coverage: every serious change should carry authority, review, and audit evidence.

audit proof

The control plane should be reviewable by the people who own risk.

These are the same public product boundaries used by pricing and status copy: current Team governance, current receipt proof, and Enterprise-only security commitments separated from roadmap work.

Governance metricGoverned-merge coverage
Team priceTeam is $49/seat/mo; self-serve supports up to 3 seats.
Agent surface6 terminal CLIs + Cursor MCP bridge; Team includes all 113 MCP tools by plan.
Audit baselineReceipts, proof pages, authority YAML, and local session handoff are the live baseline for reviewable agent work.
Enterprise boundarySSO/SAML, audit export, dedicated success, custom terms, and larger rollouts route through contact sales.

Govern the first repo before you scale the rollout.

Start with Team controls; route Enterprise security needs through contact sales.

Scope Enterprise controls