ReqProof Back to overview
Customer install surface

Install paths for connected and offline teams.

ReqProof ships as a product binary. Use the connected install paths for day-to-day developer onboarding, or mirror the same approved artifacts into an internal environment for air-gapped and controlled enterprise deployments.

Connected install

Use the rolling latest channel when you want the newest merged build.

Homebrew tap

Offline install

Mirror approved tarballs or Linux packages into your internal artifact store. ReqProof itself works offline after installation.

  • Download the approved artifact and the matching checksums file from a connected environment.
  • Mirror the files internally under your own approved distribution path.
  • Install proof from that mirrored archive or package.
  • Run proof version to confirm version, commit, and build date.
For strict offline verification, pre-stage Kind2 and Z3 and run with REQPROOF_NO_DOWNLOAD=1.

Release channels

ReqProof maintains two customer-facing channels: a rolling latest channel refreshed from merges to main, and immutable tagged releases under https://downloads.reqproof.com/releases/<version>/.

Use latest for fast internal adoption. Use tagged versions for pinning, approvals, and reproducible customer support.

Need a mirrored or licensed enterprise rollout? Contact hello@reqproof.com.