multigres

multigres: Bring Vitess-Style Scaling to PostgreSQL

Multigres adapts Vitess for PostgreSQL, aiming to bring its approach to scaling and operating databases to Postgres deployments. It is an early-stage Go project for teams exploring PostgreSQL sharding, connection pooling, and high availability.

Stars
2.7k
Forks
153
Stars, last 30 days
+32
Last commit
today
Contributors
41

Our take

Activeregular commits and releases

Health score

61/100

How it is scored
Activity
65
Community
77
Issues
46
Pull requests
56

+32 stars in the last 30 days

  • Merges more pull requests than 90% of the projects we track

Multigres is actively developed and has broad contributor participation, but its own early-stage warning makes it better suited to evaluation than as an assumed production-ready platform.

Good fit if

  • You operate PostgreSQL and want to explore a Vitess adaptation for scaling or sharding.
  • Your team can evaluate an evolving Go project and follow its development.
  • You are deploying on EKS and can use the project's getting-started guide.

Look elsewhere if

  • You need a mature system with established production track record and clearly documented operational guarantees.
  • You need a ready-to-follow installation path in the README, which currently points readers to the project site and EKS guide instead.
  • Your environment cannot accommodate Go development or Docker and Compose requirements.
All health signals
Last commit2026-10-27 (today)
Commits, last 90 days100+
Releases, last 12 months1 (latest v0.1.0, 2026-05-30)
Contributors41 (top contributor: 22% of commits)
Issues closed, last 90 days1+
Pull requests merged, last 90 days86 (typically merged in 2 days)
Project age17 months

Checked on 2026-10-28 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

2,713

Forks

159

Change since Nov 17, 2026: +2 stars·+1 forks

Overview

Multigres is an adaptation of Vitess for PostgreSQL. It aims to address the operational challenges of scaling Postgres, including the needs behind sharding, connection pooling, and high availability, while keeping PostgreSQL at the center of the system.

The project is explicitly early in development. It is aimed at teams interested in a Vitess-style approach to Postgres operations, rather than teams seeking a mature, broadly proven deployment today.

Key Features

  • Adapts the Vitess approach for PostgreSQL.
  • Targets horizontal scaling and sharding for Postgres deployments.
  • Focuses on database connection pooling.
  • Targets high-availability use cases.
  • Provides an EKS getting-started guide.
  • Publishes PostgreSQL regression, isolation, and extension test status through CI badges.

Use Cases

  • PostgreSQL operators investigating a Vitess-inspired path to horizontal scaling.
  • Platform teams evaluating sharding approaches for a growing Postgres workload.
  • Teams considering connection pooling and high availability as part of a distributed Postgres architecture.
  • Developers assessing whether an early-stage Postgres infrastructure project fits a future deployment.

What you need

Detected in the repository

  • Go 1.26 or newer (from go.mod)
  • A Dockerfile, so it can run in a container; a Compose file sets up the related services
  • Automated checks on GitHub Actions

License in plain words

Apache-2.0permissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license, the NOTICE file and a note of your changes
  • Share your changes: no
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Visit the Multigres site to try the project. For EKS, follow the getting-started guide. See the developer documentation for contribution and development details.

Considerations

The project describes itself as early-stage, so teams should validate its capabilities and operational fit before relying on it for critical workloads. Development is active, with recent commits and a release in the past year, and contributions are not dominated by one person. The README invites minor bug fixes and feedback, while saying major contributions will open up later. Go, Docker, and Compose are listed requirements. The project uses the Apache-2.0 license; review its terms for your intended use.

Found this useful?

Share it with someone who would like multigres.

Comparisons