Pre-release. HareBox is a working local build with no public service yet. Statuses on every feature say what runs today; speed and reliability figures are targets until measured. Status

New Exact forks and sleep that keeps programs running

A real computer for every AI agent.

HareBox gives each agent its own full Ubuntu VM: root, systemd, Docker and nested KVM, with its own kernel. Put it to sleep and it wakes with its programs still running. Fork it and the copy is exact. Pay by the second, 1% below boat.dev on every hour.

$0.03564 an hour for 4 vCPU and 8 GB. EU only. A 7-day trial with a card, charged nothing until day 7.

The HareBox bunny holding a glowing cube

An illustration of the flow. Timings are targets until measured.

Default size, per hour
$0.03564
Below boat.dev's list price
1%
API operations
203
Free stopped-disk retention
14 days
Region
EU only
Why a whole computer

Agents do real work. Give them a real machine.

Agents install packages, run Docker, start servers, open browsers and work for hours. A container or a function can't hold all of that. A VM with its own kernel can, and HareBox makes it cheap to keep, copy and pause.

Sleep keeps your work exactly where it was

Stopping a VM saves its disk and ends its programs. Sleep saves memory too, so a dev server, a debugger or an agent halfway through a task carries on the moment it wakes. Use it for quick returns; stop the machine to end the bill.

Real VMs, locally

Forks that are exact

Copy a running VM with its memory and latest writes. Each copy gets a new identity, keys and entropy.

Real VMs, locally

Streams, not polling

Follow an agent over SSE, WebSocket or signed webhooks, resuming from a cursor after any disconnect.

Works locally

Secrets stay out of the VM

The sandbox holds a placeholder. The real key is added on the way out, only for the host its rule names.

Works locally

Spending you can cap

Hard dollar budgets on an account, project, fleet, label or key, plus a cap on every prompt's AI spend.

Works locally

Everything a laptop has, and KVM

Ubuntu 24.04 on HareBox's own Linux 6.18 LTS kernel, passwordless sudo, systemd, Docker with BuildKit and Compose, and nested /dev/kvm for QEMU, Firecracker or an Android emulator.

Real VMs, locally

A firewall root can't remove

Rules are API objects kept outside the VM, so your tenant can be root inside and still can't change them.

Simulated
One lifecycle, one vocabulary

Five states. The same names everywhere.

The API, CLI, SDKs, dashboard, webhooks and logs use one set of state names. Billing runs per second from the moment a machine is assigned until a stop begins, sleep included. A stopped disk is free for 14 days, then moves to paid cold storage instead of being deleted.

billed per secondcreatingreadysleepingstoppedarchivedsleepwakeresumedisk free 14 dayscold storage
  1. creatingBeing prepared; billed from machine assignment
  2. readyBilled per second
  3. sleepingMemory kept; billed like running
  4. stoppedDisk kept, free 14 days
  5. archivedCold storage
Read the lifecycle guide
Pricing

1% below boat.dev, on every hour

The same four sizes as boat.dev, at 1% less per machine-hour, on every size and every tier. Plans, the trial and fees are the same as boat's, so each plan buys 1% more time. Egress is free.

HareBox hourly prices by size, with boat.dev's list price
SizeShapeHareBox, per hourboat.dev, per hourAlways on, per month
small2 vCPU · 4 GB · 51 GB$0.01782$0.018$13.01
default4 vCPU · 8 GB · 51 GB$0.03564$0.036$26.02
large8 vCPU · 16 GB · 111 GB$0.07128$0.072$52.03
xlarge16 vCPU · 32 GB · 251 GB$0.198$0.200$144.54

Dollars per hour, billed per second. boat.dev's list prices read on 2026-11-07. Plans, fees and a cost calculator.

Agent-native

Built so an agent can run it alone

Every error says what to do next. Output turns into JSON in a pipe. Prices and limits are live API facts, so nothing has to be remembered. An agent can even sign itself up and hand a human the claim link.

  • Python, TypeScript and Go SDKs, each tested against every API operation
  • llms.txt, an agent skill and an AGENTS.md template
  • Scoped keys limited by action, sandbox, label, rate, budget and IP
$ harebox new --json
{"event": "error",
 "code": "start_rate_limited",
 "message": "This account has used its 12 starts for this minute.",
 "fix": "Retry after 14 seconds, send placement: \"queue\" to wait in line, or move to a larger plan.",
 "retry_after_seconds": 14}
An error from the CLI. Every error has a code, a message and, when one exists, a fix.

Where things stand, honestly

HareBox is pre-release. Every feature on this site carries its status, and the comparison with boat.dev lists where boat is ahead.

Works locally Control plane, billing, budgets, the CLI and three SDKs. All 203 API operations answer, some through a labelled simulator.

Real VMs, locally Ubuntu 24.04 with Docker and nested KVM boots on HareBox's own kernel, with sleep, exact fork, stop and resume checked on a development machine.

Not yet Rented servers in France, uptime history, audits, and a fair benchmark against boat.dev.

Read the full comparisonSee the status page

Questions

What people ask first

Straight answers, from the FAQ in the docs.

Is this a live service?

No. It's a working local build and a specification.

Can I run real VMs?

With KVM and the Cloud Hypervisor adapter. Otherwise the labelled simulator runs, and every response says simulated: true.

Does sleep lose my programs?

No, that's the point. Open connections may break, and timers inside the VM don't fire.

Is a sleeping sandbox billed?

Yes, like a running one, and it still stops at its auto-stop. Stop it to end the bill.

How long is a stopped disk kept?

At least 14 days for free, then it moves to paid cold storage. It's never deleted because of idleness alone.

Is it cheaper than boat.dev?

On list price, by 1% on every size and tier; plans and fees are the same. On measured cost per unit of work, nobody knows yet: see Benchmarks.

What if I need the same thing as boat's `boat fork`?

harebox fork. See Migrating.

Give your agents a computer of their own.

Start from the quickstart, try the dashboard on the local build, or read how other teams use it.