It finds the flows
you forgot existed
Journey found · Buy a product
8 kinds of page
1
URL to start
No sitemap, no recorder and no test plan to hand over.
40
kinds of page tried
Product pages, carts, search, forms and menus, each used like a person would.
3
clean replays
A recorded flow is tested only after it passes three times in a row.
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.
Tried like a person
An agent opens each kind of page and uses it: picks a size, adds to cart, searches.
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
New kinds of pages, or a week since the last look, send Regress back to learn.
Your scope
Exclude paths like /admin or /blog and choose whether subdomains count.
Questions
Questions about discovery
Will it click delete buttons?
No. Until you allow more, Regress only reads, and any request that would change your data is blocked. In a signed-in app it creates and deletes only its own records, and only after you confirm it's a test account.
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.