Claim a staging slot for the next hour.
Everyone sees who has it and how long is left.
Stop asking "who has staging-3?" in Slack. StagingReservation is a shared board for the envs your team already runs — slot reservations, status, and the live ref on each one.
Real board. Real reservation chips. URL probes light the dot green when the env is reachable.
A shared board for the environments you already run
Git tracks your branches. It doesn't track which branch is live on staging, who's using that environment right now, or whether it's up. StagingReservation is that missing layer — assembled straight from your GitHub activity, with nothing for you to wire up or run.
See what's running on every environment
Each slot shows its live ref, status, and URL — updated the moment a branch lands, a tag's cut, or a deploy finishes. Open the board and you instantly know what's on staging, on prod, and everywhere between.
Claim a slot so nobody steps on your test
Grab an environment for the next hour or day. Everyone sees who's holding it and when it frees up — the end of "who has staging-3?" in Slack, and of two people clobbering the same box.
No deploy keys. No code access. No new pipeline.
It reads your GitHub activity and reflects it — that's the whole footprint. We never deploy, never touch your CI, and never fetch your source. Connect a repo and nothing about how you ship changes; you just finally have the board. How we keep that promise →
Start from a shape that fits how you ship
From dead-simple staging + prod to a full Dev → QA → Staging → Prod promotion path — pick the closest shape and tune it later. Schema-agnostic: every template is just a few rows you can rename, add to, or rebind freely. No setup required to start.
Solo or pre-PMF teams shipping from main.
Staging → branch main Prod → branch main
Modern trunk teams with per-PR preview environments.
Preview → branch pr-* Prod → branch main
QA-heavy teams that reserve envs per feature branch.
Staging → staging-1 / staging-2 / staging-3 Prod → branch main
Release-train teams using develop + tagged production.
Staging → branch develop Prod → tag v*
Regulated or larger orgs promoting a release through stages.
Dev → branch develop QA → branch qa Staging → branch staging Prod → tag v*
From sign-in to a live board in five minutes
Sign in with GitHub
OAuth via our GitHub App. Personal workspace seeded on first login.
Pick a shape
Staging+prod to multi-stage. Tune later — the schema doesn't lock you in.
Install on a repo
GitHub App install grants Contents + Deployments scopes. Pick repos.
Push code
Webhooks light up the matching slot. Your CI deploys; status flows back.
Stop asking "who has staging-3?"
Free while we're in beta. GitHub-only auth for now; Google + magic-link land soon.