Agent sandboxes / Hyperbrowser alternative

A Hyperbrowser alternative for a durable agent computer that grows online

Hyperbrowser now offers Linux sandboxes as well as managed browsers, agents and web APIs. Its sandbox snapshots capture memory, processes and filesystem state, and separate volumes survive stopped compute. Compare these actual sandbox capabilities instead of treating the product as browser-only or assuming it cannot retain a machine snapshot.

Start buildingCompare capabilities ↓

Reviewed 2026-10-18 · Published by the Sandbox0 team

When Hyperbrowser fits

Choose Hyperbrowser when its integrated browser/agent/web stack, Linux VMs, restorable execution snapshots or shared volumes match the workload. Its macOS persistent-disk beta is another distinct runtime with separate availability and lifecycle behavior.

When to consider Sandbox0

Consider Sandbox0 when a returning Linux sandbox should retain its complete writable RootFS, grow automatically online and expose supported files while compute remains paused. Validate gVisor compatibility, process-checkpoint requirements and browser-service dependencies before migration.

Capabilities

Hyperbrowser and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeHyperbrowsertimeoutMinutes measures total VM lifetime from start, configurable at creation; the reviewed guide does not establish an unbounded default.View evidence ↗Sandbox0ttl and hard_ttl default to 0 (disabled). Configure idle pause and deletion policies for the same persistent sandbox identity; an idle running sandbox still accrues compute charges.Read documentation →
Persistent filesHyperbrowserVolumes outlive all attached sandboxes; Linux snapshots separately capture the filesystem at a selected point.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSHyperbrowserLinux memory snapshots explicitly include the filesystem and execution state; this does not promise ordinary-stop retention of unpublished local writes.View evidence ↗Sandbox0Persistence extends beyond /workspace to paths such as /usr/local, /etc, and /home. Runtime tmpfs and virtual filesystems are excluded.Read documentation →
Release compute, keep stateHyperbrowserSnapshot restore starts a new sandbox; the reviewed lifecycle does not establish an in-place same-identity compute pause contract.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateHyperbrowserLinux snapshots capture memory and processes and can start new sandboxes from saved state.View evidence ↗Sandbox0Experimental memory checkpoints can preserve compatible process state. Use memory: true on both pause and resume on a compatible deployment. A filesystem checkpoint alone does not preserve running processes.Read documentation →

Online RootFS growth

On growth-enabled images, Sandbox0 automatically expands the writable RootFS as free space runs low, within a configured sparse logical ceiling up to 64 TiB. Agent processes keep running. Growth is enabled in the qualified Cloud region; confirm activation for other regions. Existing images and snapshots retain their captured storage geometry. The ceiling is logical capacity, not preallocated host disk.

Hyperbrowser supports configured image-launch disk sizes, persistent volume mounts and whole-filesystem memory snapshots. Those capabilities do not by themselves establish automatic online growth of the durable complete RootFS while processes continue; verify that requirement separately.

Files while compute is paused

Sandbox0's Files API reads persistent files without resuming compute. Filesystem-only pauses also permit edits; retained-memory pauses are read-only and reject mutations with 409. SSH, SFTP, file watching, and runtime-only mounts require running compute.

See paused file operations →

Memory snapshots capture more than a workspace directory

Hyperbrowser’s Linux memory snapshots explicitly capture memory, processes and filesystem, and can start multiple new sandboxes from one saved state. A snapshot-based launch uses saved resource sizing. Installed environments and captured processes can therefore be reused; browser-profile persistence belongs to a separate product surface.

Source 1 ↗Source 2 ↗

Volumes and instance-local disk have separate lifecycles

Team-scoped volumes survive all attached sandboxes stopping and can be mounted into multiple sandboxes. Image launches separately configure disk size, CPU and memory; defaults are two vCPUs, 2 GiB RAM and 8 GiB disk. The reviewed guides do not establish automatic online expansion of the complete RootFS or ordinary-stop retention of all uncheckpointed local changes.

Source 1 ↗Source 2 ↗Source 3 ↗

The browser meter is not the Linux sandbox meter

Browser time is $0.10/hour, while running sandboxes charge both vCPU and allocated memory. Plans provide shared credits across sandboxes, browsers, web APIs and agents. A browser profile persists user-data-directory state; it is separate from Linux memory snapshots and persistent volumes.

Source 1 ↗Source 2 ↗Source 3 ↗

Pricing

Compare billing models, then price your workload

CPU allocation, memory, billing minimums, disk, plan fees, and supported workload differ. These meters are not equal-performance machine quotes. Confirm region, resource units, and included allowances before estimating a total.

Same size. Lower compute cost.

2 vCPU · 4 GiB RAM · 730 running hours / month

Save $65.70 / month

The same CPU and memory allocation, with runtime aggregated across sessions. Monthly allowances and credits below are applied to this workload.

Hyperbrowser

Startup · $30/month with $30 usage credits

$109.50

$0.15/hour before monthly allowances

Sandbox0

Pay as you go · no monthly plan fee

$43.80

$0.06/hour · 60% lower in this example

Applies Startup’s 30,000 monthly credits at 1,000 credits per dollar, including the $30 plan fee once. Browser sessions, proxies, agent steps and retained storage are separate from sandbox CPU and RAM.

Compute and stated plan fees only. Storage, network, taxes and one-time credits are excluded; hardware and throughput can differ.

Calculation and billing assumptions

Hyperbrowser: $109.50 compute after 0 included vCPU-hours and 0 included GiB-hours, plus $30.00 plan fee, minus $30.00 applied monthly credit.

Sandbox0: 4 GiB × 730 hours × its published compute rate. CPU uses the Cloud allocation shown on the pricing page.

Includes compute and the selected plan. Excludes storage, network, taxes, one-time grants and negotiated discounts. Assumes this workload can use the full listed monthly allowances. CPU and memory counts do not guarantee equal hardware or throughput.

Checked Hyperbrowser rate source 1 ↗Hyperbrowser rate source 2 ↗Sandbox0 rates ↗

Hyperbrowser

Pricing reviewed 2026-10-18

Free
$0 to start with 5,000 credits
One concurrent session; a starting grant is not unlimited recurring usage.
Rate source ↗
Startup
$30/month with 30,000 credits
25 concurrent sessions; shared across all four product families.
Rate source ↗
Scale
$100/month with 100,000 credits
100 concurrent sessions.
Rate source ↗
Running sandbox vCPU
$0.045/vCPU-hour
Rate source ↗
Running sandbox allocated memory
$0.015/GiB-hour
Add to vCPU charges; GiB is 1024 MiB.
Rate source ↗
Managed browser time
$0.10/hour
Rate source ↗
Managed proxy
$10/GB
Rate source ↗
HyperAgent / Browser Use agent
$0.02/step plus browser usage
Rate source ↗
Enterprise
Custom terms
Rate source ↗

1,000 credits equals $1. Plan credits reset without rollover; separately purchased credits expire after 12 months. Do not treat a browser hour as a VM-hour or plan fee as additional to all included credits already spent. Confirm snapshot/volume storage fees, retained-state terms and macOS availability separately; the reviewed rate table does not establish a complete parked-storage invoice.

Check current Hyperbrowser pricing ↗

Sandbox0

$0.015/GiB-hour compute (billed by the second at approximately $0.000004167/GiB-second), plus $0.02/GiB-month of retained incremental RootFS and memory checkpoint data. Shared base images and platform recovery retention are excluded; paused sandboxes accrue storage charges only.

Compute / GiB-hour
$0.015
Retained data / GiB-month
$0.02
Paused compute
$0.00
Understand storage billing →

Before migrating from Hyperbrowser

  1. Inventory Linux image versus snapshot launches, resource baselines, mounted volumes, browser profiles, network policy, runtime URLs and any macOS-only requirements.
  2. Port compatible Linux tools and agent APIs to Sandbox0, retaining managed browser and web/agent services separately where needed.
  3. Test process and filesystem checkpoint coverage, growing outputs, paused file access, timeout behavior and combined CPU/RAM/storage/browser/model charges.

Common questions

Is Sandbox0 a drop-in Hyperbrowser replacement?

Evaluate API compatibility and product scope. A shared sandbox category does not make SDKs, lifecycle semantics, or limits interchangeable.

Does keeping files also keep a running agent?

Filesystem state and volatile process state are separate. Sandbox0 requires explicit compatible memory checkpoints to preserve running processes; its default filesystem resume starts fresh processes.

Sources and review scope

The Boat team's Battleships directory is the discovery source. References below describe the product and plan discussed on this page. Check current availability, regional terms and billing units before migrating. Where the cited material does not establish a capability or price, the comparison identifies that uncertainty.

Battleships research record ↗hyperbrowser.ai/docs/sandboxes/snapshots.md ↗hyperbrowser.ai/docs/sandboxes/create.md ↗hyperbrowser.ai/docs/sandboxes/volumes.md ↗hyperbrowser.ai/docs/sandboxes/lifecycle.md ↗www.hyperbrowser.ai/pricing ↗hyperbrowser.ai/docs/pricing.md ↗hyperbrowser.ai/docs/sessions/profiles.md ↗Sandbox0 RootFS capacity →

Related comparisons

Agent 37 vs Sandbox0 →AgentComputer vs Sandbox0 →ainclave vs Sandbox0 →Alibaba Cloud Agent Sandbox / FC / AgentRun vs Sandbox0 →Alibaba Cloud AgentBay vs Sandbox0 →Amika vs Sandbox0 →