FeatureFuel
31

Rate limits on postRest or graphql

Source: supabase/supabase#19493 · opened by @Jonatthu
How to configure or make rate-limiting decisions on each table or per action, with custom logic based on auth.jwt() or other things.

If I call from the frontend using anon key with or without JWT supabase.from('users').select('id, name') <-- What's the reate limits for this? How can I update the logic being used?

The only work around is to disallow anon and authenticated roles to use supabase queries on the frontend at all and set everything behind a edge functions and apply Upstash, but that does not seem what supabase is trying to achieve.

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