SolutionsRelease monitoring

Know the day a release breaks something

Scan on a schedule or from your CI pipeline. PixyScan compares each scan with the last one and alerts you by email, Slack or webhook when things get worse.

Start free Book a demo

app.pixyscan.com/w/…/s/…/changes

The Changes screen, with columns for new, resolved and still-open problems compared with the previous scan.

Common problems

Does this sound familiar?

If this sounds like your week, read on. Below is how PixyScan helps.

Traffic dropped in April, and it took weeks to trace it to a February release.
Your pipeline runs tests, but nothing checks that pages can still be found.
When a problem shows up, nobody can say which release caused it.

How PixyScan helps

Each card is a real screen in the app: what you see there and what you do with it.

01
See what changed
The Changes screen sorts problems into New, Resolved and Still open since the last scan of the same branch. Regressed marks a problem that now affects more pages.
02
Get alerted
Alerts go by email, to Slack or to any webhook when a scan finishes or fails, the score drops or a new critical problem appears. Set them in Settings → Alerts.
03
Stop bad releases in CI
From Basic up, add npx pixyscan-sdk run to your pipeline. It fails the build when the score drops too low, before the release goes live.

Getting started

Get started in 3 steps

Step 1
Run a first scan
Scan your live site once. Every later scan is compared with this one.
Step 2
Set a schedule and alerts
Choose daily or weekly scans in Settings → Schedule. In Settings → Alerts, send alerts by email, to Slack or to a webhook.
Step 3
Add a CI check
From Basic up, add npx pixyscan-sdk run to your pipeline. It catches problems before a release goes live.

Worth knowing

Scans run daily, weekly or monthly in your timezone. Missed scans are made up with one scan.
Reopen any past scan to see exactly when a problem first appeared.
Each scan records its branch, so preview runs never mix with your live site's history.

What it doesn’t do

Alerts cover four events, not single checks. The CI fail-on list can stop a build on one check.
No GitHub app. Nothing comments on pull requests.
It cannot name the commit that caused a problem. It names the first scan that found it.

Which tier fits

Start with Hobby or Basic

Hobby ($19 a month) is the first tier with scheduled scans and scan comparison, enough to catch a bad release within a day. Basic ($39 a month) adds the CI/CD check to stop it before it ships, with 5 sites and 10,000 pages per scan.

Compare prices

FAQ

Questions you might have

How soon after a release will I know?

As soon as the next scan finishes. That is your next scheduled scan, or straight away if your pipeline scans every deploy.

Can it tell me which commit caused the problem?

No. It tells you which scan first found it, with the branch, the time and the URLs. Your deploy log narrows it to a commit.

Will I get an email?

Yes. Alerts go by email, to Slack or to a webhook when a scan finishes or fails, the score drops or a new critical problem appears. Each email has a one-click unsubscribe link.

Can I get an alert for one specific check?

No. Alerts cover four events only. To stop a build on one check, add it to the CI fail-on list (Basic and above).