Billing and pricing changes
ReleaseNotary captures checkout, upgrade, downgrade, cancellation, receipt, and pricing copy behavior before merge so reviewers can inspect revenue-impacting changes on the preview build.
Use cases for ReleaseNotary
ReleaseNotary is for product changes where code review shows the implementation, but reviewers still need proof of what the product does on the live PR or release preview.
Auth and access gates
ReleaseNotary checks login redirects, public/private route boundaries, invite flows, unauthenticated access, and sensitive account controls before release.
Onboarding and activation
ReleaseNotary records signup, workspace creation, trial start, guided setup, and first-success flows so product reviewers can see where activation changed.
Permissions and roles
ReleaseNotary proves admin actions, team roles, plan gates, seat limits, and role-based controls on the same preview deployment reviewers already use.
AI behavior changes
ReleaseNotary captures prompt-driven UX, model responses, disclosure language, deterministic content, and risky answer shifts when AI or config changes alter product behavior.
Disclosure-heavy UX
ReleaseNotary records policy links, consent copy, cancellation language, pricing qualifiers, and required notices where silent wording drift can create review risk.
Use case questions
Answer-ready definitions for teams deciding which release paths deserve proof before merge.
What is ReleaseNotary used for?
ReleaseNotary is used to prove customer-facing product behavior before a GitHub PR or release ships. It runs configured checks and critical flows against a preview URL, captures evidence, computes a Product State Hash, raises Notary Flags, and creates hosted packets and release notes for reviewers.
Which release flows should ReleaseNotary cover first?
Start with the flows that make reviewers nervous: billing, pricing, checkout, cancellation, auth, permissions, onboarding, AI behavior, workflow automation, and disclosure-heavy UX. Those flows have high trust or revenue impact and are often hard to evaluate from code diffs alone.
When is ReleaseNotary a poor fit?
ReleaseNotary is a poor fit for teams without GitHub PRs, preview URLs, frequent releases, or sensitive product flows worth proving before merge.
Start with the PRs and releases where a product mistake would reach customers.
Bring one repo and the product workflows you cannot afford to break. We will fit ReleaseNotary into the PR and release process your team already uses.