larkspurLaunch checklist · Free to use and shareBook a call

For apps built with Lovable, Bolt, Replit, Cursor and Supabase

The launch checklist for AI-built apps.

Thirty checks to run before real users and real customers arrive. Most take minutes. Print it, tick it off, and fix what turns up. If something does not make sense, ask me.

017 checks

Who can see what

Where most of the serious problems live.

  1. 1Row Level Security is on for every table, including ones you think nobody uses.
  2. 2Every rule checks ownership (auth.uid() = user_id or a team membership), not just “logged in”.
  3. 3You signed in as one test user and failed to read, edit or delete a second user’s data.
  4. 4Insert and update rules use WITH CHECK, so nobody can write a row as someone else.
  5. 5Users cannot change their own role, plan, credits or admin flag.
  6. 6Views, functions and RPCs called from the browser enforce the same rules.
  7. 7Storage buckets holding private files are private, with rules scoped to the owner’s folder.
025 checks

Where your keys live

Anything in the browser is public, whatever the variable is called.

  1. 8The Supabase service_role key is nowhere in your frontend code or bundle.
  2. 9No OpenAI, Anthropic, Stripe secret or email-provider keys are in the frontend.
  3. 10No .env files or keys are in your repository or its history.
  4. 11Any key that was ever exposed has been rotated, not just deleted.
  5. 12Your project on the builder (Lovable, Bolt, Replit) is not shared publicly.
034 checks

Sign-in and accounts

The front door, and the easiest one to leave open.

  1. 13Email confirmation is on, and passwords have a sensible minimum.
  2. 14Sign-up has some protection from scripts creating accounts in bulk.
  3. 15Sign-in redirect URLs are limited to your own domains.
  4. 16Admin pages are checked on the server, not only hidden in the menu.
043 checks

Money and AI spend

The problems that show up as a bill.

  1. 17Anything that calls an AI model is rate-limited per user, with a spending cap.
  2. 18Prices and plan limits are enforced on the server, never trusted from the browser.
  3. 19Stripe webhooks verify their signature before marking anything paid.
055 checks

When something breaks

It will. What matters is how fast you know and how fast you recover.

  1. 20Errors on the frontend and server reach a real person within minutes.
  2. 21An uptime check watches the app and the key API.
  3. 22Backups are on, and you have restored one at least once.
  4. 23Changes go through a review and automatic tests before they reach production.
  5. 24Database changes are saved as migrations in your repository, not clicked in a dashboard.
065 checks

What buyers will ask for

Your first serious customer will send a security questionnaire.

  1. 25You can list what personal data you store, where, and who can see it.
  2. 26Every dashboard (database, hosting, Stripe, domain) has two-factor login and no shared accounts.
  3. 27Access to sensitive records is logged: who, what and when.
  4. 28You have a short written plan for a leaked key or a breach.
  5. 29Your privacy policy matches what the app actually does.

Found something? That is the point.

Send me what you found and I will tell you what it means. If you want it checked properly, a Leak Check runs every item above in 48 hours for $490, credited toward fixing it.