Cua vs Kasm Workspaces
Choose Cua for teams that want open-source computer-use sandboxes on their own Macs, servers or cloud accounts, including macOS VMs on Apple silicon; choose Kasm Workspaces for organisations that already run browser-streamed desktops and want to give agents the same isolated, policy-controlled containers. Cua uses gVisor container or VM isolation and is open source; Kasm Workspaces uses Docker container isolation.
Key differences between Cua and Kasm Workspaces
- Type: Cua is an open-source project you run yourself; Kasm Workspaces is a hosted platform.
- Isolation: Cua uses gVisor container or VM; Kasm Workspaces uses Docker container.
- Open source: Cua is open source (MIT); Kasm Workspaces is not.
- Session length: Until destroyed (Cua) versus Admin-defined (Kasm Workspaces).
- SDKs and interfaces: Only Cua lists Python, JavaScript/TypeScript, Rust, CLI and MCP server. Only Kasm Workspaces lists REST API.
What they have in common
- Both companies are based in the United States.
- Both can be self-hosted.
Cua vs Kasm Workspaces at a glance
| Attribute | Cua | Kasm Workspaces |
|---|---|---|
| What it is | 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". | Container-streamed Linux desktops and browsers, self-hosted or as Kasm SaaS, with a Developer API and a free Community Edition that Kasm also markets for agentic AI. |
| Type | Open-source project | Hosted platform |
| Isolation | 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 | Docker container per session, streamed to the browser with KasmVNC; sessions can also be RDP-gatewayed to Windows hosts |
| Open source | Yes (MIT) | No |
| Self-host / BYOC | Yes / Yes | Yes / Not documented |
| SDKs | Python, JavaScript/TypeScript, Rust, CLI, MCP server | REST API |
| Cold start (vendor claim) | Not documented | Not documented |
| Max session | Persistent 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) | Session expiry is governed by per-user usage limits; the keepalive API resets a session's expiration time |
| Persistence | suspend, resume and restart keep state: containers are paused or checkpointed, QEMU VMs are snapshotted, Lume VMs are stopped with their disk kept | Sessions are ephemeral containers; persistent profiles can be enabled per image so user data survives across sessions. Session recording available on paid tiers |
| Snapshots / pause | Yes / Yes | Not documented / Not documented |
| GPU | Not documented in the sandbox reference | GPU resources can be shared across users and workloads; release 1.19 adds SR-IOV bifurcation of Intel Arc Pro cards (press release) |
| Networking | network="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 | Administrators control inbound and outbound access per workspace; web filtering; optional PureVPN managed egress on Essentials and Premier |
| Pricing | 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 | Community Edition free (up to 5 concurrent sessions, non-commercial). Basic, Essentials and Premier editions: "Contact Us", licensed per named user or per concurrent session; Cloud and Enterprise SaaS available |
| Free tier | Free to self-host; Spaces Free plan includes 2 computers in use at once and 20 remote hours per month | Community Edition: free for individuals, nonprofits and non-commercial use, up to 5 concurrent sessions |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | San Francisco, California, United States | McLean, Virginia, United States |
| 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 | Organisations that already run browser-streamed desktops and want to give agents the same isolated, policy-controlled containers |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Cua
- 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
Reasons to choose Kasm Workspaces
- You want self-hosted, browser-streamed desktop containers with admin policy controls and a session API
- You need a free, full-featured edition for testing or non-commercial agent experiments
- You run on Kubernetes or want Terraform/Ansible-driven deployment with cloud autoscaling
Trade-offs to check first
- Cua: No hosted compute: you provision and pay for machines yourself (Cua Cloud ended October 2026)
- Cua: Licensing differs by component: MIT for the core, FSL-1.1-MIT for Cua Spaces and Driver Bench, AGPL-3.0-or-later for the optional cua-som package
- Kasm Workspaces: An agent-specific SDK or named model integrations are not documented; agents use the general Developer API
- Kasm Workspaces: Container sessions use Docker (Sysbox runtime optional), with VM-backed server workspaces as a separate type; startup figures are not documented
Both are worth piloting with your own image and region. See the full Cua profile and Kasm Workspaces profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Cua or Kasm Workspaces better for AI agents?
What is the difference between Cua and Kasm Workspaces?
Which is open source, Cua or Kasm Workspaces?
How do Cua and Kasm Workspaces isolate code?
How does Cua pricing compare with Kasm Workspaces?
Do Cua and Kasm Workspaces support GPUs?
Can you self-host Cua or Kasm Workspaces?
How long can sessions run on Cua and Kasm Workspaces?
async with block exits. Spaces plans meter "remote hours" per month (20 Free, 200 Pro). Kasm Workspaces: Session expiry is governed by per-user usage limits; the keepalive API resets a session's expiration time.Do Cua and Kasm Workspaces support snapshots or pause and resume?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Cua vs Kasm Workspaces. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/cua-vs-kasm-workspaces/