From the source
Supabase has opened a private alpha of Multigres, giving paid-plan organizations Postgres clusters that run on three nodes across availability zones with automatic failover.
- Today every Supabase project writes to a single Postgres primary, so a hardware fault or an availability-zone outage leaves the database unavailable until it is recovered, and teams that cannot accept that downtime build high availability themselves.
- Multigres is an open source operating system for Postgres built by the team behind Vitess, released as v0.1 in June under the Apache 2.0 license, and this alpha is the first time it runs on the Supabase platform.
- Supabase says failover is treated as a consensus problem rather than a monitoring one: an application is acknowledged for a write only once it has been replicated to enough nodes to survive a failure, and the remaining nodes agree on the full set of committed writes before promoting a replica.
- The alpha includes built-in connection pooling that picks its own mode per request, a single standard Postgres connection string, and support for Auth, the REST Data API, Storage, Edge Functions and the client libraries.
- It is free during the alpha for up to two projects per organization, is not available on the Free plan, and pricing may change once it leaves alpha.
- Multigres projects are not for production and are not covered by the uptime SLA, cannot be enabled on an existing project, and lack Realtime and Point-in-Time Recovery; projects are limited to East US (North Virginia) with fixed compute size, disk and replica count.
