Six ways teams sleep through the night.
Pick the persona that sounds like you. Each one is a real scenario we've watched play out — the pain, the scan, the fix, and what changed afterwards.
Shipped a Supabase app in a weekend. Doesn't know what RLS is.
Prompted an LLM to build a SaaS. The schema works, the auth works, the demo on Twitter works. The `users` table is readable by anyone with the anon key — which is shipped in the bundle.
Sentrail scanned the project, found 7 anon-readable tables and a service-role key leaking from a Vite env, and proposed a migration plus a key rotation. Total time: 11 minutes.
- 00:00User: Is my project secure?
- 00:02Sentinel: Found 7 anon-readable tables and 1 leaked service_role key
- 00:05Sentinel: I've drafted 3 migrations and a key rotation guide
- 00:08User: Apply migrations
- 00:11Sentinel: Applied. Verification scan clean.
Built for the Supabase + Vercel + GitHub stack.
Sentrail starts with the modern indie stack — Supabase, Vercel, and GitHub — and grows from the surfaces you actually deploy on.
RLS status, policy coverage, and Supabase security advisor checks.
Env var risk classification, deployment protection status.
Auth.uid() policy scoping, BOLA checks via the Supabase audit.
GitHub source code search for leaked service-role keys and exposed secrets.
Whichever persona you are — start with a read-only scan.
We do not write to your project until you press the button. Free during preview.