StageFlow

Find what to fix. See what your deployment changed.

StageFlow checks accessibility, SEO, links, and security. Start with a prioritized fix list, then compare the next run with your saved baseline.

Then pick up to 25 to scan.

Pages that block search indexing are reported as problems.

No account. Artifacts expire after 24 hours. Local projects stay in this browser.

Configure a scan · Compare releases in a local project

How it works

Save a reviewed scan as your baseline. StageFlow compares every later scan with it, so each deploy shows what it changed.

  1. 60

    Scan and save a baseline

    Point at a public URL, review the report, and keep it as your reference.

  2. 57

    Scan the next build

    The same pages again, each problem with page evidence and a specific fix.

  3. ▼ 3

    Review what changed

    3 new · 1 fixed in the real sample deployment.

Configure a scan Or create a local project

Five scanners, one merged report

Each runs in its own rootless container and merges into a single severity-ranked report — the same shape from the CLI, from CI, or from the browser.

Choose scanners

  • Axe Accessibility

    WCAG accessibility testing with axe-core engine

  • Lighthouse

    Accessibility, SEO, and best-practices audits

  • Link Checker

    Detect broken links and redirect chains

  • Security Headers

    HTTP security header analysis and scoring

  • SEO

    Meta tags, headings, and SEO optimization

CLI

$ stageflow diff baseline.json current.json --fail-on-new=anyScore: 60 → 57 (-3)New issues: 3Fixed issues: 1Unchanged: 30New Issues (Regressions):- [serious] Links must have discernible text (axe/link-name)  https://sample.stageflow.org/about.html  Selector: #careers-link- [critical] Select element must have an accessible name (axe/select-name)  https://sample.stageflow.org/pricing.html  Selector: #billing-cycle- [critical] Buttons must have discernible text (axe/button-name)  https://sample.stageflow.org/signup.html  Selector: #suggest-workspace$ echo $?1

Put regressions in your CI summary.

Scan a build, compare it with the reviewed baseline, and open the full report for evidence and fixes.

Explore the comparison →