FeatureFuel
1

Native rate limiting for client-side SELECT requests to prevent egress abuse

Source: supabase/supabase#44131 · opened by @ericzager0
I have a Next.js SaaS on Vercel that communicates directly from the browser with Supabase, secured with RLS. My concern is that a malicious authenticated user could script millions of SELECT calls from the browser console and generate huge egress costs. Is there any native Supabase mechanism to prevent this without routing requests through a server-side proxy?

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests