# Supabase — Multigres private alpha: automatic failover for Supabase Postgres

- Company: Supabase (supabase.com)
- Announced: 2026-10-29
- Category: availability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://supabase.com/blog/multigres-private-alpha
- Record: https://forck.live/items/29430-multigres-private-alpha-automatic-failover-for-supabase-postgres
- Subject: Supabase
- License: Apache 2.0
- Pricing: free during the alpha for up to two projects per organization

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.

## Evidence

Verbatim from https://supabase.com/blog/multigres-private-alpha:

> Multigres brings high availability to Supabase projects, and it's now in private alpha. Organizations on a paid plan can request access and create projects that run Postgres on three nodes across availability zones, with automatic failover and connection pooling included.
> 
> Today, every Supabase project writes to a single Postgres primary. This works well for most applications, and it will stay the default. The downside is what happens when the primary fails. If the underlying hardware has a fault or its availability zone has an outage, your database is unavailable until it is recovered.
> 
> Teams that can't accept that downtime usually build high availability themselves. They run replicas, add a failover manager, put a pooler in front, and write runbooks for the cases the tooling doesn't handle. The hardest part is making sure no committed writes are lost when a replica is promoted. With Multigres, Supabase takes care of all of this for you.
> 
> What is Multigres? #
> 
> Multigres is an open source operating system for Postgres, built by the team behind Vitess . Vitess was created at YouTube to scale MySQL. In 2025, we announced Multigres to build the same kind of system for Postgres.

---

Record: https://forck.live/items/29430-multigres-private-alpha-automatic-failover-for-supabase-postgres
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md