Run a coding agent all day

Always-on mode is for a computer that needs an admitted capacity reservation across the day. It is not a job scheduler; interruptions remain possible. All computers run in one location. The selected billing mode, current reservation and observed lifecycle state are separate facts.

Choose the appropriate deadline

An on-demand computer has a run timer. Extend it with the keepalive permission before its current deadline, or update its configured timeout according to Pause, stop and timeouts. A background process has no process deadline by default, but it still stops when the computer stops or reboots. Adding a process timeout does not extend the computer timer.

Always-on stores the configured timeout but does not run the on-demand timer. Switching back to on-demand restores the timer rules. Mode changes go through capacity and billing admission; an unreserved always-on computer cannot assume that its previous slot is still available.

Low balance and restart

Low balance can release the reservation. A top-up does not run the computer and does not itself restore that reservation. Explicit capacity admission or a switch to on-demand is required. While unreserved, always-on compute and its own storage charges remain paused; account-storage charges resume when retention clears. Use the original account and computer reads to decide the next action.

After a planned restart, reserved always-on computers are started again according to the documented policy; on-demand computers return stopped. There is no service-level agreement. We make no availability promise. Make the application recoverable from a restart and keep independent backups. Pricing specifies the cap and billing exclusions; Honest limits explains the shared-infrastructure risks.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.