Supabase · Auth · Data
Supabase in preview with the anon key everywhere is not a backend. Production needs RLS, the right URLs, and secrets off the client.
We connect Replit apps to Supabase for database, auth, and the APIs around them. We also troubleshoot the Agent setup: service role in the frontend, policies that don't exist, or a project that only ever talked to localhost.
This is the same work as database help, with a named stack. Migrations, permissions, and the auth callback that still points at a Replit URL.
PostgreSQL-only apps without Supabase live on the next page. If you're not sure which you have, send the Replit — the review will say.
What we do
01
Tables, auth, storage, and which keys the Replit is actually using.
02
RLS, user-scoped rows, and admin paths that aren't a secret URL.
03
URL, anon vs service, and the deploy that still has preview values.
What we skip
Related
Frequently Asked Questions
Fixed fee · 3–5 days · credited toward the finish