Example page made by Ghostlaunch. This product doesn't exist yet.

Back to the example

For Lovable and Bolt apps on Supabase

Prove one user can't see another's data before launch

Paste your app's URL. Vettly signs up two test users, tries to reach one's data from the other, and probes your login. You get a clear pass/fail and copy-paste fixes.

Just your URL. No code access. We never store user data.

The app works. You're just scared to post the link.

You built something real without ever learning how logins or database permissions work. Now real signups are coming, and nobody can tell you if it's safe.

"Is the login actually secure? Can one person see another person's data?"
You have no idea how to check, and a working app doesn't tell you whether an outsider could open someone else's records.
"I asked the AI to review it. It found bugs, but did it catch the scary stuff?"
Every review gives a different list. Some nitpicks, some real, and no clear answer on whether you're safe to launch.
"Every prompt, I worry it quietly broke something that was fine yesterday."
Your app changes daily. A new feature can open a hole in a table that was locked down last week.
"I keep reading about leaked Supabase tables and wondering if that's me."
Exposed keys and open tables make the rounds on Reddit. Hiring a security person for a zero-revenue side project isn't an option.

A real check in three steps

No code access, no setup, no security vocabulary required.

  1. 1

    Paste your app URL

    That's all Vettly needs. It works on your live Lovable or Bolt app running on Supabase.

  2. 2

    Let Vettly test it like real users

    It creates its own test accounts, tries to reach one user's data from another, probes the login and looks for exposed keys.

  3. 3

    Paste the fixes back into your builder

    Each issue comes with a plain-English explanation and a prompt you copy into Lovable or Bolt. Then re-run to confirm it's fixed.

What Vettly checks before your users do

It tests how your app behaves, not just how the code reads. That's the difference between guessing and knowing.

Proof that users can't read each other's data

Vettly signs up two test accounts, creates data as one, then tries to read, edit and delete it as the other. Every table gets a clear pass or leak.

A login that holds up to a curious outsider

It tries weak passwords, repeated guesses, reused reset links, sessions after logout and pages that should need sign-in, the same things a poking user would try.

Fixes you can apply without learning to code

Every finding explains the risk in plain English and gives a prompt written for your builder. Paste it in, then let Vettly confirm the hole is closed.

Know today's prompt didn't break yesterday's fix

Re-run the same checks after every change. Because the tests are identical each time, you see exactly what's new instead of a fresh random list.

Built for first-time builders about to share the link

Vettly is for you if

  • You built it with Lovable or Bolt on Supabase

    Your app has a login and stores user data, and you never learned how auth or database permissions work.

  • Real signups are coming

    You're about to post in r/lovable, share with a waitlist or hand it to your first customers.

  • You need a verdict, not a code review

    You want to know if it's safe, in plain words, and what to paste in to fix it if it isn't.

Not a fit (yet) if

  • Your app runs on Firebase or a custom backend. Lovable and Bolt on Supabase only for now.
  • You need a formal penetration test or a compliance report for auditors.
  • Your app has no login and stores no user data.

Why not just ask the AI, or hire someone?

Asking your AI is free but reads code, not behavior. A pentester is thorough but priced for funded teams.

CriteriaVettlyAsking your AIFreelance pentester
Tests the live app, not just the codeYesNoYes
Confirms user A can't read user B's dataYesNoYes
Same checks every runYesNoPartly
Plain-English pass/fail verdictYesPartlyPartly
Fixes written as prompts for your builderYesPartlyNo
Fits a pre-revenue budget$29 one-timeFree$500+

Check once before launch. Keep checking as you build.

Start with one full pre-launch scan. Add monthly re-checks if your app keeps changing.

Recommended

Launch Scan

One full check before you share your app with real people.

$29one-time

  • Cross-user data access test on every table
  • Login and password checks
  • Exposed key detection
  • Plain-English pass/fail report
  • Copy-paste fix prompts for Lovable or Bolt
  • One re-check to confirm your fixes

Monthly Re-check

For apps that change every day. Catch what a new prompt broke.

$19/ month

  • Everything in Launch Scan
  • Unlimited re-checks after each change
  • History of what changed between scans
  • Alerts when a passing check starts failing

Prices shown are early access pricing. No charge until your first scan runs.

Questions builders ask

Why pay $29 when I can ask Claude or Lovable to review the code for free?

An AI review reads code and guesses. It gives a different list each time and can't confirm what actually happens. Vettly runs the live app with real test accounts and shows whether user B can really open user A's data. You get a verdict, not a maybe.

What do you need from me?

Just your app's URL. No code access, no Supabase password, no API keys. Vettly signs up through your app like any new user would.

Do you see or store my users' data?

No. Vettly only creates and uses its own test accounts and the data they create. We never store your real users' data.

Which apps are supported?

At launch, apps built with Lovable or Bolt that use Supabase for login and data. Firebase and other builders aren't supported yet. Tell us what you use when you sign up.

Will the scan break my app or mess up my database?

Vettly only acts as its own test users and works on the data those accounts create. You'll see test signups in your user list, which you can delete afterwards.

I don't understand security terms. Will I understand the report?

That's the point. Each finding says what could happen in plain words, like "any signed-in user can read every invoice," and comes with a prompt to paste into your builder.

Does a pass mean my app is 100% secure?

No tool can promise that. Vettly covers the basics that most often go wrong in AI-built apps: login, cross-user data access and exposed keys. It isn't a substitute for a full professional audit.

Share your link knowing your users' data stays theirs

Paste your URL, get a clear pass/fail on login and data access, and fix anything that fails before real people sign up.

Vettly is almost ready

We're opening scans to a small group of Lovable and Bolt builders first. Leave your email and we'll let you know when you can run your first scan.