Deployment Overview
Forge is designed to run the same accountable agent contract in multiple execution environments.
Deployment targets
| Target | Use |
|---|---|
| Local and WASI | Development, sandboxed local runs, deterministic tests. |
| Container and cloud | Services, APIs, Kubernetes, and internal platforms. |
| Edge | Low-latency agent entry points near users or devices. |
| Aut0 | Durable autonomous-organization execution through Flowers. |
| Sigil | Chain-adjacent or on-chain accountable execution paths. |
What must travel with the agent
A deployable Forge agent needs more than code:
- provider configuration
- OAS identity or identity derivation path
- ACT or delegated capability boundary
- tool registry
- telemetry sink
- health and lifecycle policy
- memory and storage policy when used
- WASI or host capability grants when sandboxed
Deployment rule
Do not deploy an agent with broader authority than it had in development. Deployment should narrow capabilities, not expand them.
Read the target-specific pages in this section before choosing a packaging model.