Maestro flows are easy. Pie writes them.
Stop editing a flow each time a screen changes. Pie’s agents write and run the tests, where Maestro’s YAML flows are your team’s to write and update.
Pie is an agentic testing platform whose agents explore your iOS and Android apps and write the tests, so your team has no flow files to write or maintain.
Maestro is a free, open-source CLI that runs UI flows on Android and iOS. Your team writes each flow in YAML.
Pie vs Maestro at a glance
- What it is
- An agentic testing platform for web, iOS and Android apps.
- Who writes the tests
- Pie’s agents explore your app and generate them. Your team adds the cases that matter in plain English.
- What a test is
- Plain-English steps and checks. No scripts to write, no locators to break.
- Where it runs
- iOS apps on the iOS Simulator, Android apps on the Android Emulator, and web apps in a browser. Nothing to install.
- AI help
- The whole product. Agents explore, write and run the tests, and group what they find into issues.
- What it is
- A free, open-source CLI that runs UI flows on Android and iOS, with web support in beta.
- Who writes the tests
- Your team, in YAML. Maestro Studio can turn your taps into commands.
- What a test is
- A YAML file of commands such as launchApp, tapOn and inputText.
- Where it runs
- On your own emulators, simulators and Android devices, or on Maestro Cloud’s hosted devices.
- AI help
- An MCP server for coding assistants, plus AI assertions its docs call experimental.
Five jobs in every mobile test. Who does each one?
A working mobile test needs an environment, a script, a device, upkeep and someone to read the failure. Here is who handles each part with Maestro, and who handles it with Pie.
MaestroYour team installs the CLI, Java 17 or higher, and Android Studio or Xcode for the virtual devices.
PieNothing to install. Upload an iOS simulator build or an Android APK.
MaestroYour team, one YAML flow per journey. Maestro Studio can generate commands from your taps.
PiePie writes it. Tell Pie Chat what to check, and it explores the flow and drafts the test for your OK.
MaestroYour own emulators, simulators and Android devices. Local Android runs go one device at a time. Parallel runs need Maestro Cloud, at $250 per device per month.
PieSimulators and emulators for iPhone, iPad and Android phones and tablets, on the OS version you pick.
MaestroYour team edits the flow. Self-healing with local agents is on Maestro’s free plan.
PieNo locators to repair. Pie re-reads the screen on every run.
MaestroYour team, from the report, the logs and a screenshot of the failing step.
PiePie groups related findings into issues. Your team decides what counts as a bug.
Four reasons to stop writing Maestro flows.
- 01
Easy to write is still written by you
A Maestro flow is short, readable YAML. Your team still writes one for every journey, so the suite covers the flows somebody found time for. Pie’s agents explore your running app and generate the tests.
Source - 02
The CLI is free. The flows aren’t.
The Maestro CLI is free. The cost is the people who write the flows and repair them. In one study, flaky tests alone took at least 2.5% of a team’s productive time. In Pie, nobody on your team writes or repairs a flow.
Source - 03
AI that still hands you YAML
It does. An MCP server lets a coding assistant write and run flows, and its AI assertions are marked experimental. The result is still YAML your team keeps and edits. Pie’s agents find the flows themselves.
Source - 04
Tests your whole team can read
A Maestro flow is YAML in a repo. Pie’s tests are plain-English steps anyone on your team can read or add to, on iOS and Android. Web testing is a core part of Pie too.
Who writes the flow, row by row.
Maestro makes a flow quick to write. Pie’s agents write it.
| What you’re comparing | Pie | Maestro | Advantage |
|---|---|---|---|
| Cost to run it | No scripts to write and no locators to break, so your team spends those hours on your product. | Your team’s hours to write and repair flows, plus your own devices or Maestro Cloud. | Pie |
| Getting started | Upload an iOS simulator build or an Android APK. You get results in hours, not weeks. | Install the CLI, Java, and Android Studio or Xcode, then write your first flow. | Pie |
| Writing a new test | Agents generate tests by exploring your app. Anyone on your team can add one in plain English. | Your team writes a YAML flow, by hand or by recording taps in Maestro Studio. | Pie |
| When the UI changes | No locators to update. Pie re-reads the screen on every run. | Flows find elements by text or ID. Self-healing with local agents is on Maestro’s free plan. Otherwise someone edits the YAML. | Pie |
| Web apps | Web testing is a core part of Pie. | In beta, on Chromium only, with a fixed viewport size and locale. | Pie |
| Fixing the bug | Pie groups related findings into issues, and can open a Fix PR in a repo you connect. Merging it is always your team’s call. | Maestro reports which step failed, with logs and a screenshot. Triage and the fix are your team’s. | Pie |
| License cost | Custom pricing, tailored to your team’s requirements and testing volume. Contact Pie for a quote. | The CLI is free and open source, under the Apache 2.0 license. Maestro Cloud is $250 per device per month. | Maestro |
Which fits your team, Pie or Maestro?
Pick Pie to
- Get mobile tests without writing a flow for each one.
- Test on iPhone, iPad and Android phones and tablets, on the OS version you pick.
- Give your team back the hours it spends writing and repairing flows.
- Run your suites on a schedule or on every new build, with nobody starting them.
- Bring your web app in when you’re ready.
Pick Maestro if
- Your team has the time to write a flow for every journey.
Switch from Maestro one flow at a time
No big rewrite. Your Maestro flows keep running until Pie covers the same journey.
- 1
Upload a build
Give Pie an iOS simulator build or an Android APK, or a URL for your web app. If the app has a login, add a test login through a supported path.
- 2
Let Pie explore
Pie explores your app’s reachable flows and generates tests. You get results in hours, not weeks.
- 3
Add your edge cases
Type the cases only your team knows into Pie Chat in plain English. Pie explores each flow, drafts the test and runs it once you confirm.
- 4
Retire flows as Pie covers them
Compare Pie’s results with your Maestro runs, and delete each YAML flow once Pie covers the journey.
FAQ
Did we miss a question?
Email us directly →
Yes. Pie replaces the flows your team writes and maintains with tests its agents generate by exploring your app.
The Maestro CLI is free. Stay if your team has the time to write a flow for every journey.
The Maestro CLI is free and open source under the Apache 2.0 license. Maestro Cloud, which adds hosted devices and parallel runs, costs $250 per device per month.
The other cost is your team’s time to write the flows and keep them passing. In one study of about 30 developers over five years, flaky tests alone took “at least 2.5% of the productive developer time”.
Maestro ships an MCP server that lets a coding assistant write and run flows, and AI assertion commands its docs call experimental. A person still decides what to test, and the result is YAML your team keeps and edits.
Pie’s agents find the flows by exploring your app, and the tests stay in plain English.
Real devices are available on demand. Pie runs iOS apps on iOS simulators and Android apps on Android emulators, on the OS version you pick.
Our guide to real devices, emulators and simulators covers which bugs need which.
Yes, and both are in beta. Pie runs whole API flows call by call, and checks each screen its tests reach for accessibility problems.
Your UI, API and accessibility testing sit in one place.
Whoever owns quality today, such as a QA lead or an engineer who owns releases. Pie does the exploring, writing and re-running, and the owner decides what matters and what counts as a bug.
Anyone on the team, including a product manager, can read a test or add one in plain English.
Pie’s pricing is custom, tailored to your team’s requirements and testing volume.
You buy one product: agents explore your web, iOS and Android apps, write and run the tests, group related findings into issues and can open a Fix PR.
Book a demo, tell us what you ship and how often you release, and we’ll send you a quote.
Stop writing flows. Start reading results.
Book a demo and bring the journey you haven’t had time to write a flow for. We’ll show you Pie testing it.
Sources
- Maestro on GitHub. Apache 2.0 license; flows run on emulators, simulators, browsers and physical Android devices; “Physical iOS devices are not yet supported.”github.com/mobile-dev-inc/Maestro
- Maestro pricing. Local plan free and open source, listing self-healing with local agents; Cloud at $250 per device per month with hosted devices and parallel runs; Enterprise Cloud custom.maestro.dev/pricing
- Maestro quickstart. Flows are YAML files with an appId and a list of commands; local runs need Java 17 or higher and Android Studio or Xcode for virtual devices.docs.maestro.dev/get-started/quickstart
- Maestro docs, React Native. Recommends targeting a testID over text, which breaks when labels change or are translated.docs.maestro.dev/get-started/supported-platform/react-native
- Maestro docs, Android. Local runs use one device at a time; parallel runs need Maestro Cloud.docs.maestro.dev/get-started/supported-platform/android
- Maestro docs, web browsers. Beta; Chromium is the only supported browser; the locale and viewport size are fixed.docs.maestro.dev/get-started/supported-platform/web-browser
- Maestro docs. The Maestro MCP server ships in the CLI for coding assistants; assertWithAI is described as an “experimental feature”.docs.maestro.dev/get-started/maestro-mcp · docs.maestro.dev/reference/commands-available/assertwithai
- Cost of Flaky Tests in CI, ICST 2024 industry track. Five years of history, about 30 developers, one commercial project; “at least 2.5% of the productive developer time”. Not specific to Maestro.conf.researchr.org/details/icst-2024/icst-2024-industry/1