The former cloudrouter.dev rate-card URL now leads to Manaflow’s corporate site. The discovery directory marks cloudrouter discontinued, but the cited materials do not establish a separate vendor shutdown announcement or current hosted terms. Confirm access before relying on an existing account. Read the source ↗

Development environments / cloudrouter (Manaflow) alternative

Cloudrouter alternative for your agent runtime

Cloudrouter’s public repository describes a CLI-and-skill workflow for remote development sandboxes, file sync, terminals, desktops, and browser automation. Its former pricing URL currently redirects to Manaflow’s corporate homepage. Treat the public integration code and the availability of a hosted service as separate facts.

Start buildingCompare capabilities ↓

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

When cloudrouter (Manaflow) fits

The public cloudrouter integration may be useful to an existing deployment that needs its directory upload/watch workflow, browser CDP actions, VNC, or browser editor. Verify that the backing account/service is usable before planning new hosted adoption.

When to consider Sandbox0

Consider Sandbox0 when building the underlying hosted agent environment around a durable writable RootFS, online growth, and supported file access during compute pauses. Recreate or retain browser automation, editor, desktop, and sync behavior separately where needed.

Capabilities

cloudrouter (Manaflow) and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimecloudrouter (Manaflow)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 filescloudrouter (Manaflow)Upload/download and lifecycle commands are documented; current hosted durable-retention terms are not established.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFScloudrouter (Manaflow)Directory synchronization does not establish complete writable 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 statecloudrouter (Manaflow)The client documents stop and extend, but that does not establish current hosted restoration semantics.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process statecloudrouter (Manaflow)The browser computer snapshot is an accessibility observation, not evidence of execution-memory capture.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 public sync and CLI workflow does not establish automatic online expansion of a durable complete RootFS. Compare the actual backing runtime and its retained-data policy before attempting a migration.

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 →

A public client does not prove a current hosted service

The cloudrouter repository remains readable and documents remote sandbox commands. Its former public rate-card route now leads to Manaflow’s corporate page about other projects. The discovery directory marks the service discontinued; the cited materials do not establish a separate vendor shutdown announcement. Confirm current access and retention terms before relying on old signup or billing examples.

Source 1 ↗Source 2 ↗Source 3 ↗

A browser snapshot is not a machine checkpoint

The repository’s computer snapshot command retrieves a browser accessibility tree for subsequent actions. That observation is different from a saved filesystem or a RAM/process checkpoint. Likewise, uploading a directory with watch support synchronizes selected files; it does not establish whole-RootFS retention or cross-node machine recovery.

Source 1 ↗

Historical wrapper and backend bills must not be blended

A client wrapper can involve its own subscription and the backing runtime’s resource charges. The current public pricing URL does not verify numeric cloudrouter fees, included compute, or retention. Use an existing account’s effective terms when available; no current free-tier or savings figure can be inferred from source-code availability.

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.

cloudrouter (Manaflow)

Pricing reviewed 2026-10-18

Current hosted cloudrouter fees
Current hosted rate not established
Rate source ↗
Public integration repository
MIT-labelled client/skill; not a hosted compute allowance
Rate source ↗
Backing compute and retained data
Confirm the effective service/account terms
Rate source ↗

The directory’s discontinued marker is discovery evidence, not an independently verified shutdown announcement. Public CLI source does not establish that new managed accounts or old prices are available. Exclude unverified historical subscription and backend rate figures from a current cost estimate.

Check current cloudrouter (Manaflow) 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 cloudrouter (Manaflow)

  1. Verify access to the source service and export essential files, synced directories, credentials, browser state, and any account-held artifacts while available.
  2. Package required tools in a Sandbox0 template and replace runtime lifecycle/command/file calls; implement needed sync, editor, browser, or desktop interfaces separately.
  3. Validate repeated system changes, growing outputs, paused file access, required process behavior, and the complete effective runtime and application cost.

Common questions

Is Sandbox0 a drop-in cloudrouter (Manaflow) 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/manaflow-ai/cloudrouter ↗cloudrouter.dev/pricing ↗manaflow.com/ ↗Sandbox0 RootFS capacity →

Related comparisons

Agency Tool Company vs Sandbox0 →Amp Orbs vs Sandbox0 →Bitrise RDE vs Sandbox0 →boxes.dev vs Sandbox0 →Capy vs Sandbox0 →Claw 2 Agent vs Sandbox0 →