Your Supabase is broken and it's the middle of the night.

I'm awake. Send me the error, I'll fix it before you wake up.

$100flat · no hourly · no scope creep

→ You pay after it works. Not fixed, not paid.

What I actually fix

RLS that won't behave. infinite recursion detected in policy, rows leaking across tenants, or a policy that silently returns zero rows.
Permission errors that make no sense. SECURITY DEFINER functions exposed to anon, views that lost security_invoker, permission denied for table.
Edge Functions failing in production. CORS preflight passing but POST dying, 150s timeouts, cold-start errors, secrets not loading.
Migrations that won't apply. Diverged history, non-idempotent migrations, numbering collisions, a db push that wants to drop your data.
PostgREST queries returning the wrong shape. Ambiguous embeds with two foreign keys, PGRST300, schema cache stale after a change.
Postgres that got slow overnight. Missing index, a query plan that flipped, connection pool exhaustion, lock contention.

Don't take my word for it — audit yourself first

I wrote a free, open-source SQL file that finds twelve of the failure modes above in your own project. Paste it into the Supabase SQL Editor and run it. No install, no npm package, no connection string handed to a stranger — it only reads system catalogs, so you can check what it does before you run it.

github.com/Concepto505/supabase-audit · MIT

If it comes back clean, you didn't need me and it cost you nothing. If it comes back with a list you'd rather not spend your night on, that's what the $100 is for.

Or just read what I've written about these

Five write-ups on the failures above — the mechanism, the fixes that look right and aren't, and how to tell them apart in thirty seconds:

infinite recursion detected in policy for relation — and the three fixes that don't work.
Every function you create is callable by anon — until you say otherwise. Postgres grants EXECUTE to PUBLIC by default.
42501 on INSERT, when the INSERT policy is innocent — RETURNING is gated by your SELECT policy.
The RLS mistake that costs 10,000x and never throws an error — 178 seconds to 12 milliseconds.
Your Edge Function CORS error is usually not a CORS problem — it's a 500 you can't see.

If one of them solves your problem for free, good. That's the point of writing them down.

How it works

You send the error, the relevant schema or file, and read access if it's needed.
I diagnose and tell you the root cause in plain language — usually within the hour, free, before any money moves.
I fix it and hand you the patch plus a one-line explanation of why it broke.
You verify it works. Then you pay $100 by PayPal. If it isn't fixed, you owe nothing and you keep the diagnosis.

Why the diagnosis is free: you have no reason to trust a stranger at 2am. So I take the risk, not you. If I can't solve it, I'll tell you straight away instead of billing you for four hours of guessing.

Straight answers

Who are you? David Borrás, developer based in Spain, registered self-employed. I build production Supabase/Postgres apps every day — invoicing engines, OCR pipelines, multi-tenant systems with real RLS. I don't have a public portfolio, which is exactly why I don't ask you to pay up front.

Is my code safe? I only ask for the minimum needed to fix the problem. No credentials pasted in chat — use a scoped key and revoke it when we're done. Happy to sign an NDA before you send anything.

What if it's bigger than one bug? I'll tell you after the free diagnosis. The $100 covers one clearly-defined problem. Anything larger, we agree a price first or you walk away.

Send me the error

Or email david_bc3@hotmail.es. Reply usually within the hour while it's night in Europe.