# Revyl vs Limrun

Canonical: https://revyl.com/compare/revyl-vs-limrun/
Published: 2026-11-04
Last updated: 2026-11-04

> Revyl Free: up to 1,200 free device minutes a month on iOS, Android, web and Mac, no card. Limrun: a one-time 120-credit trial, then plans from $20/month.

Last verified: November 4, 2026.

Limrun pricing starts with a one-time free Trial of 120 credits, which is 60 iOS simulator minutes, then plans from $20 a month. 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, 20 times that trial, and it renews. Past that, Revyl's $0.075 per device minute on iOS and Android is below Limrun's iOS simulator rates of $0.08 and $0.10 a minute.

**Limrun and Revyl at a glance**

| | Limrun | Revyl |
|---|---|---|
| Cloud iOS simulators | Yes ([source](https://docs.limrun.com/docs)) | Yes ([source](https://docs.revyl.com/infrastructure/quickstart)) |
| Cloud Android emulators | Yes ([source](https://docs.limrun.com/docs)) | Yes ([source](https://docs.revyl.com/infrastructure/quickstart)) |
| Remote builds | Yes ([source](https://docs.limrun.com/docs)) | Yes ([source](https://docs.revyl.com/remote-builds)) |
| MCP server | Yes ([source](https://docs.limrun.com/docs/agents/remote-mcp)) | Yes ([source](https://docs.revyl.com/reference/mcp-tools)) |
| Embeddable live device | Yes ([source](https://docs.limrun.com/docs/platform/embed-simulator)) | Yes ([source](https://docs.revyl.com/devices/embed)) |
| Existing test suites | Support for Maestro, Appium, XCTest and others on remote simulators and emulators ([source](https://limrun.com/pricing)) | Appium suites through a source-installed driver, for the documented command set (Maestro through a separate runner) ([source](https://docs.revyl.com/infrastructure/appium)) |
| Concurrency | Unlimited on all plans, subject to abuse-prevention quotas ([source](https://limrun.com/pricing)) | 2 devices at once on Free, 10 on Pro, unlimited on Enterprise ([source](https://revyl.com/pricing/)) |
| What a run leaves behind | Session recording, log recording and network inspection ([source](https://limrun.com/pricing)) | A run report with video, step timeline, performance metrics, device logs and network traffic (on iOS and debuggable Android builds) ([source](https://docs.revyl.com/tests/reports)) |
| On the pull request | A preview link reviewers open to run the PR's build in the browser ([source](https://docs.limrun.com/docs/ci/pr-previews)) | A preview URL posted on the PR that auto-starts a simulator with that exact build when a signed-in teammate opens it, plus a proof-of-changes comment with a live preview link and a verdict with findings, screenshots and evidence links ([source](https://docs.revyl.com/builds/ci-builds)) |
| Cloud builds | Credits per minute: Xcode 2 active / 0.4 warm; Android build 1 active / 0.2 warm ([source](https://limrun.com/pricing)) | Revyl builds the app in its cloud and stores the finished build on your app, so you can launch it on a device straight away ([source](https://docs.revyl.com/remote-builds)) |
| Free tier | Trial: 120 credits, one time only, which is 60 iOS simulator minutes or 120 Android emulator minutes ([source](https://limrun.com/pricing)) | Revyl Free: up to 1,200 free device minutes a month on iOS, Android, web and Mac, and the allowance renews ([source](https://revyl.com/pricing/)) |
| Past the free tier | Entry $20/month with 500 credits; overage $0.10/min iOS, $0.05/min Android ([source](https://limrun.com/pricing)) | No monthly fee: Pro is pay as you go at $0.075 per device minute on iOS and Android ([source](https://revyl.com/pricing/)) |
| SSO | SSO + SCIM on the Company plan ([source](https://limrun.com/pricing)) | SAML SSO and SCIM on Enterprise ([source](https://revyl.com/pricing/)) |

## What is the difference between Limrun and Revyl?

Limrun pricing runs on credits, from a 120-credit trial to plans from $20 a month, while Revyl prices device time by the minute with a Free plan of up to 1,200 free device minutes a month on iOS, Android, web and Mac. [Limrun](https://docs.limrun.com/docs) is cloud infrastructure for coding agents that build mobile apps. It offers four instance types (iOS simulator, Android emulator, Xcode sandbox and Gradle sandbox) that compose: attach a simulator to an Xcode sandbox and every successful build installs and launches on it. Agents reach it through the lim CLI and skills, typed SDKs, and an [MCP server](https://docs.limrun.com/docs/agents/remote-mcp). Revyl also builds apps and runs them on cloud iOS simulators and Android emulators, then keeps what each run observed: a report with video and logs, an Atlas record of the app's screens and a verdict on the pull request through proof of changes. Limrun gives your agent the building blocks; Revyl also keeps a record of what each run did.

## Who should pick Revyl?

Pick Revyl when a run has to leave evidence behind. The loop has five steps:

1. Build. [revyl build](https://docs.revyl.com/remote-builds) runs your recipe in Revyl's cloud and stores the finished build on your app, so you can launch a device with it straight away.
2. Run. The [device quickstart](https://docs.revyl.com/infrastructure/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](https://docs.revyl.com/agents/mcp), and can describe a target in natural language instead of coordinates.
3. Capture evidence. Every test run produces a [report](https://docs.revyl.com/tests/reports) with video, a step timeline, CPU, memory and FPS, device logs and network traffic (on iOS and debuggable Android builds), all synced to the video.
4. Add to Atlas. [Atlas](https://docs.revyl.com/atlas) groups what runs observed into screens, states and transitions, each tied to the screenshots it came from. People open it in the dashboard; agents query it with revyl atlas. Atlas is built from observed runs, so a new build's map fills in as sessions, tests or explorations run against it.
5. Prove it on the pull request. Revyl leaves a [pull-request comment with a live preview link](https://docs.revyl.com/integrations/cursor/setup) to the PR's build. With [proof of changes](https://docs.revyl.com/agents/proof), Revyl installs the PR's build in a live session, runs the changed flows and posts a verdict with findings, screenshots and evidence links.

## How does Limrun pricing compare with Revyl pricing?

Both price device time by the minute, so compare in that unit. Limrun prices are from [limrun.com/pricing](https://limrun.com/pricing), checked November 4, 2026; Revyl prices are from [revyl.com/pricing](https://revyl.com/pricing/).

- Revyl Free plan: up to 1,200 free device minutes a month on iOS, Android, web and Mac, and the allowance renews. Limrun's Trial is 120 one-time credits, which is 60 iOS simulator minutes or 120 Android emulator minutes, and it does not renew.
- Limrun (Entry, Individual): $0.08/min for an iOS simulator and $0.04/min for an Android emulator from the monthly allowance, then $0.10/min and $0.05/min in overage.
- Revyl past the free minutes, on Pro: $0.075 per device minute on iOS and Android, 10 devices at once, a $20 starting credit and no monthly fee.

Limrun's Entry is $20/month for 500 credits and Individual is $200/month for 5,000, and every Limrun plan includes unlimited concurrency. Revyl has no monthly fee: Free runs 2 devices at once, Pro runs 10, and Enterprise has unlimited devices at once.

Revyl's $0.075 per device minute on iOS and Android is below Limrun's iOS rate of $0.08 a minute inside a monthly plan's credits and $0.10 a minute in overage ([pricing](https://revyl.com/pricing/), [Limrun pricing](https://limrun.com/pricing)). For Android emulators, Limrun's $0.04 in-plan and $0.05 overage rates are lower. Revyl is usually worth the premium because you get the data and the record: each run adds a report to your run history and what it saw to Atlas, and that record compounds.

Limrun charges builds in credits per minute: an active Xcode sandbox is $0.08 a minute from a monthly plan's credits and $0.10 in overage, and an active Android build is $0.04 and $0.05, less while warm ([Limrun pricing](https://limrun.com/pricing)). Revyl's [remote builds](https://docs.revyl.com/remote-builds) store each finished build on your app, so you can launch devices and run tests against it.

## Can Revyl replace Limrun?

Yes. Revyl has cloud iOS simulators and Android emulators, remote iOS and Android builds, an MCP server and CLI for agents, and an [iframe embed](https://docs.revyl.com/devices/embed) for a live device in your own pages. For work that needs a full macOS environment, such as running `xcodebuild` yourself, [Mac computers](https://docs.revyl.com/computers) give agents commands, files and processes on a Mac. Each run also leaves a report, an Atlas record and a pull-request verdict from proof of changes. Appium and Maestro suites run through source-installed adapters for documented command sets.

## How do you move from Limrun to Revyl?

1. Install the [Revyl CLI](https://docs.revyl.com/infrastructure/quickstart), run revyl auth login, then revyl init in your project.
2. Replace lim xcode build and lim gradle build with revyl build --remote --platform ios or android (add --profile to pick a build profile from your config).
3. Replace instance creation with revyl device start --platform ios (or android) and the app ID from .revyl/config.yaml.
4. Point your coding agent at the [Revyl MCP server](https://docs.revyl.com/agents/mcp) instead of mcp.limrun.com.
5. Configure [PR previews](https://docs.revyl.com/integrations/github#configure-pr-previews) in place of Limrun's preview links, and turn on [proof of changes](https://docs.revyl.com/agents/proof) for a verdict on your pull requests.

Some things don't carry over. Limrun-specific pieces such as the @limrun/ui component, the credit model and Bazel remote execution need replacing. Limrun's public ADB tunnel for standard Appium drivers is Limrun-specific; on Revyl, Appium and Maestro suites run through source-installed adapters that support documented command sets ([Appium driver](https://docs.revyl.com/infrastructure/appium), [Maestro runner](https://docs.revyl.com/infrastructure/maestro)).

## Beyond cloud simulators for agents: what else Revyl runs

Giving an agent a simulator is one of the jobs Revyl runs. The same account covers the rest:

- Web apps run in Chrome sessions that stream to your browser. Web is on every plan at $0.05 a minute and runs in its own lane of up to 100 sessions at once ([Web builds](https://docs.revyl.com/builds/web), [pricing](https://revyl.com/pricing/)).
- iOS simulators and Android emulators start from the dashboard, the CLI or an agent and stream to your browser or to an embed in your own pages ([sessions](https://docs.revyl.com/sessions)).
- Mac computers, at $0.05 a minute on Pro, are full macOS environments on demand: a desktop streamed to your browser, commands, files and processes through `revyl computer`, and GitHub Actions jobs with `runs-on: revyl-macos` ([Mac computers](https://docs.revyl.com/computers)).
- Atlas gives agents memory between runs: the screens, states and transitions earlier sessions observed, which agents query with `revyl atlas` and people open in the dashboard ([Atlas](https://docs.revyl.com/atlas)).
- One Revyl CLI and MCP server cover every runtime, so an agent that drives a simulator can also drive a browser or a Mac ([MCP](https://docs.revyl.com/agents/mcp)).
- Each test run leaves a report with video, a step timeline and logs, and Revyl posts a verdict on the pull request through proof of changes ([reports](https://docs.revyl.com/tests/reports), [proof of changes](https://docs.revyl.com/agents/proof)).

## Common questions

**How much does Limrun cost?**

Limrun's Trial is free with 120 one-time credits. Entry is $20/month (or $192/year) with 500 credits, and Individual is $200/month (or $1,920/year) with 5,000 credits; Company is custom. An iOS simulator uses 2 credits a minute and an Android emulator 1. Overage on Entry and Individual is $0.05 per credit. Source: limrun.com/pricing, checked November 2026.

**Is Limrun cheaper than Revyl?**

Not for iOS simulators. Revyl's Free plan includes up to 1,200 free device minutes a month on iOS, Android, web and Mac, and the allowance renews; Limrun's Trial is 120 one-time credits, which is 60 iOS simulator minutes. Past that, Revyl's $0.075 per device minute on iOS and Android is below Limrun's iOS rates of $0.08 a minute inside a plan's credits and $0.10 in overage. For Android emulators, Limrun's $0.04 in-plan and $0.05 overage rates are lower. Revyl's minutes also return a run report, an Atlas record and a pull-request verdict from proof of changes.

**Does Limrun have an MCP server?**

Yes. Limrun's organization-level MCP server at mcp.limrun.com has 16 tools for creating, driving and deleting iOS simulators and Android emulators. Builds and file uploads go through the lim CLI and SDKs instead. Revyl also ships an MCP server, alongside its CLI.

**Can I run my Appium or Maestro tests on Revyl like on Limrun?**

Revyl runs Appium and Maestro suites through a source-installed Appium driver and Maestro runner that attach to a Revyl session and support documented command sets; their docs list the commands each runs. Limrun lists support for Maestro, Appium and XCTest.

**Can I embed a live simulator in my web app with either?**

Yes. Limrun's RemoteControl component from @limrun/ui streams a simulator or emulator into a React app. Revyl's embed is an iframe that puts a live device in your own pages.

**Do Limrun and Revyl build iOS apps without a Mac?**

Yes, both build in the cloud. Limrun runs Xcode and Gradle sandboxes and bills them in credits per minute. Revyl's revyl build builds the app in Revyl's cloud and stores the finished build on your app, so you can launch it on a cloud iOS simulator or Android emulator straight away.

**What else does Revyl do?**

The CLI and MCP server your agents use for simulators also start web sessions in Chrome on every plan, iOS simulators and Android emulators, and full macOS computers, and Revyl builds iOS, Android and Web apps remotely. Each test run leaves a report, Atlas keeps the record of what the app does, and proof of changes posts a verdict on the pull request.

## Sources

- [Limrun pricing](https://limrun.com/pricing)
- [Limrun docs introduction](https://docs.limrun.com/docs)
- [Limrun remote MCP server](https://docs.limrun.com/docs/agents/remote-mcp)
- [Limrun GitHub Actions](https://docs.limrun.com/docs/ci/github-actions)
- [Limrun embed a simulator](https://docs.limrun.com/docs/platform/embed-simulator)
- [Limrun PR previews](https://docs.limrun.com/docs/ci/pr-previews)
- [Limrun Android emulator](https://docs.limrun.com/docs/android/run-emulator)
- [Revyl remote builds](https://docs.revyl.com/remote-builds)
- [Revyl device quickstart](https://docs.revyl.com/infrastructure/quickstart)
- [Revyl device infrastructure](https://docs.revyl.com/infrastructure)
- [Revyl MCP](https://docs.revyl.com/agents/mcp)
- [Revyl reports](https://docs.revyl.com/tests/reports)
- [Revyl Atlas](https://docs.revyl.com/atlas)
- [Revyl proof of changes](https://docs.revyl.com/agents/proof)
- [Revyl embed a live device](https://docs.revyl.com/devices/embed)
- [Revyl Appium driver](https://docs.revyl.com/infrastructure/appium)
- [Revyl Maestro runner](https://docs.revyl.com/infrastructure/maestro)
- [Revyl pricing](https://revyl.com/pricing/)
- [Revyl Web builds](https://docs.revyl.com/builds/web)
- [Revyl sessions](https://docs.revyl.com/sessions)
- [Revyl Mac computers](https://docs.revyl.com/computers)
- [docs.revyl.com/reference/mcp-tools](https://docs.revyl.com/reference/mcp-tools)
- [docs.revyl.com/builds/ci-builds](https://docs.revyl.com/builds/ci-builds)
