Compare/Azure Foundry Hosted Agents vs CUA

AI tool comparison

Azure Foundry Hosted Agents vs CUA

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

A

Developer Tools

Azure Foundry Hosted Agents

Per-session isolated agent sandboxes on Azure — scale to zero, any framework

Mixed

50%

Panel ship

Community

Paid

Entry

Microsoft Azure's Foundry Agent Service now offers Hosted Agents in public preview — per-session isolated compute sandboxes purpose-built for running AI agents at scale. Each session gets its own container with a persistent filesystem, internet access (optional), and a Python environment pre-loaded with common agent dependencies. Sessions spin up in seconds and terminate — and stop billing — the moment the agent task completes. The design is framework-agnostic: it officially supports LangGraph, OpenAI Agents SDK, Claude Agent SDK, and Microsoft's own Agent Framework, with others planned. This removes one of the most awkward parts of deploying agents in production: figuring out where they actually run. The persistent filesystem per session means agents can read and write files across their task without external storage configuration. Pricing is $0.0994/vCPU-hour and $0.0118/GiB-hour — competitive with Lambda/Cloud Run for bursty workloads. The service is available in six Azure regions at launch. For enterprises already invested in Azure, this is a compelling "we just figured out the infra" moment. Independent developers can also use it without an enterprise agreement.

C

Developer Tools

CUA

Open-source infra to build agents that drive real computers — any OS

Ship

75%

Panel ship

Community

Paid

Entry

CUA is an open-source infrastructure platform for building, testing, and deploying computer-use AI agents. It provides a unified Python SDK that lets agents take screenshots, click buttons, type text, and run shell commands across macOS, Linux, Windows, and Android — treating every OS as a consistent, programmable API surface. The project ships as several modular pieces: Cua Driver for background macOS app control without disrupting the user's session, Cua Sandbox for cross-platform virtual environments, CuaBot for multi-agent CLI orchestration integrated with Claude Code, and Cua-Bench for standardised benchmarking of agent performance across tasks. Lume adds full macOS and Linux virtualisation on Apple Silicon. With 16,400 GitHub stars, 482 releases, and a fresh driver update shipping in May 2026, CUA has become a de facto foundation for teams building computer-use applications. The MIT license and thorough documentation at cua.ai make it accessible for both academic research and production deployments where GUI automation via API simply isn't available.

Decision
Azure Foundry Hosted Agents
CUA
Panel verdict
Mixed · 2 ship / 2 skip
Ship · 3 ship / 1 skip
Community
No community votes yet
No community votes yet
Pricing
$0.0994/vCPU-hour, $0.0118/GiB-hour (public preview)
Open Source (MIT)
Best for
Per-session isolated agent sandboxes on Azure — scale to zero, any framework
Open-source infra to build agents that drive real computers — any OS
Category
Developer Tools
Developer Tools

Reviewer scorecard

Builder
80/100 · ship

Framework-agnostic hosted sandboxes with scale-to-zero is exactly what I need for deploying agents without maintaining my own Kubernetes cluster. The per-session isolation eliminates a whole class of security concerns I was handling manually. The Claude Agent SDK support means I don't have to choose between Azure and my preferred model.

80/100 · ship

The cross-platform API abstraction is genuinely well-designed — the same agent code that drives a Linux terminal works on macOS GUI apps without modification. CuaBot with Claude Code is a surprisingly capable local autonomous agent stack for tasks that have no API.

Skeptic
45/100 · skip

Public preview means production instability risk and pricing could change significantly at GA. The cold start time for agent sessions needs to be benchmarked against real workloads before committing. And six regions is thin coverage for global deployments — wait for broader availability.

45/100 · skip

Computer-use agents are still brittle against real-world UI variance. CUA solves the infrastructure problem well but doesn't solve the underlying reliability problem — agents still fail on unexpected popups, resolution changes, or app version updates. Infrastructure is necessary but not sufficient.

Futurist
80/100 · ship

The battle for agent infrastructure is the next cloud wars — and Microsoft just answered Google Cloud's agent platform launch with their own. Framework-agnostic compute that works with any model provider is a smart commoditization play: own the infrastructure layer, let the model battle play out above it.

80/100 · ship

CUA is load-bearing infrastructure for the era where software agents don't call APIs — they use computers the way humans do. Every major enterprise workflow that can't be API-ified becomes automatable once agents can reliably see and interact with a screen.

Creator
45/100 · skip

This is squarely developer infrastructure — not directly relevant to creative workflows unless your studio runs its own agents. Worth watching for the ecosystem tools that get built on top of it.

80/100 · ship

Automating Figma, Notion, or browser-based tools that have no API is genuinely exciting from a creative workflow standpoint. Waiting eagerly for the macOS agent reliability to mature enough to handle complex creative app workflows without hand-holding.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later

Azure Foundry Hosted Agents vs CUA: Which AI Tool Should You Ship? — Ship or Skip