Trailcam vs Maestro Cloud

Both run your Maestro flows on hosted simulators and emulators, from CI. Trailcam also checks them around the clock against your production build, opens an incident when one breaks, and tells you why.

Start free See pricing

What sets them apart

Production checks built in
Trailcam runs a flow against the build your customers have as often as every 5 minutes, runs a failure again at once, and opens an incident on the second. Maestro Cloud runs when you or your CI start it.
Pay for runs, not devices
Maestro Cloud is $250 a month for each concurrent device. Trailcam's Team plan is $249 a month, with 5 concurrent runs per platform and 25,000 runs.
Why it failed, on every plan
Trailcam AI reads the screen at a failure, names the likely cause, and suggests the change when the flow is what's out of date.

Side by side

Maestro Cloud's side as its own pages describe it, on October 23, 2026.

Devices and flows

Devices: TrailcamPhones, tablets and a foldable, as iOS simulators and Android emulators: a clean one for every run; Maestro CloudVirtual iOS and Android devices, wiped between tests
Builds: TrailcamAn iOS simulator build, an Android APK; Maestro CloudAn iOS simulator build, an Android APK
Flows: TrailcamMaestro 2, apart from features that read files from your computer or make web requests; Maestro CloudMaestro flows
Writing flows: TrailcamFound in your build and written by Trailcam AI, from a description, or in the editor, which suggests every command; Maestro CloudMaestro Studio, on your computer

Production checks

On a schedule: TrailcamEvery 5 minutes on Team and Business, 15 on Starter; Maestro CloudOn your CI's own schedule
Incidents and uptime: TrailcamYes; Maestro CloudNo
Alerts: TrailcamEmail, Slack and webhooks; PagerDuty on Business; Maestro CloudEmail, Slack and webhooks, after a run

When a run fails

What you see: TrailcamA recording in step with the flow, the screen at the failure and the device's log; Maestro CloudA video of the steps, and logs

CI

From CI: TrailcamA GitHub Action and a command-line tool, with guides for GitLab, Bitrise, CircleCI, Codemagic, Xcode Cloud and EAS Build; Maestro CloudThe maestro command-line tool
Pull requests: TrailcamA status check, and one comment with every flow's result; Maestro CloudA comment, and a check that can block the merge

Price

What you pay for: TrailcamRuns, with everyone on your team included; Maestro CloudPer concurrent device
Price: TrailcamFrom $49 a month; Team $249, with 5 concurrent runs per platform; Maestro Cloud$250 a month for each concurrent device
To try it: Trailcam200 runs a month on Android, for as long as you like; Maestro CloudA free trial

Trailcam and Maestro Cloud, feature by feature
Devices and flows
	Trailcam	Maestro Cloud
Devices	Phones, tablets and a foldable, as iOS simulators and Android emulators: a clean one for every run	Virtual iOS and Android devices, wiped between tests
Builds	An iOS simulator build, an Android APK	An iOS simulator build, an Android APK
Flows	Maestro 2, apart from features that read files from your computer or make web requests	Maestro flows
Writing flows	Found in your build and written by Trailcam AI, from a description, or in the editor, which suggests every command	Maestro Studio, on your computer
Production checks
On a schedule	Every 5 minutes on Team and Business, 15 on Starter	On your CI's own schedule
Incidents and uptime	Yes	No
Alerts	Email, Slack and webhooks; PagerDuty on Business	Email, Slack and webhooks, after a run
When a run fails
What you see	A recording in step with the flow, the screen at the failure and the device's log	A video of the steps, and logs
CI
From CI	A GitHub Action and a command-line tool, with guides for GitLab, Bitrise, CircleCI, Codemagic, Xcode Cloud and EAS Build	The maestro command-line tool
Pull requests	A status check, and one comment with every flow's result	A comment, and a check that can block the merge
Price
What you pay for	Runs, with everyone on your team included	Per concurrent device
Price	From $49 a month; Team $249, with 5 concurrent runs per platform	$250 a month for each concurrent device
To try it	200 runs a month on Android, for as long as you like	A free trial

5 concurrent runs on each platform

5 concurrent runs on iOS and 5 on Android, and 40,000 runs a month: a busy team's pull requests and production checks.

Trailcam

$399a month

Team, $249, has 5 concurrent runs per platform, with 25,000 runs and 15,000 more at $10 per 1,000.

Maestro Cloud

$2,500a month

10 devices at $250 each, priced per concurrent device.

Choose Trailcam if

You want your journeys checked in production, with incidents and alerts, not only on pull requests.
You want to know why a run failed, and the change that fixes the flow.
You need several concurrent runs and would rather pay for runs than for each device.
You'd like people who don't write YAML to describe a journey and get a flow.

Maestro Cloud may suit you better if your flows read files from your computer or make web requests.

Moving from Maestro Cloud

Your flows run on Trailcam as they are: paste one into a project's editor, and upload your builds from CI with Trailcam's GitHub Action or command-line tool. The editor marks the few Maestro features a hosted device can't use.

What flows can't do on Trailcam

Where this comes from

What we say about Maestro Cloud is from its own pages, as they were on October 23, 2026. Prices change: if something here is out of date, tell us and we'll put it right.

Maestro and Maestro Cloud are mobile.dev's. Trailcam runs flows written for the open-source Maestro framework, and isn't affiliated with or endorsed by mobile.dev.

More comparisons

Find out before your customers do

Start with the journey that would hurt most if it broke, usually sign-up or checkout. One reliable check beats ten flaky ones.