Avrea Sandboxes lets you fork an entire computer like a Git branch

Is 'fork' missing operation in sandboxes?

Avrea Sandboxes lets you fork an entire computer like a Git branch

Avrea Sandboxes offers full virtual machines, not just command-execution APIs, built on Apple M5 Max and AMD Zen 5 EPYC hardware with no CPU oversubscription. They boot with Git mirrors and colocated package caches already warm, bill by the second, and support pause, resume, and fork of the whole disk. The pitch: a computer should be something you copy and discard as casually as a branch.

Forking is to computers what branching is to source code.
  1. thepoet

    Nice writeup. The step after forking paused sandboxes would be to fork live running sandboxes with the RAM, device state and disk all being forked. Get the same execution point with all processes still running rather than having to resume. You then also have to take care of kernel RNG

    state, boot ID, clocks, cached session keys etc. before the forked version starts meaningful work.

    Disclosure: I am working an open-source KVM-based VMM for agent sandboxes, https://github.com/instavm/tarit

  2. jstanley

    I'm curious how you handle open TCP sockets etc. at forking time? Do all sockets just get closed on one branch of the fork?

    EDIT: I see you're only cloning filesystem contents, never mind.

  3. damezumari

    I wrote up about our sandboxes. Everyone and their dog is offering them, but I think the fork operation is somewhat interesting at least for our own use - being able to fire copies of sandbox with a single API call has been convenient for our agentic use (reusing all earlier setup steps has saved lots of time and tokens).

    Disclaimer: I know there's some more effort 'snapshotting' and other concepts elsewhere too, but from our point of view making it first-class citizen in both UI and API felt sensible and it has been useful.

More from this day

2026-11-22