Cenk KurtoğluSecurity audit

Supabase · PostgreSQL · RLS

Fix the database boundary, not just the visible symptom.

I diagnose Supabase access failures involving Row Level Security, tenant isolation, auth claims, migrations and privileged server paths. The work begins with a reproducible case and ends with a reviewable fix plus regression evidence.

Contracting and payment stay on Upwork. Never send production secrets or service-role keys in chat.

01

Reproduce

Capture the failing role, query, auth context and expected boundary before changing policies.

02

Trace

Review schemas, grants, RLS predicates, JWT claims, privileged paths and relevant migrations.

03

Fix

Deliver the smallest reviewable SQL or TypeScript change that corrects the access decision.

04

Prevent

Add negative-path regression tests so the same cross-user or cross-tenant failure stays closed.

Good diagnostic inputs

Enough context to reproduce—without exposing customer data.

Before you order

Supabase debugging questions

What kinds of Supabase problems can you diagnose?

The service focuses on RLS policy behavior, authentication context, tenant isolation, grants, migrations, failing PostgreSQL queries and privileged server-side access paths.

Do I need to share production credentials?

No. Start with an anonymized schema, relevant policies, the failing role and a synthetic reproduction. Never send a service-role key or production password in chat.

What do I receive?

You receive a reproducible diagnosis, a reviewable SQL or TypeScript fix where the scope permits it, and negative-path regression evidence for the affected authorization boundary.

Where are contracting and payment handled?

The fixed-price starting scope is ordered through Upwork, where contracting, messages and payment remain on-platform.

Verify the method before hiring.

The public repository contains runnable isolation tests and the guide explains the negative-path matrix behind them.

Read the RLS testing guide →