Our live SaaS client portal is throwing critical errors and I need an experienced hand on it right now. Supabase Row-Level Security is behaving unpredictably—authorized users are being blocked, a few unauthorized requests are slipping through, and the resulting data inconsistencies are starting to show on customer dashboards. On the Next.js side, server-side rendering is intermittently breaking, some API routes are timing out, and client-side data fetching isn’t hydrating properly after page transitions. Because the portal is already in production every minute counts; you’ll be working directly in the live environment, so a solid track record with both Next.js and Supabase in production is non-negotiable. Deliverables I need from you: • Stable, correct RLS rules that reliably gate access. • Working SSR output with zero hydration mismatches. • Repaired API routes returning expected data and status codes. • Verified data-fetch hooks that stay in sync with Supabase real-time updates. • A concise changelog summarising what you touched so I can trace the fixes. Acceptance criteria: – No access denial for valid sessions, no unauthorized reads or writes. – Lighthouse and console are clean of SSR or hydration warnings. – All portal features that depend on affected routes pass manual smoke testing. – You demonstrate the fix in a short Loom or live call before we deploy. I’m ready to give you immediate repo access and jump on a call as soon as you respond. Please include at least one link to a Next.js + Supabase project you’ve shipped so I know you can hit the ground running.