Deployment Operations
| Operation | Description |
|---|---|
| Single deploy | Deploy one agent to one gateway |
| Bulk deploy | Deploy one agent to multiple gateways simultaneously |
| Fleet deploy | Deploy all agents to a specific gateway (useful when onboarding a new gateway) |
| Undeploy | Remove an agent from a gateway. The definition is preserved; only the runtime binding is removed. |
Deployment States
Each deployment transitions through a simple lifecycle: deploying → active (on success) or deploying → failed (retry available). The system tracks the gateway ID, agent definition version, and deployment timestamp for each binding.
Deployment Fields
| Field | Description |
|---|---|
agentId | Reference to the agent definition in the registry |
gatewayId | Target gateway runtime |
status | deploying, active, or failed |
version | Agent definition version at deployment time |
deployedAt | Timestamp of the deployment operation |
Gateway-Agent Matrix
The system maintains a matrix of which agents are deployed where. This matrix is queryable for capacity planning (“which gateways are underutilized?”), incident response (“which agents were running on the failed gateway?”), and compliance (“is this agent deployed only to approved gateways?”).When a workflow step is dispatched, the interpreter resolves the assigned agent and verifies an active deployment exists on the target gateway before routing through Bridge.
In Burgundy: Deploy agents from the agent detail page. →