I will build a secure supabase backend with row level security and tests


About this gig
Most Supabase projects ship with RLS either switched off or written by guesswork. Both end the same way.
I write the database layer properly.
What I do:
- Schema design with constraints enforced in Postgres, not just in your UI
- Row-level security policies per table and per role, written to be readable later
- Multi-tenancy where one organisation can never see another's rows
- RPCs for the operations that shouldn't be a client-side query
- pgTAP tests proving each policy denies what it should, and the suite is yours to keep
- Realtime, triggers and migrations set up so your team can keep moving
I run a multi-tenant POS platform on exactly this: every venue isolated by row-level security, realtime broadcast from the database, money stored as integer minor units, with a pgTAP suite in CI.
Tell me your tables and your roles, and I'll show you where the current policies leak before you order.
Get to know Kenneth F
Full Stack Developer building internal ops tools with React and React Native
- FromIndonesia
- Member sinceJan 2024
- Avg. response time1 hour
Languages
English, Indonesian, Japanese

