On-demand and always-on
On-demand is the default mode. Always-on additionally reserves capacity for the computer, subject to admission and the low-balance release rules. Changing a label in client code does not reserve a slot: use the documented update operation and inspect its returned state.
| Property | On-demand | Always-on |
|---|---|---|
| Running compute | Billed by observed running interval | Billed under the always-on policy (the cap spread over 730 hours) |
| Paused capacity | Released | Kept while reserved |
| Run timer | Active while running | Configured value stored but inactive |
| Resume | May refuse for capacity | Uses the retained reservation, unless it was released |
| Monthly cap | Per-computer counter | Same counter, not a second cap |
Both modes share the computer's monthly cap history. A mode switch does not reset usage or retroactively charge earlier free time. A resize raises the applicable cap only after it finishes; the counter itself remains.
Low balance can release an always-on slot. Repaying or clearing retention does not reacquire it and does not start the computer. Explicit capacity admission (a start or resume that succeeds) or a switch to on-demand is necessary; account storage resumes separately from unreserved compute and own storage. Always-on capacity is limited, so entering always-on needs capacity to be available; a refused switch leaves all fields unchanged. See Always-on agents and the full Pricing rules before choosing a long-running workflow.
Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.