Skip to content

Developer tool / release check

DeployProof

DeployProof compares preview behaviour with production before a change is merged.

Open the working result View the source ↗

Role

Independent tool by Loke Development: design, engineering, and release checks.

Audience

Teams shipping public web applications through preview deployments and continuous integration.

TypeScriptNode.jsGitHub ActionsSARIFHTTP
DeployProof comparing a preview deployment with production before a merge.
Project view from the working product.

01 / Problem

What needed to be clearer.

A green build and a convincing screenshot cannot show whether redirects, headers, cookies, or metadata changed at the deployment boundary.

02 / Constraints

Boundaries shaped the work.

  • Stay read-only and avoid requiring an account or credentials.
  • Keep response bodies, cookie values, and custom request headers out of reports.
  • Fit local CLI use and GitHub Actions without a hosted dashboard.

03 / Decisions

The useful choices.

  • Compare the same request against preview and production.
  • Report readable terminal output, JSON, GitHub annotations, and SARIF.
  • Make timeouts, redirect limits, and body-size limits part of the safety boundary.

04 / Working result

See it in use.

A live CLI and GitHub Action that exposes deployment drift before merge.

Talk about a similar problem