Waldo vs Detox
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
Quote on request
Quote onlyFree and open source
Open sourceWhat drives the bill
The metric that actually scales your invoice.
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 and open source. You pay in engineering time and CI minutes.
Free tier
Free trial.
Everything, self-hosted
Open source
MIT
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Emerging
Tricentis (formerly Waldo) · since 2019
Widely used
Wix · since 2017
Strengths
- 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.
- 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.
Limitations
- 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.
- 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.
Best for
Tricentis customers extending into mobile. Small teams that wanted Waldo's self-serve simplicity should look at Maestro instead.
React Native teams that want low-flake E2E tests in their existing toolchain.
All of these integrate with: Bitrise, GitHub Actions, CircleCI.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.