The 10-point check before you launch your Lovable + Supabase app
Your app works for you in the Lovable preview. Before real users arrive, run these ten checks. Most take a couple of minutes, and together they catch the problems we see most often in AI-built apps: open data, login loops, blank pages after deploy and payments that don't unlock anything.
1. RLS is on for every table
Row level security off means your anon key (which ships in the browser) can read or change the whole table.
How to check: In Supabase, open Database → Tables (or Security Advisor) and confirm no table in public shows RLS disabled, and every table has policies that check auth.uid().
2. Storage buckets have their own policies
Table RLS does not cover file uploads. Storage uses policies on storage.objects, and public buckets serve files to anyone with the URL.
How to check: In Storage → Policies, check each bucket has insert and select policies scoped to the owner, and that only truly public files live in public buckets.
3. A second, logged-out account can't see your data
Most data leaks only show up when someone other than you uses the app.
How to check: Sign up with a fresh email in an incognito window, try to open your first account's records (change IDs in the URL too), then sign out and try again.
4. The service_role key is not in the client
The service_role key bypasses RLS completely. If it's in your frontend bundle, anyone has admin access.
How to check: Search your repo and the deployed JS (DevTools → Sources) for service_role and your secret key. Only the anon/publishable key should appear; keep the other in server code or Edge Function secrets.
5. Auth redirect URLs point at production
Logins that work in preview often loop or land on localhost on your real domain.
How to check: In Supabase → Authentication → URL Configuration, set Site URL to your live domain and add it (and any OAuth callback) to Redirect URLs. Then log in on the live site.
6. Environment variables are set on your host
Keys in your local .env don't travel with the code, so the live site gets undefined values or a blank page.
How to check: Compare your .env with the host's settings (e.g. Vercel → Settings → Environment Variables for Production), keep the right prefix (VITE_ etc.) and redeploy after changes.
7. Email confirmation and reset links work
Confirmation and password-reset emails use the Site URL and email templates, and default email sending is heavily rate limited.
How to check: Sign up and request a password reset with a real inbox; confirm both links land on your live domain and log you in. Set up custom SMTP before real traffic.
8. Stripe webhooks are verified and drive access
Unlocking paid features on the success page lets people in for free; unverified webhooks can be faked.
How to check: Check your webhook handler verifies the Stripe-Signature header with your signing secret, that the live-mode endpoint exists in the Stripe dashboard, and that a test payment upgrades the account.
9. Errors show a message, not a blank screen
Failed requests that aren't handled leave users with spinners and white screens, and you never hear about it.
How to check: Turn off Wi-Fi or block a request in DevTools, then submit a form and load a page. You should see a clear message and a way to retry, not a frozen screen.
10. You have a backup you can restore
A bad migration or an AI-written query can wipe data in seconds.
How to check: In Supabase → Database → Backups, confirm backups exist for your plan (free projects don't get them, so take your own pg_dump), and know how you'd restore.
Quick checklist
- RLS is on for every table
- Storage buckets have their own policies
- A second, logged-out account can't see your data
- The service_role key is not in the client
- Auth redirect URLs point at production
- Environment variables are set on your host
- Email confirmation and reset links work
- Stripe webhooks are verified and drive access
- Errors show a message, not a blank screen
- You have a backup you can restore
Want a second pair of eyes?
If any of these fail, or you'd rather not check them yourself, get a free scan and we'll tell you what's broken and what's risky in plain English. Know what you need fixed? Get a single fix for the €49 launch price. If we can't fix it, you don't pay.
Get a free scan Fix it for €49
Related: Supabase auth redirect loop on Vercel · Blank page after deploying a Vite app · Stripe success page unlocks paid access for free
Not sure what else is wrong? Paste your app link into the free instant check and get a plain-English list of problems in seconds.