Riza announced hosted Code Interpreter API and dashboard shutdown for October 1, 2025. Hosted prices below are historical; existing offline-licensed self-hosted containers have a separate status. Read the source ↗

Agent sandboxes / Riza Code Interpreter alternative

A Riza Code Interpreter alternative for a persistent agent runtime

Riza announced that its hosted Code Interpreter API and dashboard would shut down on October 1, 2025. The comparison is a migration guide for interpreter workloads and existing self-hosted deployments, rather than a new hosted-service purchasing decision.

Start buildingCompare capabilities ↓

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

When Riza Code Interpreter fits

An existing Riza self-hosted deployment may still fit a narrow interpreter workflow with an offline license. The vendor’s shutdown notice says those containers continue with existing keys; confirm the license and support arrangement for the deployment you own.

When to consider Sandbox0

Sandbox0 fits the broader case where generated code must install Linux tools, build repositories, retain system changes, and return to one durable RootFS. This requires adapting a request/response interpreter integration to a sandbox lifecycle.

Capabilities

Riza Code Interpreter and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeRiza Code InterpreterHistorical hosted plans were bounded interpreter invocations: 30 seconds on Hobby and up to 15 minutes on Pro.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 filesRiza Code InterpreterNot established in this reviewSandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSRiza Code InterpreterThe reviewed interpreter exposes request-scoped writable /mnt/req, with the rest of its filesystem read-only.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 stateRiza Code InterpreterNot established in this reviewSandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateRiza Code InterpreterNot established in this reviewSandbox0Experimental 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.

Riza’s request-scoped writable directory is different from an accumulating Linux RootFS. For agents that install system tools or retain build environments, inventory those new requirements before choosing the Sandbox0 template and storage policy.

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 hosted API retirement changes the decision

The official shutdown notice disabled new signups and set October 1, 2025 as the hosted API and dashboard end date. Existing offline-licensed containers are treated separately. Do not use the old Pro checkout as evidence that a new hosted deployment is available.

Source 1 ↗

A code invocation and an agent computer have different scope

Riza’s published interpreter limits describe WebAssembly execution, request-provided files, HTTP networking, and a restricted writable /mnt/req directory. Sandbox0 provides a persistent Linux environment, so port runtime dependencies, file paths, and process management deliberately.

Source 1 ↗Source 2 ↗

Use historical rates only to understand the source workload

Riza’s remaining public price page lists request-bundled plans and per-invocation limits. Those numbers describe the retired hosted offer, not a current quote. Estimate the replacement from actual running time, memory needs, and retained data instead of translating request counts directly into machine-hours.

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.

Riza Code Interpreter

Pricing reviewed 2026-10-18

Historical Hobby plan
$0/month
Retired hosted offer: up to 100,000 requests monthly with a 30-second execution limit.
Rate source ↗
Historical Pro plan
$250/month
Retired hosted offer: 1,000,000 included monthly requests and execution up to 15 minutes.
Rate source ↗
Current self-hosted deployment
Confirm existing license and operating costs
The shutdown notice preserves existing offline-license operation; it does not publish a new hosting quote.
Rate source ↗

All hosted plan figures are historical. Riza announced hosted shutdown for October 1, 2025. Operating an existing licensed container has infrastructure and maintenance costs that the old request plan does not cover.

Check current Riza Code Interpreter 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 Riza Code Interpreter

  1. Identify whether the source is the retired hosted API or an existing licensed container; export request files and custom runtime dependencies.
  2. Replace interpreter HTTP calls with Sandbox0 command execution, output collection, file transfer, and explicit timeout handling.
  3. Test isolation assumptions, repeated-task state, installed packages, RootFS growth, and cleanup so request-scoped code does not accidentally share another user’s environment.

Common questions

Is Sandbox0 a drop-in Riza Code Interpreter 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 ↗riza.io/blog/shutting-down-hosted-code-interpreter ↗riza.io/pricing ↗/docs/sandbox ↗/pricing ↗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 →