All use cases
DevOps & SRE
Stop paying for environments nobody opened this month
Idle previews sleep after two hours and delete themselves when the branch merges.
Before Fenwaveindefinitely waiting
“Does anyone still need staging-3? It has been up since March and I do not want to be the one who deletes it”
What the wait costs
Long-lived environments accumulate because deleting one carries risk and keeping one carries only a line on a bill nobody reads.
Environment sprawl is a decision problem, not a cost problem: nobody can safely tell whether an environment is still needed, so it stays. Tying lifecycle to the branch removes the judgement call. The branch is merged, therefore the environment is finished — no meeting required. Sleep-on-idle handles the middle case where a branch is open but nobody is looking at it.
How it works
- 01Set the default lifespan per environment type — 7 days for dev.
- 02Idle environments sleep after two hours without traffic.
- 03A merged branch triggers deletion of its namespace.
- 04Staging and production are exempt: they are permanent by configuration.