The Launch-Day Security Checklist Lovable's Scan Does Not Run
A code scan and a project configuration are two different objects. Lovable's scans read the first. Most of Supabase's own production checklist lives in the second, and it is off until somebody turns it on.
If your app keeps breaking, start with our guide on how to fix an AI-built app without rebuilding it.
Checking your database first? Follow our step by step guide on how to check your Supabase RLS policies before you launch.
Two different objects
A security scan reads your code. A production checklist reads your project's settings. They are different objects, and only one of them ships inside the repository your builder hands over. That is the gap most launch-day security conversations fall into: the code came back clean, so the app is assumed to be safe, while the database it talks to is still running on the defaults it was created with.
Lovable is unusually clear about this. Its security documentation states that you are responsible for ensuring that your app meets the security requirements appropriate for its use case, and that its tools help identify common security issues, but they cannot guarantee complete security. That is not a disclaimer to skim past. It is an accurate description of where the platform's reach ends.
What the built-in scans do cover
Lovable ships a basic scan, which runs fast configuration and dependency checks, and a deep scan, which is a slower agentic review of the codebase. Between them they audit npm dependencies for known vulnerabilities, detect credentials hardcoded in the codebase instead of stored in Secrets, and lint row-level security policies and schema for unsafe access patterns. Optional Wiz and Aikido integrations extend that with vulnerability scanning and AI penetration testing.
That is a genuinely useful surface, and it covers the two mistakes behind most early incidents: a key in the bundle, and a table with no policy on it. What a code scan cannot do is reach into your Supabase project and change a setting.
Who owns each control
| Control | Where it lives | Does a code scan see it? |
|---|---|---|
| Row-level security on every table | Supabase database | Partly: policy linting flags unsafe patterns, not a table you left open on purpose. |
| Hardcoded API keys | Your codebase | Yes: detection is built in and points you at Secrets. |
| VITE_ variables in the bundle | Build configuration | Yes as code, but the decision about what belongs there is yours. |
| SSL enforcement | Supabase database settings | No. |
| Network restrictions | Supabase project settings | No. |
| Multi-factor auth on the Supabase account | Your Supabase account | No. |
| Custom SMTP and OTP expiry | Supabase Auth settings | No. |
| Point-in-time recovery | Supabase plan and settings | No. |
Nine questions to answer before you publish
None of these is exotic. None of them is an argument against building on Lovable, which we do every week. They are simply the questions a code scan was never looking at.
- Is row-level security on for every table, including the three you added last week? RLS is the layer that still holds when the frontend or an edge function gets something wrong. The scan lints the policies that exist; it cannot know that a table was left open deliberately. Supabase's own production checklist puts enabling RLS on all tables first, for the same reason.
- Does any authorisation decision happen in the browser? Lovable's own best-practice documentation is blunt: all frontend code runs in the user's browser and can be inspected, modified, or bypassed, and frontend validation improves user experience but provides no security guarantees. Authentication decisions belong server-side, validated in edge functions. A hidden admin route is a UI preference, not a control.
- Do you know which of your variables are public? Anything prefixed VITE_ is embedded at build time, not runtime. It is in the bundle your users download, and changing it means rebuilding. Anything that must stay private belongs in Secrets and must be read server-side, because secrets stored in frontend code are visible to users and should be considered compromised.
- Is SSL enforcement on, and have you set network restrictions? Both are Supabase project settings, both are on the production checklist, and neither appears anywhere in your code. Turning on multi-factor authentication for the Supabase account itself is on the same list and takes about a minute.
- Is your auth email yours? Custom SMTP, email confirmations enabled, and an OTP expiry that Supabase recommends keeping to 3600 seconds or less. The default sender is fine for a prototype with five test users; it is not a thing to launch on.
- Are two projects pointing at one database? On 11 September 2026 Lovable added warnings when multiple Lovable projects share the same Supabase project. If your v2 rebuild or your staging copy is wired to production data, a migration run in the wrong browser tab is not a rollback situation.
- Will you find out when something breaks? Supabase added Health Check Advisors on 18 September 2026, tracking error rates across PostgREST, Auth, Storage and Edge Functions, and on 13 September 2026 added structured log access through a query_logs tool on its MCP server. Monitoring is not security, but an incident you hear about from a customer is one you are handling late.
- Whose calendar does the patch land on? Next.js announced an out-of-band release for 22 September 2026, versions 16.3.6 and 15.5.26, for a critical issue in an upstream dependency, with the advisory published alongside the update. The technical work is a version bump. The question worth settling before launch is who is watching for the announcement at all.
- Does your backup posture match the data you now hold? Supabase recommends point-in-time recovery once a database passes 4 GB, notes that backups on the Free plan cannot be downloaded, and warns that Free plan projects pause. The day you hold real customer data, this stops being the same question it was in week one.
The honest version of production-ready
Production-ready is a claim about code. Most of the nine questions above are claims about configuration, and configuration is the part that stays yours after every handover, from us or from anyone else. A build that ships clean code into a project still running week-one defaults is not finished; it is half-finished in the half nobody photographs.
So the useful thing to ask any builder, including us, is not whether the app is secure. It is which of these nine they set, which they left to you, and which they never looked at. Three different answers, and only the third one should worry you.
Where we land
Our own numbers, for the record: 80 jobs on Upwork, 100% Job Success and a 4.9 rating from 30 reviews. Both build tiers, Founding Client at $2,999 and Publishable MVP at $4,999, include production deployment, monitoring, documentation and handoff, and 90-day support until your first paying customer, and the revenue guarantee is first paying customers within 90 days of launch or a full refund. The Founding Client tier carries a 14-day build guarantee with a full refund if the deadline is missed. A Strategy Audit is $499 and is credited toward any build.
If you want a second pair of eyes on those nine questions before you publish, that is what the intro call is for. Book your free 20-minute intro call.
Sources
- https://docs.lovable.dev/features/security
- https://docs.lovable.dev/tips-tricks/security-best-practices
- https://docs.lovable.dev/tips-tricks/external-deployment-hosting
- https://docs.lovable.dev/changelog
- https://supabase.com/docs/guides/deployment/going-into-prod
- https://supabase.com/changelog
- https://nextjs.org/blog/upcoming-nextjs-security-release-september-22-2026