Zero Downtime

Nomploy can roll out new versions of your application with zero downtime, so traffic keeps flowing while the new version starts and only switches over once it is healthy.

How it works

By default, a new deployment replaces the running version. Without a readiness signal there can be a brief gap while the new container starts up — which can surface as a Bad Gateway. To avoid it, configure a health check: Nomploy waits for the new version to report healthy before it routes traffic to it and retires the old one.

Configure a health check

1. Make sure your application exposes a health endpoint that returns 200 — for example, a /health route on the port your app listens on.
2. Open your application's Advanced tab and configure the Health Check under Cluster Settings.
3. Point the check at your health endpoint and save.

Once the health check is in place, each new deployment only takes over after the new version passes it — giving you zero-downtime deploys.