Pausing & hibernation
An environment that gets no traffic and no deployments for a while stops running, so it no longer counts as a live environment. What happens depends on your plan.
| Free | Standard | Pro | Platform | Enterprise | |
|---|---|---|---|---|---|
| Idle sites | Paused after 14 days | Hibernated after 30 days | Hibernated after 30 days | Hibernated after 14 days | Never hibernated |
When an environment is idle
An environment is idle when all three are older than your plan's number of days:
- its creation;
- its last request, to a page, an API route or a static file;
- its last deployment.
It's checked once a day.
Paused (Free)
A paused environment answers every request with a 503 "Site paused" page. Its deployments, variables and domains stay as they were.
To bring it back, deploy to it again, or roll back to one of its deployments. Either needs a live environment to spare on your plan.
Hibernated (paid plans)
A hibernated environment wakes up on its own:
- The first request gets a 503 "Waking up…" page, which reloads itself after a few seconds.
- Meanwhile, Hiraiship publishes the environment's current deployment again.
- The reload, and every request after it, reaches your app as usual.
Waking takes a few seconds. An environment that must answer instantly at any time needs traffic, even a periodic health check, to stay awake. Enterprise never hibernates environments.
A hibernated environment doesn't wake while its workspace is suspended.