Cua Spaces adds AWS and Hetzner deployment in customer accounts

• Cua Spaces now deploys inside customers' AWS and Hetzner accounts in early access, according to Cua's announcement.
• Running 256 RL sandboxes eight hours daily for a month comes to $700 versus $10.2k on E2B in Cua's cost estimate.
• Existing E2B Python code runs unchanged through the wrapper in Cua's demo; the company also advertises Daytona compatibility in its update.
• Local performance numbers include a network advantage: Cua's benchmark compares a Mac Studio with E2B across the internet.

The runtime docs default local Linux sandboxes to gVisor, with explicit options for plain runc containers or QEMU VMs. A separate Hermes plugin skips risky-command prompts for Spaces it creates, but retains them when attached to an existing Space.

The early-access integration places Spaces on servers in the customer's cloud account. Cua showed these connection commands:

In its test, the next batch landed on an already-running server: creation took 10.6 seconds, with 139 ms to the first command. Those figures describe placement on existing capacity, rather than provisioning a fresh server.

Self-hosting on Macs and Linux boxes already works, according to Cua's availability post. The download page also offers a Windows app, labeled as a preview.

Cua priced the following workload:

• 256 RL sandboxes.
• Eight hours of operation per day for a month.
• Approximately $10,200 on E2B versus $700 on Cua Spaces, about 93% lower.

The launch post gives the concurrency and schedule, but no per-sandbox CPU, RAM or storage configuration.

Separately, Cua's published pricing lists Pro at $18 per month and Teams at $30 per seat per month. Its free tier includes two live sessions and 20 remote hours monthly; customers' cloud providers bill for the VMs.

Cua demonstrated an existing E2B Python program running unchanged in a local Space, the strongest part of the pitch. The wrapper takes this form, with your_program.py standing for the existing script:

Compatibility access has a rollout caveat: Cua's availability post invites users to request E2B and Daytona support “the day it lands.” The demonstrated E2B wrapper is more concrete than the Daytona claim, for which the supplied launch thread gives no equivalent command.

Cua's same-day benchmark compared local execution on an M2 Max Mac Studio with E2B over the internet, so the command timings include network distance.

| Metric | Cua, local Mac Studio | E2B, over the internet |
| --- | ---: | ---: |
| Cold start | 185 ms | 322 ms |
| Command round trip | 0.7 ms | 64 ms |
| Snapshot | 0.52 s | 2.0 s |
| Rollout loop | 317 steps/s | 101 steps/s |

Cua's relay FAQ says hosted relay connections terminate TLS at Cua. The relay can read the desktop stream, input and files in transit, although the company says it does not store them.

Spaces reached directly bypass the relay. Teleport session bundles on Space images receive separate end-to-end sealing to the destination Space's key, so the relay forwards those bundles as ciphertext.