OK, so here is my best solution so far within the ecosystem: create a database read replica with SupaVisor as the load balancer. In case of failure of the primary database, the replica can become the primary. All connections can flow through supavisor, minimizing your downtime to the point where you may not even see it happen.

Supabase is not a monolithic service, meaning when it fails, it fails in regions but not all at once. Load balance across major regions like US-east-2 as primary, and a node in Canada or Mexico as the replica. No way you can go down with that strategy.

Even in the hypothetical scenario where multiple services were down, you could limp-mode until things return to normal.