Pricing anchored on the work a tester would do, not the seconds a machine takes to do it. You pay for outcomes — we absorb the noise.
We map your first 3–5 critical workflows and stand up real coverage against your sandbox — so you see it working before committing to a tier. Most pilots are live within 1–2 weeks.
Each plan gives you a pool of Protected UI Minutes — the time a tester would spend running your processes under ideal conditions. Scale as your cadence and coverage grow.
Annual commitment saves 15% and waives the one-time buildout fee. All prices in USD.
Every process is recorded once, on the real UI, under defined ideal conditions. That runtime is the price — and it stays fixed until the process materially changes.
If we metered raw server time, you'd pay more every time Salesforce had a slow day or our infrastructure retried a step. That's our problem, not your line item.
We set the meter on the time a real tester would take, doing the job correctly. Whether we replay it in 3 minutes or 12, your bill doesn't move. You're buying outcomes, not seconds.
Clean path, first try — no fat-fingering or backtracking.
No time for write-ups or ticket filing — the agent reports instantly.
Productive minutes only — pure execution time.
Excludes unusual Salesforce slowness or outages — a slow day doesn't punish you forever.
Warnings at 70 / 85 / 100% plus a grace buffer. You choose what happens at the cap — never silent throttling.
When your processes change, we re-record them. Every plan includes a monthly allowance; beyond it, billed transparently.
When a Salesforce release breaks a selector, we fix it within your SLA. Platform breakage is never a billable change.
A few things are quoted separately when you need them: unusually complex buildout, dedicated environments, longer retention, custom security review, and high-frequency per-PR CI gates.
Not your problem. The meter is set by ideal tester time, not wall-clock. Slow sandboxes and our own retries never appear on your invoice.
For the Salesforce regression layer, most teams don't. Customers redirect freed-up QA toward new-feature and exploratory testing.
Per-action billing punishes complexity and is hard to forecast. One intuitive unit — tester time — anchors to a real-world cost you can compare to a hire.
Yes, up or down, any time. Month-to-month by default; annual saves 15%. Your data and run history export on the way out.
Start with a pilot of your 3–5 most critical workflows.
Plan a pilot →