Product State Hash
5b1f0e8f3c8a7d9e2a1b4c6d8e4f2a7c1b0d9e3f8a6c4b1dReleaseNotary runs core flows on each PR or release build and gives reviewers proof packets they can inspect before merge.
5b1f0e8f3c8a7d9e2a1b4c6d8e4f2a7c1b0d9e3f8a6c4b1dEVI-7G4K2LHomepage renderEVI-9H2M1NPricing reviewEVI-3P8Q7RLogin redirectEVI-T16U5VCheckout stateReleaseNotary: REVIEW REQUIRED. Pricing disclosure changed; inspect hosted packet before merge. Product State Hash: 5b1f0e8f3c8a7d9e2a1b4c6d.
Teams use ReleaseNotary for flows where a quiet regression can block revenue, trust, or compliance.
Plan changes, checkout behavior, cancellation paths, receipts, and upgrade/downgrade copy.
Login redirects, public/private route boundaries, invite flows, and unauthenticated access surprises.
Signup, workspace creation, trial starts, guided setup, and first-success moments.
Admin actions, team roles, plan gates, seat limits, and sensitive account controls.
Prompt-driven UX, model responses, disclosure language, deterministic content, and risky answer shifts.
Policy links, consent copy, cancellation language, pricing qualifiers, and required notices.
Bring one repo, a working PR or release build, and the flows your team worries about. We set up the review path and run it across real release work.
Connect the build. Run the core flows. Give reviewers evidence they can read.
Use the GitHub PR, preview deployment, staging build, or release candidate your team already reviews.
We configure the flows where a silent regression would hurt customers or block revenue.
Reviewers get a packet, PR comment, risk flags, and release record they can read.
ReleaseNotary saves screenshots, notes, flags, and files for the release review. Reviewers see changed behavior without reading raw diffs.
A structured bundle with flags, evidence links, PR context, release notes, and the raw files behind them.
A stable ID for product behavior in that run, separate from the commit or deployment ID.
Explainable product-risk signals across access gates, disclosures, billing, AI behavior, and critical flows.
Reviewer-ready notes with changed behavior, review points, and evidence links.
Screenshots, DOM, visible text, logs, diffs, and configured capture output with redaction.
Compact PASS/FAIL feedback in the PR, with the richer review kept on hosted proof pages.
A reusable operator check that confirms hosted access, GitHub feedback, and leak hygiene.
Executive, product, developer, and agent-ready briefs that open in the hosted packet and export when needed.
Different tools answer different release questions.
| Capability | ReleaseNotary | Code review: GitHub, GitLab, CodeRabbit | Visual QA: Chromatic, Percy, Applitools | Observability: Datadog, Sentry, New Relic | Compliance: Vanta, Drata, Secureframe |
|---|---|---|---|---|---|
| Primary focus | Product behavior on a live preview | Code quality and implementation changes in GitHub, GitLab, or AI review tools | UI appearance consistency in tools like Chromatic, Percy, or Applitools | Runtime health and performance in Datadog, Sentry, or New Relic | Policy adherence and controls in Vanta, Drata, or Secureframe |
| Verified surface | Critical flows, product states, copy, access gates, and configured checks | Syntax, style, tests, static analysis, and implementation risk | Pixel and DOM diffs across builds | Metrics, logs, traces, alerts, and incidents | Configurations, controls, policies, and audit evidence |
| Output | Review packet, behavior fingerprint, risk flags, hosted release notes | GitHub or GitLab comments, suggested changes, and summaries | Diff reports, baselines, and changed screenshots | Dashboards, alerts, traces, and incident timelines | Audit reports, control status, and spreadsheets |
| Human workflow | Review proof, inspect evidence, assess risk, and understand the release | Review code, request changes | Accept visual diffs or update baselines | Investigate, diagnose, resolve | Collect evidence, prove compliance |
| Differentiation | Product-behavior proof with evidence engineers, PMs, and executives can read | Reads repository changes and implementation details | Catches screenshot and DOM changes; misses business logic and critical paths | Reads runtime signals after release; lacks review-time product evidence | Tracks policy posture and controls |
Use the CLI, GitHub App, private worker, hosted packets, API, and proof commands around the release workflows your team already runs.
Define projects, critical flows, checks, redaction, and capture behavior as code.
Receives PR and deployment events, creates checks, and posts compact reviewer feedback.
Runs in your infra. Captures preview evidence without broadening the hosted surface.
Clean, shareable release notes and packet views for product reviewers.
Project-scoped run history, packet access, audit rows, and integration endpoints.
Repeatable hosted, GitHub, and leak-scan commands for operator acceptance.
ReleaseNotary redacts sensitive evidence and keeps packet access bounded to the review path.
Secrets, PII, and tokens are detected and redacted from durable artifacts.
Signed packet access stays ephemeral; proof artifacts must not store rn_access URLs.
Scoped, revocable keys keep packet access bounded to the project.
Artifacts stay private by default. Reviewers share them through intentional review paths.
Every run is logged with actor, config, hash, and evidence trail.
Send the repo, preview setup, and the flows you want covered. We confirm fit and scope the 30-day pilot.