Agent infrastructure
Cua
Open-source infrastructure for computer-use agents, with sandboxed macOS, Linux and Windows environments.
cua.ai · LinkedIn · Data run November 13, 2026
Momentum, week of November 9, 2026
66 from 4 of 5 signals
- Agent infrastructure: #6 of 18
Signal percentiles: Headcount change, 3 months 27; Tranco rank movement, ~30 days 90; Recency of last funding round 52; Launch and discussion activity, 90 days 93.
What the data says
Positive signals
- Tranco top-sites rank climbed 41.2% over about 30 days.
- Raised within the last 12 months: Seed (Jan 2026).
- 5 Hacker News stories linked to the company in 90 days.
Watch-outs
- Headcount flat over three months (as of Jul 30, 2026).
Key facts
- Headquarters
- San Francisco, California, United Statessource
- Founded
- 2025source
- Last round
- Seed (Jan 2026)sourceas of round date Jan 1, 2026
- Headcount
- 8sourceas of Jul 30, 2026
- Headcount change
- 3m 0% · 12m +60%as of Jul 30, 2026
- Monthly web visits
- n/a
- Web traffic change
- 3m n/a · 12m n/a
- Tranco top-sites rank
- #248,173sourceas of Nov 12, 2026
- Tranco rank, ~30 days
- +41.2%as of 2026-10-15 to 2026-11-12
- LinkedIn followers
- 2.5Ksource
- Hacker News stories, 90 days
- 5source
Recent news and launches
- Oct 15, 2026 · Shared Spaces for Your Agents (Hacker News (2 points)) · discussion
- Oct 15, 2026 · Cua launches shared desktops for teams and AI agents (RuntimeWire)
- Oct 3, 2026 · Cua Spaces (Hacker News (3 points)) · discussion
- Aug 31, 2026 · Run OpenClaw on Cua Cloud Fleet (Hacker News (1 points)) · discussion
- Aug 28, 2026 · Omarchy Desktops on Cua Cloud Fleets (Hacker News (2 points)) · discussion
- Aug 25, 2026 · Run Minecraft in a Windows sandbox for computer use agents (Hacker News (23 points)) · discussion
- Jan 30, 2026 · A Story of Computer-Use: Where We Started, Where We're Headed (Hacker News (2 points)) · discussion
- Jan 18, 2026 · Show HN: Lume 0.2 – Build and Run macOS VMs with unattended setup (Hacker News (154 points)) · discussion
n/a means our sources had no value; we do not estimate. Spot an error? Request a correction with a public source.