the same computers, on our hardware.

01

the problem cloud solves

you built against microsandbox locally. now you need to run many of them at once, in production, without operating a fleet of hosts, and with your team's identity and your finance team's invoices wrapped around it.

our cloud runs the same runtime on our hardware. you keep the sandbox you already wrote and hand us the operations.

02

the same code, one config change

one sdk. one api. local or cloud is a config change, not a rewrite.

the create call you wrote locally is the call that runs in the cloud. you point the sdk at the cloud backend and the rest of your integration does not change.

03

what the organization layer actually does

• sso and two-factor login: your team signs in with your identity provider, not a shared password.
• roles: control who can create and remove sandboxes, and who can administer the org.
• audit logs: every action is recorded, so a security review has something to read.
• quotas: cap what an org can consume, so one runaway job cannot run up the bill.
• private registries: pull images from your own registries, with credentials the guest never sees.
• metering and invoices: usage is billed per sandbox, and it reconciles to a monthly invoice.

04

run it like production

the cloud is built to run large concurrent fleets, so a spike of agent tasks does not become your problem to schedule. capacity, placement, and the isolation floor are ours to operate.

05

getting access

access is by request while we widen the private beta. invitations go out in batches, and we tell you where you are in line. it is intentionally small right now so the people we let in have a good first week.