greenlıt

Guide · Before launch

Is my Lovable app secure? A checklist before launch

AI builders like Lovable, Bolt, v0 and Replit get you from idea to live app in a weekend. They don't always get the safety parts right, and you may never have read the code. These ten checks cover what goes wrong most often, in the order that matters.

Updated 18 November 2026

The three that can sink you

1. No secret keys in your website

Anything your site sends to the browser is public. A Stripe secret key, an OpenAI key or a Supabase service_role key in there means anyone can charge cards, run up your AI bill or read and change your whole database. Some keys are meant to be public (the Supabase anon key, the Stripe pk_ key). Secret ones never are.

If you find one: rotate it first, then move the call to a server.

2. Every database table has rules

On Supabase, Row Level Security decides what a stranger can read with your public key. A table without it is open to the whole internet. A rule that just says true is the same. Ask your builder: "Turn on Row Level Security for every table and make sure users can only read and change their own rows." Then check that it really did.

3. Sign-up doesn't let just anyone in

If anyone can sign up without confirming their email, rules that say "signed-in users only" protect nothing. Email confirmation slows this down, but anyone can still sign up with a real inbox in seconds. Your rules must check whose data it is, not just whether someone is signed in.

The ones that hurt later

4. Uploaded files aren't public by accident

A public storage bucket serves every file to anyone with the link. Fine for product photos, not for ID documents, invoices or anything users uploaded about themselves.

5. Server functions check who's calling

Edge functions and API routes should confirm the caller is signed in and allowed to do what they ask. A function that charges, emails or deletes without checking can be called by anyone who finds its address.

6. Payment messages are verified

If Stripe tells your app "this person paid" through a webhook, your app must check Stripe's signature. Otherwise anyone can send a fake "paid" message and unlock your product for free.

7. Your source code isn't handed out

Source maps, a public .env file or a reachable .git folder give away your code, your comments and sometimes your keys. None of them should be reachable on your live site.

8. Basic security headers are on

Frame protection stops other sites from putting your app inside theirs. A Content-Security-Policy limits what an injected script can load or do. They're cheap to add and easy to forget.

The ones that break a live app

9. No leftovers from building

Payments still in test mode, a page calling localhost, a placeholder title, a test email sender, or a setting that hides the site from Google. Each one is small, and each one makes a launch look broken.

10. Things only you can answer

Do you have backups? A spending limit on your AI and cloud accounts? A separate test database, so experiments don't touch real users? No scanner can see these. Write the answers down before launch.

How to check most of this without reading code

Use your builder's own security review if it has one, then check from the outside: that's how a stranger sees your app. Greenlit looks at what your live site actually sends, grades it from A to F, explains each problem in plain words, and writes a prompt you can paste straight into Lovable, Bolt or v0 to fix it. Run it again after each fix to confirm the grade went up.

The web check covers secret keys, source maps, headers and launch leftovers. For your database, storage and sign-up settings, check your app, then choose "Check my database here" and add the tag it gives you. Or run npx greenlitlab yourapp.com --mine on your own computer. Items 5, 6 and 10 need you or your builder to look.

Check your app in 30 seconds

Paste your app's address. Free, no sign-up, and it reads only what every visitor already sees.

Check your app

More guides