
A cloud machine that is awake, and the same machine asleep. Example data.
Compute plans
You buy a compute plan, a monthly subscription, and the plan decides the largest machine you can create. A plan always allows its own size and every smaller one. This subscription covers machine time and disk, not app hosting allowances. App hosting is authorized and billed independently; you do not need to rent a machine to host an app. Settings shows the authoritative current subscription price, machine guarantees, included disk and extra running-hour rate. Guaranteed CPU and memory are reserved together; do not assume spare-host bursting is part of the offer. Persistent disk is one machine volume, not a separate hidden image-cache fee. New subscriptions and next-period changes are different authorizations. For a new paid machine subscription, an organization owner or admin must review the server’s exact monthly/hourly terms and explicitly accept that version before payment can appear. Readiness is checked again at checkout; stale terms, a changed organization, missing API support or a commercial hold prevent payment. An existing subscription instead uses the separate next-period acceptance flow; it cannot be replaced through new-signup checkout. Coupons and your own computer remain accessible when paid signup is held. Proposed pricing is not current pricing. The proposed machine catalog remains held until its capacity is commissioned and published prices and billing reconciliation are verified. Settings presents proposed terms separately from your current subscription. An owner or admin may accept the exact proposed terms for a reported next-period boundary when the server allows it; acceptance remains pending and does not itself activate pricing or change this period’s charges. Missing readiness information means unavailable, not permission to buy an old plan as a fallback. No additional machine size or machine-PAYG offer is introduced here.Included hours and extra time
The proposed catalog preserves 160 running hours at the plan’s own size. The billing version fixes exact cost-weighted allowance exchange rates across permitted sizes. These are not dollar, AI or hosting credits, and are independent of retail overage prices. Other-size equivalents are not powers of two: use the versioned equivalent-hours display rather than multiplying Small-machine hours. Mixed or concurrent machines share one period balance. The size picker shows approximate equivalent hours where the server can verify the version and balance. Accounting retains exact fractions; a displayed rounded hour is not a rounded charge. Time counts while running, even when idle; suspension stops runtime consumption, not persistent-disk billing. Unknown versions or routes hold new paid work and reconciliation rather than inventing a rate. When the included hours are used up, you choose what happens in Settings → Billing, under extra machine time:- Stop at my included hours. Machines will not start once the hours are used, and nothing extra is charged.
- Allow extra time, up to a monthly limit. Machines keep running and the extra time is billed, but never beyond the limit you set.
- Allow extra time with no limit.
Waking and suspending
A cloud machine does not run all the time. After a period with no activity it suspends: its compute is released and you stop using hours, but its disk is kept (and billed, below), so your checkout, installed tools and uncommitted work are exactly where you left them. You choose how long “no activity” is when you create the machine: 15 minutes, 30 minutes (the default), 1 hour, 2 hours or 4 hours. Four hours is the most the platform accepts. Only work you or an agent asked for counts as activity: an open tab or background polling doesn’t keep a machine awake. You do not have to wake a suspended machine yourself. When a chat running on it, or an automation needs it, Reliant resumes it and the run continues once it has reconnected; this takes a short while, and the machine shows as waking in Settings → Machines until it does. You can also Suspend and Resume it by hand there.
Machines asleep and waking. Example data.
Creating and managing machines
In Settings → Machines, choose Create Machine, give it a name, optionally pick a repository to clone, choose a size (only the sizes your plan allows are offered) and set the idle timeout. The same page lets you open a machine to see its status, size, storage and idle timeout, restart it, Resize it to another size your plan allows, Grow disk where your plan allows a bigger disk (a disk can’t be made smaller again), grant outside apps access to it, and delete it. Plans, upgrades and cancellation are under Settings → Billing; see Billing, wallet & Reliant AI.Related topics
- Machines overview
- Your own computer, for a machine that costs no compute hours
- Billing, wallet & Reliant AI
- Troubleshooting, if a machine will not connect