FREE SCAN — 150 founder credits, no card

Free Security Scan for Supabase Apps

Scan your Supabase app for RLS gaps and exposed service keys.

Why Supabase Apps Get Hacked

Supabase is fast to ship on because the database is reachable directly from the client — which is also its single biggest risk. If Row Level Security is off or misconfigured, the anon key lets anyone read or write your tables. And if the service-role key (which bypasses RLS entirely) ever reaches the browser, the whole database is exposed. We scan for the Supabase-specific failure modes that cause real breaches.

Common Supabase Vulnerabilities

Disabled or weak RLS

Row Level Security off, or policies that effectively allow all rows, means the public anon key can read and modify every record. This is the #1 Supabase breach cause.

Service-role key in the client

The service_role key bypasses RLS completely. If it is in a NEXT_PUBLIC_ var, frontend code, or a leaked .env, an attacker owns your entire database.

Over-permissive policies

Policies that check authentication but not ownership (USING (true) or missing auth.uid() = user_id) let any logged-in user read every other user's data.

Exposed Storage buckets

Public buckets or missing storage policies expose uploaded files — invoices, IDs, private media — to anyone with the URL pattern.

Unprotected Edge Functions / RPC

Postgres functions and Edge Functions exposed without authorization checks or rate limits become a direct path to data and abuse.

What the Sable Scan Checks

Exposed secrets & API keys

We scan your client-side bundles and responses for leaked API keys, tokens, database URLs, and 100+ secret patterns that ship to the browser by accident.

Security headers & TLS

HSTS, CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy, and TLS protocol/cipher configuration — graded A-F with copy-paste fixes.

CORS & access control

Overly permissive CORS, wildcard origins with credentials, and broken object-level authorization (IDOR/BOLA) where one user can reach another user's data.

Injection & API surface

SQL/NoSQL injection, exposed OpenAPI/Swagger specs, GraphQL introspection, mass assignment, missing rate limits, and excessive data exposure.

OWASP Top 10 coverage

Autonomous pentesting agents test against the full OWASP Top 10 2025, validate each finding with a proof-of-concept, and re-test after you fix.

Validated findings, not noise

Every reported issue is confirmed by an agent before it reaches you — so you get real, exploitable findings with severity and remediation, not scanner spam.

Scan Your Supabase App in Minutes

Create a free account, point the agents at your app, and get validated findings with proof-of-concept and fix guidance. 150 founder credits, no credit card.

Get 150 Free Credits

Frequently Asked Questions

How do I know if my Supabase RLS is configured correctly?
Test it from the client with only the anon key: try to read and write rows you should not be able to. If RLS is off or a policy uses USING (true), you will succeed — which means anyone can. Sable probes your tables and storage with the public key and reports exactly what is reachable.
What happens if my Supabase service-role key leaks?
The service-role key bypasses all Row Level Security, so a leak means full read/write access to your entire database. Rotate it immediately, keep it server-only, and never put it in a NEXT_PUBLIC_ variable. Sable scans your client bundle for exposed Supabase keys.
Is the security scan really free?
Yes. The Headers Scan runs instantly with no signup. For the full agent scan you create a free account and get 150 founder credits with no credit card required — enough to run real scans against your app on demand. Paid credit packs and monthly tiers exist for continuous testing, but you can start for free.
How does Sable scan my app?
Sable runs autonomous pentesting agents (pen-scout, pen-recon, pen-triage, pen-fixer, pen-compliance) that map your attack surface, test against the OWASP Top 10, validate every finding with a proof-of-concept, and re-test after you ship a fix. You chat with the agents on demand instead of waiting weeks for a manual engagement.
Will the scan break or slow down my production app?
No. Scans are designed to be safe and non-destructive. We demonstrate impact with proof-of-concept evidence rather than causing damage, and we never exfiltrate or alter your data.

Security Scans for Other Stacks