Branch live VMs instantly.

Virtual machines with git-like semantics. Fork a live VM: memory, processes, sockets, and all in milliseconds. Run a thousand agent trajectories in parallel. Roll back a bad deploy in one call.

Used by agent swarms, CI preview environments, and teams who ship on Friday afternoons.

How it works

Three primitives. Branchable, committable, resumable VMs.

01 branch

Branch

Clone a running VM to take it in a different direction. Do it a hundred times. The parent keeps running.

CLI TypeScript

$ vers branch vm-abc123
→ vm-9f2e77

02 commit

Commit

Freeze a running VM to a permanent commit. Tag stable states, ship known-good builds, and continue moving fast in new branches.

CLI TypeScript

$ vers commit vm-abc123 --tag stable
→ c1a2b3c4

03 restore

Restore

Boot a VM from any commit. Reproduce a bug from the exact state it shipped in, spin up a clean demo, onboard a new engineer without setup scripts, or roll back a bad deploy in one call. Any commit, any time, the full running state.

CLI TypeScript

$ vers restore c1a2b3c4
→ vm-d41c09 booted

Simple Syntax Familiar Commands

  • vers run
  • vers branch
  • vers commit
  • vers connect
~/vers

$ vers branch

Cloning current moment...

Files [copied]

Processes [carried]

Memory [mapped]

Branched vm-abc123 → vm-9f2e77 in 0.586ms

Mental Model

It's git for running machines.

A root VM is a main branch. Every branch is a living fork. Every commit is a restorable snapshot. Walk the tree, prune dead experiments, roll back production in one call.

  • root: base image
  • branch: live fork
  • commit: content-addressable snapshot
  • restored: booted from a commit

A tree of live virtual machines: one root VM, three branches (two agent trajectories and a CI preview), each with its own commits and sub-branches, and one restored rollback.

  • ROOT: vm-abc123 base · ubuntu-24.04
  • BRANCH: vm-9f2e77 agent_1 · path A
  • BRANCH: vm-55dd01 agent_2 · path B
  • BRANCH: vm-ff22c8 ci · preview-#482
  • COMMIT: c1a2b3 tag: stable
  • BRANCH: vm-1e04 rolled back
  • COMMIT: d7f09a pre-deploy snapshot
  • RESTORED: from c1a2b3 one-call rollback

Use Cases

Built for teams that branch compute, not just code.

Agent swarms

Fork one VM into a thousand. Let agents explore in parallel, keep the winners, discard the rest.

CI + CD

Every PR gets a perfect copy of production. Branch at HEAD, boot an ephemeral deployment, tear it down on merge.

Reliability

Commit before risky migrations. If the deploy blows up, restore the commit: live memory and all.

Durability

Checkpoint long chains at every tool call. Resume from the last known-good state on crash.

FAQ

How is this different?

Most sandbox platforms give you ephemeral VMs: boot, run, throw away. Vers gives you a tree of live machines you can branch, commit, and restore: memory, processes, sockets and all. Branches fork in milliseconds with no cold boot, so you're not paying for warm pools sitting idle. Different primitive, different jobs.