Detox vs Waldo
Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.
Entry price
Free and open source
Open sourceQuote on request
Quote onlyWhat drives the bill
The metric that actually scales your invoice.
Free and open source. You pay in engineering time and CI minutes.
No longer priced as Waldo — it is part of a Tricentis Mobile quote, which is an enterprise sales conversation rather than the self-serve signup Waldo once had.
Free tier
Everything, self-hosted
Free trial.
Open source
MIT
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Widely used
Wix · since 2017
Emerging
Tricentis (formerly Waldo) · since 2019
Strengths
- Automatic synchronisation with the RN bridge eliminates most timing flake.
- Same JavaScript and Jest tooling the app team already uses.
- Fast execution because there is no external driver round trip.
- No SDK and no code — a designer or PM can record a regression flow.
- Self-healing keeps recorded flows working across releases.
- Runs on every build without device lab management.
Limitations
- React Native only — useless for native or Flutter apps.
- Requires building a special test binary, which complicates the pipeline.
- Grey-box coupling means an RN upgrade can break your test setup.
- You can no longer buy Waldo as such — it is a component of Tricentis Mobile, sold on an enterprise contract.
- Limited support for complex logic or data-driven scenarios.
- Cloud-only.
Best for
React Native teams that want low-flake E2E tests in their existing toolchain.
Tricentis customers extending into mobile. Small teams that wanted Waldo's self-serve simplicity should look at Maestro instead.
All of these integrate with: GitHub Actions, Bitrise, CircleCI.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.