Skip to main content
Each deployment creates a version of your app with its own ID. An active version can scale to zero while idle.

​
Inspect and Wait

wait checks that the deployed endpoint or asgi version is healthy. For other workloads, it waits for active status; check your app’s health URL separately. Add --json to beam deploy for deployment details in JSON.

​
Rollout Strategies

Writable disks require replacement. Redeploying a scheduled job stops its previous schedule. Use beam deployment list to find and stop older versions you no longer need.

​
Stop, Start, or Delete

Stop a version to shut down its containers; start it to reactivate it. Delete it to remove the deployment record.

​
Restart or Roll Back Through MCP

The MCP redeploy tool creates a version from existing code and configuration. Pass name to restart the active version, or an older deployment_id to roll back. Changing resources or environment variables also deploys a new version. Update your source to preserve those changes on future CLI deploys. See versioned URLs, logs and metrics, and container scaling.