Deployments
Auto-deploy on push, preview deployments, rollback, and deployment status.
Production and preview deployments
| Type | Trigger | Serves |
|---|---|---|
| Production | Push to your configured production branch | Your live *.vorynza.cloud domain and any custom domains |
| Preview | Push to any other branch, or a manual redeploy | Its own unique deployment URL only |
Auto-deploy on push
Once your repository is connected, every push to your production branch starts a new build automatically. If another build for the same app is already in flight when a new push arrives, the older one is superseded — you're never stuck waiting behind a stale build, and a superseded build can't overwrite a newer one's result even if it finishes later.
Vorynza reports build and deploy status back to the commit on GitHub, so you'll see it directly on your pull request or commit.
Deployment status
| Status | Meaning |
|---|---|
queued | Waiting to start |
building | Installing dependencies and running your build command |
deploying | Publishing build output |
ready | Live |
failed | Build or deploy failed — see logs for why |
canceled | Stopped manually, or superseded by a newer build |
Canceling a build
While a deployment is queued, building, or deploying, you can cancel it from the deployments list. This stops the build and marks it canceled — it won't affect production.
Rollback
Every successful deployment stays available. To roll back, open any previous Ready deployment and promote it back to production — your custom domains and platform subdomain immediately start serving that version again. For a Next.js app, this is instant: the previous deployment's function is already running, promotion just repoints traffic.
Manual redeploy
Trigger a new production build at any time from your app's overview page, without needing a new commit — useful after changing environment variables, which don't take effect until the next deployment.