On this page
Maestro vs Revyl: Maestro runs YAML UI flows locally or on Maestro Cloud, and Revyl runs web browsers, cloud iOS simulators, Android emulators and macOS computers, builds the app, runs natural-language and YAML tests with a report for each test run, and can post a pull-request verdict through proof of changes. As of November 2026, 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.
Scroll the table sideways to see all 2 columns.
What is the difference between Maestro and Revyl?
Maestro is an open-source UI automation framework. You write tests as YAML flows, and Maestro drives the app through its visual and accessibility layers, so one syntax works for native Android and iOS apps, React Native, Flutter and web (supported platforms). The CLI, Maestro Studio and the Maestro MCP server are free. Maestro Cloud adds hosted devices, parallel runs, reporting and pull-request integration.
Revyl is a cloud runtime for coding agents and teams. For iOS and Android apps, the Revyl CLI builds the app in the cloud, starts a cloud iOS simulator or Android emulator, and runs tests written as natural-language steps or YAML. Each test run produces a report and adds observed evidence to Atlas, and with Proof of changes, Revyl posts a verdict on the pull request.
Who should pick Revyl?
Pick Revyl when an agent or a reviewer needs the app built, run and recorded without local Macs or emulators. The loop has five steps:
- Build. revyl build runs your build commands on cloud runners and stores the artifact.
- Run. revyl device start launches a cloud iOS simulator or Android emulator with that build and prints a live viewer link (device quickstart). Workflows run groups of tests in parallel up to your organization’s device concurrency.
- Capture evidence. Every test run produces a report with video, a step timeline, CPU and memory, and device logs, plus FPS on iOS runs and network traffic for iOS and debuggable Android builds.
- Add to Atlas. Atlas fills in from observed runs (sessions, tests and explorations), grouping the screens, states and transitions they saw, each tied to its screenshots.
- Prove it on the pull request with proof of changes: Revyl installs the PR’s build, exercises the changed flows and posts a verdict with findings, screenshots and a verification confidence score.
Revyl tests can be natural-language steps, so a test can say “Tap the Sign In button” instead of naming a selector (first test guide).
How does pricing compare?
Revyl, as of November 2026 (revyl.com/pricing):
- Free: $0, with up to 1,200 free device minutes a month on iOS, Android, web and Mac and 2 devices at once, no card needed.
- Pro: pay as you go at $0.075 per device minute on iOS and Android and $0.05 a minute on web and Mac, with 10 devices at once, free minutes every month, a $20 starting credit and no monthly fee.
- Enterprise: custom, with volume pricing and unlimited devices at once.
- Every plan has unlimited developers and agents, with no seat fees.
Maestro (maestro.dev/pricing):
- Local: free and open source on your own devices.
- Cloud: $250 per device per month. The monthly price is based on your maximum concurrent executions, with unlimited hosted test runs.
- Enterprise Cloud: custom. Web/Chromium device pricing is on request.
Revyl’s Free plan begins with hosted usage: up to 1,200 free device minutes a month on iOS, Android, web and Mac, and Pro is pay as you go at $0.075 per device minute on iOS and Android. Maestro’s free option is local runs on your own devices, and Maestro Cloud bills for parallel capacity at $250 per device per month (Maestro pricing). On Revyl the total depends on the device minutes you use.
Each test run also leaves a report with video, a step timeline and logs, plus network traffic for iOS and debuggable Android builds.
Can Revyl replace Maestro Cloud?
For hosted iOS and Android runs, yes. Revyl builds the app, runs it on cloud simulators and emulators, runs groups of tests in parallel workflows, and gates pull requests from a CI job or with proof of changes. Existing flows can move through the Maestro runner or a revyl-macos job, both covered below, or become natural-language Revyl tests.
Maestro also runs free on your own devices, including physical Android devices (supported platforms).
Can existing Maestro flows run on Revyl?
Yes, in two ways. Revyl’s Maestro runner runs supported flows against a Revyl session. It embeds the Maestro 2.10.0 runtime and runs assertions, taps, long presses, text input, key presses, deep links, location, dark mode, screenshots, and runFlow with visible, notVisible and platform conditions. The runner is built from source with Java 21 and runs against a session where the app is already installed and launched.
You can also run existing Maestro iOS flows in a GitHub Actions job with runs-on: revyl-macos, which gets a single-use Revyl Mac with Xcode and the iOS Simulator (cookbook).
How do you move from Maestro Cloud to Revyl?
Build or upload your app with revyl build, start a session with revyl device start, and run a supported flow with the revyl-maestro launcher and that session’s ID. Other flows move over as Revyl tests. The migration guide has the full steps.
Beyond mobile UI testing: what else Revyl runs
YAML flows and natural-language tests on cloud devices are one part of a Revyl account. The same account and CLI also cover:
- Web apps run in Chrome. A Web session runs the app from a bundle Revyl builds or a deployed preview URL you register, and natural-language tests run against it the same way as against iOS and Android builds. Web is on every plan.
- iOS simulators and Android emulators start in the cloud with your build. revyl device start launches one and prints a live viewer link (device quickstart).
- macOS computers give an agent or a person a full macOS environment in the cloud with Xcode and the iOS Simulator, started, used and stopped on demand, with the desktop streaming live to the browser (Mac computers). revyl computer exec runs commands such as xcodebuild test, and a GitHub Actions job with runs-on: revyl-macos gets a single-use Revyl Mac (GitHub Actions guide).
- Atlas fills in from observed runs and keeps the screens, states and transitions they saw, each tied to its screenshots, as the record of what the app does.
- Coding agents start and drive sessions through the Revyl CLI and MCP server.
- Every test run produces a report with video, a step timeline and logs, and with 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.
- Maestro docs: what is Maestro
- Maestro docs: supported platforms
- Maestro docs: iOS
- Maestro pricing
- Run tests on Maestro Cloud
- Maestro Cloud limits
- Maestro pull request integration
- Maestro MCP
- Maestro releases
- Revyl Maestro runner
- Revyl device quickstart
- Revyl remote builds
- Revyl first test from the CLI
- Revyl workflows
- Revyl reports
- Revyl Atlas
- Revyl proof of changes
- Revyl MCP setup
- Revyl pricing
- docs.maestro.dev/maestro-cloud/readme.md
- docs.revyl.com/concepts
- docs.revyl.com/reference/mcp-tools
- maestro.dev/blog/security-milestone-soc-2-type-2
- trust.revyl.com
Frequently asked questions
Is Revyl an alternative to Maestro Cloud?
Yes, if you want hosted iOS simulators and Android emulators plus cloud builds, test-run reports, Atlas evidence from observed runs and, with Proof of changes, a pull-request verdict. Existing flows can run through Revyl's Maestro runner, or as Maestro iOS flows in a GitHub Actions job on a Revyl Mac. Maestro also runs free on your own devices, including physical Android devices (docs.maestro.dev supported platforms).
Can I run my Maestro YAML flows on Revyl?
Partly. Revyl's Maestro runner is source-installed. It embeds Maestro's YAML parser and execution engine with a Revyl device driver, and runs against an existing Revyl iOS simulator or Android emulator session. It runs commands including assertVisible, tapOn, inputText, runFlow with visible, notVisible and platform conditions, and env parameters, and its docs list its full command set. Flows built on JavaScript, optional commands or retry blocks move over as Revyl tests.
How much does Maestro Cloud cost?
As of November 2026, Maestro Cloud is $250 per device per month, and the monthly price is based on your maximum concurrent executions. Local Maestro on your own devices is free and open source. Enterprise Cloud is custom-priced, and web/Chromium device pricing is on request.
How much does Revyl cost?
As of November 2026, Revyl's Free plan is $0 and includes up to 1,200 free device minutes a month on iOS, Android, web and Mac and 2 devices at once, no card needed. Revyl's Pro plan is pay as you go at $0.075 per device minute on iOS and Android and $0.05 a minute on web and Mac, with 10 devices at once, free minutes every month, a $20 starting credit and no monthly fee. Enterprise is custom.
Do Maestro and Revyl work with coding agents?
Yes. The Maestro MCP server ships inside the Maestro CLI and lets agents such as Claude Code and Codex write, run and debug flows. Revyl's MCP server and CLI let an agent build the app, start a cloud iOS simulator or Android emulator, drive it, run tests and read each test run's report.
What else does Revyl do?
Besides running supported Maestro flows on cloud iOS simulators and Android emulators, Revyl runs web apps in Chrome sessions and gives agents and people full macOS computers in the cloud with Xcode and the iOS Simulator. Atlas fills in from observed runs as the record of what the app does, coding agents drive sessions through the CLI and MCP, and test runs produce reports, with a pull-request verdict from proof of changes.