Docs

Sleeping apps

An app nobody is using scales to zero, and wakes on its next request.

How it works

An app with no HTTP requests for its idle time, 30 minutes unless you change it, is put to sleep: its replicas stop and its addresses are routed to datahuru's waker. The next request wakes it. A browser sees a short waking-up page that reloads itself; other clients are held until the app is ready, for up to a minute.

What you pay

A sleeping app is not charged for CPU or memory, only for any storage it holds. An hour it slept part of is charged for the part it was awake.

Turning it on or off

• On Hobby, apps sleep by default; on Pro they stay awake by default.
• Change the default for your whole team on the Team page, or for one app in its Settings, with an idle time of its own of 5 minutes or more.
• Wake now and Sleep now on the app's page do it at once.

Sleep suits websites, admin tools and APIs with quiet hours. An app that must answer instantly, or that works in the background without receiving requests, should stay awake.