Tests the half of your app
behind the login

Most of your product lives after sign-in, and that's exactly where most testing tools give up. Record your login once and every scan gets in, checks it worked, and tells you when it didn't.

Six ways in

Whatever your login,
there's a way in

Recording covers almost everything. The other five are there for the logins that need something specific.

Safeguards

Handled like the keys they are

Security details

Encrypted

Passwords, tokens and recorded steps are encrypted with AES-GCM before they're stored.

Verified before scanning

Recorded and password logins are checked before pages are visited, and the last success is shown in settings.

Masked everywhere

The dashboard shows a masked username and never the password.

Questions

Questions about signed-in testing

Does it work with SSO and 2FA?

Yes. Record the login in a live browser with whatever provider you use. For 2FA on a scripted login, add the shared TOTP secret and Regress generates the code.

Should I use my own account?

Use a dedicated test account with normal user permissions. Tests click through your app like a person would.

What if the login stops working?

For recorded and password logins, the scan reports auth failed, keeps scanning your public pages and shows the problem in Project settings. Record the login again and you're back.

Can different projects use different logins?

Yes. Each project has its own sign-in setup.

Test what your users actually see

Free for 500 pages a month. Record a login in under a minute.

Tests the half of your app behind the login

Whatever your login, there's a way in

Handled like the keys they are

Questions about signed-in testing

Test what your users actually see

Tests the half of your app
behind the login

Whatever your login,
there's a way in