Zero-downtime deployments

How it works

compos uses an approach where your current version keeps serving traffic while the new version builds and starts. Only once the new version passes its health checks does traffic move across to it. A failed deployment routes traffic back to the previous version instead of taking your app down.

Health checks

Health checks are verified before a new version receives traffic. If the endpoint does not respond as expected, the deployment pauses so you can inspect what went wrong before deciding whether to proceed or roll back.

Rollbacks

The previous version stays available while a deployment runs. You can roll back from the dashboard or the CLI. Rollbacks return users to the last known good version rather than to an error page.