Cloud Macs for AI agents: the 2026 landscape
Agents now need macOS for Xcode, simulators and signing. A map of who offers a Mac an agent can drive, how they bill, and which kind of agent each one fits.
· 9 min read
Need a Mac for this? NoMac gives your agent full macOS with Xcode, from $9.99 a month, billed by the second. Start now →
Coding agents are good at iOS now. They write SwiftUI, fix compiler errors and read crash logs. What they cannot do is run Xcode on the Linux machine they usually live on. So in 2026 a new category appeared: Macs that an agent, not a person, starts, drives and throws away.
These products look similar from a distance and are built for quite different agents. This guide sorts them by the job the agent is doing.
Two kinds of agent need a Mac. A developer agent needs a shell with Xcode: compile, test, sign, boot a simulator. A computer-use agent needs a screen to look at and a mouse to move. Some services do both; most are clearly built for one.
The landscape in September 2026
Bitrise Remote Dev Environments
Bitrise opened Remote Dev Environments in beta in June 2026: on-demand macOS and Linux dev machines running on the same stacks and caches as Bitrise CI. You connect over SSH, VS Code, Cursor, JetBrains or VNC, and an open-source MCP server lets agents create and drive sessions. Claude Code and Codex come preinstalled. Sessions can be archived and restored, and plans run from $20 a month for 480 macOS minutes on M2 Pro machines, up to five concurrent VMs. It is built for mobile teams who already live on Bitrise, and it requires a Bitrise workspace. It replaces Bitrise's earlier experimental macOS MCP server, which is now deprecated. Full comparison.
Cua
Cua builds open-source computer-use tooling, including the Lume VM manager, and runs a cloud macOS offering aimed at computer-use agents, evaluations and data generation. At the time of writing, cloud macOS is a partnership waitlist aimed at fleets of hundreds or thousands of machines, without public pricing.
use.computer
use.computer sells macOS sandboxes on dedicated M4 Mac minis with an SDK in Python, TypeScript and Go: screenshots, mouse, keyboard, the accessibility tree, SSH and recordings. It is strongest for computer use. Reservations are for 24 hours or more, so it suits long-running agents better than short bursts.
NoMac
NoMac is built for the developer agent working alone or with one human. A session is a fresh macOS VM with root, Xcode, an iOS simulator runtime and the usual toolchains. The agent reaches it over a local or hosted MCP server, a CLI, a REST API or SSH. It bills by the second from weekly hours ($9.99 a month for 5 hours a week, $29.99 for 25), one session at a time, and deletes the VM on stop. It is headless: the simulator works through simctl, but there is no remote desktop.
The traditional options
Dedicated rentals (RentAMac, MacinCloud, MacStadium) and hourly bare metal (AWS EC2 Mac, Scaleway) all work with agents if you give the agent SSH. They were built for people and pipelines, so the agent has to manage provisioning, cleanup and 24-hour minimums itself. See every cloud Mac compared.
Side by side
| Built for | GUI | Billing | State | Self-serve | |
|---|---|---|---|---|---|
| Bitrise RDE | Teams on Bitrise | VNC | Monthly minutes, then per minute | Archive and restore | Yes, with a workspace |
| Cua cloud | Computer-use fleets | Yes | Not public | Not public | Waitlist |
| use.computer | Computer use | Yes, via API | 24 h reservations | During reservation | Yes |
| NoMac | Developer agents | Headless | Per second from weekly hours | Deleted on stop | Yes |
| EC2 Mac, Scaleway | Infrastructure teams | VNC | 24 h minimum | Until released | Yes |
What an agent actually needs from a Mac
- ·Durable commands. Builds take minutes and connections drop. An agent needs to start a job, lose its connection, and come back to the same job and its output. NoMac's
exec_macreturns a job ID, and output is read with a cursor. - ·Idempotent requests. If the response to “start a Mac” is lost, retrying must not start a second, billed Mac. Look for request keys.
- ·Hard limits. Agents forget to clean up. Idle timeouts, maximum durations and spending caps turn that into a small cost instead of a large one.
- ·A way in from a sandbox. Hosted agents often cannot open raw SSH. An HTTPS MCP endpoint works where SSH does not.
- ·Root. Agents install things. An agent that cannot run
brew installwill spend its time working around that.
How to choose
If your team is on Bitrise, try Remote Dev Environments first: matching CI is a real advantage. If you are building a computer-use product, look at use.computer or join Cua's waitlist. If you are one developer whose agent needs Xcode for a few minutes at a time, NoMac is designed for exactly that. To try it with Claude Code, follow the five-minute setup.