Single staging
Best for: Solo or pre-PMF teams shipping from main.
One staging environment and one prod environment, both tracking the main branch. The simplest viable shape — pick this if you have one app, one team, and one branch you care about.
Shape
Staging → branch main Prod → branch main
What it seeds
Picking this template creates the following environments and slots in your workspace:
| Environment | Slot | Trigger | Pattern |
|---|---|---|---|
| Staging | main | branch | main |
| 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 Single staging from the picker on /new-workspace. Existing workspace? Go to Settings → Environmentsand use the "Reset to a starting shape" card.