48-Hour Verdict · $299 · Supabase

Supabase security audit: prove who can read which rows.

A $299 senior review of row-level security, secret keys, storage policies, Edge Function auth and what your data API exposes, signed within 48 hours of access.

No mandatory callSenior-reviewedDeveloper-ready output

48 hoursFrom access
Named seniorSigns the verdict
EvidenceDeveloper-ready
AccessRead-only first

The decision before delivery

Most Supabase exposure sits in the policies.

Authorization gaps were the most common pattern in the production issues we reviewed across about 25 projects in October 2026. On Supabase, that usually means a missing or permissive policy.

01

The publishable key is public by design

Anyone can call your data API with the publishable key (formerly the anon key), so row-level security has to protect every exposed table, including ones the app never uses.

02

Login is not ownership

A policy that only checks that a user is signed in lets any user read or change another user’s rows by ID.

03

Secret keys bypass everything

A secret key (formerly the service_role key) in client code, a repository or a public function skips row-level security entirely.

Exact output

A signed verdict with a fix list you can hand over.

Findings explain exposure, evidence, remediation, acceptance criteria, dependencies, and effort.

01

Row-level security review

Every exposed table checked for RLS, with policies tied to the signed-in user, team or tenant.

02

Ownership and direct-ID tests

Requests by ID tested across accounts, not only through the interface.

03

Key and secret exposure

Supabase secret keys and other credentials traced through client code, repositories and functions.

04

Storage policy review

Buckets private by default, with policies on every upload and download path.

05

Edge Function and auth settings

Identity checks before work, redirect URLs, email confirmation and sessions.

06

Signed fix list

Severity-ranked findings with evidence, remediation, acceptance criteria and an effort band.

How the work happens

Forty-eight hours, following the data.

The method adapts to the audit domain while preserving the same evidence and accountability standard.

01Map tables, roles and keys

List exposed tables, policies, roles, functions, buckets and where each key is used.

HOUR 0–12
02Test data isolation

Request other users’ rows and files by ID and through every exposed path.

HOUR 12–30
03Review functions and settings

Check Edge Function auth, database functions that bypass RLS, and auth configuration.

HOUR 30–40
04Sign the verdict

Rank findings, write remediation and acceptance criteria, and sign the decision.

HOUR 48

An honest boundary

Know when this is—and is not—the right product.

Qualification protects both teams and prevents a compact review from being sold as certification, incident response, or an enterprise programme.

RIGHT FIT

Use this audit when a Supabase app is about to hold real data.

  • Supabase app built with Lovable, Bolt, Cursor or similar
  • Real users or customer data are arriving
  • You are not sure every table has row-level security
  • An enterprise or investor security question is coming

NOT THIS PRODUCT

Use a different qualified path when the need exceeds scope.

  • Active breach or incident response
  • Formal penetration test
  • SOC 2, HIPAA or legal certification
  • Self-hosted multi-service estates needing a full programme

Code, access, and accountability

Your code stays yours.

Read-only first

Access starts at the minimum level required to establish evidence.

NDA available

Confidentiality can be agreed before repository access is granted.

Access removed

External access is revoked at delivery or at the agreed audit-window end.

Named senior review

Automation collects evidence; a senior engineer owns and signs the decision.

Connected resources

Use the smallest useful next step.

Free tools reduce uncertainty before purchase. Service and lane links explain what happens when implementation is required.

Straight answers

Before access is granted.

How much does a Supabase security audit cost?

The 48-Hour Verdict is $299 and covers a Supabase app’s security surface against the Production Readiness Standard. Deeper multi-system reviews are scoped separately.

Do you need production access?

Read-only access to the repository and the Supabase project settings is enough to start. We do not change anything to audit it.

Is the Supabase publishable key a secret?

No. The publishable key (formerly the anon key) is meant to be public, which is why row-level security has to protect every exposed table. The secret key (formerly the service_role key) bypasses row-level security and must never reach the browser.

Do you fix the findings too?

We can. Each finding comes with remediation your own developers can follow, and we can scope the repair from the same list.

Start without a meeting

Start with the 48-Hour Verdict.

Send a short intake on the Verdict page and pay by secure checkout. A named senior engineer reviews your app and sends a signed recommendation within 48 hours of access.

What to have ready

  1. 01Your repository or app URL (no passwords or keys)
  2. 02The one concern that matters most
  3. 03Your stage: prototype, private beta, live or paying customers
  4. 04Two sentences of context
Start the Verdict — $299 Prefer to talk it through?

The next decision

Know who can read your data before your users find out.

A named senior engineer reviews your row-level security, keys, storage and Edge Functions and signs a written fix list.

Scroll to Top

Optional tracking stays off until you enable it. You can change your choice at any time.

Essential — always active
Security, requested features, and remembering these choices.

Read our cookie policy