# Cua Spaces

Shared desktops and programmable sandboxes on your own computers or cloud accounts.

Use Cua directly through its app, SDK or CLI. Sandbox Router does not currently route sandboxes to Cua Spaces.

## From Cua Fleet to Cua Spaces

Cua ended its hosted Cloud/Fleets service on 18 October 2026. Spaces is its current offering for computers you supply. Existing links to Cua Fleet in this catalog now lead here. [Cua Cloud/Fleets migration notice](https://cua.ai/docs/cua-sdk/guides/cua-cloud-ended).

## Capabilities

- **Where it runs:** Your computer, other computers you connect, or your own AWS, Google Cloud, Hetzner or Modal account. You pay the cloud provider for that compute. [Cua runtimes and compute locations](https://cua.ai/docs/cua-sdk/guides/local-runtimes).
- **Desktop and code:** The SDK exposes screenshots, mouse and keyboard input, a clipboard, shell commands, files and PTY terminals. Spaces can be shared with people and agents. [Sandbox SDK interfaces](https://cua.ai/docs/cua-sdk/reference/python/sandbox).
- **Operating systems and isolation:** Containers and VMs use host-dependent runtimes such as gVisor, QEMU and Lume. macOS VMs require Apple silicon; Linux and Windows VM support depends on the host and image. [Cua runtimes and compute locations](https://cua.ai/docs/cua-sdk/guides/local-runtimes).
- **Warm pools and lifecycle:** The local daemon can keep sandboxes ready, with minimum and maximum ready capacity and idle expiry. Suspend, resume and restart are local operations; cloud sandboxes have cleanup time limits. [Lifecycle and local warm pools](https://cua.ai/docs/cua-sdk/guides/lifecycle).
- **Connecting and sharing:** Connect directly on your network or through Cua's hosted relay. Sharing supports viewers and editors; Teams adds shared computers, roles and device approval. [How Cua Spaces works](https://cua.ai/docs/spaces/concepts/how-spaces-works).
- **Resource limits:** CPU, memory, disk and capacity depend on your machines, cloud provider and runtime. There is no single Cua-hosted sandbox size or hourly compute rate to compare here. [Cua runtimes and compute locations](https://cua.ai/docs/cua-sdk/guides/local-runtimes).
- **Licensing:** Spaces is source-available under FSL-1.1-MIT, with each release converting to MIT after two years. Cua Driver and Lume use MIT licenses. [Cua Spaces pricing and licensing](https://cua.ai/pricing).

## Cua service plans

USD. Checked 10 Nov 2026.

| Plan | Monthly billing | Annual billing | Includes |
| --- | --- | --- | --- |
| Free | $0 | $0 | 2 remote computers at once; 20 remote hours/month. |
| Pro | $18/month | $180/year | 5 remote computers at once; 200 remote hours/month. |
| Teams | $30/seat/month | $300/seat/year | 5 remote computers and 200 remote hours per seat/month, pooled across the team. |

These plans cover Cua's software, sharing and relay. Compute bills are separate. Local and direct connections do not consume relay allowances. Annual prices are charged yearly. [Cua Spaces pricing and licensing](https://cua.ai/pricing).

## Sources

- [How Cua Spaces works](https://cua.ai/docs/spaces/concepts/how-spaces-works)
- [Cua runtimes and compute locations](https://cua.ai/docs/cua-sdk/guides/local-runtimes)
- [Sandbox SDK interfaces](https://cua.ai/docs/cua-sdk/reference/python/sandbox)
- [Lifecycle and local warm pools](https://cua.ai/docs/cua-sdk/guides/lifecycle)
- [Cua Spaces pricing and licensing](https://cua.ai/pricing)
- [Cua Cloud/Fleets migration notice](https://cua.ai/docs/cua-sdk/guides/cua-cloud-ended)