Skip to main content
State on a computer is ephemeral by default — a destroy tears it down. Snapshots and volumes are the two ways to make state outlive a single computer or session.

​
Checkpoints

A checkpoint is a durable snapshot taken without stopping the VM. The computer keeps running while its disk state is captured, so you can mark a known-good baseline mid-task and return to it later.

​
Forks

A fork creates a new computer from a checkpoint. The fork is an independent computer with its own lifecycle — and it is billed like a fresh create: there is no creation fee, just per-second metering while it runs.
Use a checkpoint + fork to explore branches from a common setup: prepare a baseline once, then fork several computers to try different approaches in parallel.

​
Persistent volumes

A persistent volume keeps a computer’s disk — and its memory when paused — alive across park and sleep. Attach one at create time and the computer’s state survives the idle cycle instead of being ephemeral.
A destroy tears everything down, including an attached volume’s contents. Volumes protect state across park/sleep — not across a destroy. Promote anything you must keep permanently to Files.

​
Pause & resume

Pause and resume map directly onto the runtime’s wake/sleep cycle. A paused computer keeps its disk (and, with a volume, its memory) and resumes with state intact — so idle time costs storage only, not compute. This is the same mechanism the durable runtime uses between turns.
CLI

​
Fields

​
string
A persistent volume to attach. Disk survives park and sleep; memory survives a pause.

Next: networking

Outbound access, HTTP preview URLs, and the coming egress pinning.