Deploy

Deploying builds a production bundle of the current version and serves it at a public URL. It takes one click.

What happens

1. Qyant snapshots the current version's files.
2. A fresh container installs dependencies, runs next build, and starts the production server.
3. When the app answers, traffic is switched to the new container. The previous deployment is retired a moment later — a brief overlap, never a gap.
4. The deployment is live at https://<slug>.apps.qyant.dev.

Progress streams into the builder; a failed build shows its log so you can fix and redeploy.

Configuration

Deployments receive DATABASE_URL for the project's database automatically, plus the variables from your .env. .env itself is never copied into the image. See Environment variables.

Same isolation as the preview

A deployment runs in the same kind of sandboxed container as the preview — kernel-isolated, capability-dropped, resource-limited — and against the same private database. See Isolation.

Redeploying and rolling back

Deploy again at any time to publish the current version. To roll back, revert to an earlier version in the builder and deploy.

Custom domains

Deployments currently live on apps.qyant.dev. Bringing your own domain is not available yet; if you need it, tell us — it helps us prioritise.

Limits

The number of live deployments per account depends on your plan — see Limits. One deployment per project is live at a time.