Centralised authentication?
Hi,
I’m exploring how to design a Supabase backend that supports a centralised authentication service while also having separate backend instances for each region.
At a high level, the architecture I’m considering looks like this:
Authentication → Region Router (based on IP or user location) → APAC / Americas / Europe instance
Can anyone please advise on the recommended setup or best practices for achieving this type of architecture with Supabase?
I’d love to understand what’s possible regarding centralised user management while maintaining regional data separation.
I’m exploring how to design a Supabase backend that supports a centralised authentication service while also having separate backend instances for each region.
At a high level, the architecture I’m considering looks like this:
Authentication → Region Router (based on IP or user location) → APAC / Americas / Europe instance
Can anyone please advise on the recommended setup or best practices for achieving this type of architecture with Supabase?
I’d love to understand what’s possible regarding centralised user management while maintaining regional data separation.
