Deploying

Auto-deploy from Git

Connect a GitHub, GitLab or Bitbucket repository and pick a branch. Every push to that branch triggers a new deployment automatically — no extra setup.

You can disable auto-deploy or change the branch any time in Settings → Build & Deploy.

Manual actions

The buttons in the service header control the lifecycle:

Action	What it does
Redeploy	Build and deploy the current branch again. Use after changing env vars at build-time, or to retry a failed build.
Restart	Restart the running container without rebuilding. Fast — picks up runtime env-var changes.
Stop	Shut the service down. Compute is released; env vars and disk are kept.
Start	Bring a stopped service back up using the last successful build.

Build process

When you trigger a deploy:

1. The selected branch is cloned.
2. A container image is built — from your Dockerfile, or with auto-detection.
3. The image is rolled out with zero downtime — the old version stays up until the new one passes its health check.

Build logs stream live on the Overview tab. If a build fails, the previous version keeps serving traffic.

For the full lifecycle, deploy states and health check behaviour, see Runtime.