Eight rollouts in 1.8 seconds: one forked machine per seed, each starting from the same bytes as the source machine.
What the primitives give you
- Isolation per rollout. Each fork is a hardware-isolated microVM with its own kernel, disk, and network identity. Nothing leaks between workers.
- Byte-identical starts. Every fork of the same source machine continues from the same instruction, with the same processes, memory, and files.
- Real-time branching. A fork copies live memory directly, machine to machine, with no snapshot written to disk first. When rollouts branch on the fly, forking skips the round-trip of saving and loading state, which keeps your GPUs busy instead of waiting on environment resets.
- Stateful resets. A checkpoint rewinds one machine to a saved moment in place, so episode N+1 starts exactly where episode N did.
- A durable starting state. A snapshot saves the prepared environment under a name that outlives the machine. Give each environment version its own name and it stays comparable across a whole training run.
Prepare one warm source machine
Set the environment up once, on one machine:Fork per rollout
Each rollout forks the source machine, runs its episode, reports its result, and is deleted. The TypeScript and Python SDKs drive this from your training loop:- TypeScript
- Python
Verify reproducibility
The check is two forks with the same seed:Reset between episodes
To reuse one machine across episodes instead of forking per rollout, save a checkpoint at the starting state and rewind to it:A starting state that outlives the machine
A checkpoint belongs to its machine and disappears with it. When the starting state needs to outlive the machine, or a teammate needs the same starting point, save a snapshot:env-v3 still means the same environment a month later. This is how a result stays reproducible after the source machine is gone.
Scaling out
Rollouts are independent, so they scale sideways. Idle machines hibernate on their own after 4 hours without network traffic, which keeps a pool affordable between batches, and a hibernated worker wakes in about 85ms when the next batch starts. The cap is 50 machines per organization by default, extendable on request for fleet-sized runs. See Resources and limits. When a policy executes untrusted or generated code, create the workers with--isolated so a rollout cannot reach your account or your other machines. An isolated machine keeps outbound internet unless you set an egress allowlist. See Sandboxes.