ReleaseNotary runs your high-risk workflows on PRs and releases. It finds customer-facing failures that code review tools are blind to.
5b1f0e8f3c8a7d9e2a1b4c6dNOTARY FLAGS
github-actionscommented on PR #184
REVIEWReleaseNotary found 2 product issues. The annual checkout is missing its cancellation disclosure, and an access gate opened without a session.
Open Notary Packet01 / The review loop
ReleaseNotary runs those scenarios on PRs and releases and flags the mismatch before approval.
Read about product behavior proofShow us the checkout, access gate, AI response, or workflow that could block the release.
ReleaseNotary drives the product, checks the expected behavior, and records any mismatch.
Your team gets a GitHub check and a Notary Packet with the finding, evidence, and release notes.
02 / Where to begin
Start with flows where one wrong price, permission, or AI response can reach customers.
Checkout, plan changes, cancellation paths, receipts, and pricing copy.
Login redirects, invite flows, private routes, and permission leaks.
Signup, workspace creation, trial starts, and the first successful run.
Admin actions, team roles, plan gates, seat limits, and account controls.
Model responses, disclosure language, fixed answers, and risky output shifts.
Policy links, consent copy, cancellation language, and required notices.
03 / The release file
Engineers can inspect screenshots, visible text, logs, and diffs. Product and leadership get Notary Flags and release notes that explain the customer impact.
One release record with the findings, evidence, PR context, and release notes.
A stable fingerprint for the product behavior captured in the run, separate from the commit SHA.
Product-specific findings such as a wrong price, exposed route, missing disclosure, or changed AI answer.
A readable account of the changed product behavior, review points, and supporting evidence.
Screenshots, visible text, logs, diffs, and captured output with sensitive values redacted.
A compact PASS, FAIL, or REVIEW result in the PR with a link to the full finding.
04 / Where ReleaseNotary fits
A PR can look sound in the diff and still expose a private route, charge the wrong price, or change an AI answer. ReleaseNotary runs those product scenarios on PRs and releases before approval.
See the full tool comparison| Review question | ReleaseNotary | Code review: CodeRabbit, GitHub Copilot | Visual QA: Chromatic, Percy | Observability: Sentry, Datadog |
|---|---|---|---|---|
| Primary focus | Product-specific errors in live PR and release builds | Implementation issues in the pull request | Screenshot, component, and DOM changes | Runtime errors, latency, and incidents |
| What it inspects | Billing, auth, permissions, AI behavior, and workflows | Code diffs, tests, static analysis, and repository context | Pixels, layouts, components, and visual baselines | Logs, traces, metrics, and production events |
| Issues it finds | Wrong prices, exposed routes, broken roles, changed AI answers, and workflow regressions | Bugs, security problems, style issues, and test gaps visible in the code | Layout breaks, styling drift, and unexpected UI changes | Exceptions, slow requests, outages, and service degradation |
| Review output | Notary Flags, evidence, Product State Hash, release notes, and a GitHub check | Inline comments, summaries, and suggested code changes | Visual diffs, snapshots, and baseline approvals | Alerts, traces, dashboards, and incident timelines |
| When it helps | Before merge or release, against the deployed PR or release build | During pull-request review, from repository context | During UI review and continuous integration | After deployment, while the system is running |
05 / Founder-led pilot
Bring one repo, active PRs or release builds, and the product scenarios your team worries about. We configure the review path with you and tune it against live work.
06 / Evidence and access
Each run creates a Notary Packet with screenshots, flags, release notes, and the Product State Hash. ReleaseNotary redacts sensitive values and keeps the underlying artifacts private.
Read the security modelReleaseNotary removes detected secrets, PII, and tokens before evidence becomes durable.
GitHub organization access controls who can open the hosted release record.
Each key stays scoped to its project and can be removed without changing the evidence.
Screenshots, logs, and other artifacts move through deliberate reviewer links.
Send us a repo, and we will scope the 30-day pilot around its key flows.