multigres/multigres

Health v2 · maintenance only

Adoption not part of the score

2559 stars · 130 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Multigres is an adaptation of Vitess for PostgreSQL, providing a two-level proxy layer (Multigateway and Multipooler) for connection pooling, failover shielding, and read traffic routing. It enables horizontally scalable, multi-tenant, highly available, and globally distributed Postgres deployments while remaining compatible with standard Postgres.

Use cases

• horizontally scale a Postgres database across shards
• add connection pooling in front of Postgres instances
• shield clients from Postgres restarts and failovers
• route read traffic to Postgres replicas
• run multi-tenant globally distributed Postgres deployments
• deploy sharded Postgres on Kubernetes/EKS

When to choose

• you need Vitess-style sharding and pooling for Postgres rather than MySQL
• your Postgres workload has outgrown a single node and needs horizontal scaling
• you want transparent failover and connection pooling without changing client drivers

When to avoid

• you need a battle-tested production solution today - the project is in early development
• your workload fits comfortably on a single Postgres instance
• you need full Vitess feature parity, which is not yet implemented

Facets

service · maturity experimental

database caching routing middleware databases microservices backend self-hosted go self-hosted cloud postgres sharding connection-pooling vitess horizontal-scaling high-availability proxy-layer linux docker kubernetes

Member repositories

For agents

markdown · JSON · MCP: product_card(name="multigres/multigres")