CLI v0.3.12Desktops, replicated storage & saved connections

Give your agents
a machine of their own.

AHVM runs stateful Linux microVMs on hardware you control. Shells that reattach, files that stay put, memory you can checkpoint. A real computer for every coding agent, experiment and side quest.

curl -fsSL https://ahvm.app/install.sh | bash
Read the docs
~/code — ahvm · connection home Illustrative session
  • 0public ports needed. SSH does the talking.
  • 30sof quiet before a resident pause. Resumes on demand.
  • 60minidle before a full stop frees RAM. Disk stays.
  • €0to self-host, up to $1M ARR.
  • Ubuntu
  • Node.js LTS
  • Bun
  • Python
  • Git
  • Claude Code
  • Codex
  • OpenCode
  • Pi
  • build tools
  • your agent here

01 Why a machine

Most sandboxes forget.
AHVM remembers.

A throwaway sandbox

  • Starts empty, every time
  • Loses the shell when the client drops
  • Runs on somebody else’s schedule
  • Rebuilds the world for every task

A machine of its own

  • Persistent disk, sessions and memory checkpoints
  • Terminals that outlive the client. Detach, come back.
  • A real guest kernel in a KVM microVM
  • On your Linux server, under your limits

02 How it fits together

Your laptop. Your server.
Their machines.

The client talks to your host over SSH. The daemon runs microVMs on KVM. No domain, no public API port, and the admin token never leaves the server.

Your computer ahvm CLI macOS (Apple Silicon) · Linux x86_64 ahvm use home
Your Linux server AHVM daemon
x86_64 · KVM · systemd
agent-01running
experiment-02paused
omarchydesktop · stopped
your code & agentguest kernelmicroVM · libkrun fork

Prefer not to run a server? AHVM Cloud is in invitation-only early access. Same CLI: ahvm use cloud.

03 The primitives

Everything a sandbox needs.
Nothing in the way.

Run anything a shell can.

Execute commands through the CLI or HTTP API, with output and exit codes ready for your automation. --json and redirected stdio never open an interactive shell, so scripts stay scripts.

❯ ahvm exec dev -- ahvm-dev npm test
❯ ahvm exec dev -- ahvm-dev git status
❯ ahvm create ci-01 --json # never opens a shell

Leave. Reattach. Continue.

Persistent terminal sessions with live input, resize and detach. Ctrl ] detaches without ending anything. Your session, and the agent in it, can outlive the client.

❯ ahvm shell dev
ahvm@dev:/workspace$ claude
  … agent working. Ctrl-] to detach.
❯ ahvm shell dev # later, from anywhere

Move the actual files.

Stream large uploads without a fixed file-size cap. The guest file is replaced only when the transfer completes, so an interrupted upload never clobbers the original.

❯ ahvm files put dev ./dataset.tar /workspace/dataset.tar
❯ ahvm files get dev /workspace/report.md ./report.md

Make room to experiment.

Save disk and memory state before the risky part. Restore a checkpoint as a new sandbox, or stop and start from saved state. Let the agent try the bold refactor.

❯ ahvm snapshot create dev before-change
❯ ahvm stop dev   # disk + memory checkpoint
❯ ahvm start dev  # back where you were

See what you’re building.

Authenticated HTTP previews and WebSocket forwarding for your guest applications. Private TCP access is explicit, never accidental.

ahvm@dev:/workspace$ bun run dev --port 3000
→ authenticated HTTP preview
→ WebSockets forwarded
  raw TCP: only when you ask for it

Give it a screen.

Some agents need a desktop. Pull a desktop image, create a machine and open it at the resolution you want. Desktop VMs use disk-only stop and start.

❯ ahvm image pull omarchy-desktop
❯ ahvm create omarchy --image omarchy-desktop --no-shell
❯ ahvm desktop omarchy --resolution 1080p

One CLI. Many homes.

Save connections to your own hosts and switch with one word. Names belong to their connection; AHVM never goes looking on other hosts behind your back.

❯ ahvm host add home --ssh root@192.168.1.50 --install
❯ ahvm use home
❯ ahvm --context home list # one-off override

04 Lifecycle

Busy when it works.
Quiet when it doesn’t.

Idle machines give their resources back on their own. Nothing is ever deleted unless you say so.

  1. Running

    Commands, shells, file transfers and managed agent jobs. Connected shells keep it awake, even quiet ones.

    active
  2. Paused

    RAM and disk stay resident for a near-instant resume. The next guest command wakes it automatically.

    resident · auto-resume
  3. Stopped

    Memory is released. Disk and a memory checkpoint are kept. ahvm start brings it back.

    RAM freed · disk kept

Timeouts are the defaults and configurable by the operator. Local snapshots are not off-host backups. Hosts configured for replicated storage add optional remote disk durability.

05 Get started

Three commands.
One machine of their own.

  1. 1

    Install the client

    On your Mac or Linux machine. Needs curl, gzip and Python 3. Prefer Homebrew? brew install mariobm/ahvm/ahvm

    curl -fsSL https://ahvm.app/install.sh | bash

  2. 2

    Connect your host

    Provisions AHVM over SSH. The Ubuntu image downloads straight to the server. Linux x86_64 with KVM and glibc 2.35+.

    ❯ ahvm host add home --ssh root@YOUR_IP --install
  3. 3

    Create a workspace

    Bash opens inside the VM as the ahvm user in /workspace. Type exit and it keeps running.

    ❯ ahvm create dev --cpus 2 --memory 4096

06 Choose your home

Your machine.
Or one of ours.

Run it yourself, let us host it, or get your team set up with a hand from us.

01Self-hosted

On your hardware.

€0/ software

Your host. Your tools. Your control.

  • CLI and HTTP API
  • Ready-to-code Ubuntu workspaces
  • Persistent sessions and snapshots
Install AHVM

Free up to $1M worldwide ARR, including affiliates. License terms ↗
Hosting and AI usage are separate.

02AHVM CloudEarly access

Leave the hosting to us.

Invite onlyPricing announced before launch

An agent workspace, minus the server setup.

  • AHVM-hosted Linux workspaces
  • Your familiar CLI and AI tools
  • Bring your own AI provider
Join the waitlist

Invitation-only pilot in development.
Launch pricing and allowances are tentative.

03Team pilot

A little help getting started.

€299/ month, from

A dedicated host. Hands-on guidance.

  • Host setup and configuration
  • Onboarding for your first workflow
  • Updates and direct email support
Discuss a pilot

Management fee only. Infrastructure, AI usage and taxes are additional. Three pilot places.

License and pilot details

Self-hosted. You manage hosting, updates and backups. Above $1 million worldwide ARR, including affiliates, a paid commercial software license is required. Read the full license terms ↗

Team pilot. Scope, capacity, onboarding costs and duration are agreed before you start. The management fee does not include an above-threshold commercial software license.

Cloud. Pricing, resource allowances and availability will be announced before launch. AI model usage is separate and billed by your provider.

First in line

Meet your next workspace.

Get one email when AHVM Cloud opens its doors. Nothing else.

A different setup in mind? Let’s talk ↗

07 Good questions

Before you
spin it up.

Is this a hosted service?

AHVM is available to self-host today. AHVM Cloud is our upcoming hosted service for developers who want to use our infrastructure, with an invitation-only pilot underway. Pricing and resource allowances will be announced before launch. Teams can also discuss a separate paid pilot for dedicated host setup and hands-on support.

Can I run my coding agent inside?

Yes. New sandboxes include Ubuntu, Node.js LTS, Bun, Python, Git, Claude Code, Codex, OpenCode and Pi. Sign in with your own provider account or API key.

What happens when a sandbox stops?

A normal stop saves a local disk and memory snapshot for the next start. Idle-stop is automatic; starting again is explicit. Worker recovery uses the latest saved checkpoint, not unsaved RAM. Local snapshots are not off-host backups.

Does AHVM support Firecracker or macOS?

The current runtime uses libkrucible, our libkrun fork. The qualified server bundle is Linux x86_64/KVM. Standalone clients are available for Apple Silicon Macs and Linux x86_64. A macOS server package and a Firecracker backend are not included.

Is it ready for production?

This is an early release for evaluation on your own hardware. We’re improving the development experience before the first stable release. It is not a production security sign-off for hostile multi-tenant workloads.