Skip to main content
Save a named checkpoint of a runtime, then start new runtimes from it or fork several copies. The original runtime keeps running. Pause keeps this same runtime. A template is the image a new runtime boots from. A snapshot is work the runtime has already done.

Save a snapshot

Save after installs, clones, or data prep, or before a step you may want to undo. See Save a snapshot.
  • The source runtime keeps its ID. It pauses briefly while the snapshot is stored, then continues. Reconnect SSH, terminals, and streams after the call returns.
  • The call waits until the snapshot is ready. A cold snapshot of a large disk takes longer than a hot snapshot of a small working set.

Restore a runtime

Start a new runtime from the snapshot when you want that saved state on a new ID. See Restore a snapshot. A cold snapshot boots fresh with the saved files. A hot snapshot continues from the saved memory, including running processes.
  • New runtimes start in the snapshot’s region. Pass the same cloud and region as the source. If that region has no capacity, create fails.
  • Start several runtimes from one snapshot when they should all begin from the same point.

Fork a runtime

Fork when you want several independent runtimes from one capture, from a running runtime or from a snapshot you already saved. See Fork a runtime.

Snapshot object

Endpoints