Skip to main content
A full Linux VM. Dedicated kernel. KVM isolation. Your own root. Boots in 411ms. Sleeps for free. Wakes without moving data. Resizes live. Storage survives everything. Think of it as EC2, except the instance starts in under a second, sleeps to zero cost, wakes without reprovisioning, and resizes CPU and memory while your process is running.

​
Compute

Each machine runs on a dedicated Cloud Hypervisor microVM with its own Linux kernel. Not a container. Not a shared-kernel sandbox. Hardware-level KVM isolation.
Cold start411ms from a pre-warmed host pool
Wake from sleepSub-second. userfaultfd demand-pages 2 GB in 18ms
Live resizeACPI hotplug. Add vCPU and memory to a running VM. No restart.
Live migrationfd-passing between hosts. Sub-millisecond for local migration.
GPUVFIO passthrough. Full device, not emulated, not time-sliced.
TimeoutNone. Machines run until you stop them.

​
Storage

/home/machine is backed by S3 via virtio-fs. It’s not a local disk. It’s a disaggregated filesystem that exists independently of the VM.
PersistenceSurvives sleep, wake, host failure, live migration
CapacityConfigurable. Not bounded by local disk.
DurabilityS3 (99.999999999% durability)
On sleepCompute released. Storage untouched. No data movement.
On destroyRetained 30 days per retention policy, then deleted.
Root filesystemEphemeral. Rebuilt from snapshot on each wake.

​
Billing

Per-second while awake. Monthly for storage. Sleeping machines pay storage only.
StateCompute costStorage cost
RunningPer-secondMonthly
SleepingZeroMonthly
DestroyedZeroZero (after retention)
No idle tax. No minimum runtime. No reserved instances. Sleep a machine at 3 AM, wake it at 9 AM, pay for zero compute in between.

​
Access

Four ways to interact with a running machine.
MethodUse case
Execution APIRun a command, get stdout/stderr. Stateless RPC.
SSHInteractive shell. Port forwarding. SCP.
Terminal APIWebSocket-based PTY. For browser-based terminals.
Preview URLsExpose a port to the internet. For web servers, notebooks, UIs.
All four require the machine to be in running state. If it’s sleeping, wake it first (or let the SDK handle it).

​
Lifecycle

Four states. Predictable transitions. No hidden states.
TransitionWhat happens
CreateControl plane admits request. Host agent boots VM from snapshot.
SleepVM stops. CPU and memory released. virtio-fs state preserved.
WakeFresh VM boots. virtio-fs restored via userfaultfd. Sub-second.
DestroyVM removed. Storage enters 30-day retention.
ResizeHotplug applies immediately. No state change.

Quickstart

Create a machine and run code. CLI, Python, TypeScript, Go.
Last modified on April 9, 2026