The published computeruse-sdk README marks the package a preview: hosted access is private preview/waitlist and Sandbox methods raise PreviewError. Planned runtime capabilities are not treated as available production features. Read the source ↗

Computer-use platforms / Computer Use Cloud (computeruse.run) alternative

Computeruse.run alternative

Computer Use Cloud at computeruse.run publishes a preview SDK for a managed browser and desktop on one Linux machine. Its current README explicitly says the hosted API is not live for the preview package and every method raises PreviewError. Evaluate that published status before treating the SDK shape as a working runtime.

Start buildingCompare capabilities ↓

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

When Computer Use Cloud (computeruse.run) fits

The preview fits developers inspecting or prototyping against the planned browser/desktop interface while arranging access with the vendor. It is not evidence of a generally available production API or an established disk-persistence contract.

When to consider Sandbox0

Consider Sandbox0 when you need a running agent environment with durable installed tools, system configuration and files, online RootFS growth and supported paused-file operations. Build or integrate a compatible browser/desktop agent loop explicitly; do not assume API equivalence with a preview SDK.

Capabilities

Computer Use Cloud (computeruse.run) and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeComputer Use Cloud (computeruse.run)Not 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 filesComputer Use Cloud (computeruse.run)The published preview does not verify a running hosted durable-disk contract.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSComputer Use Cloud (computeruse.run)A planned shared Linux machine is not proof of full RootFS persistence.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 stateComputer Use Cloud (computeruse.run)Preview methods raise PreviewError; a production machine pause/restore contract is not established.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateComputer Use Cloud (computeruse.run)The planned runtime milestone does not establish shipped arbitrary process-memory checkpoint/restore.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.

The preview describes one Linux machine for browser and desktop work, but does not establish whole-RootFS durability or automatic online growth. Sandbox0 retains the complete writable RootFS, including installed system tools and growing files, under its separate lifecycle contract.

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.

The preview does not establish supported file access while hosted compute is paused. A future browser-download/desktop-file example is different from a verified paused Files API.

See paused file operations →

Published SDK shape is not a running hosted API

The repository describes the package as a preview intended for reading, type checking and preparing code. Sandbox methods raise PreviewError rather than starting compute. The organization page calls hosted access private preview/waitlist and places the runtime release on a future milestone. Neither package publication nor a roadmap establishes current service availability.

Source 1 ↗Source 2 ↗Source 3 ↗

Two interfaces describe a planned shared computer

The SDK presents browser and computer surfaces on the same Linux machine, with examples of a browser download becoming available to desktop actions. That is the documented intended design. The preview cannot verify those examples as functioning end-to-end behavior, and it does not establish complete RootFS retention or process-memory restore.

Source 1 ↗

Model choice is a separate dependency

The preview documents choosing a model and bringing the relevant provider key. Model access, browser/desktop control and durable runtime state are different responsibilities. Confirm actual hosted access, credential handling and billing before planning a deployment rather than assuming a free SDK includes model inference or free compute.

Source 1 ↗

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.

Computer Use Cloud (computeruse.run)

Pricing reviewed 2026-10-18

Preview SDK software
Apache-2.0 preview package
This is a software license, not an included hosted-compute allocation.
Rate source ↗
Hosted production usage
Production access and commercial quote required
The published SDK says its hosted API is not live; arrange actual access and terms with the vendor.
Rate source ↗

The published SDK is preview-only; planned rates are not a production service quote. Model-provider costs and any future hosted resource charges are separate. Confirm production availability and commercial scope before estimating a total.

Check current Computer Use Cloud (computeruse.run) 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 Computer Use Cloud (computeruse.run)

  1. Identify preview-only SDK calls and separate working local prototypes from code that currently raises PreviewError; save required code and artifacts.
  2. Port compatible agent logic to a Sandbox0 template and integrate a supported browser/desktop and model interface explicitly.
  3. Test real tool execution, whole-RootFS retention/growth, paused files, lifecycle recovery and the complete model plus runtime budget.

Common questions

Is Sandbox0 a drop-in Computer Use Cloud (computeruse.run) replacement?

Evaluate API compatibility and product scope. These products serve different core workflows, so a change may require a different architecture.

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 ↗github.com/computeruse-run/sdk ↗github.com/computeruse-run ↗github.com/computeruse-run/runtime ↗Sandbox0 RootFS capacity →

Related comparisons

Bytebot vs Sandbox0 →CloudAxis vs Sandbox0 →Coasty vs Sandbox0 →ComputerUse.space vs Sandbox0 →Cyberdesk Windows Automation vs Sandbox0 →Google Agent Platform Sandbox (Code Execution / Shell / Computer Use) vs Sandbox0 →