---
title: "Multigres v0.1 Alpha: an operating system for Postgres"
description: "Multigres v0.1 alpha is an open-source release of a system intended to provide Vitess-grade horizontal scaling, high availability, and operational simplicity for Postgres. It manages Postgres instances with sharding, connection pooling, automatic failover, and backup orchestration, while this release adds advanced pooling, automatic failovers, and a Kubernetes operator. Its high-availability protocol builds on unmodified Postgres replication, supports user-defined durability policies, resolves split-brain scenarios without losing succeeded commits, and permits replica changes while running. The release is suitable for experimentation but not production workloads: v0.1 is single-shard, sharding is absent, the custom-resource API may change, backward compatibility is not guaranteed, and performance benchmarks are still in progress."
---

# Multigres v0.1 Alpha: an operating system for Postgres

[Supabase](https://yomu.fyi/company/supabase) · sugu\_sougoumarane · Jun 4, 2026

**Type:** Announcement

## Summary

Multigres v0.1 alpha is an open-source release of a system intended to provide Vitess-grade horizontal scaling, high availability, and operational simplicity for Postgres. It manages Postgres instances with sharding, connection pooling, automatic failover, and backup orchestration, while this release adds advanced pooling, automatic failovers, and a Kubernetes operator. Its high-availability protocol builds on unmodified Postgres replication, supports user-defined durability policies, resolves split-brain scenarios without losing succeeded commits, and permits replica changes while running. The release is suitable for experimentation but not production workloads: v0.1 is single-shard, sharding is absent, the custom-resource API may change, backward compatibility is not guaranteed, and performance benchmarks are still in progress.

## Context

Postgres at scale is described as operationally complex because teams must manage read replicas, failovers, connection limits, backups, and related operational tasks. The release is intended to bring horizontal scaling, high availability, and operational simplicity to Postgres, but it is explicitly not ready for production workloads.

## Approach / What changed

Multigres holistically manages Postgres instances through a Kubernetes operator and a system combining high availability, connection pooling, and backup orchestration. Its two-service pooler uses a multigateway for routing and a multipooler for backend connections; HA uses generalized consensus on top of unmodified Postgres replication; backups use pgBackRest and are taken from replicas.

## Takeaways

- The HA protocol supports user-defined durability policies, including cross-zone durability, instead of requiring a fixed majority-quorum rule.
- The connection pooler tracks request state, pins stateful requests when necessary, maintains separate per-user pools, and consolidates prepared statements across gateways.
- The alpha is a single-shard release; sharding is not included, the CR API is unstable, future releases may not be backward compatible, and performance benchmarks are pending.

**Tags:** [Kubernetes](https://yomu.fyi/topic/kubernetes), [Open Source](https://yomu.fyi/topic/open-source), [Postgres](https://yomu.fyi/topic/postgres), [Reliability](https://yomu.fyi/topic/reliability), [Scalability](https://yomu.fyi/topic/scalability)

- Source: [Supabase](https://supabase.com/blog/multigres-v0-1-alpha)
- Source URL: https://supabase.com/blog/multigres-v0-1-alpha
- Ingested by Yomu: 2026-08-30T08:00:52.849Z

[Read original post](https://supabase.com/blog/multigres-v0-1-alpha)