Sentris logo

Sentris

For developers: Sentris scans your Supabase app for security exposures like leaked keys and unguarded routes so you fix vulnerabilities before attackers find them.

Built by Luca Urti · Developer Tools · SaaS · Freemium

Visit website

In category: #226 of 988 · Developer Tools

Sentris is a Community listing on Launch Llama with 52 total upvotes, founded by Luca Urti who joined in Aug 2026, compared against 5 alternatives.

Community listing

Listing status

52upvotes

Community score

Luca Urti (Joined Aug 2026)

Founder

Launched on Launch Llama Aug 17, 2026 · #20 of 122 that day

Sentris

About

Sentris scans your Supabase repository and live application to detect critical security exposures including leaked service_role keys, tables without row-level security, public storage buckets, and unguarded routes. It provides exact file locations, masked evidence, and copy-paste fixes for each finding. Free scanning available with paid tiers for full four-check analysis and enterprise pentests.

Competitors: Snyk, GitGuardian, Wiz, Lacework, Semgrep

Key Features

  • Scan Supabase repositories for leaked API keys and exposed credentials
  • Detect tables missing row-level security configurations
  • Identify publicly accessible storage buckets
  • Flag unprotected application routes and endpoints
  • Receive exact file locations and line numbers for each vulnerability
  • Access templated fixes and remediation code snippets

Use Cases

  • Run Sentris's free security scan on your Supabase repository to identify leaked service_role keys and misconfigured tables before deploying to production
  • Use Sentris to detect tables missing row-level security policies and get exact file locations and copy-paste fixes to implement them immediately
  • Scan your live Supabase application with Sentris's paid tier to check all four security categories including unguarded routes and public storage buckets
  • Leverage Sentris's masked evidence reports to audit security exposures across your team without exposing sensitive credentials in findings
  • Schedule Sentris enterprise pentests to conduct comprehensive security assessments of your Supabase infrastructure as part of your release process

Who it is for

  • Developers building Supabase apps with AI coding tools like Claude Code, Cursor, or Windsurf
  • Indie makers and small teams shipping AI-written code to production
  • Security-conscious developers who want file-and-line evidence for each finding

Pricing

Scanning is free with no login required. Findings and fixes start at $19/month, and you can cancel any time.

View Sentris pricing →

FAQ

Is this a penetration test?

No, and it never claims to be. Sentris reports reproducible findings with evidence, at a point in time. It is not a pentest, not a certification, and carries no warranty. If you need an attestation to close an enterprise deal, you need a pentest firm, not us.

Do you store my code?

No. The repo is never cloned. Files are read during the scan and discarded when it ends. What we keep is the findings, and any secret inside them is masked before it is written anywhere.

Can Sentris write to my repo?

Only if you switch it on, per repository, and it is off for every repository until you do. When it is on, Sentris opens a pull request that adds exactly one new file: a migration closing findings it confirmed against your running system. It never pushes to your default branch, never replaces an existing line, never merges anything, and never opens a pull request for something it could not prove. Secrets are excluded on purpose: a pull request that deletes a leaked key creates false safety, because the key is still compromised and only you can rotate it. Leave the switch off and Sentris behaves exactly as it did before this existed.

What if you find nothing?

You get a clean result that lists exactly what was checked and what is explicitly out of scope, so you know what the result covers. Then it keeps re-scanning on your plan's schedule (weekly on Starter, nightly on Pro and Team) and alerts you the first time something new appears. The value is the ongoing 'still clean', not only the first report.

Isn't this just ChatGPT reading my code?

Four of the deep scan's six stages have no model in them at all: the repo is partitioned by a table of rules, candidates are deduplicated deterministically, the coverage ledger is arithmetic, and suppression is a set operation. The model appears twice: once to read a component and once, in three independent lenses, to try to disprove what the first pass claimed. After that a finding has to quote your file character-for-character or it is dropped before it is stored. And with no model key configured, a deep scan returns exactly the deterministic rule checks rather than an error: the AI half can be absent without the product being broken.

Does my code end up training someone's model?

Nothing is kept here to train on: the repo is never cloned and the files are discarded when the scan ends. During the scan itself the file contents do go to a model provider. That is what an AI pass is, and any tool that runs one and tells you otherwise is worth a second look. The current provider is named on the subprocessors page rather than in this answer, so it stays accurate when it changes. If you want none of it, leave the deep scan off: the rule checks are pattern matching on our own machines and never send your code anywhere.

How do you keep false positives down?

Two ways. Rules classify by capability, so anon and publishable keys, which belong in your client, are never flagged. And anything code alone cannot prove is labelled potential rather than sold to you as a breach. Every detector has clean and vulnerable cases, and the clean repo must return zero findings before a repo rule ships. The repo and Deep Scan corpus is also the measurement: precision 1.000 and recall 1.000 across 38 planted findings in 11 repositories, published in full at /precision with the date, the commit and the command to reproduce it. Nobody else in this category publishes theirs.

Supabase already warns me about missing RLS. Why do I need this?

Because the advisor reads your running database, and that is only one of the places these mistakes live. It cannot see the migration sitting in your branch before it ships, it cannot see the service_role key your client bundle is serving to every visitor, and it cannot see a route handler that takes an id and never checks who is asking. It also does not watch: it answers when you open it. Sentris covers all four surfaces and re-checks them on a schedule. If missing RLS is genuinely your only concern, use the advisor: it is free and it is good.

What do I get for $19?

Every exposure the deterministic checks find, each with the exact file and line, masked evidence, and a copy-paste fix, plus re-scans on a schedule that alert you the first time something new appears. Scanning itself is free and needs no login: you see the count and the grade before you pay anything. What you are paying for is where they are and how to close them. Worth saying plainly: a URL-only scan reaches four of the checks, because the rest of them live in code a browser never sees. Connect the repo and a free scan runs all twenty rule checks instead of four, still without paying. The AI pass is the part that needs a subscription, because it spends tokens. No trial maze, no upsell ladder.

Can I see a real report before I pay?

Yes, the whole thing, at /sample. It is an unedited scan of a deliberately vulnerable Supabase app we maintain, rendered by the same code that renders a customer's report: every finding, every file and line, the masked evidence and the SQL fix. We publish that repo rather than a customer's, and nothing on the page is trimmed for the screenshot.

Alternatives

More in Developer Tools

All Developer Tools tools

New on Launch Llama

Launched this week · This month's launches · All products A–Z

Tags

#supabase security#security scanner#row-level security#leaked api keys#vulnerability scanning#storage bucket audit#unguarded routes#pentesting

Ask AI about Sentris

ChatGPT Claude Perplexity Grok

Supporters

15 founders

15 founders supported Sentris on Launch Llama.

TomAshkan SotoudehNikolaos KorakianitisHey BristolNicolasRakesh Kumar RAbdul Haseeb
+3

Reviews

1 comment

Luca UrtiComment
Aug 17, 2026

I've been building in public on X for a few weeks, and Sentris actually started as a totally different idea (lead-magnet micro-tools for SaaS founders). But the more I worked with AI-generated code, the clearer it got: the real gap is security. Vibe-coding makes it super easy to ship fast — but just as easy to miss an open Supabase table or a secret sitting in the client bundle. So I rebuilt Sentris from scratch: an automated scanner that takes a GitHub repo and/or a live URL, detects the typical exposures (missing RLS, leaked keys, IDOR, public storage buckets), and shows you the fix directly.

Third-party sources

For bots & AI agents

Machine-readable versions of Sentris and Launch Llama. Fetch these instead of parsing this page.

This listing (.md) llms.txt llms-full.txt ai.txt Full catalog (.md) Endpoint index API docs MCP server MCP manifest Developer docs