Deployment Models

Dari is designed around one control-plane API for agents, versions, sessions, messages, and files. The control plane owns the public contract. Harnesses live in the control plane. Sandboxes are the execution substrate used when a harness needs actual runtime execution.

​

Managed deployment

Managed deployment is the current public flow:

1. Publish source with dari deploy
2. Dari stores a versioned agent resource in the control plane
3. The Pi harness coordinates session and message execution
4. When execution is needed, the harness uses a sandbox

This is the path covered by the current Quickstart, Manifest Reference, and Agents and Versions pages.

​

Sandbox-hosted deployment

Dari is also being shaped to support a sandbox-hosted deployment model with the same public API. In that model:

• the control plane still owns agents, versions, sessions, messages, and auth
• the harness still defines the behavior behind the API
• the runtime is deployed onto sandboxes directly instead of only through the current managed publish flow

This is a near-term direction, not the current public quickstart path.

​

Harnesses

A harness is not the sandbox runtime. It is the control-plane behavior that turns durable API resources into a running session lifecycle. The harness is responsible for:

• session and message orchestration
• event and status progression
• retry and lifecycle behavior
• deciding when sandbox execution is needed

Pi is the current public harness. Future harnesses should follow the same pattern: the control plane exposes the API, the harness implements behavior, and the sandbox provides execution.

​

What stays stable

Across deployment models, the intended stable contract is:

• one control-plane API under /v1
• durable Agent, Session, Message, and File resources
• organization-scoped auth and versioning behavior
• session-first execution semantics