Sleep when idle
A server app that nobody is using does not need to run. Choose how long each app waits before it sleeps, and the next visitor wakes it.
Sleep modes
| Mode | Sleeps after | Good for |
|---|---|---|
| Eco | 5 idle minutes | Consider sleep after 5 idle minutes. Best for occasional tools and prototypes; the next visitor may wait for startup. |
| Balanced | 15 idle minutes | Consider sleep after 15 idle minutes. A middle ground for everyday team apps. |
| Responsive | 60 idle minutes | Keep the app warm between visits for up to an hour of inactivity. |
| Stay warm | Never | Disable automatic idle sleep. Useful for background work and latency-sensitive apps; compute keeps running. |
Apps without a chosen mode use the platform default. Sleep applies to server apps; static sites never run an app process.
Change the mode
Open the app's cost controls and choose a mode. The next scheduled idle check uses the new setting; saving does not stop or wake the app immediately. The same screen shows the recorded activity behind each sleep decision.
Waking up
When a request arrives for a sleeping app, Aozumi's gateway starts it, and that visitor waits while it becomes ready. Once it is awake, later visitors do not wait. How long startup takes depends on the stack and the app.
What still costs while asleep
Sleeping stops compute. Storage, databases, traffic and other resources can still cost while the app sleeps. During the beta, plan prices and cost estimates in the console are estimates, not charges.
Questions
- What happens when someone opens a sleeping Aozumi app?
- The gateway starts the app and the visitor waits while it becomes ready. The link stays the same while the app sleeps.
- How do I stop my app from sleeping?
- Set the app's sleep mode to Stay warm. Automatic idle sleep is then off and compute keeps running.
- Do static sites sleep?
- No. Static sites have no running app process; the gateway serves the files directly, so there is nothing to wake.
Checked against the product on .