Waldo vs Autify
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 onlyQuote on request
Quote onlyWhat 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.
Quote-based annual contracts sized by test runs.
Free tier
Free trial.
Two-week free trial.
Open source
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Emerging
Tricentis (formerly Waldo) · since 2019
Emerging
Autify, Inc. · since 2016
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.
- Very low barrier to a first working suite — recording plus a managed browser cloud.
- Maintenance burden is genuinely reduced by the self-healing model.
- Covers web and native mobile from one vendor.
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.
- No self-hosted option.
- Limited support for complex data-driven scenarios.
- Smaller international presence and support footprint than the US vendors.
Best for
Tricentis customers extending into mobile. Small teams that wanted Waldo's self-serve simplicity should look at Maestro instead.
Small QA teams that need automation without an engineering hire.
All of these integrate with: GitHub Actions, CircleCI, Slack, Jira.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.