Agent Sandboxesagentsandboxes.org
Sandbox profile · Open-source project

Cua

Answer in brief

Open-source computer-use infrastructure: Linux sandboxes as gVisor containers and macOS or Windows sandboxes as VMs, run locally, in your own cloud account or as shared "Spaces". The broadest open-source option for computer-use sandboxes across macOS, Linux and Windows, now firmly a self-run toolkit after the hosted cloud shut down.

By the Agent Sandboxes editors · Updated

Overview

Cua (trycua/cua on GitHub, about 32k stars) is an open-source toolkit for computer-use agents. Its cua SDK (Python, TypeScript, Rust) and CLI create sandboxes from published images: Ubuntu 24.04 runs as a gVisor container by default, while macOS 15/26, Windows Server 2022, Omarchy and Android images run as VMs through Lume (Apple's Virtualization.Framework on Apple silicon) or QEMU, with HVF, KVM or Hyper-V acceleration depending on the host. Sandboxes default to the local machine; the docs also describe running them in your own AWS, Google Cloud or Modal account. Cua Driver lets agents operate native apps and browsers on macOS, Windows and Linux via CLI, MCP or SDK, and Cua Bench creates and scores computer-use tasks.

Sandboxes persist until destroyed (or are ephemeral within a context block); suspend/resume checkpoints containers and snapshots QEMU VMs. Cua Spaces is a desktop app that turns computers you own into shared desktops for agents, with a relay for remote use; it is source-available under FSL-1.1-MIT (each release becomes MIT after two years) and is the paid tier ($18/month Pro, $30/seat Teams). Cua's hosted Cua Cloud and Fleets ended on 18 October 2026, and the older cua-computer, cua-agent and cuabot packages are no longer maintained; the migration guide points to local, own-cloud or Spaces targets instead.

Notable

  • Cua Cloud and Fleets ended on 18 October 2026; on="cloud" now raises a "Cua Cloud has ended" error (migration guide)
  • Repository has about 32.1k stars and 2.4k forks; core is MIT, Cua Spaces and Driver Bench are FSL-1.1-MIT, cua-som is AGPL-3.0
  • Spaces pricing: Free (2 computers, 20 remote hours/month), Pro $18/month, Teams $30/seat/month

Cua specifications

AttributeDetails
IsolationLinux images run as gVisor containers by default (runc optional); macOS and Windows images run as VMs via Lume (Apple Virtualization.Framework on Apple silicon) or QEMU
DeploymentOpen-source project · Self-hostable
Open sourceYes (MIT)
SDKs and interfacesPython, JavaScript/TypeScript, Rust, CLI, MCP server
Cold start (vendor claim)Not documented
Max session lengthPersistent sandboxes live until you destroy them; ephemeral sandboxes are deleted when the async with block exits. Spaces plans meter "remote hours" per month (20 Free, 200 Pro)
Persistencesuspend, resume and restart keep state: containers are paused or checkpointed, QEMU VMs are snapshotted, Lume VMs are stopped with their disk kept
GPUNot documented in the sandbox reference
Networkingnetwork="default" gives outbound access like a Docker container; network="none" removes egress but requires a local QEMU VM (unsupported for containers and Lume). Ports exposed via service(), public_url() (TTL 60 s to 24 h) and tunnels
PricingSDK, CLI, Driver and Lume are free (MIT). Cua Spaces: Free $0; Pro $18/month or $15/month billed yearly; Teams $30/seat/month or $25/seat/month billed yearly. Cua does not host compute; VMs in your AWS, Google Cloud or Modal account are billed by that provider
Free tierFree to self-host; Spaces Free plan includes 2 computers in use at once and 20 remote hours per month
ComplianceNot documented
RegionsNot documented

Facts from Cua’s public documentation, verified November 9, 2026. Performance numbers are vendor claims.

Strengths and trade-offs

Strengths

  • You want macOS, Linux and Windows computer-use sandboxes from one open-source SDK
  • You need macOS VMs on Apple silicon for agents that must drive native Mac apps
  • You run sandboxes on your own hardware or cloud account and want no vendor-hosted compute
  • You are building computer-use benchmarks or training data with Cua Bench

Trade-offs

  • No hosted compute: you provision and pay for machines yourself (Cua Cloud ended October 2026)
  • Licensing is mixed across the repository (MIT, FSL-1.1-MIT, AGPL components) and must be checked per directory
  • Egress-free networking is only supported for local QEMU VMs, not gVisor containers or Lume
  • No compliance attestations are documented

Good fit for: Teams that want open-source computer-use sandboxes on their own Macs, servers or cloud accounts, including macOS VMs on Apple silicon.

Use cases Cua fits

  • Computer use: Open-source computer-use sandboxes on your own Macs, servers or cloud accounts, including macOS VMs on Apple silicon.
  • Open source & self-hosted: Open-source computer-use sandboxes spanning macOS, Linux and Windows VMs.

How Cua compares

SandboxIsolationOpen sourceSelf-host / BYOCCold start (vendor)Max sessionSnapshots / pauseGPUSDKs
CuagVisor container or VMYesYes / NoNot documentedUntil destroyedYes / YesNot documentedPython, JavaScript/TypeScript, Rust, CLI, MCP server
ScrapybaraNot documentedNoNo / No<1 s (claimed)1 h default, configurableNo / YesNoPython, JavaScript/TypeScript, REST API, MCP server, CLI
OrgoIsolated VM (hypervisor not named)NoNo / NoSeconds (claimed)Unlimited (paid)Yes / YesYesPython, JavaScript/TypeScript, REST API, CLI, MCP server
Kasm WorkspacesDocker containerNoYes / NoNot documentedAdmin-definedNo / Not documentedYesREST API
MicrosandboxMicroVM (libkrun)YesYes / Yes<100 msNot documentedYes / Not documentedNoTypeScript, Python, Rust, Go, Ruby, CLI, MCP server
Docker SandboxesMicroVMNoYes / NoNot documentedUntil removed (local)Yes / YesYessbx CLI, TypeScript (cloud), REST API (cloud)
gVisorUser-space kernelYesYes / Noms (claim)Not documentedYes / Not documentedYesCLI

See all Cua alternatives →

Frequently asked questions

What is Cua?
Open-source computer-use infrastructure: Linux sandboxes as gVisor containers and macOS or Windows sandboxes as VMs, run locally, in your own cloud account or as shared "Spaces". The broadest open-source option for computer-use sandboxes across macOS, Linux and Windows, now firmly a self-run toolkit after the hosted cloud shut down.
How does Cua isolate code?
Cua documents its isolation as: Linux images run as gVisor containers by default (runc optional); macOS and Windows images run as VMs via Lume (Apple Virtualization.Framework on Apple silicon) or QEMU.
Is Cua open source?
Yes (MIT). It can be self-hosted.
How much does Cua cost?
SDK, CLI, Driver and Lume are free (MIT). Cua Spaces: Free $0; Pro $18/month or $15/month billed yearly; Teams $30/seat/month or $25/seat/month billed yearly. Cua does not host compute; VMs in your AWS, Google Cloud or Modal account are billed by that provider Check the official pricing page for current rates.
What are the alternatives to Cua?
Common alternatives include Scrapybara, Orgo, Kasm Workspaces, Microsandbox, Docker Sandboxes, gVisor. See Cua alternatives for a full comparison.

Sources

  1. cua.ai/
  2. cua.ai/pricing
  3. cua.ai/docs
  4. cua.ai/docs/cua-sdk/reference/python/sandbox
  5. cua.ai/docs/cua-sdk/guides/cua-cloud-ended
  6. github.com/trycua/cua

Cite this page

Agent Sandboxes. (2026). Cua. agentsandboxes.org. Last reviewed November 9, 2026. https://agentsandboxes.org/sandboxes/cua/

Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.