Multigres private alpha: automatic failover for Supabase Postgres

Supabase has launched Multigres in private alpha to provide managed high availability for paid-plan projects through three-node Postgres clusters distributed across availability zones, automatic failover, and integrated connection pooling. Built as an Apache 2.0 open-source system by the team behind Vitess, Multigres operates around standard Postgres rather than modifying it, managing routing, replication, backups, pooling, and failover while retaining a standard connection string and compatibility with most Supabase services. Its consensus-based approach uses synchronous replication so writes are acknowledged only after reaching enough nodes to survive a failure, aiming to prevent acknowledged commits from being lost during promotion of a new primary. The alpha is free for up to two projects per organization but is not intended for production, lacks SLA coverage, Realtime support, point-in-time recovery, cross-region replicas, resizing, and migration paths to or from standard projects; it is currently limited to newly created projects in East US and cannot be combined with OrioleDB.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.