Preview URLs and rollback
Every deployment is immutable and keeps its own URL. Production is a pointer to one deployment, so switching it is instant.
URLs
| URL | What it serves |
|---|---|
https://q3-variance.apps.contoso.com | Production: whichever deployment is promoted |
https://q3-variance--d7f3a2.apps.contoso.com | The deployment d7f3a2, forever |
The -- separator (instead of nested subdomains) means one wildcard certificate covers every project and preview. Preview URLs sit behind the same sign-in and the same access rules as production.
Deploy a preview
tc deploy --preview
Over MCP, call deploy with promote: false. The deployment builds and becomes ready on its preview URL; production doesn't change.
Promote
Make any ready deployment serve production:
- Console: Deployments, then Promote on the row.
- CLI:
tc promote <deployment-id> - MCP:
promote - API:
POST /api/projects/:name/promotewith{ "deploymentId": "d7f3a2" }
Roll back
Rolling back promotes the newest ready deployment older than the current production. Give a deployment id to go somewhere specific.
- Console: Deployments › Roll back (the button at the top), or Roll back on an older row.
- CLI:
tc rollback, ortc rollback --to d7f3a2 - MCP:
rollback - API:
POST /api/projects/:name/rollbackwith{}or{ "to": "d7f3a2" }
If there is no earlier ready deployment, the answer is There is no earlier ready deployment to roll back to. Only ready deployments can be promoted.
What rollback does not undo
- Database migrations. Migrations run forward only. Write migrations that the previous version can live with (add columns rather than renaming them), or apply a new migration that reverses the change.
- Environment variables. Variables belong to the project, not the deployment. A deployment started after a variable change gets the new value.
- Files and grants. Storage and integration grants are project-level too.
Source of every deployment
vastframe stores the exact source bundle of every deployment. Rollback, promote and redeploy work without any git repository.