Free tools · Machines

Pin a machine as a template and clone fleets from it

Pin a configured machine as a golden template and create linked clones from it. Clones share blocks with the golden rather than copying it, so a fleet costs about as much disk as one machine and each member can be disposed of on its own.

macOS 26 or later · Apple silicon · free on both tiers

Step by step

  1. 1vm template pin base

    Mark a configured, stopped machine as a golden others can be cut from.

  2. 1vm create worker-1 --from base

    A linked clone. `--full` makes an independent copy instead.

  3. 1vm clone dev dev-experiment --rekey-ssh

    Clone an existing machine and regenerate the guest host keys so the two are distinguishable.

  4. 1vm archive worker-1

    Compress a stopped machine and reclaim its disk. Run it again to restore.

Worth knowing

  • Goldens, fleets and archive are Pro. The underlying clone speed is the same on both tiers — Free simply keeps fewer machines.
  • `1vm golden capture <vm>` records firmware, drivers and first-boot state into golden.json; a Windows guest needs a READY guest agent, or `--force`.
  • `1vm du` shows what the library actually costs once clones are sharing blocks.

The long version

This page is the short path. For the whole area in prose — the options, the edge cases and what to do when it does not work — read Inside a VM bundle.

Download 1VMToolWhat Pro lifts

Related

Create a Linux VM

One command to a booted Debian, Ubuntu or Omarchy guest — or a prepared toolchain with nothing left to install.

Read it →

Run Windows on Apple silicon

The first-party 1VM engine boots Windows on ARM without QEMU — installed from your own ISO, with the virtio drivers attached.

Read it →

Snapshot and restore a VM

A snapshot is an APFS clone, not a copy — take and restore finish in well under a millisecond no matter how big the disk.

Read it →

Frequently asked questions

What is the difference between a clone and a full copy?

A linked clone shares unchanged blocks with its source and only stores what diverges. `--full` copies everything, which costs the disk but leaves no dependency on the golden.

Can I delete the golden a clone came from?

Not while linked clones depend on it. Use `--full` if the clone has to outlive its source, or archive the golden rather than deleting it.

Is this how disposable task machines work?

Yes. `1vm task run -- <cmd>` clones a golden, waits for it to be ready, runs the command and disposes of the machine, which is the whole pattern in one command.