# multigres/multigres

Vitess for Postgres

Repository: https://github.com/multigres/multigres
Canonical: https://ross.abutalabs.com/products/multigres
Homepage: https://multigres.com
Language: Go
License: Apache-2.0
License Family: permissive
Topics: connection-pooling, database, distributed-systems, high-availability, horizontal-scaling, postgres, postgresql, sharding, vitess
Last push: 2026-08-26T18:28:46+00:00

## Health v2 (maintenance only)
Score: 70/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 54, longevity 32
- inputs: {"age_days": 449, "days_push": 7, "days_rel": 96, "gap_med": null, "n_releases_24m": 1}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2559, forks 130 (observed 2026-08-28T04:07:00.895267+00:00)

## What it is
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
- artifact type: service
- maturity: experimental
- function: database, caching, routing, middleware
- domain: databases, microservices, backend, self-hosted
- platform: go, self-hosted, cloud
- tags: postgres, sharding, connection-pooling, vitess, horizontal-scaling, high-availability, proxy-layer, linux, docker, kubernetes

## Member repositories
- multigres/multigres (main) score 70

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:00.895267+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:23:33.346281+00:00, confidence not recorded.
  - readme: https://github.com/multigres/multigres (fetched 2026-08-28T04:07:00.895267+00:00, sha f039b7c02e0e)
  - homepage: https://multigres.com (fetched 2026-08-29T10:06:08.440625+00:00, sha ec73dfe4ac1d)
  - site_page: https://multigres.com/docs (fetched 2026-08-29T10:06:08.449240+00:00, sha de7439e3d368)
- Data as of 2026-08-30T08:39:29.467469+00:00.