Supabase and Lovable apps
Your Supabase app, checked and fixed before your users find the gaps.
AI app builders get a working app online fast. The access rules underneath are where data leaks. We check your Supabase project for the mistakes that let a stranger read or change data, fix them, and run the same attacks again to show they no longer work.
Updated · Railo
What usually goes wrong
- Tables with row-level security switched off, or policies that allow every row with
true. - Users who can edit their own
rolecolumn and make themselves an admin. - Admin checks that read
user_metadata, which every user can set for themselves. - The service-role key in frontend code, where every visitor can copy it.
- Public storage buckets holding private files, and edge functions anyone can call without a login.
A sample audit
We wrote a small booking app in the structure Lovable generates, with the mistakes above, then audited and fixed it. Attacks used only what any browser has: the public key and a normal sign-up.
| Before | After | |
|---|---|---|
| Findings | 13: 6 critical, 5 high, 2 medium | 0 |
| Attacks that worked | 8 of 8 | 0 of 8 |
| Normal use for clients and advisors | 5 of 5 working | 5 of 5 working |
Before the fixes, a visitor could read every user's email and phone number, passport numbers and scans; anyone who signed up could post messages as someone else and make themselves an admin. The fixes were one database migration and three code files. The app, the fixes and the attack script are public: read the sample report.
Price
| Offer | Price | What you get |
|---|---|---|
| Quick check | USD 149 | Within 48 hours: every table, policy, function, bucket and key checked, and a written list of findings with the fix for each |
| Audit and fix | USD 497 | The quick check, then fixes for every critical and high finding as a pull request, and the attacks run again on a copy to show they stop |
| Pre-launch hardening | USD 1,000 to 1,250 | Audit and fix, plus prompt-injection tests for AI features in the app and a CI check so new tables cannot ship without row-level security; quoted after a short call |
Every price is confirmed in writing before work starts.
What you send us
- Access to the code. Lovable syncs to GitHub; add us as a collaborator on that repository, or send an export.
- Read access to the Supabase project, or an export of its schema and policies.
- Written permission from the app's owner. We only test apps whose owner has asked us to.
What you get back
- A report: each finding, why it matters, where it is, and how it was fixed or what we recommend.
- The fixes as a pull request: a new database migration and any code changes. You review and merge it, or apply it from Lovable.
- The attacks run again against a copy after the fixes, with the results.
- A list of anything we chose not to change, and why.
What we do not do
- We do not test anything without written permission from its owner.
- We do not run attacks against your live app; we use a copy.
- We do not push to your main branch. You merge.
- We do not promise there is nothing else wrong. We check access control, keys, storage and functions; business logic outside those is out of scope unless agreed.
Have scanner or pentest findings in other code? See pentest remediation.
Want your app checked?
Send us the app's link and what it stores. We reply within one business day with the next step.
Ask for a Supabase audit