What they genuinely get right
Fastest zero-to-first-test
Sign up, type a sentence, watch a cloud browser go. The onboarding in this category is genuinely excellent, and it raised the bar for everyone — including us.
Managed cloud infrastructure
Parallel cloud browsers with nothing to install. We will say it plainly: our cloud browsers and parallel runs are coming — today they have this and we do not.
One vendor, one bill
No API keys to procure, no provider accounts. For teams that want a single line item and zero setup decisions, that simplicity is real.
The credit is doing a lot of work
A "credit" is an abstraction with one job: stop you from seeing what the underlying model call cost. Once cost is invisible, three things follow.
- The markup is unknowable. You cannot compare a credit to a provider's list price, so you cannot know what you are really paying for AI — or notice when the rate quietly changes.
- Cloud browsers stop at your VPN. A browser in their cloud cannot reach staging behind your VPN, hold your SSO session, or use your real logged-in state. The apps that most need testing are exactly the ones it cannot reach.
- Your tests live in their format. Export is an afterthought when lock-in is the business model. Leaving means rewriting.
Your browser. Your key. Your files.
Runs in your own Chrome
Real logged-in sessions, behind VPN and SSO, on the machine that already has access. No allowlisting, no tunnel, no test-only auth path built just for the vendor.
BYOK, at cost, metered live
Anthropic, Bedrock, Gemini, or Groq — model spend passes through at the provider's list price with a live meter and a hard budget ceiling. No key? Managed credits at provider price + 15%, both numbers shown.
Portable by default
Tests are human-readable YAML you can open in any editor. The whole stack self-hosts on Node + Postgres. Leaving is a copy, not a migration project.
Verdicts you can trust
Pass, fail, or blocked with screenshots; failures re-driven by a stronger model; flaky passes labeled "passed on retry". Healing that silently accepts a wrong page is not healing.
Side by side
| Credit-metered AI SaaS | TestAutomate | |
|---|---|---|
| Where the AI cost lives | Inside a credit — markup invisible | On your key at provider list price, metered live |
| Browser | Theirs, in their cloud | Yours — real sessions, real access |
| Behind VPN / SSO | Requires tunnels or allowlisting, if possible at all | Works today, because it is your Chrome |
| Parallel cloud runs | Yes, today | coming |
| Test format | Proprietary | Portable, human-readable YAML |
| Self-hosting | Rarely offered | Full stack: Node + Postgres |
Still the right choice for: teams testing fully public apps who want managed parallel cloud runs today and would rather pay a markup than manage an API key. That is a coherent trade. If your app lives behind a login, a VPN, or SSO — read how execution works and the BYOK economics post first.
See the meter before you spend a cent
Bring a key or start on transparent credits. Either way, you will always know what a run cost — to the cent, at list price.