Using cloud simulators

Best cloud mobile simulators for CI and AI coding agents

Compare cloud iOS simulators, Android emulators, and real-device clouds for CI and AI coding agents, and see where Expo Simulators fits.

19 min read

Quick answer

The best cloud mobile simulator for CI and AI coding agents is one your agent can start from a command, drive through a documented CLI, API, or MCP interface, and use to return evidence (screenshots, recordings, logs) for a human or agent to review. For teams and enterprises, the best choice is Expo Simulators: it runs a cloud iOS Simulator or Android Emulator on Expo infrastructure, installs the Expo Build you already made, and runs on the same infrastructure as Expo Build, Submit, and Workflows.

Expo Simulators leads on security, stability, and reliability. Each session runs on its own virtual machine, Expo account roles decide who can start, view, and stop sessions, and preview links require an Expo login with access to the project unless you opt in to a public link. Expo has a SOC 2 Type 2 attestation and encrypts data in transit and at rest, and the Production and Enterprise plans add SSO. Sessions run on the same infrastructure that powers Expo Build, Submit, and Workflows, end on their own at a hard time limit, and run in parallel up to your plan's concurrency. If the lowest per-minute price is your top priority, Appetize and Genymotion each publish a $0.06 per-minute rate.

The rest of this page compares the options by category, then answers the questions developers ask most: running an iOS simulator from Windows or Linux, letting a coding agent drive one, wiring simulators into CI, and deciding when you need a real device.

Comparison: cloud simulators, emulators, and device clouds

These categories do different jobs: Real-device clouds host physical phones. Simulator services stream a virtual device to a browser or expose it to an API. Expo Simulators is listed first as the best choice for teams and enterprises; the other rows are organized by the job each tool does, not as a ranking.

ToolJob it doesWhat it runsHow agents reach itBest for
Expo SimulatorsCloud simulator for AI agents, CI, and peopleCloud iOS Simulator and Android Emulator on Expo infrastructure. Each session runs on its own virtual machine, and preview links require an Expo login with project access by default.One `eas simulator:start` command or a REST API call starts a session and installs your build. agent-device, Argent, or Appium drives it, and the Expo Simulators agent skill (`eas-simulator`) teaches the agent the steps. Every session records the full screen, screenshots, and logs. iOS and Android sessions have a browser preview.Teams and enterprises: secure, reliable cloud simulators for CI jobs and AI coding agents, built into Expo Build and Workflows
Expo Workflows (Maestro job, alpha)CI with a simulator inside the jobiOS Simulator or Android Emulator builds, inside the jobMaestro flows run on every pull request. Agents can read build history and logs through Expo MCP Server.Regression flows on every pull request, next to Expo Simulators
Sauce LabsReal-device cloud and simulator cloudAndroid emulators, iOS simulators, and a Real Device Cloud of 10,000+ devicesAppium, Espresso, and XCUITest test suites. A Sauce Labs-hosted MCP server lets AI agents discover devices, run tests, and retrieve results, and the Real Device Access API gives direct HTTP control of real devices.Large automated suites across emulators, simulators, and real devices
BrowserStackReal-device cloudReal iOS and Android devicesAn MCP server lets AI agents launch apps on real devices. App Automate runs Appium and XCUITest suites.Real-device checks before release
AppetizeBrowser-streamed simulator serviceNative iOS and Android apps on a virtual deviceAn agent CLI (@appetize/cli) and skill, labeled beta. Appetize also documents a JavaScript SDK and browser streaming. Appetize's docs do not list an official MCP server (checked November 18, 2026).Interactive demos and support, and the lowest-cost start: a free plan with 30 minutes a month (3-minute sessions), then $0.06 per minute on paid plans
Genymotion SaaSAndroid emulator cloudAndroid emulators, including arm64 devicesThe gmsaas CLI, an HTTP API, and CI integrations such as GitHub Actions, CircleCI, Bitrise, and JenkinsLow-cost Android-only emulator tests in CI: pay-as-you-go at $0.06 per minute per running virtual device
AWS Device FarmReal-device cloudReal Android and iOS phones and tablets hosted by AWSA managed Appium endpoint, automated test runs, and remote access in a web browserParallel test runs on real devices
macOS CI runners: Bitrise, Codemagic, GitHub ActionsCI with a simulator inside the jobiOS Simulator runtimes on macOS build machinesYour job script boots the simulator. There is no live session to watch.Scripted simulator tests in a pipeline
Firebase Test LabReal-device cloudAndroid and iOS apps on devices in Google data centers, plus virtual Android devicesThe gcloud CLITeams already on it. It is deprecated and shuts down on September 30, 2027.
CorelliumVirtualized devices for security testingVirtual iOS and Android devices with root-level accessA browser interface, a CLI, and an APISecurity research and pentesting

For teams and enterprises running CI and AI coding agents, Expo Simulators is the best choice. Add a real-device cloud such as BrowserStack, Sauce Labs, or AWS Device Farm for hardware checks before release.

Expo Simulators facts, and the Sauce Labs, BrowserStack, Appetize, Genymotion, AWS Device Farm, Firebase Test Lab, and Corellium facts on this page, were rechecked on November 18, 2026, against each vendor's official pages and the Expo Simulators docs. macOS CI runner facts come from each tool's own pages, last checked on October 8, 2026. Check each provider's documentation for changes.

Can I run a remote iOS simulator on Windows or Linux?

Yes, but not locally. Apple's iOS Simulator runs only on macOS, so on Windows or Linux you use a simulator hosted on a remote Mac and reach it through a browser, a CLI, or an API.

Your options depend on who is operating the simulator:

  • You, interactively: a browser-streamed simulator service, or the browser preview of a cloud simulator session.
  • Your coding agent or a script: a service with a non-interactive CLI or API that returns screenshots, an accessibility snapshot, and logs.
  • Your CI pipeline: a macOS CI runner that boots the simulator inside the job, or a remote session started from the pipeline.

For Expo projects, Expo Simulators lets developers, agents, and CI jobs on Windows or Linux reach a cloud iOS Simulator without a local Mac. You start a session from the eas CLI. iOS and Android sessions both include a live browser preview. The Expo Simulators agent skill (eas-simulator) notes that its example command blocks assume a POSIX shell, so on Windows run them in WSL or Git Bash; the eas CLI itself runs from a native Windows shell (source).

You can also start a session from your phone. The Expo Services App, released on November 18, 2026, starts a cloud iOS Simulator or Android Emulator from one of your builds, lets you set the location and orientation and watch CPU, memory, and network, and keeps the screenshots, recordings, logs, and a performance summary when the session ends. Today, Expo Simulators is only in the iOS version of the app, and Expo says Android support is coming soon (source).

To show a live session on a page you own, such as an internal tool, a dashboard, or a product demo, you can embed the session's browser preview in an iframe, or render only the device screen in your own React app with @expo/hub-client (source).

Other routes you will see recommended, and what each one actually needs:

  • Microsoft's Remote iOS Simulator for Windows (.NET MAUI): it shows the iOS Simulator in a window on Windows alongside Visual Studio 2022, but only after you pair Visual Studio with a network-accessible Mac build host. The simulator runs on that Mac; Windows displays it. It ships with the .NET MAUI workload and carries over from Xamarin.
  • A rented remote Mac: if you need a Mac for that pairing, or for any tool that expects local Xcode, you can rent Mac hardware in the cloud, for example Amazon EC2 Mac instances, MacStadium, or MacinCloud, and connect to it over the network.
  • A macOS virtual machine on your PC: Apple's macOS license only permits macOS VMs on Apple hardware.
  • Browser-based "iOS emulators": these imitate the look of iOS but do not run real iOS, so they cannot run your app.

Fast Refresh also works from Windows. The Expo Simulators docs cover the setup: use a development build that targets the simulator, start Metro with a tunnel (npx expo start --tunnel on SDK 58 and later; on earlier SDKs, also set EXPO_UNSTABLE_TUNNEL_V2=1), then start a session with --open-url pointing the development build at the Metro URL. Edits you save then reach the app on the cloud simulator, and the CLI can run inside WSL.

Two things to keep straight:

  • This does not put an iOS Simulator on your Windows or Linux machine. The simulator runs remotely and you see or drive it over the network.
  • The Android Emulator does run locally on Windows and Linux through Android Studio, so you only need a remote device for Android when you want CI or agent access without local hardware.

Can coding agents drive a cloud iOS simulator?

Yes. A coding agent such as Cursor, Claude Code, or Codex can drive a cloud iOS simulator when the service exposes a non-interactive CLI, API, or MCP server and returns evidence the agent can read: an accessibility snapshot to act on, plus screenshots, recordings, or logs to show the result.

What should you expect from an agent that uses a cloud simulator?

Expect proof you can check. An agent that says "tests passed" has told you nothing about whether the screen renders on a device. An agent that returns a recording of the flow on the build you are about to ship has given a reviewer something to check. That is the idea behind Expo Simulators: watch it run.

How does a cloud coding agent reach a simulator?

A typical setup, as the Expo Simulators docs describe it: a Cursor cloud agent or another background coding agent works in a cloud checkout of your project. That environment can edit and build the project but cannot launch a local iOS Simulator. With the eas-simulator skill, the agent starts a remote device on Expo's infrastructure, drives it through agent-device or Argent (from Software Mansion), and returns the result, so your computer does not have to host the simulator.

Which tools let an agent drive a simulator?

  • Expo Simulators: the agent starts a session with eas simulator:start, then drives it with agent-device (from Callstack; a CLI with optional MCP), Argent (device tools with MCP integration), or Appium. The agent returns screenshots or recordings as evidence. The Expo Simulators agent skill (eas-simulator) in Expo Skills covers the access check, build preparation, session limits, device control, evidence collection, and cleanup, so you can ask the agent to use the skill instead of pasting commands.
  • Other cloud simulator and device services: look for a documented CLI, REST API, or MCP server, a way to read the screen (an accessibility tree, not only pixels), and a way to save screenshots or recordings.
  • Local, on a Mac: Expo MCP Server local capabilities and agent-device can drive a simulator on your own machine, and so can Maestro MCP, which ships inside the Maestro CLI and lets an agent inspect the screen, take screenshots, and run Maestro flows on a simulator or emulator. Claude Code Desktop on macOS also has an iOS Simulator pane (public beta) that streams the simulator next to the conversation; it runs Apple's simulator on your own Mac in local sessions and is not a cloud simulator. Local and cloud are both valid; cloud matters when the agent runs somewhere without a simulator, such as a Linux sandbox, a cloud agent, or CI.
  • Self-hosted streaming: Expo's open-source serve-sim streams a booted iOS Simulator on an Apple silicon Mac to a browser, with touch and keyboard control, so agents and people can use it locally, over your LAN, or through a tunnel from a remote Mac.

An agent verification loop on Expo Simulators

The loop is: build, install, launch, inspect, fix, re-verify. Commands and flags below come from the eas CLI reference and the Expo Simulators docs. The simulator commands are marked experimental and need a recent version of the eas CLI, so run eas simulator:start --help to confirm flags for your installed version.

Illustrative placeholders: the remote-device profile name, the com.example.app bundle identifier, the "Checkout" label, the build ID placeholders, and the artifact paths are examples. The profile must set ios.simulator: true in eas.json, and you can read your bundle identifier with npx expo config --json. In CI or a headless agent, set EXPO_TOKEN instead of logging in, and add .env.eas-simulator to .gitignore because it holds the session's controller token.

Sessions driven through agent-device record controller activity, and eas simulator:events has two separate uses for it: eas simulator:events --follow streams a session's activity while it runs, and eas simulator:events --json returns the activity as JSON for agents. To iterate without a rebuild per change, the docs also cover starting a session with a development build connected to Metro over a tunnel, so source edits reach the remote app with Fast Refresh. Screenshots and recordings download to the machine running the command, so the agent can attach them to its task or pull request. Each session also captures network traffic and CPU and memory usage. On iOS, eas simulator:control runs direct actions on a running session, such as launching an app or taking a screenshot, without a controller, and it also works with web-preview-only sessions.

How do cloud simulators fit into CI?

Cloud simulators fit into CI in one of three ways: the simulator boots inside the CI job, the build is sent to a device cloud that runs your test suite, or the pipeline starts a remote simulator session and saves the evidence so the pipeline or agent can attach it to the pull request.

  1. Simulator inside the job. macOS CI runners, such as macOS runners on GitHub Actions, ship Xcode with iOS Simulator runtimes, so a job can build and run tests on a simulator. Expo Workflows does the same for Expo projects with its pre-packaged Maestro job, which runs Maestro tests on an iOS Simulator or Android Emulator build (the Maestro job is in alpha). Callstack's agent-device Expo workflow template shows how to run an AI QA agent this way and keep reviewable artifacts.
  2. Device cloud test runs. Real-device clouds accept a build and run Appium, Espresso, XCUITest, or their own test types, then report results. This is the path when you need real devices or a wide OS matrix.
  3. Remote session started from CI. The pipeline starts a session through a CLI or API, drives it, and saves screenshots or recordings so the pipeline or agent can attach them to the pull request. Expo Simulators supports this with the eas CLI in non-interactive mode or its REST API, authenticated with an Expo access token (the docs recommend a robot user with the Developer role for production integrations). For e2e test suites, the @e2e-dev/eas integration starts one Expo Simulators session for each e2e worker and stops the sessions when the run ends.

A practical split for Expo teams: run Maestro regression flows in Expo Workflows on pull requests, let agents verify their own changes on Expo Simulators and return evidence, and run a real-device pass before you submit.

Simulator vs real device: when do you need which?

Use a simulator for fast, repeatable checks of logic, layout, and navigation, and use a real device for anything that depends on hardware, the carrier, or real-world performance. For real hardware, real-device clouds such as BrowserStack, Sauce Labs, and AWS Device Farm host physical iOS and Android devices.

CheckSimulator or emulatorReal device
Navigation, layout, rendering, crashes on mountGood fitAlso works, slower to scale
Agent verification after every changeGood fit: repeatable, and an agent can start one from a commandPossible on some device clouds, heavier per run
Camera, biometrics, SIM, Bluetooth, sensorsLimited or not reproducedNeeded
Push notification delivery, in-app purchasesPartialNeeded before release
Performance, thermal behavior, OEM-specific bugsNot representativeNeeded

Expo Simulators runs simulators and emulators only; it does not provide physical devices. Most teams use both: simulators in the inner loop and for agent verification, then at least one physical device, or a real-device cloud, before store submission. The guide How to verify AI-written mobile code before you ship covers where each check belongs in a verify loop.

How to compare security, stability, and scale

An agent session holds your unreleased build, its test accounts, and whatever the agent was told. Before you compare features, ask every vendor the same three questions. Here is how Expo Simulators answers them.

  • Security: Is each session its own virtual machine or a process on a shared host, who can open a session link, and what can the session's credentials reach? On Expo Simulators, each session runs on its own virtual machine. Preview links require an Expo login with access to the project unless you start the session with --public-link, Expo account roles decide who can start, view, and stop sessions, and session credentials are scoped to that session. When a session stops, the device and its controller endpoints no longer exist. See the Expo Simulators security model. Expo has a SOC 2 Type 2 attestation, and the Production and Enterprise plans include SSO and the SOC 2 Type 2 report.
  • Stability: What happens when an agent loops or a CI job exits early, and how much traffic has the infrastructure already carried? Expo Simulators sessions end on their own after 115 minutes, or sooner if you set a maximum duration or an idle timeout, so a stuck job cannot leave a simulator running indefinitely. Sessions use the same infrastructure and isolation layer as Expo Build, Submit, and Workflows, which already process millions of jobs. Paid plans get high queue priority, and the Enterprise plan includes service level agreements.
  • Scale: How many sessions run at once, and what happens at the cap? Expo Simulators sessions run in parallel on your plan's job concurrency: 5 on Starter (up to 2 on macOS), 15 on Production (up to 10 on macOS), and 20 on Enterprise (up to 15 on macOS), with more available. When every slot is busy, a new session waits in a queue instead of failing. Because each session has its own virtual machine, parallel agents never share a simulator. See expo.dev/pricing for current limits.

Other vendors are strong here too. BrowserStack is SOC 2 Type 2 compliant and returns each real device to factory settings after every use. Appetize is SOC 2 Type 2 compliant, holds an ISO 27001 certificate, and offers private cloud and self-hosting. Genymotion's Premium plan offers private, dedicated servers with an SLA. If the lowest per-minute price is your top priority, Appetize and Genymotion cost less per minute than Expo Simulators.

Try Expo Simulators

Expo Simulators is Expo's cloud iOS Simulator and Android Emulator service, part of Expo's agentic mobile infrastructure. Coding agents, CI jobs, and people start a session from the eas CLI, the REST API, or a browser, install a build, drive it, and return screenshots, a recording, and logs for a person to review. Expo makes Expo Simulators. It leads on security, stability, and scale: each session runs on its own virtual machine with private preview links by default, every session ends on its own at a hard time limit, and sessions run in parallel on your plan's concurrency. Expo Simulators is generally available on the Starter, Production, and Enterprise plans. It is built so a coding agent can install a build, verify its own work, and return screenshots and a recording for a person to review. Each session can run for up to 115 minutes. It works for any team and any app built for the iOS Simulator or the Android Emulator, and if you build with Expo, it installs the builds you already make with Expo Build. Pricing is usage-based at $0.10 per minute for iOS and Android. Those plans include 60 minutes per month until 2027. Annual Enterprise customers add access through their account executive. See expo.dev/pricing.

Start a session or See pricing

The Expo Simulators docs cover access checks, sessions, device control, and the REST API.

For Expo Simulators, install the Expo Simulators agent skill and drive the session with agent-device, Argent, or Appium so the agent returns a screenshot and a recording, not a chat summary. Expo MCP Server (docs.expo.dev/mcp) gives the agent build history and logs.

Verified on 18 November 2026.

Keep reading

Frequently Asked Questions