For people who test by clicking around
You have an app to ship and no time to check every flow by hand. Describe the flows that matter once. Run them before a release, after a deploy, or whenever you want to be sure.
Ship every week without writing test code
You're building alone, a lot of the code came out of Cursor or Claude Code, and you're not going to write Playwright tests. Describe what should work, in a sentence or two, and an agent checks it in a real browser before your users do.
- Sign up and start your first run in under two minutes. No credit card.
- No selectors, so a layout change doesn't break the test
- Paste the replay link into your next bug-fix prompt
“It worked yesterday.”
Every developer has said it. Run the flow again and find out what changed, with a replay of exactly what the browser did.
Stop asking someone to click through the app before a release
Two to ten engineers, a staging URL, and a release checklist that takes an afternoon. Describe each critical flow once. Run all of them, for every role, at the same time, and get a replay for anything that fails.
- Up to 10 applications on Pro, unlimited on Team
- A saved login for each role, so Admin and Viewer both get checked
- Run history kept for 90 days on Pro and a year on Team
“Who tested the release?”
Five agents did, eleven minutes ago, and here are the replays. Anyone on the team can open a run and see what happened.
Common places to start
Most people start with checkout or signup. Each of these is one test to set up.
Check signup after every deploy
Connect GitHub, GitLab, or Vercel. After each successful deploy, an agent signs up with a fresh account and confirms it lands where it should.
“Sign up with a new email, confirm the welcome screen appears, and check the account shows up in settings.”
Try the code an AI wrote
Shipped a big change from Cursor, Claude Code, or v0? Have an agent walk through the affected flows before you promote it.
“Create a project, rename it, and check the new name appears in the sidebar.”
Login, checkout, and password reset
The flows that cost money when they break, and that nobody notices until a customer emails. Run them before every release.
“Add an item to the cart, pay with the test card, and confirm the order confirmation page loads.”
Run one flow in ten browsers
Send several agents through the same flow at once. Double submits and race conditions show up when real browsers overlap.
“Ten browsers sign up at the same time with different emails. Every account should reach the dashboard.”
Check what each role can see
Save a login for Admin, Viewer, and a second tenant. Confirm each one sees its own data and nothing else.
“Log in as Viewer and confirm the billing page can't be opened.”
Smoke test staging before you promote
Run your saved tests against staging before production. Come back to a pass or fail for each one, with a replay.
“Log in, open the most recent invoice, and download the PDF.”
Give your app a sanity check.
15 free runs a month. No credit card. Setup takes less than two minutes.