Skip to main content

Roadmap

ProdVerdict should expand only where founders prove they want repeat verification.

Current shipped scope​

  • Access for custom Stripe, Paddle, Postgres, and Stripe Entitlements billing state.
  • Entitlements migration.
  • Config.
  • Migration.
  • Boundary.
  • Webhook.
  • Restore.

Validation targets​

These are planned areas, not shipped contract schema:

  • Clerk-aware route gates.
  • Usage limits.
  • Credits and burndown.
  • Seats.
  • Deeper permission contracts.

Product principle​

Reposition publicly now, but keep shipped claims honest. Access is the first proof point for custom billing state. Usage, Clerk-aware gates, credits, seats, and permissions should move from roadmap to shipped only after audit evidence shows repeat demand.

What not to position as​

Do not position ProdVerdict as:

  • AI code security.
  • SAST or DAST.
  • A Clerk replacement.
  • A general policy engine for every application rule.
  • A cloud that stores customer subscription rows or PII.