ProdVerdict

ProdVerdict

MIT engine · rules only · secrets stay local

Your billing says paid.Your app might disagree.

Money-path production contracts for AI-assisted SaaS. First proof: Access checks for Stripe, Paddle, and Postgres. Rules only — no LLM.

Run demo

npx prodverdict demo
See the FAILRead docs

Pure Clerk Billing? Use Clerk Gates, not Access.

Example: Access contract

Billing

status: active

Access gate

Database

access: false
VERDICT: FAIL

Billing says paid. App says no. npx prodverdict demo

Money-path contracts

Production contracts, not code review

Jest checks code. Snyk checks vulns. ProdVerdict checks the rules that protect paths that charge or spend money.

First proof point

Access Contract

Compares custom Stripe, Paddle, or Postgres billing state against app access so paid users are not locked out and canceled users are not still in.

Scheduled checks. Slack on fail. One command to install.

Roadmap validation areas (usage, credits, seats, deeper permissions) are not shipped contract types yet. See what's planned.

Pure Clerk Billing apps: Clerk Gates, not Access reconciliation. Fit guide in docs.

Demo

See a real FAIL before wiring credentials

The bundled fixture shows paid access disagreeing with app state. Same deterministic engine as production checks — no billing account required.

Canceled in billing, still Pro in your app - demo shows FAIL

Run npx prodverdict demo - no API keys. Wrongful-access scenario by default.

0:00 Hook/0:05 Mismatch/0:12 Cost/0:18 FAIL/0:37 Architecture/0:48 CI/0:56 CTA

Watch on YouTube/Download MP4

Sample finding

Access contract

FAIL
[HIGH] user:usr_alice
Billing status is active, but app access is false.
Fix: sync has_paid_access or repair the webhook/backfill path.

Run it yourself

npx prodverdict demo

Saw the FAIL? Scan your repo next (no credentials), then wire one contract — or ask for a free audit.

Scan your repo

npx prodverdict scan
Agent setup

Proof to habit

Demo. Scan. Wire. Run.

See a known FAIL, learn which contracts fit your repo, configure one, then run it in CI or on a schedule.

  1. 01

    See the FAIL

    Run the Access demo. No API keys. Billing says paid; the app says no.

    npx prodverdict demo

  2. 02

    Scan your repo

    Detect which contracts apply to your stack. No credentials required.

    npx prodverdict scan

  3. 03

    Wire one contract

    Bootstrap prodverdict.yml for the contract that matches your stack. Secrets stay local.

    npx prodverdict setup

  4. 04

    Run where it belongs

    Access and Restore on a schedule. Config, Migration, Boundary, Webhook, and Clerk Gates on PR.

    npx prodverdict scheduled --install

Where it runs

Same engine. Three free surfaces.

Not another LLM reviewer. Deterministic PASS, WARN, or FAIL through CLI, GitHub Action, and local MCP. Team cloud tools stay in pricing.

Local CLI

Demo, setup, doctor, and live Access checks. Secrets stay on your machine.

GitHub Action

PR gates plus hourly Access so drift is caught after live events.

Local MCP

Agents call the same engine before they ship billing changes.

Pricing

Engine is free. Pro is the team loop.

Live Access stays on your runner — that check is free forever. Pro is for teams that already run scheduled or CI checks and need shared history, remote MCP, and policy templates. Not a CI log mirror.

Free

MIT engine, unlimited runs

$0

  • Unlimited CLI, GitHub Action, and local MCP
  • All shipped contracts on your runner
  • Public and private repositories
Install from npm

Pro Cloud

After CI habit

History · remote MCP · teams

$39/ project / mo

Billed via Paddle. Cancel anytime.

  • Shared run history across PR and scheduled checks
  • Remote MCP for repo-only scans (no billing keys on our cloud)
  • Unlimited dashboard projects and CI upload
  • Policy templates and audit log
ProdVerdict — Your billing says paid. Your app might disagree.