Reduce costs when your apps are idle.
Let apps and databases sleep during periods of inactivity and wake when needed. Reduce idle compute costs while keeping their stored data.
Quiet for a while. Ready when someone comes back.
An app with a realistic period of inactivity.
- 1
Nobody uses it, it sleeps
Eligible web processes and databases sleep while idle.
- 2
Someone opens it, it wakes
A request wakes the app; a new connection wakes the database.
- 3
The data is still there
Stored data is kept while compute sleeps.
What makes it work
Apps sleep and wake
Eligible web processes wake on an incoming request.
Databases too
Eligible PostgreSQL databases wake on a new connection.
Policies and controls
For the supported environment and offer.
Data kept
Persistent data stays while compute sleeps.
Practical questions
Is an idle app free?
Sleep reduces idle compute. Storage and other applicable charges continue, and plan minimums may apply.
How long does waking take?
Waking can take a moment, so the first request after a pause is slower than the next ones.
Can every worker and database sleep?
It depends on the component and its configuration. Database sleep applies to supported single-instance setups, and active connections keep a database awake.
Keep occasional-use apps available.
Without keeping all their compute running all the time.