> Projects like postgrest have been down this journey and spell out their solutions. It's all a little vague with Supabase Just in case it's not entirely clear

> Projects like postgrest have been down this journey and spell out their solutions. It's all a little vague with Supabase Just in case it's not entirely clear: supabase is just PostgreSQL + PostgREST. We contribute to + maintain PostgREST, so if it works with PostgREST it also works with Supabase. > there isn't anything magical about their authorization approach either I 100% agree with this, and that's intentional. We don't want to do anything special here, we want our solutions to be as interoperable as possible with existing approaches