Sleep and wake
A web app on Ownkube Compute can sleep when nobody is using it and wake on the next request. A sleeping app bills no CPU or memory. Databases and caches can sleep too, and an app that wakes brings its linked database and cache up with it.
Turn it on
Section titled “Turn it on”-
Open Settings
On the web app’s page, open Settings and find Sleep when idle.
-
Set the idle window
Choose Idle before sleep in minutes, 1 to 60. The default is 5. After that long with no requests, the app scales to zero.
-
Save
The change rolls out like any other. The Overview tab shows Asleep once the app has gone idle.
Requirements
Section titled “Requirements”- The app needs a public hostname. An incoming request is what wakes it.
- A single replica with autoscaling off. Set the replica count back to one to enable sleep.
- Ownkube Compute only. Own-cloud clusters do not sleep.
What a wake looks like
Section titled “What a wake looks like”The first request after sleep is held while the container starts, then served. Every request after that is served normally until the app goes idle again. This pause is a cold start; how long it takes depends on how fast your app boots, so keep startup lean and use a startup probe that reflects it.
Leave sleep off for anything that must answer instantly or receives webhooks that cannot retry.
Databases and caches
Section titled “Databases and caches”A Postgres database or Valkey cache can sleep on its own idle window from its Settings tab. Sleep on a database or cache requires Public access on, because the public endpoint is what receives the waking connection. While a database sleeps only its storage bills; a sleeping cache bills nothing.
Linked services wake together. When a sleeping web app receives a request, Ownkube wakes the app and, by name, the database and cache it is linked to, so the app finds them ready. Linking is described on Variables.
Sleep and the bill
Section titled “Sleep and the bill”| State | Compute bill | Other charges |
|---|---|---|
| Web app asleep | Nothing | Nothing |
| Database asleep | Nothing | Storage, per GB per month |
| Cache asleep | Nothing | Nothing |
Sleep is the sharpest tool in cost control for personal software and staging stacks that sit idle between visits. It is different from pausing: a paused deployment (0 replicas, or a spend limit reached) does not wake on its own.