Kobiton 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
From $83 per month (Startup, 500 device minutes)
Free tierQuote on request
Quote onlyWhat drives the bill
The metric that actually scales your invoice.
Startup includes 500 device minutes a month; Accelerate is $399 for 3,000. Priced by device minutes and concurrent sessions, and the on-premise hybrid option is licensed separately.
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
Free trial with limited device minutes.
Free trial.
Open source
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Emerging
Kobiton · since 2016
Emerging
Tricentis (formerly Waldo) · since 2019
Strengths
- Hybrid model lets you keep sensitive devices in-house while using one interface.
- Manual session recording converts into Appium scripts, shortening authoring.
- Cheaper than the top-tier enterprise clouds.
- 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
- Smaller device catalogue than BrowserStack or Sauce Labs.
- Generated Appium scripts still need substantial cleanup.
- Mobile only.
- 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
Mobile teams that want a device cloud but must keep some devices on premises.
Tricentis customers extending into mobile. Small teams that wanted Waldo's self-serve simplicity should look at Maestro instead.
All of these integrate with: Jira, GitHub Actions.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.