Plans, limits and idle sleep
Your plan sets pooled limits for your account: memory, CPU, disk, number of workspaces, nodes and members, replicas
per app, audit history, custom domains and idle sleep. Billing (Plan and billing) shows your usage against
the plan, compares plans, and lists invoices. Payment is by card or M-Pesa.
When you cancel, the plan runs to the end of the period, then the account moves to Free limits.
If an account goes over its plan after a downgrade, new growth is blocked. Nothing is deleted.
How usage is counted
Section titled “How usage is counted”- Memory and CPU: the sum of each running node’s limits (per replica for apps). Cron jobs and nodes with no container (domains, secrets, object storage) don’t count.
- Disk: measured volume usage.
- The usage bars warn at 80% and refuse a deploy that would go over 100%.
Idle sleep
Section titled “Idle sleep”On plans with idle sleep (such as Free), a node that gets no visits for a while is stopped to free its memory, and started again on the next visit.
- A node doesn’t sleep while it has open connections, uses CPU, or is deploying. A service only sleeps when nothing awake depends on it.
- A visitor to a sleeping app sees Waking
… this takes a few seconds , and the page reloads by itself. API requests are held for up to 15 seconds while it wakes. Linked services wake first. - The panel shows asleep with a Wake button.
- Keep awake (Settings: Never put this to sleep) opts a node out.
These never sleep: Linux boxes, cron jobs, Observability, and apps with a published TCP port.
Caches lose what they hold in memory when they sleep.