Cua Cloud/Fleets stopped October 16, 2026 and remaining customer data was deleted. Current Spaces uses your own machines; its Windows client is preview. Read the source ↗

Remote access tools / Cua Windows Fleet (ended) / Spaces alternative

Cua Fleet Windows alternative after hosted service closure

Cua Cloud and Fleets stopped on October 16, 2026, and the official notice reports deletion of remaining customer data. Current Cua Spaces shares computers you own or rent elsewhere; its Windows client is preview. That collaboration product is different from the former hosted Windows fleet.

Start buildingCompare capabilities ↓

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

When Cua Windows Fleet (ended) / Spaces fits

Use current Cua Spaces when sharing and controlling your own machines fits the workflow, with its Windows preview requirements. Underlying OS, storage and cloud-machine bills remain the responsibility of the selected machine/backend.

When to consider Sandbox0

Consider managed Sandbox0 for compatible Linux agents needing a durable whole writable RootFS, automatic online growth and supported paused files. Native Windows applications still need suitable Windows infrastructure; former Fleet access cannot recover deleted hosted data.

Capabilities

Cua Windows Fleet (ended) / Spaces and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeCua Windows Fleet (ended) / SpacesThe hosted Windows Fleet service ended on October 16, 2026. Current own-machine Spaces sessions have a separate backend and lifecycle.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 Windows Fleet (ended) / SpacesHosted Fleet customer data was deleted at closure; own-machine persistence is a separate backend contract.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSCua Windows Fleet (ended) / SpacesThe former hosted Windows fleet no longer provides a current whole-RootFS retention offer.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 Windows Fleet (ended) / SpacesFormer Cloud/Fleet lifecycle operations no longer reach a service; current lifecycle depends on the selected 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 Windows Fleet (ended) / SpacesCurrent Spaces sharing/relay subscriptions do not establish a general hosted RAM checkpoint contract.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 former hosted Fleet has ended. Current Spaces can share an existing computer, but its relay plan does not supply automatic low-space whole-RootFS expansion; that depends on the machine/backend.

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.

A connected desktop or relay is different from native file access while its guest compute stays paused. The current own-machine offering does not establish an arbitrary paused whole-OS file API.

See paused file operations →

The former hosted fleet has ended

The notice covers Cloud, pools, claims, warm replicas and the Terraform provider. Deprecated Cloud/Fleet operations no longer reach a hosted service. Locate copies or backups outside that service rather than planning an export from a still-running old Windows pool.

Source 1 ↗

Spaces provides access to your own computers

The current pricing page explicitly says Cua does not rent machines. Free/Pro/Teams pay for sharing and relay capabilities with session/hour allowances. The Windows download is preview, and features such as SSO/audit export have their own release status.

Source 1 ↗

Machine persistence belongs to the backend

A Windows desktop you own can preserve installed software and files, but that is the machine/storage provider’s lifecycle. A relay subscription does not establish a hosted RootFS growth, checkpoint or paused-files contract. Price the actual machine alongside the access service.

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 Windows Fleet (ended) / Spaces

Pricing reviewed 2026-10-19

Cua Cloud / Fleets
Service ended October 16, 2026
No current hosted Windows Fleet compute tariff.
Rate source ↗
Current Spaces Free — separate product
$0
Own machines; hosted relay allowance of 2 live sessions and 20 relay hours monthly.
Rate source ↗
Current Spaces Pro — separate product
$18/month
One person; up to 5 live sessions and 200 relay hours monthly; machine costs separate.
Rate source ↗
Current Spaces Teams — separate product
$30 per seat-month
Each seat adds 5 live sessions and 200 relay hours to the team pool; annual terms differ.
Rate source ↗

Spaces prices are access/relay subscriptions, not Windows VM rental rates. Confirm the Windows preview, current feature availability, relay scope and underlying machine charges. Do not use old hosted Fleet descriptions as current compute pricing.

Check current Cua Windows Fleet (ended) / Spaces 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 Windows Fleet (ended) / Spaces

  1. Locate surviving local copies/backups and native Windows dependencies; the provider reports remaining hosted Fleet data was deleted.
  2. Recreate required Windows stages on suitable infrastructure and move compatible Linux agent stages from available files to managed Sandbox0.
  3. Test returning system state, online growth, paused files and complete machine, relay and Linux runtime/storage costs.

Common questions

Is Sandbox0 a drop-in Cua Windows Fleet (ended) / Spaces 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/cua-sdk/guides/cua-cloud-ended ↗cua.ai/pricing ↗Sandbox0 RootFS capacity →

Related comparisons

Teclada vs Sandbox0 →Agency Tool Company vs Sandbox0 →Agent 37 vs Sandbox0 →Agent Relay vs Sandbox0 →AgentComputer vs Sandbox0 →ainclave vs Sandbox0 →