Lovable apps usually ship with Supabase for auth, database, and storage. That stack is productive and easy to misconfigure.

Before you launch

  • [ ] RLS is enabled on every table, with explicit policies.
  • [ ] No service_role key in the browser bundle.
  • [ ] Storage buckets are private unless they are meant to be public.
  • [ ] Auth email confirmation is enabled.
  • [ ] No .env, .env.bak, or .git on the production domain.
  • [ ] Source maps are disabled in production.
  • [ ] The app does not expose an open AI endpoint or an MCP server.

Why "the platform scans it" is not enough

Lovable runs a basic scan on publish. It checks database configuration, RLS rules, and known misconfiguration patterns in about 10 to 15 seconds. That is a useful floor, not a full external review. It cannot see your Stripe keys, your custom API routes, or a backup file you uploaded to the domain.

Run the checks

Use the free scan to verify the external surface, then fix the critical findings before inviting users.