For founders

You built it with AI. Now real people are signing up.

Your app works, which is exactly why nobody has checked who else can read it. Paste the repo and get a plain-English report, a fix with the proof attached, and re-checks as you keep prompting.

Leak check · manra399/patchlabs-demo-appfix proven

What we found

1 table holding personal data was readable by the wrong people: profiles (email, phone), by anyone on the internet. No exposed AI or API keys in the code or its full git history.

The fix

Only let people read their own profile. Risk that something on your site behaves differently: low.

anon0 rowsDENIED
stranger0 rowsDENIED
owner1 rowOK
From the real report on our demo app, 9 Nov 2026. See the whole report.

What you get

Answers, not a dashboard of warnings.

01Know

Who can read what

Every table a stranger can read, and the columns exposed, in plain English. Plus keys in your code and history, and the risky code patterns AI tools write.

02Fix

A fix you can apply yourself

A migration file with the proof attached. Paste it into Supabase or commit it on GitHub in one click; or hand it to an engineer.

03Keep

Re-checks while you keep building

Every prompt can change your database. Monthly re-checks on Free, weekly on Maker, with an email when something new appears.

Your first hour

From repo to fixed, without learning row level security.

  1. Paste the repo

    Your public GitHub repo and your email. No account needed for the first check.

    github.com/you/app
  2. Prove it’s yours

    Commit one small file with a one-time code. A link opens GitHub’s editor for you.

    patchlabs-verify.txt
  3. Read the report

    Usually within minutes. Business questions come with a recommended answer.

    profiles LEAK fix PROVEN
  4. Apply the fix

    Download the migration or commit it on GitHub. Then add the app to keep watching it.

    …_patchlabs_leak_fix.sql

Questions

Founder questions.

Something not covered? Email the founder.

I’m not technical. Will I understand the report?

Yes. It’s written in plain English: what leaked, who could read it, the fix and what it changes. The SQL is there for whoever applies it.

Is it really free?

Your first app is free, with monthly re-checks, every finding and every fix proven. It isn’t a trial. Maker is £19 a month for 3 apps and weekly re-checks.

Can it break my app?

Nothing changes until you apply the fix. Each fix is proven so the owner still reads their own data, and the report rates the risk that something behaves differently.

What does it not cover?

It checks specific, documented things (each with an ID) in your repo. It isn’t a pentest or a compliance certificate, and it can’t see changes made by hand in your Supabase dashboard.

Free check

Find out what a stranger can read. It’s free.

Paste your public repo. You’ll get the leaks, the fix and the proof on one page.