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.
48-Hour Verdict · $299 · Supabase
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
The decision before delivery
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.
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.
A policy that only checks that a user is signed in lets any user read or change another user’s rows by ID.
A secret key (formerly the service_role key) in client code, a repository or a public function skips row-level security entirely.
Exact output
Findings explain exposure, evidence, remediation, acceptance criteria, dependencies, and effort.
Every exposed table checked for RLS, with policies tied to the signed-in user, team or tenant.
Requests by ID tested across accounts, not only through the interface.
Supabase secret keys and other credentials traced through client code, repositories and functions.
Buckets private by default, with policies on every upload and download path.
Identity checks before work, redirect URLs, email confirmation and sessions.
Severity-ranked findings with evidence, remediation, acceptance criteria and an effort band.
How the work happens
The method adapts to the audit domain while preserving the same evidence and accountability standard.
List exposed tables, policies, roles, functions, buckets and where each key is used.
HOUR 0–12Request other users’ rows and files by ID and through every exposed path.
HOUR 12–30Check Edge Function auth, database functions that bypass RLS, and auth configuration.
HOUR 30–40Rank findings, write remediation and acceptance criteria, and sign the decision.
HOUR 48An honest boundary
Qualification protects both teams and prevents a compact review from being sold as certification, incident response, or an enterprise programme.
RIGHT FIT
NOT THIS PRODUCT
Code, access, and accountability
Access starts at the minimum level required to establish evidence.
Confidentiality can be agreed before repository access is granted.
External access is revoked at delivery or at the agreed audit-window end.
Automation collects evidence; a senior engineer owns and signs the decision.
Connected resources
Free tools reduce uncertainty before purchase. Service and lane links explain what happens when implementation is required.
Straight answers
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.
Read-only access to the repository and the Supabase project settings is enough to start. We do not change anything to audit it.
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.
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
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
The next decision
A named senior engineer reviews your row-level security, keys, storage and Edge Functions and signs a written fix list.
We use optional cookies for analytics and marketing. You can accept or reject them.