Regress

The bug report
writes itself

Sign upAlerts guide
When something breaks you get an alert where your team already looks, and a report with the flow, the step, the timing, a screenshot and the console error. No digging through CI logs.
CheckoutFailed
  1. Open /checkout412ms
  2. Fill in the card160ms
  3. Accept the terms74ms
  4. Click “Pay”5000ms
Copy report linkExport JSON
step 4 · screenshot

Payment

Pay $42.10

Pay button disabled

Waited 5s for it to become clickable.

console: TypeError: Cannot read properties of undefined (reading 'total')

Where it lands

Wherever your team
already looks

All integrations
Pick the channels per project. Each one carries enough detail to start fixing without opening anything else.

GitHub

A check run on the pushed commit and a comment on its pull request.

Slack

The project, what changed and a link straight to the report.

Email

Affected pages sorted by severity, for whoever owns the app.

The report

Timings for every step and screenshots captured during the flow, kept for up to 90 days.

Questions

Questions about reports

How long are results kept?

7 days on Free, 30 days on Starter and 90 days on Professional.

Can I share a report with someone who isn't on Regress?

Copy the report link to share it with your team, or export the whole run as JSON for your own tools.

Will I get alerted for every tiny change?

No. Data changes are ignored by design. Alerts are for broken flows and real structural regressions.

Can I wire results into my own systems?

Yes. Poll the scan status endpoint from CI, or export runs as JSON. The API guide has the details.

Get better bug reports than your users write

Free for 500 pages a month. Results land where you already work.

Sign upSee pricing