Cua Cloud and Fleets stopped on October 16, 2026. The vendor says remaining customer data was deleted. Current Cua Spaces uses your own computers and is a separate offering. Read the source ↗

Development environments / Cua Fleet alternative

A Cua.ai alternative after the hosted Fleets service ended

Cua’s official notice says Cloud and Fleets stopped on October 16, 2026 and remaining customer data was deleted. Cua’s current Spaces offering shares computers you own or rent separately. A migration decision must distinguish that collaboration product from the former hosted sandbox fleet.

Start buildingCompare capabilities ↓

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

When Cua Fleet fits

Current Cua software fits teams that want shared desktops on their own machines or cloud accounts, computer-use tooling, and its local runtime ecosystem. Spaces does not rent the machines; host capacity, storage, and cloud billing remain separate.

When to consider Sandbox0

Consider Sandbox0 for hosted Linux agent compute with a durable writable RootFS, online growth, and supported persistent-file access while compute stays paused. It does not replace Cua Spaces collaboration, desktop sharing, or native Windows/macOS requirements as a drop-in feature set.

Capabilities

Cua Fleet and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeCua FleetThe hosted Fleets service has ended; former claim lifetime settings are no longer a usable service contract.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 filesCua FleetThe notice reports deletion of remaining Cloud/Fleets customer data; current own-machine storage is a different product boundary.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSCua FleetNo current hosted Fleets RootFS-retention offer remains established by the vendor notice.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 stateCua FleetFormer hosted pool/claim APIs no longer reach a service. Current local or own-cloud lifecycle depends on the backend.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateCua FleetOld Fleet descriptions cannot establish a currently available hosted process-memory checkpoint service.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 ended hosted Fleet service is not a current automatic-growth option. On present Cua Spaces deployments, root storage and its growth policy belong to the connected machine or external cloud provider. Sandbox0 supplies its own persistent RootFS growth on enabled templates.

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 shutdown notice supersedes old Fleets guides

Cua explicitly ended the managed pools, claims, warm replicas, and Terraform service and removed the old Fleet pages. Its notice says former cloud targets no longer reach a service and are being removed from the SDK. Old claim TTLs and warm-pool settings are not a current hosted offer. The notice reports deletion of remaining customer data, so do not promise that a new backend can recover it.

Source 1 ↗

Spaces subscriptions buy collaboration, not VM capacity

Cua Spaces connects machines the team owns or rents and supplies sharing and relay access. Local, direct-network, and hosted-relay use have different accounting. Existing SDK and image workflows can instead target local or user-owned cloud execution, but those destinations have their own lifecycle and costs rather than being a replacement Fleet pool.

Source 1 ↗Source 2 ↗

Keep current Spaces prices separate from historical Fleet compute

The current public rate card prices Free, Pro, and Teams Spaces plans in live sessions and relay hours. It explicitly leaves machine bills with the owner. Do not apply those fees to hosted Fleet vCPUs, RAM, or storage, and do not include roadmap audit or SSO features as shipped entitlements.

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.

Cua Fleet

Pricing reviewed 2026-10-18

Cua Cloud / Fleets
Service ended October 16, 2026
No current hosted Fleet compute quote is offered by this notice.
Rate source ↗
Current Spaces Free — different product
$0
Bring your own machines; hosted relay allowance is 2 live sessions and 20 relay hours per calendar month.
Rate source ↗
Current Spaces Pro — different product
$18 per month
One person, up to 5 live sessions and 200 relay hours monthly. Machines are billed separately.
Rate source ↗
Current Spaces Teams — different product
$30 per seat per month
Each seat adds 5 live sessions and 200 relay hours to the team pool; machine/provider bills remain separate.
Rate source ↗

Spaces subscriptions are not hosted sandbox compute rates. Annual commitments use different prices. The current page marks expiring share links and audit history as coming soon, and SSO/audit export as later work. Verify those release states before counting them in a comparison.

Check current Cua Fleet 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 Cua Fleet

  1. Remove dependencies on ended Fleet endpoints and inventories; use independent exports or backups already held, because the vendor notice says remaining hosted data was deleted.
  2. Rebuild compatible Linux tools and agent integrations on Sandbox0, while retaining an appropriate platform for required desktop-sharing or native-OS behavior.
  3. Validate repeated system state, online RootFS growth, paused file access, lifecycle policy, and the full compute plus collaboration cost.

Common questions

Is Sandbox0 a drop-in Cua Fleet 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 ↗cua.ai/docs/fleets.md ↗cua.ai/pricing ↗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 →