BREACHPROBE / LAUNCHGUARD
LaunchGuard alternatives in 2026
Five tools that answer some version of “is my app leaking its database”, scored on the same six criteria, with every figure read off that tool's own page.
5 compared· 6 criteria, identical for every column· every competitor figure read off that company's own page· last verified 2026-09-18
Pick by what you are actually doing. If you have not checked anything yet, open the Supabase Security Advisor first — it is already in your dashboard, it runs on its own, and it sees configuration problems no external scanner can. If you want to read the code that is testing you, or point it at something private, SecurifyAI's scanner is the only open-source option here. If you want the check to happen on every deploy without you remembering, that is LaunchGuard at $29/month. If you want a surface you work in every day that also keeps a continuous anon-key probe running, that is Suparbase — free forever for up to 3 connections, “$12 per user / month” for the continuous scans. And if you want a one-off answer about a shipped URL with no account and nothing installed, that is BreachProbe, free, with a $19 report if you want the fixes written out. The five are close on price and far apart on what they actually test — read the two middle rows of the table before the top one.
| CRITERION | LAUNCHGUARD | SUPABASE SECURITY ADVISOR | SUPARBASE | SECURIFYAI RLS SCANNER | |
|---|---|---|---|---|---|
| What it costs | Free · Pro $29/month“Free $0 forever … Pro $29 / month”. The free tier is not a findings paywall: “It is not a paywall on findings.” | Not publishedThe advisors documentation states no price; they are part of the dashboard. | Free · Hosted $12 per user/month“Free $0 forever” covers one solo workspace and “Up to 3 Supabase connections”; “$12 per user / month” adds unlimited connections and Agent Sentry’s continuous scans. | Free, open source“Is the Supabase Security Scanner free to use? Yes. This Supabase RLS scanner is open source and free to use.” | Free scan · $19 report · $39 with monitoringThe scan is free. “$19 one payment, one report”; “$39 one payment, 30 days” adds the nightly re-scan. |
| What it needs from you | A URL; sign-up to see full key details“Signing up (still free, no card) reveals the full leaked key and the fix prompt.” | Access to your Supabase project, through Studio, MCP, the CLI or the Management APIThe documentation was rewritten after this row was read on 4 September 2026. It now says "You or an agent can pull the same checks from: Studio: Security Advisor and Performance Advisor. MCP: get_advisors with type set to security or performance. CLI: supabase db advisors. Management API: security advisors and performance advisors." The dashboard is one of four routes rather than the only one. | A Supabase URL and an API key“Paste a Supabase URL + API key”. The key is encrypted at rest and proxied server-side rather than held in the browser. The free Security Scanner is the lighter path — it needs no account. | Run it locally, or a browser extension“You can inspect the code, run it locally, and customize it”; the page also offers “Install Firefox Extension”. | One URL“No account · nothing installed · read-only · one URL”. |
| Tests as a signed-in user | Yes“Logged-in tests included: we sign in as a real user, not just a stranger”. | Not publishedThe advisors inspect the project's own configuration; the documentation describes no test of a running app as a signed-in user. | No — anonymous probe, plus a simulatorThe scanner is explicitly the stranger’s view: “See what a stranger can read from your Supabase project.” Roles are covered separately inside the admin, which can “simulate SELECT/INSERT/UPDATE/DELETE as any role with custom JWT claims. All rolled back.” That is a simulation against your own connection, not a request made by a signed-up account. | Not published | YesIt creates its own accounts rather than asking for yours. |
| Tests one user reading another's rows | Yes, as a saved guardThe free tier saves “up to 2 guards … for a cross-user leak, a payment bypass, or any rule you name”. | Not published | Simulated, one role at a timeThe “RLS debugger” sets custom JWT claims and runs a statement as that role, and the write is “All rolled back.” So one user reading another’s rows is something you construct query by query, rather than a result the tool signs up two accounts to produce. | Not published | YesThe page lists it as a row a passive scan cannot test: "rows one user can read that belong to another", where a passive scan "cannot test it" and the probe "counts them, table by table". |
| Re-checks after you ship | Every deploy, on Pro“It re-checks on every deploy, automatically, the moment you ship”. | Automatically"The advisors run automatically in Studio. After an authorized fix, rerun the relevant advisor and confirm that the finding no longer appears." | Yes, on the paid tier“Agent Sentry continuous scans” is a Hosted line item, described on the homepage as a “Continuous anon-key probe” with per-AI-agent session attribution and one-click undo. | Not published | Nightly for 30 days, on the $39 tier“a nightly re-scan for 30 days and an email the moment a new critical or high issue appears”. |
| What you get | Findings, the request receipt, and a fix“Every finding, and the receipt: the exact request we sent and what your app sent back”. | A numbered list of lint findingsThe published check list includes “0002 auth users exposed” and “0003 auth rls initplan”. | An admin workspace; the scan is on-screenWhat you buy is a surface you work in — “Row cards, type-aware forms, FK lookups, bulk operations, CSV/JSON in + out, undoable deletes”. The free scanner keeps nothing: “the security scanner is stateless”. | Findings from a read-only scan“No. It is read-only and …” — the scanner does not modify the project it inspects. | Findings, a cross-tenant table, a written fix"Every finding located, table by table, a written fix per issue." |
Every figure below was read off that company's own page; each source URL and the date it was read are listed at the foot of this page. BreachProbe is one of the 5 compared and is the one publishing this table.
“Not published” means that company does not state the figure on the page cited at the foot of this page. It is not a claim that no such figure exists. A company that publishes no limit most likely has none — but “most likely” is not a fact, and this table prints what was read rather than what was inferred.
| TESTS AS A SIGNED-IN USER | whether the tool authenticates and probes as a real account, rather than only reading what an anonymous stranger can reach |
|---|---|
| TESTS ONE USER READING ANOTHER'S ROWS | the two-account test. It is the only check that can tell a working row-level security policy from one that is merely present |
What is the best free Supabase security scanner?
Four of the five here are free to run. The Supabase Security Advisor costs nothing and is already inside your dashboard, but it inspects your project's configuration rather than your shipped app. SecurifyAI's RLS scanner is open source and free to use, and can be run locally or as a Firefox or Chrome extension. Suparbase's Security Scanner is free with “no sign-up, no email wall, and no trial timer”, and shows “which of your tables an anonymous visitor can read right now”. BreachProbe's scan is free with no account and nothing installed. LaunchGuard also has a free tier that its pricing page states is not a findings paywall.
Which of these actually tests row-level security?
Only the ones that sign in. BreachProbe signs up two accounts and reports cross-tenant results table by table. LaunchGuard signs in as a real user and lets you save a cross-user leak as a guard it can re-run. Suparbase gets closest of the rest: its scanner is explicitly the anonymous view, but its admin can “simulate SELECT/INSERT/UPDATE/DELETE as any role with custom JWT claims. All rolled back.”, which answers the question one query at a time rather than reporting it. The Supabase Security Advisor and SecurifyAI's scanner do not publish a test of one authenticated user reading another's rows on the pages cited here. That distinction matters more than price: a policy that is enabled but wrong looks identical to a correct one from the outside, because both of them refuse an anonymous request.
Do I need to give a scanner access to my Supabase project?
Two of these ask for it. The Supabase Security Advisor runs inside the dashboard, so it needs dashboard access by construction. Suparbase asks you to “Paste a Supabase URL + API key”, which it encrypts at rest and proxies server-side so the key never reaches the browser — though its free Security Scanner needs no account. BreachProbe needs one URL and states “No account · nothing installed · read-only”. LaunchGuard scans from a URL, with sign-up (free, no card) required to see the full detail of a leaked key. SecurifyAI's scanner runs on your own machine or in your own browser, which is why it is the one to reach for when the app cannot be exposed to a third party at all.
How often should a vibe-coded app be re-scanned?
Every time you ship, because the failure mode is a new table or a changed policy rather than a new vulnerability in old code. Three of these automate it: LaunchGuard's Pro tier re-checks on every deploy automatically, Suparbase's Hosted tier runs “Agent Sentry continuous scans” as a continuous anon-key probe, and BreachProbe's $39 tier re-scans nightly for 30 days and emails on a new critical or high finding. The Supabase Security Advisor runs automatically inside the dashboard but only sees configuration. A scan you have to remember to run is a scan that stops happening in week three.
BreachProbe is not the right answer to every version of this question, and a comparison page that pretends otherwise is an advert. Each case below is a real one.
You ship every week and want the check to run itself. LaunchGuard is the only tool in this table that re-checks on every deploy automatically and keeps a history — “Memory: we remember every result and every call you made” — and at $29/month that is cheaper than buying a one-off report every month. It also covers Firebase, which BreachProbe does not.
You have not run anything yet. It is already inside the dashboard you are logged into, it runs on its own, and it sees things no external scanner can — an unindexed foreign key, a table with RLS disabled, a function with a mutable search path. Run it first, whatever else you do. It reads your project's configuration rather than your shipped app, which is why it is a different check and not a lesser one.
You want one tool that both RUNS your Supabase project and watches it, rather than a check you run at launch. Suparbase is the only option in this table that is also a working admin — prod→staging sync, a per-row audit log, inline editing, and a live RLS simulator that can “simulate SELECT/INSERT/UPDATE/DELETE as any role with custom JWT claims”. Its free tier is genuinely free forever for up to 3 connections, and at “$12 per user / month” its Agent Sentry keeps a continuous anon-key probe running, which is the cheapest standing watch here. Its five free tools — a Security Scanner, an RLS generator, a schema visualiser, a type generator and a secret scanner — also need no account at all: “no sign-up, no email wall, and no trial timer.”
You want to read the code that is testing you, or run it against something you cannot expose to a third party. It is the only option here that is open source — “This Supabase RLS scanner is open source and free to use. You can inspect the code, run it locally, and customize it” — which also makes it the only one you can point at localhost or an internal environment.
Prices and limits move, and a page quoting a stale one is worth less than a page quoting none. Every source is printed here so a reader can check it against the day they are reading this, and a job re-fetches each of these URLs on a schedule and fails when a figure above no longer appears on the page it came from.
| TOOL | SOURCE | GAVE | READ |
|---|---|---|---|
| LaunchGuard | www.launchguard.dev/pricing | What it costs, What it needs from you, Tests as a signed-in user, Tests one user reading another's rows, Re-checks after you ship, What you get | 2026-09-18 |
| Supabase Security Advisor | supabase.com/docs/guides/database/database-advisors | What it costs, What it needs from you, Tests as a signed-in user, Tests one user reading another's rows, Re-checks after you ship, What you get | 2026-09-18 |
| Suparbase | suparbase.com/pricing | What it costs, Re-checks after you ship | 2026-09-18 |
| Suparbase | suparbase.com | What it needs from you, Tests as a signed-in user, Tests one user reading another's rows, What you get | 2026-09-18 |
| SecurifyAI RLS Scanner | securifyai.co/supabase-rls-scanner-open-source-supabase-security-audit-tool/ | What it costs, What it needs from you, Tests as a signed-in user, Tests one user reading another's rows, Re-checks after you ship, What you get | 2026-09-18 |
| BreachProbe | breachprobe.thecompound.tech/ | What it costs, What it needs from you, Tests as a signed-in user, Tests one user reading another's rows, Re-checks after you ship, What you get | 2026-09-18 |
Last verified 2026-09-18. https://breachprobe.thecompound.tech/alternatives/launchguard