Post-deploy verification

Did the deploy actually work?

DeployProof logs in as every user role, crawls your site safely, runs the flows that matter, and tells you exactly what broke — before your users find it.

Read-only by default · runs in CI or on a schedule · no agent to install.
How it works

Three steps, no agent

Point it at a URL and a test login. DeployProof does the rest.

01

Point & verify

Give it your URL and a dedicated test login. Prove you own the domain with a DNS record or token file.

02

Log in & crawl safely

It signs in as each role and crawls read-only — following links, never clicking buttons or submitting forms.

03

Get the verdict

Broken pages, failed requests, console errors, and flow failures — as a report, in CI, or on your dashboard.

Safe by construction

An authenticated crawler you can trust

A logged-in bot can delete data or wander off-site. DeployProof is built so it can't — these controls are on by default and can't be switched off.

✓

Read-only crawl

Discovers pages via links only. POST/PUT/DELETE are blocked outside your login.

✓

SSRF & metadata guard

Any request to a private, loopback, or cloud-metadata address is refused.

✓

Scope lock

Navigation is confined to the domains you verify. Redirects off-scope are stopped.

✓

Destructive routes skipped

Logout and routes like /account/delete are never visited.

✓

Secrets redacted

Passwords, tokens, cookies, and auth headers are scrubbed from every report.

✓

Production protection

Production scans need explicit confirmation; data-changing flows are refused there.

What it checks

The things that break a release

Crawling proves pages load. User flows prove features actually work.

✓
Broken pages — 5xx, unexpected 4xx, failed navigations
✓
Failed requests — dead subresources and API calls
✓
Console errors — uncaught exceptions and error logs
✓
Auth redirects — logged-in users bounced to login
✓
Broken links — internal links that 404
✓
User-flow failures — your critical flows, step by step
Fits your pipeline

Gate every deploy in CI

One call, a clear exit code, and reports your pipeline can read.

Run a hosted scan after deploy and fail the build if the site is broken. JSON, HTML, and JUnit reports come back for your CI to publish.

exit 0 · passed exit 1 · findings exit 2 · error
# .github/workflows/deploy.yml
- name: Verify the deploy
  run: deployproof ci run \
    --target staging --wait
  env:
    DEPLOYPROOF_API_KEY: ${{ secrets.DEPLOYPROOF }}

Know your deploy works.

Set up your first scan in minutes. Read-only, safe, and honest about what it finds.