Run Cloud’s Linux microVM sandboxes are deprecated and unavailable to new organizations. Existing workloads run during a deprecation window; iOS simulators, Android emulators, and Xcode builds are unaffected. Read the source ↗

Agent sandboxes / Run Cloud alternative

A Run Cloud Linux sandbox alternative for existing workloads

Run Cloud’s Linux microVM sandbox capability is deprecated and unavailable to new organizations. Its iOS simulators, Android emulators, and Xcode builds remain separate products. This page helps existing Linux sandbox users assess a persistent agent runtime without implying Sandbox0 replaces mobile device simulation.

Start buildingCompare capabilities ↓

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

When Run Cloud fits

Keep Run Cloud in the evaluation when iOS simulators, Android emulators, or managed Xcode builds are central requirements. Existing Linux sandbox users should confirm their deprecation window and migration terms directly with the provider.

When to consider Sandbox0

Consider Sandbox0 when migrating Linux code execution to a long-lived per-user environment with durable whole-RootFS state, automatic online growth, and supported file operations while compute stays paused. Recreate any mobile-specific environment separately.

Capabilities

Run Cloud and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeRun CloudNot established in this reviewSandbox0ttl 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 filesRun CloudThe deprecated sandbox workflow saves filesystem snapshots for later restoration.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSRun CloudSnapshots capture the prepared sandbox filesystem, not merely a source-code export.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 stateRun CloudThe legacy API exposes paused/stopped state and resume; these deprecated capabilities require migration.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateRun CloudThe reviewed snapshot guide specifies filesystem capture without an explicit live-memory restoration guarantee.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.

Run Cloud’s deprecated Linux documentation describes reserved resources and reusable filesystem snapshots. It does not establish automatic online expansion of a durable writable RootFS; migration should validate disk growth as a separate requirement.

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 →

The deprecation applies to Linux sandboxes, not the company

Run Cloud’s current documentation directs users to migrate from the sandbox CLI and SDK surfaces before removal. It states that existing workloads continue during the deprecation window, while mobile simulators and Xcode builds are unaffected. No universal removal date is established in the reviewed notice.

Source 1 ↗

Filesystem snapshots seed new sandbox identities

The deprecated snapshot workflow captures the prepared filesystem and restores a new sandbox with its own ID. The documented CPU reservation is a billing floor with additional consumed CPU billed as burst; RAM remains a hard reservation. Preserve those resource assumptions when measuring a replacement workload.

Source 1 ↗Source 2 ↗

Current simulator prices are not legacy Linux rates

The current public price page quotes active-minute simulator billing and beta Xcode builds. It does not provide a current numeric Linux sandbox rate card. Existing customers should retrieve their effective Linux CPU, memory, and retained-artifact terms; applying the mobile minute rate would price the wrong product.

Source 1 ↗Source 2 ↗

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.

Run Cloud

Pricing reviewed 2026-10-18

Deprecated Linux sandbox rates
Confirm existing-account terms
The current public pricing page does not establish numeric Linux sandbox resource rates.
Rate source ↗
Separate current iOS / Android simulator products
$0.02 per active session-minute
Shown only to distinguish current product scope; this is not a Linux sandbox rate.
Rate source ↗
Separate current Xcode build product
$0 during beta
Rate source ↗

Do not reuse old directory Linux prices as a current offer. Legacy docs describe reserved CPU plus burst consumption and reserved memory, while paused/stopped resources still occupy organization capacity until destroyed. Check exports and snapshot availability before the deprecation window closes.

Check current Run Cloud 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

A 4 GiB agent, 100 running hours

$6.00 compute

4 GiB × 100 hours, billed by the second. Keeping 20 GiB of billable incremental data for a full billing month adds $0.40. CPU is derived from memory by the platform; choose a tier that fits your workload.

Understand storage billing →

Before migrating from Run Cloud

  1. Confirm the Linux retirement timetable for the account and export required files, snapshot IDs, images, and active workload configuration.
  2. Port Linux commands, credentials, service ingress, SDK calls, and reconnect behavior; keep mobile simulator and Xcode workflows on a compatible service.
  3. Validate a representative agent workload, including CPU bursts, retained packages, multi-task RootFS growth, paused file access, and the target runtime bill.

Common questions

Is Sandbox0 a drop-in Run Cloud 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 ↗docs.run.cloud/sandboxes/index.md ↗docs.run.cloud/sandboxes/snapshots.md ↗run.cloud/pricing/ ↗docs.run.cloud/sandboxes/run-sandbox.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 →