Watch
Stay locked after every change.
- Scan every week and after every deploy
- Email alert when a key leaks or a table opens
- Monthly report in plain English
- Included in Ship Premium
Security · free scan
AI builders ship fast and often leave the locks off: secret keys in public code, databases anyone can read. Find out what's exposed in seconds, free.
2 urgent · 1 to fix · 6 passed
Your customers table answers without a login.
sk-proj… in /assets/index-4f2a.js
Source maps let anyone rebuild your code.
What the scan looks for
Stripe, OpenAI, Anthropic, AWS and Supabase service keys bundled into the code every visitor downloads.
Supabase tables without Row Level Security, and Firebase rules left open to everyone. Checked once you show the app is yours.
Storage buckets that list every uploaded file, from invoices to ID photos.
.env settings files and .git folders that hand out passwords, keys and your code history.
Source maps published with your app let anyone rebuild your code, including how it reaches your data.
HTTPS and the security headers that block common script, framing and downgrade attacks.
Logins, roles, API routes and payment webhooks need someone to read the code. That's what Deep Review is for.
Found a leak?
Run the free scan, or send us your app and we'll run it with you.
We switch on database rules table by table, and close open storage and files.
Every exposed key is replaced, the old one switched off, and secrets moved to the server.
We re-scan and send a clean report you can show your team or your clients.
Security plans
Stay locked after every change.
For a leak the scan found.
One-time
Before launch, payments or sensitive data.
One-time, quoted first
Work beyond the included hours is $75 an hour, quoted before we start. Hosting and database fees stay with your providers, in your name. We fix what we find; no one can honestly guarantee an app is unbreakable.
Yes. It reads only what any visitor's browser can already reach, and never logs in or changes anything. Database and storage checks run only after you add a verification tag to your site, and even then we count rows, we don't read them.
Checking whether a database is open means asking it for data. We only do that for apps whose owners say yes, by placing a tag only they can add. It keeps the scan from being used on other people's apps.
Assume it's been copied. Replacing it and switching the old one off is the first thing we do in Lockdown, then we move it to the server so it can't leak again.
Never. You invite us to Supabase, Firebase or your hosting with a limited role, and remove us when we're done.
No one honestly can. We close the problems we find, show you a clean re-scan, and tell you plainly what's left.
Lovable, Bolt, Replit, v0, Cursor and hand-written code, on Supabase, Firebase, Vercel, Netlify and Cloudflare.