Cloud Servers and billing

A cloud sandbox for coding agents on Isolation costs what its machine uses while it runs. Every Cloud session is its own machine: created when you launch, billed per second while it runs, a fraction of a cent per hour while it is paused, nothing once it is finished. There is one bill — the organization's prepaid balance — and the numbers are on the pricing page, with a calculator.

Connected Servers never bill at all.

Cloud sessions

On the Servers page a Cloud server looks like any other: a label, an Isolation region (Europe, USA or Asia) and the sandbox types it offers, each with the price per hour it will charge while a session runs. Underneath it is a configuration, not a machine. When a member launches on it, Isolation places a fresh machine for that session in the region, on the same isolation-server and OpenSandbox runtime every server runs, and the meter starts. When the session pauses the machine sleeps and only its storage bills; when it finishes the machine is gone.

Each Cloud session has its own addresses: an ssh name of its own (ssh <route>@d-<id>.isolation.cc, direct over IPv6 on every plan; from an IPv4-only network the connection goes through Isolation's doorstep, which Professional and Enterprise include) and a preview address of its own for anything it serves on a port.

launch    → a machine is created for the session, the meter starts (per second)
working   → billed at the type's hourly price, in whole cents as they accrue
pause     → the machine sleeps; cpu and memory stop billing, the disk keeps billing
resume    → the machine wakes in a second, where you left off
finish    → the machine is gone, every charge stops

Creating one

On the Servers page choose New Cloud Server and pick an Isolation region and the sandbox types it offers — the four standard sizes, or any shape you draw — or in a chat app send /add-server <label>. It exists the moment you confirm, at no cost, and every member can launch on it from then on. Personal organizations may keep one; Professional up to twenty. An Owner or Admin can remove it at any time: no new sessions start on it, the ones running keep running until they end, and then it is gone.

Sandbox types and the price

A sandbox type is a shape: a cpu class, vCPUs, memory and disk. Its price is the sum of its parts at the region's rates — a shared or dedicated vCPU per hour, a gigabyte of memory per hour, a gigabyte of disk per hour — minus your plan's percentage. CPU and memory bill while the session runs; disk bills for as long as the session exists, paused or not. The pricing page has the rate card for every region and a calculator; the dialog that creates a type shows the same number.

Shared vCPUs are burstable: full speed in bursts, a slice of a core sustained — right for editing, agents and test runs. Dedicated vCPUs are a whole core each, for builds and long compute, at a higher rate per vCPU. Memory, disk and egress cost the same in both classes.

The price is frozen on the session at launch: a change to the type, the plan or the rates reaches the next session, never one already running. Where the machine physically lands is Isolation's choice inside the region; a region is priced at the dearest of its locations, so the number is one fixed number.

Egress

Every gigabyte a session sends is billed at the region's egress rate, from the first byte. There is no allowance and no cap: a session is never cut off, and its info shows the total sent and what it cost. Traffic into a session is free.

Pause when you are not working

A paused Cloud session keeps its disk so it resumes in a second, and the disk is the one part that keeps billing — cpu and memory stop the moment you pause; a fraction of a cent per hour for most sizes. Pause, resume, save and finish explains what survives. Finishing a session ends every charge; the work is in the workspace. On the Personal plan up to three sessions may be paused at once, for up to 14 days; after that the platform finishes them.

The balance

The organization has one prepaid balance, funded by the Owner or an Admin from the Stats page or with /topup <amount>, in whole dollars from $5 to $500. Members never enter a card. The balance pays for Cloud sessions — running, paused and egress. AI is never on it, because AI providers are personal credentials, and Connected Servers are free.

The Stats page warns you when the balance drops below a threshold. If it runs out anyway, every Cloud session of the organization — running or paused — is stopped with its work saved. Nothing is lost and nothing keeps charging. A launch that the balance cannot cover is refused with a message that says so, from the website, a chat or MCP alike.

Choosing between the two

Use a Connected Server when you have a machine to spare: an office box, a spare Mac, a VPS you already pay for. It is free, you can pair several, and it runs the same software. Use Cloud sessions when you do not, when the one you have is closed for the night, or when a task needs more than it has. Many organizations run both: a Connected Server as the default, Cloud sessions for overflow and for the work that must keep running with everyone's laptop shut. A workspace launches on whichever you choose, so moving a task from one to the other is a matter of picking a different server at launch. What every session measured, on either kind, rolls up in metrics per member and team.