Uploaded July 2026 | Updated November 2026, 14 hours ago
Use promo code TECHBRO to try managed Hermes with Hostinger today: hostinger.com/techbro10
Here's how I scaled my Supabase app to 45,000 users and the two specific optimizations that made the biggest difference in performance.
This is the third video in my scaling series. Most of the heavy lifting happened between 0 and 10,000 users, but at 45,000 we started hitting real latency issues that forced two specific changes. The first was moving away from row-level security rules as our primary query defense mechanism, which was adding 10 to 20 seconds of load time as our database grew. The second was migrating from Supabase's getUser to getClaims, which shaved off up to two seconds per authenticated request. I also get into whether dropping RLS is actually a security risk and how I think about the tradeoffs.
The app I'm building is Yorby, an AI social media marketing tool, currently running on the same Supabase tier we've been on since 10,000 users with a compute upgrade along the way.
Chapters:
00:00 45K Users Milestone
00:41 Proof and What Yorby Is
02:31 Fix #1: Row-Level Security Was Killing Performance
04:35 Sponsor: Hermes by Hostinger
05:55 Is Dropping RLS Actually Safe?
08:57 Fix #2: Migrating from getUser to getClaims
10:12 Wrap Up
Check Out Yorby, the social media marketing tool for startups: https://www.yorby.ai?utm_source=yatb-yt
Want to work with me 1:1? Book some time with me at youraveragetechbro.com
Check out my AI-powered interview prepping tool: perfectinterview.ai/?utm_source=yatb-yt
Check out my latest SaaS product to start automating your job: montee.ai/?utm_source=yatb-yt
Follow me on TikTok: tiktok.com/@youraveragetechbro
Follow me on Instagram: instagram.com/youraveragetechbro
#supabase #nextjs #buildinpublic
Use promo code TECHBRO to try managed Hermes with Hostinger today: hostinger.com/techbro10
Here's how I scaled my Supabase app to 45,000 users and the two specific optimizations that made the biggest difference in performance.
This is the third video in my scaling series. Most of the heavy lifting happened between 0 and 10,000 users, but at 45,000 we started hitting real latency issues that forced two specific changes. The first was moving away from row-level security rules as our primary query defense mechanism, which was adding 10 to 20 seconds of load time as our database grew. The second was migrating from Supabase's getUser to getClaims, which shaved off up to two seconds per authenticated request. I also get into whether dropping RLS is actually a security risk and how I think about the tradeoffs.
The app I'm building is Yorby, an AI social media marketing tool, currently running on the same Supabase tier we've been on since 10,000 users with a compute upgrade along the way.
Chapters:
00:00 45K Users Milestone
00:41 Proof and What Yorby Is
02:31 Fix #1: Row-Level Security Was Killing Performance
04:35 Sponsor: Hermes by Hostinger
05:55 Is Dropping RLS Actually Safe?
08:57 Fix #2: Migrating from getUser to getClaims
10:12 Wrap Up
Check Out Yorby, the social media marketing tool for startups: https://www.yorby.ai?utm_source=yatb-yt
Want to work with me 1:1? Book some time with me at youraveragetechbro.com
Check out my AI-powered interview prepping tool: perfectinterview.ai/?utm_source=yatb-yt
Check out my latest SaaS product to start automating your job: montee.ai/?utm_source=yatb-yt
Follow me on TikTok: tiktok.com/@youraveragetechbro
Follow me on Instagram: instagram.com/youraveragetechbro
#supabase #nextjs #buildinpublic










