2 · The thirteen checks
01 Secrets out of the repo and browserlaunch-blocking Are all API keys and secrets out of the repository and out of the browser bundle?
Yes Not sure No
02 Paid APIs called server-sidelaunch-blocking Are calls to paid APIs (OpenAI, Stripe, email, SMS) made from a server or edge function — never directly from the browser?
Yes Not sure No
03 Database access ruleslaunch-blocking Does every database table have access rules (Supabase RLS, Firestore rules) that stop one user reading another user's data?
Yes Not sure No
04 Auth on the real domainlaunch-blocking Do sign-in, sign-out, refresh and password reset all work on your real domain and on a phone?
Yes Not sure No
05 Separate environmentsimportant Do you have separate development, preview and production environments with their own configuration?
Yes Not sure No
06 Live-mode payment verifiedimportant Have you completed one real live-mode payment end to end, including the webhook and a refund?
Yes Not sure No Not applicable
07 Versioned schemaimportant Is the database schema captured as versioned migrations in the repository, and do they match production?
Yes Not sure No
08 Errors handledimportant Does a bad input or a failed API call show the user a sensible message instead of a blank screen?
Yes Not sure No
09 Tests on the money pathsimportant Are there automated tests around sign-up, checkout and the app's core action?
Yes Not sure No
10 Deploy and rollbackimportant Can you deploy from the repository with one command — and roll back in one command if it breaks?
Yes Not sure No
11 Monitoring and alertsimportant Would you know within minutes if the app went down or errors spiked — without a customer telling you?
Yes Not sure No
12 Backups testedimportant Are database backups automatic, and have you actually restored one to check it works?
Yes Not sure No
13 Real-data performancegood practice Have you loaded a page with a thousand or more real records and checked it's still fast?
Yes Not sure No
Answered 0 of 13
Answer all thirteen to see your score, the launch-blocking gaps, and the fix for each.
Get the real audit — two business days → Self-assessment plus what a file tree can prove — not a code review. The paid audit reads the code, the database policies and the deploy.