It finds the flows
you forgot existed
Journey found · Buy a product
6 pages · 2 states
1
URL to start
No sitemap, no recorder and no test plan to hand over.
7
levels deep
Modals in tabs in drawers are explored, not skipped.
50
states per page
Room for every tab, dialog and menu a page can show.
16
step types
Enough to express real journeys and real assertions.
What it understands
Built for real apps,
not demo sites
Dynamic routes
Thousands of /product/:id pages are recognised as one route, not crawled forever.
Hidden states
What only appears after a click gets found, fingerprinted and tested too.
Behind your login
Record a login once and discovery covers everything your users see after it.
Journeys, not pages
Tests follow a user across pages, the way real bugs do.
Kept up to date
When a page changes, its journeys are re-read and the tests follow along.
Your scope
Exclude paths like /admin or /blog and choose whether subdomains count.
Questions
Questions about discovery
Will it click delete buttons?
Exploration skips anything labelled delete, remove, revoke, disable and similar. It does fill in and submit ordinary forms, so point it at a test account or a staging app.
What about pages behind a login?
Record a login once in a live browser, with SSO or 2FA if you use them. Every scan signs in the same way before discovery starts.
Does it handle single-page apps?
Yes. Pages are rendered in a real browser and Regress waits for the network, loading boundaries and the DOM to settle before it reads anything.
Can I keep it out of parts of my app?
Yes. Add excluded paths in Project settings and choose whether subdomains are part of the scan.
Find out what your app really does
Free for 500 pages a month. One URL is all it takes.