Docs / Deploys

How deploys work

A deploy clones or unpacks your source, runs the build command (or builds a Docker image), starts a candidate container, runs health checks, then swaps traffic to the new instance. Failed deploys leave the previous live container running.

Deploy queue

Deploys are queued in SQLite and processed sequentially per service. The dashboard shows build status, live build logs, and deploy history on the Events tab.

Triggers

• Git push (when auto-deploy is enabled)
• Manual deploy from the dashboard or API
• Deploy hooks (HTTP)
• Cron scheduler (for cron job service type)

Zero-downtime

Web services and static sites use blue-green deploys: a candidate container must pass the health check before the old container is replaced. See Zero-downtime deploys.

Artifacts

Build output and per-deploy log files are stored under the control plane data directory. Runtime logs come from docker logs on the running container.