I will set up your supabase backend with auth, database, and row level security

O
osmium_a
O
osmium_a
Amritendu K

About this gig

Most Supabase backends I audit have misconfigured RLS meaning any authenticated user can read or edit rows that aren't theirs. That's the #1 security gap I fix.

I'll set up your Supabase project end-to-end: normalized schema, auth (email + OAuth), Row Level Security policies scoped to your actual data model, and storage wired directly into your Next.js/React codebase with typed queries if you're on TypeScript.

No placeholder policies. No "allow all" shortcuts to make the demo work. Clean migration files you can read and extend yourself.

Recent backend builds: a producer management platform, an agency landing site, and a music agency platform all shipped with the same auth/RLS approach I'll use for you.

Tell me what your app does and I'll design the schema as part of delivery you don't need one ready.

Get to know Amritendu K

Amritendu K

building sustainable systems

  • FromIndia
  • Member sinceJan 2024
  • Avg. response time1 hour
  • Languages

    English, Hindi, Bengali
Full-stack developer specializing in Supabase backends. I build auth systems, database schemas, and Row Level Security policies that don't leak data — the part most Supabase setups get wrong. Delivered backend infrastructure for a producer management platform, a software agency site, and a music agency platform. I work in Next.js/React on the frontend and treat RLS as non-negotiable, not optional.