# Expo Simulators vs Run Cloud: Cloud simulators for React Native teams, and for everyone else.

> A detailed comparison of Expo Simulators (EAS Simulator) and Run Cloud for cloud iOS simulators and Android emulators: access, per-minute pricing, agent control, Appium and Maestro, camera input, embedding, and builds.

Canonical: https://run.cloud/compare/expo-simulators-vs-run-cloud/ · Updated 2026-11-13

Both products give you an iPhone simulator and an Android emulator in the cloud, so nobody on the team needs a Mac to see the app run. Expo Simulators is part of Expo Application Services and plugs into EAS Build, Workflows, and the Expo development loop. Run Cloud is a standalone device API with a lower per-minute rate, live camera and microphone input, and an embed contract on every account. This article compares what each one documents today, and where each is the better fit.

By [Timothy Lindblom](https://run.cloud/authors/timothy-lindblom/) · Published 2026-11-13 · Updated 2026-11-13 · Expo details are taken from expo.dev and docs.expo.dev as checked on November 13, 2026, while Expo Simulators is still in preview.

## At a glance

| Topic | Expo Simulators | Run Cloud |
| --- | --- | --- |
| Availability | Preview. The docs describe access for select partners through a waitlist; the pricing page lists sessions on the Starter, Production, and Enterprise plans. | Self-serve sign-up. Start with $5 of usage and no card. |
| Platforms | iOS Simulator (iPhone and iPad) and Android Emulator (phones, tablets, foldables). No physical devices. | iOS simulator (iPhone and iPad families, one runtime today: iOS 26.5) and Android emulator sessions. No physical devices. |
| Price | $0.10 per minute for iOS and Android, billed per second, on top of a $19 or $199 monthly plan. 60 minutes a month are included until 2027. | $0.02 per active minute for iOS and Android, with no plan fee. The first $15 of usage each month is free once a card is on file. |
| Session limits | Up to 115 minutes per session. Sessions share the plan’s job concurrency: 2 macOS slots on Starter, 10 on Production. | You set the inactivity and hard timeouts per session. A capacity queue waits for a free device instead of failing the call. |
| Agent control | Session types: agent-device (taps, text, installs, screenshots, recordings), Argent (its tools and MCP server), Appium, or web preview only. | Taps, swipes, typing, keys, hardware buttons, rotation, accessibility tree, screenshots, recordings, logs, and location from the CLI, TypeScript SDK, REST, or a hosted MCP server. |
| Test frameworks | An Appium session type. Maestro flows run as separate EAS Workflows jobs at $0.05 per run plus CI minutes. | No first-party Appium or Maestro runner. Tests drive sessions through the SDK, CLI, or MCP. |
| Camera and microphone | A simulated camera feed you click in the browser; Expo says it is not yet exposed to agents. | Live browser webcam into the app camera, plus uploaded video, images, and microphone audio, all available through the API and MCP. |
| Embedding | iframe or @expo/hub-client, on the Production ($199 a month) and Enterprise plans. | Signed iframe URL or React RemoteControl, with readiness events and parent-page commands, on every account. |
| Builds | EAS Build, priced separately; sessions install by build ID or fingerprint. Fast Refresh over a Metro tunnel with a development build. | Cloud Xcode builds on the same account, free during beta: simulator apps, signed IPAs, and JavaScript-only rebundles of an Expo native shell. |

## What Expo Simulators is

Expo announced the product as EAS Simulator in September 2026, as an iPhone in the cloud for developers who do not own a Mac, and later renamed it Expo Simulators. A session starts with `eas simulator:start` or with a `POST` to the Expo REST API, installs a build from EAS by build ID or native fingerprint (or from an archive URL), and returns a browser preview that several people and agents can watch and use at once.

The session type decides how it is driven. `agent-device` gives an agent taps, text entry, installs, screenshots, and recordings; `argent` attaches Software Mansion's Argent toolkit and its MCP server; `appium` lets an existing Appium suite connect; and `web-preview-only` is for people. Session replays with timelines are pitched as evidence on pull requests, and CLI flags exist for network capture.

Expo is clear that it is not limited to Expo apps: any iOS simulator build or Android APK runs, whether it came from React Native, Swift, Kotlin, Flutter, or Unity. The deepest integration is still with Expo itself, where a development build can Fast Refresh against the cloud simulator over a Metro tunnel. The docs label the product a preview and warn that commands and flags change often.

[Expo Simulators documentation](https://docs.expo.dev/preview/simulators/introduction/)

## What Run Cloud is

Run Cloud is one API for the devices an agent needs: iOS simulator sessions, Android emulator sessions, and cloud Xcode builds that archive, sign, and export a signed IPA. Sessions are created with `runcloud ios create` or `runcloud android create`, with the `@run-cloud/sdk` TypeScript client, over REST, or by an agent through the hosted MCP server at mcp.run.cloud, which signs in with OAuth instead of an API key.

Every session can be scripted: taps, swipes, typing, keys, hardware buttons, rotation, the accessibility tree, screenshots, screen recordings, device logs, and a simulated location. The distinguishing capability is input. A browser webcam can be carried into the simulator camera, so a QR scanner or document-capture flow sees live frames, and uploaded video, images, and microphone audio make the same run repeatable.

The signed session URL also works as a product surface. It takes an embed mode and an optional loading guard, emits readiness, app-launch, inactivity, and completion events to the parent page, and accepts commands for reload, Home, rotation, and screenshots. That is available on every account, not on a higher plan.

[Run Cloud simulator documentation](https://docs.run.cloud/ios/run-simulator)

## Price: a plan plus minutes, or minutes only

Expo Simulators costs $0.10 per minute for either platform, billed per second while a session runs, and requires a paid Expo plan: Starter at $19 a month or Production at $199 a month, with 60 simulator minutes a month included until 2027. Embedding a session needs Production. Run Cloud charges $0.02 per active minute for either platform, has no plan fee, and gives the first $15 of usage each month free once a card is on file.

At 1,000 simulator minutes a month, Expo on Starter comes to $19 plus 940 billed minutes, about $113. The same minutes on Run Cloud are $20 before the monthly free grant, which brings the bill to $5. If you already pay for an Expo plan for builds and updates, the plan fee is a sunk cost and the difference is the per-minute rate: five times lower on Run Cloud.

[Run Cloud pricing](https://run.cloud/pricing/)

## Ecosystem fit

This is where Expo has the stronger case for a team that already lives on Expo. Builds come from EAS Build, sessions install them by fingerprint, Maestro runs as a Workflows job, Orbit and the free Device Hub cover the local half of the loop, and everything sits under one Expo account. Fast Refresh to a cloud simulator is a React Native feature that a general device API does not try to match.

Run Cloud fits when the device is one piece of a larger system. It does not care which framework or CI built the app: install a simulator `.app` archive or an APK from anywhere, including EAS, or build it with `runcloud xcode build`. For Expo projects, `runcloud xcode rebundle` reuses a compatible native shell when only JavaScript and assets changed. Run Cloud never accepts an App Store Connect key, so the TestFlight upload stays in your own pipeline.

## Where each one is strong

Expo Simulators

- Tight integration with EAS Build, Workflows, and the Expo account a React Native team already has.
- Fast Refresh from a development build to a cloud simulator over a Metro tunnel.
- A choice of driver per session, including an Appium session type for existing suites and Argent’s MCP tools.
- Shared browser previews that several people and agents can use at once, plus session replays for pull requests.
- Network capture options and Maestro jobs in EAS Workflows.

Run Cloud

- A fifth of the per-minute rate, $0.02 against $0.10, with no monthly plan required to start.
- Self-serve today, rather than a preview behind a waitlist.
- Live camera and microphone input that agents can use, not only a person in the browser.
- Embedding with readiness events and parent-page commands on every account.
- Cloud Xcode builds on the same account, free during beta, including signed IPAs and Expo JavaScript-only rebundles.
- A hosted MCP server that Claude, ChatGPT, Claude Code, and Codex connect to with one URL and an OAuth sign-in.

## Which one should you pick?

Choose Expo Simulators when

- Your team already pays for EAS and wants simulators inside the same account and dashboard.
- Fast Refresh into a cloud simulator is the main thing you need.
- Your test suite is Appium or Maestro and you want a hosted runner for it.
- You need more iOS device types than one iPhone model and one runtime.

Choose Run Cloud when

- You want to start today, self-serve, without joining a waitlist or buying a plan.
- Per-minute cost matters at volume, and five times the rate is five times the bill.
- Your app depends on the camera or microphone and an agent should test those flows.
- You are embedding a live device in your own product and are not on an enterprise plan.

The two also work together. EAS can keep producing builds, and the simulator .app archive or APK it outputs installs on a Run Cloud session like any other build.

## Frequently asked questions

### What is the main difference between Expo Simulators and Run Cloud?

Expo Simulators is a cloud simulator inside Expo Application Services, built around EAS Build, Workflows, and the Expo development loop, and it is still in preview. Run Cloud is a standalone, self-serve device API for iOS simulators, Android emulators, and cloud Xcode builds, with a lower per-minute rate, live camera and microphone input, and embedding on every account.

### Is Expo Simulators only for Expo or React Native apps?

No. Expo says it runs any iOS simulator build or Android APK, including Swift, Kotlin, Flutter, and Unity apps. Fast Refresh and the React tooling need a React Native development build. Run Cloud is framework-agnostic in the same way: it installs any simulator .app archive or APK.

### Which one is cheaper?

Run Cloud, on published rates. Expo Simulators costs $0.10 per minute and requires a paid Expo plan from $19 a month, with 60 minutes a month included until 2027. Run Cloud costs $0.02 per active minute with no plan fee, and the first $15 of usage each month is free once a card is on file. At 1,000 minutes a month that is about $113 on Expo Starter against $5 on Run Cloud.

### Can I use Run Cloud with an Expo app?

Yes. Install the iOS simulator build or Android APK that EAS Build produces, or build the project on Run Cloud with runcloud xcode build, which detects Expo projects. When only JavaScript and assets change, runcloud xcode rebundle reuses the previous native shell instead of running a full native build.

### Do both support Appium and Maestro?

Expo Simulators has an Appium session type, and Maestro flows run as EAS Workflows jobs on Expo simulators and emulators. Run Cloud has no first-party Appium or Maestro runner today; tests and agents drive sessions through its CLI, TypeScript SDK, REST API, or MCP server, which cover taps, swipes, typing, the accessibility tree, screenshots, recordings, and logs.

### Can agents test camera flows?

On Run Cloud, yes: a browser webcam, an uploaded video or image, or looped microphone audio can be fed into the app through the API and the MCP server. Expo describes a simulated camera feed that a person selects in the browser preview and says it is not yet exposed to agents.

## Try the simulator before you decide.

Create a session, install your EAS or local build, and drive it from the CLI, the SDK, or your agent. Sign-up is self-serve, and sessions bill by the active minute.

[Start a simulator](https://run.cloud/login/) [See what simulators do](https://run.cloud/simulators/)
