Browse categories
Explore
Fiverr Pro
English
$
USD
I will fix your supabase auth, rls, storage and edge function errors
Mehmet R.
About this gig
Need a production-grade fix for your Supabase app? I diagnose and resolve issues across your stack and ship with a clean PR, a short Loom walkthrough, and practical documentation.
What I fix
- Auth/OAuth: redirect loop, callback URLs, session issues, exchangeCodeForSession
- RLS/Policies: 403/empty results, data overexposure, multi-tenant isolation (tenant_id + claims)
- Storage/Signed URL: private file access, public leakage, headers/content-type
- Realtime: missing/duplicate events, channel permissions, reconnect strategy
- Edge Functions/Webhooks: 500/timeout, signature verification (Stripe, etc.), secrets
- Stripe Billing: Checkout, Customer Portal, webhooks, subscription state sync
- Performance: N+1 queries, missing indexes, slow endpoints, pagination design
- Deploy/DevOps: Vercel/Railway builds, env/DNS, image domains, preview production
Process
- Reproduce the issue (repo + URL)
- Fix & open PR
- Loom video (what changed & why)
- Docs (env/callbacks/commands) + optional test users/seed and monitoring (Sentry)
Get to know Mehmet R.
Mehmet R.
Fullstack SaaS and Automation Developer with NextJs, Supabase, OpenAI
- FromTurkey
- Member sinceJul 2021
- Avg. response time1 hour
Languages
English, Turkish
I help startups and digital businesses build scalable SaaS and automation with NextJS, Supabase, and Open AI.
What I do best;
End to end SaaS: auth to payments with NextJS, Supabase, Stripe
AI and API integrations: Open AI, Telegram, Discord, Meta
Workflow bots and automations: Python, Make automation tool, serverless
Dashboards and analytics: real time insights with optimized SQL
Send your use case and I’ll reply with a quick plan, timeline, and fixed price.
My Portfolio
FAQ
What do you need to start?
A short error description, when it happens, affected tables/modules, intended roles, and any recent changes. Optional: temporary repo access or a schema export.
Will you need access to my production data?
No. I prefer a dev or staging setup with test data. If prod access is required, we keep a clear rollback plan and limited scope.
What issues do you fix?
Auth, RLS policies, Storage, Realtime, SQL queries, performance indexes, simple triggers, and small API or UI integration related to Supabase.
How do you diagnose RLS problems?
I reproduce the flow, trace the failing call, inspect policies and role context, and test with targeted SQL to confirm the exact rule that blocks or leaks data.
How do you verify the fix?
Minimal tests or demo queries, plus an end-to-end check of the original failing action. I include notes so you can re-run the same checks.
