Multi-slot reservation pool
Best for: QA-heavy teams that reserve envs per feature branch.
Three staging slots that you bind to different feature branches as you reserve them, plus one production slot tracking main. Closest to the original app default.
Shape
Staging → staging-1 / staging-2 / staging-3 Prod → branch main
What it seeds
Picking this template creates the following environments and slots in your workspace:
| Environment | Slot | Trigger | Pattern |
|---|---|---|---|
| Staging | staging-1 | branch | staging-1 |
| staging-2 | branch | staging-2 | |
| staging-3 | branch | staging-3 | |
| Prod | prod | branch | main |
How updates flow
When something matches a slot's pattern (a push to that branch, a tag with that name, a deployment with that environment), the GitHub webhook fires and the slot card updates in place. Your CI then deploys based on that push and emits deployment_status events, which flow back to update the slot status from Deployingto whatever your workflow ends in. We don't deploy for you.
See Trigger patterns for the full reference, or The board for how to read what you see.
Try it
New workspace? Pick Multi-slot reservation pool from the picker on /new-workspace. Existing workspace? Go to Settings → Environmentsand use the "Reset to a starting shape" card.