> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beam.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment Lifecycle

> Inspect revisions, wait for endpoints, choose rollouts, and roll back

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

## Inspect and Wait

```bash theme={null}
beam deployment list
beam status
beam deployment wait YOUR_DEPLOYMENT_ID --timeout 300
```

`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

```bash theme={null}
beam deploy app.py:handler --rollout auto
beam deploy app.py:handler --rollout blue-green
beam deploy app.py:handler --rollout replace
```

| Strategy | Behavior |
| - | - |
| `auto` | Default behavior; older always-on versions may keep running. |
| `blue-green` | Starts the new version alongside the old one. Requires spare capacity. |
| `replace` | Stops the old version first. Can cause downtime. |

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

```bash theme={null}
beam deployment stop YOUR_DEPLOYMENT_ID
beam deployment start YOUR_DEPLOYMENT_ID
beam deployment delete YOUR_DEPLOYMENT_ID
```

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](/v2/endpoint/versioning), [logs and metrics](/v2/operations/observability), and [container scaling](/v2/hosting/containers#scaling-and-idle-time).