Cloud computer billing
Found this helpful? Share it:
Found this helpful? Share it:
Cloud computers bill your Credit balance by the second. Here is how the counting works and what happens when the balance runs out ⏱️
A cloud computer bills your Credit balance per weighted second at the prices shown in the app, so you pay for exactly how long it runs. Larger machines draw proportionally faster, because a bigger machine costs more per second. GPU and CPU differ only in price, never in how they are metered.
On the free tier the smallest machine (standard.xs) runs on your welcome credit: 60 minutes per session, and it pauses after about 15 minutes of inactivity. Anything bigger, or a GPU, draws your balance the same way. For what a cloud computer is and how to launch one, see Cloud computers.
When your balance cannot cover a machine's next tick, idapt suspends it so it stops running up a cost. Resume it after adding credits or turning on auto top-up (see Credits and auto top-up). On the free tier the session and idle caps suspend the machine on their own.
To pause a standard machine and stop using your plan, suspend it. Suspending stops and backs up its containers, then releases the compute, so the charge stops. Resuming provisions a fresh machine and restores them.
A machine that is only stopped still bills at its full rate, because the server stays allocated to you. To actually stop paying for compute, suspend the machine, don't just stop it.
Suspend a computer whenever you step away. It keeps your balance for when you need it.
Related articles
Cloud computers
Launch an on-demand cloud machine, understand what it costs per second, and suspend it when you're done.
Plans, credits, and the welcome credit
How the welcome credit, subscription plans, and your Credit balance fit together, and what happens when you reach a limit.
Credits and auto top-up
Add a prepaid Credit balance, keep it funded automatically, and see exactly how it settles your usage.
Was this helpful?