$launchguard/how-scanning-works

Three layers.
Zero blind spots.

Each tier goes deeper into your app's attack surface. Surface-level checks are free. The real vulnerabilities hide behind login.

depth
01

SURFACE SCAN

Free

Scans your app without logging in, like a bot or beginner hacker would. Finds your Supabase project and probes everything reachable with the anon key.

Exposed Supabase tables readable without auth
Callable RPCs & edge functions via anon key
Open storage buckets with public files
API endpoints responding without authentication
Service role keys leaked in client-side code
analogy

"Walking up to every door and checking if it’s locked."

02

AI VERIFICATION

Pro

The surface scan finds unlocked doors. AI verification opens them, inspects the contents, and writes lockdown instructions.

Probes resources for sensitive vs. public data
Runs attack chains between endpoints
Classifies findings: exposed or harmless
Generates ready-to-paste fix prompts
analogy

"Opening every unlocked door and analysing what’s inside."

03

AUTHENTICATED TESTING

Pro

Signs in as a real user and checks if User A can access User B’s data. Catches broken RLS policies that look fine from the outside.

Queries every table with an authenticated session
Detects broken Row Level Security (IDOR)
Finds cross-user data leaks by row & column
Reports exact exposure scope and row counts
analogy

"Checking if hotel guests can enter each other’s rooms."

ONGOING GUARD

Continuous monitoring

Security isn't a one-time check. Every deploy can introduce new vulnerabilities. Ongoing Guard watches your app and re-scans automatically — free for all signed-in users. Pro users get deeper AI verification on each re-scan.

Detects new deployments automatically
Re-runs full scan on every deploy
Alerts on new vulnerabilities
Works with any hosting provider

Why the surface scan isn't enough

The free scan catches the obvious things: exposed tables, leaked keys, open storage buckets. But most AI-generated apps have subtler problems.

An LLM might write RLS policies that look correct but fail under specific conditions. It might create an API endpoint that exposes admin data to any logged-in user. These issues only surface when you test with real authentication and chain requests together — which is exactly what the Pro tiers do.

$ launchguard scan --url your-app.com

See what's exposed in 40 seconds

No signup required. Free surface scan, instant results.

Scan your app