On this page
Run Cloud and Revyl both run cloud iOS simulators and Android emulators; Revyl adds web browsers, macOS computers and Atlas. Revyl's Free plan includes up to 1,200 free device minutes a month on iOS, Android, web and Mac, with no card and no monthly fee; Run Cloud's monthly free usage, with a card, covers up to 750 active minutes (run.cloud/pricing). Its $0.02 active minute is lower. Revyl is usually worth the premium: each app run feeds run history and Atlas.
Scroll the table sideways to see all 2 columns.
What is the difference between Run Cloud and Revyl?
Run Cloud and Revyl both run cloud iOS simulators and Android emulators that coding agents start and drive. Run Cloud offers them with Xcode builds behind one API, all labelled early access (run.cloud). A Run Cloud session is created from the runcloud CLI or SDK, installs a build and returns a signed browser URL (simulators).
Revyl, which also runs web browsers and macOS computers, builds the app, runs it in a cloud session, records each test run as a report, adds what it saw to Atlas, and comments on a pull request with a live preview link and, through proof of changes, a verdict. Teams start at $0, with up to 1,200 free device minutes a month on iOS, Android, web and Mac and no card (pricing).
What does Revyl add to each test run?
The Revyl loop has five steps:
- Build: revyl build runs your build recipe in Revyl’s cloud and stores the finished build on your app, so you can launch devices and run tests against it.
- Run: the device quickstart starts a cloud iOS simulator or Android emulator with that build and prints a live viewer link. Agents drive it through the CLI or MCP and can name a target in natural language.
- Evidence: each test run produces a report with video, a step timeline, performance metrics and device logs, all synced to the video.
- Atlas: Atlas groups what runs observed into screens, states and transitions, each tied to the screenshots it came from. People open it in the dashboard, and agents query it with
revyl atlas. - Proof on the pull request: through proof of changes, Revyl installs the PR’s build in a live session, runs the changed flows and posts a verdict with findings, screenshots and evidence links. It needs the Revyl GitHub App and a build profile for pull requests.
How do the free tiers and pricing compare?
Prices below were checked on November 11, 2026.
Revyl’s Free plan is $0, with up to 1,200 free device minutes a month on iOS, Android, web and Mac, 2 devices at once and no card needed (pricing). On Run Cloud, with a card on file, the first $15 of usage each month is free, which Run Cloud says covers up to 750 active simulator minutes (pricing).
Run Cloud then charges $0.02 per active minute for iOS simulators and Android emulators, and its Xcode builds are free during beta. On Revyl, Pro is pay as you go, with 10 devices at once instead of 2, a $20 starting credit and no monthly fee. Past the free minutes, usage is $0.075 per device minute on iOS and Android, and $0.05 a minute on web and Mac. Free and Pro include unlimited developers and agents with no seat fees, Atlas maps of your app’s screens and flows, the CLI, API and CI, and run history and artifacts. Enterprise is custom, with volume pricing, unlimited devices at once, SAML SSO and SCIM.
Past the free minutes, Revyl’s per-minute rate buys more than device time. Each test run leaves a report, Atlas keeps a record of your app’s screens and flows from the runs it observes, and through proof of changes, the pull request gets a verdict. That record carries forward.
Can Revyl replace Run Cloud?
Yes. Both run cloud iOS simulators and Android emulators that a coding agent starts and drives, and Revyl covers that job from its CLI and MCP server. On Revyl, each test run also leaves a report, Atlas records the screens it observed and, through proof of changes, the pull request gets a verdict. A live simulator inside your own product moves to a Revyl embed.
Xcode builds move to revyl build.
Run Cloud also feeds a browser webcam into the simulator camera (simulators), and its privacy policy places its hardware in the European Union.
How do you move from Run Cloud to Revyl?
- Install the Revyl CLI, run
revyl auth login, thenrevyl initin your project. - Replace
runcloud xcode build .withrevyl build --remote --platform ios(add--profile <profile>when your project has several build profiles), and build Android with--platform android. - Replace
runcloud ios createandruncloud android createwithrevyl device start --platform ios --app-id <app-id>or--platform android --app-id <app-id>(or pass--build-version-id <build-id>for an exact build); the build must already exist. - Point your coding agent at the Revyl MCP server in place of the Run Cloud skill.
- Turn on PR previews and proof of changes so eligible pull requests get a comment with a live preview link and a verdict.
Run Cloud session IDs, uploaded assets and iframe messages are specific to Run Cloud. A Revyl embed uses its own iframe and JavaScript API, and its sessions provide up to 10 minutes of active device time with a 3-minute idle window.
Beyond cloud simulators and emulators: what else Revyl runs
The same Revyl account, CLI and record also cover these runtimes and tools:
- Web browsers: a Revyl web session opens your web app in Chrome with desktop and mobile viewports, on every plan (pricing).
revyl device start --platform webstarts one from the same CLI that starts your simulator. - iOS simulators and Android emulators: the sessions compared on this page stream to the browser and start from the dashboard, the CLI, the API or an agent (sessions).
- macOS computers: a Revyl Mac computer is a macOS computer in the cloud that an agent or a person starts, uses and stops. Its desktop streams to the browser,
revyl computerruns commands and works with files on it, and it can host Web and iOS app sessions. GitHub Actions jobs can run on a single-use Revyl Mac withruns-on: revyl-macos(GitHub Actions). - Atlas: Atlas is the shared record of what your app does, built from observed runs as screens, states and transitions tied to their screenshots.
- Agent access: coding agents reach Revyl through the CLI and the MCP server, and query Atlas with
revyl atlas. - Run reports and pull-request verdicts: each test run produces a report with video, a step timeline, performance metrics and device logs, and through proof of changes, Revyl posts a verdict on the pull request.
Sources
Facts were checked against these public pages on November 11, 2026. Spot an error? Email support@revyl.ai and we will correct it.
- Run Cloud home
- Run Cloud simulators
- Run Cloud pricing
- Run Cloud Android emulator docs
- Run Cloud CLI quickstart
- Appetize vs Run Cloud (by Run Cloud)
- Limrun vs Run Cloud (by Run Cloud)
- Run Cloud privacy policy
- Revyl sessions
- Revyl Mac computers
- Revyl GitHub Actions on Mac computers
- Revyl device quickstart
- Revyl remote builds
- Revyl reports
- Revyl Atlas
- Revyl proof of changes
- Revyl MCP
- Revyl embed a live device
- Revyl Appium driver
- Revyl Maestro runner
- Revyl pricing
- docs.revyl.com/devices/quickstart
- docs.revyl.com/integrations/cursor/setup
Frequently asked questions
What is Run Cloud?
Run Cloud (run.cloud) is infrastructure for mobile development and agent builders, run by Small Scale Labs AB in Sweden. It offers iOS simulators, Android emulators and Xcode builds behind one API, with a runcloud CLI, a TypeScript SDK and a signed browser URL for every session. Run Cloud labels these products early access, and Xcode builds are free during beta.
Can I start with Revyl for free?
Yes. Revyl's Free plan is $0, with up to 1,200 free device minutes a month on iOS, Android, web and Mac, 2 devices at once and no card needed. Pro is pay as you go, with 10 devices at once, a $20 starting credit and no monthly fee. Past the free minutes, usage is $0.075 per device minute on iOS and Android, and $0.05 a minute on web and Mac. Source: revyl.com/pricing.
Does Run Cloud run Appium or Maestro tests?
Run Cloud's own comparison page says first-party test-framework support is planned, and that today sessions are driven through the CLI, SDK or embed. Revyl tests are written as natural-language steps. Revyl's Appium driver runs the documented native Appium command set and its Maestro runner runs the documented Maestro command set; other suites move over as natural-language tests. Sources: run.cloud/compare/limrun-vs-run-cloud, docs.revyl.com/infrastructure/appium, docs.revyl.com/infrastructure/maestro.
Can a coding agent drive Run Cloud?
Yes. Run Cloud publishes an agent skill for Claude Code and Codex that teaches the agent to create sessions, install builds, open deep links and release sessions, on top of the runcloud CLI and SDK. Revyl gives agents an MCP server and CLI, and each test run an agent starts produces a report.
Can I embed a live simulator in my product with either?
Yes. Run Cloud returns a signed iframe URL per session, with lifecycle events and parent-page commands. Revyl has an iframe embed with a JavaScript API; Revyl embed sessions provide up to 10 minutes of active device time with a 3-minute idle window.
Is Revyl a Run Cloud alternative?
Yes, for teams whose agents need each simulator or emulator test run as evidence: a report, Atlas entries for the screens Revyl observed, and a pull request verdict through proof of changes. Run Cloud focuses on a per-minute device primitive. Source: run.cloud/pricing.
What else does Revyl do?
Revyl is one runtime platform for web browsers, iOS simulators, Android emulators and macOS computers. Web apps run in Chrome sessions on every plan, and Mac computers are macOS computers in the cloud that an agent or a person starts, uses and stops. Atlas is the shared record of what your app does, built from observed runs. Agents drive Revyl through the CLI and MCP. Each test run produces a report, and through proof of changes, Revyl posts a verdict on the pull request.