{"slug": "multigres", "name": "Multigres", "category": "databases", "category_name": "Databases", "description": "", "recommenders": 4, "commenters": 6, "warners": 0, "score": 4.106, "rising": 0.02, "first": "2025-12-13", "latest": "2026-09-10", "why": "One of my favorite solutions so far is https://multigres.com/!", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 4, "neutral": 3, "compare": 1, "warn": 0}, "spark": [0, 1, 0, 0, 0, 0, 0, 1, 1, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "One of my favorite solutions so far is https://multigres.com/!", "kind": "", "icon": true, "domain": null, "github_repo": "github.com/multigres/multigres", "official_url": "https://multigres.com", "pricing": "", "aliases": ["Multigres"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 790929200, "item_id": 49433075, "url": "https://news.ycombinator.com/item?id=49433075", "by": "massimodeluisa", "date": "2026-08-25", "stance": "recommend", "quote": "One of my favorite solutions so far is https://multigres.com/!", "excerpt": "I already read the article in your website: https://planetscale.com/blog/the-history-of-postgres-sharding, which I found very interesting. One of my favorite solutions so far is https://multigres.com/!", "context": "", "use_case": "", "switched_from": "", "story": "The History of Postgres Sharding"}, {"id": 782945200, "item_id": 48934075, "url": "https://news.ycombinator.com/item?id=48934075", "by": "hasyimibhar", "date": "2026-07-16", "stance": "recommend", "quote": "Multigres is being built in public since day 1", "excerpt": "I'm surprised no one has mentioned Multigres yet, they are the competitor of Neki. I'm a big fan of both and has been following them since they were announced last year. I think this blog post is the first time they are talking about the internals of Neki. In contrast, Multigres is being built in public since day 1, you can see their high-level architecture here [1], though I'm still waiting for more details on their", "context": "", "use_case": "", "switched_from": "", "story": "Making 768 servers look like 1"}, {"id": 781205857, "item_id": 48825366, "url": "https://news.ycombinator.com/item?id=48825366", "by": "khurs", "date": "2026-07-07", "stance": "recommend", "quote": "Supabase one is open from start", "excerpt": "Looked it up, says 'Will be released as an open source project' but announcement was in July 2025 and no public repo yet which is strange, so time will tell if they will stick to this. https://planetscale.com/blog/planetscale-for-postgres#vitess-for-postgres https://planetscale.com/neki ... Supabase one is open from start: https://github.com/multigres/multigres https://multigres.com/", "context": "", "use_case": "", "switched_from": "", "story": "Why we built yet another Postgres connection pooler"}, {"id": 775767697, "item_id": 48485481, "url": "https://news.ycombinator.com/item?id=48485481", "by": "hasyimibhar", "date": "2026-06-10", "stance": "recommend", "quote": "I'm highly optimistic they will solve a lot of the problems Postgres have.", "excerpt": "What about Multigres[0]? It builds on top of Postgres and adds HA (based on Flexible Paxos[1]), sharding, etc. They're still not production-ready, but I'm highly optimistic they will solve a lot of the problems Postgres have. For example, with Multigres, you should be able to achieve true zero downtime major version upgrade by simply resharding [2]. With vanilla Postgres + pgBouncer, you can only achieve near-zero do", "context": "", "use_case": "Postgres HA and sharding", "switched_from": "", "story": "PgDog is funded and coming to a database near you"}, {"id": 740118768, "item_id": 46257423, "url": "https://news.ycombinator.com/item?id=46257423", "by": "benjiro", "date": "2025-12-13", "stance": "recommend", "quote": "when its complete. From the guy that made Vitess for Mysql.", "excerpt": "https://github.com/multigres/multigres ... when its complete. From the guy that made Vitess for Mysql. And yes, i agree, the PG failover setup (and especially dealing with a failure afterwards, to restore the ex-master is beyond infuriating). But its not pay 10x the amount, while eating easily 10x performance infuriating :)", "context": "", "use_case": "", "switched_from": "", "story": "Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["postgres ha and sharding", "sharded postgres", "sharding layer for postgres", "horizontal postgresql scaling"], "compared": [{"slug": "neki", "name": "Neki", "co": 4, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 774463248, "item_id": 48403953, "url": "https://news.ycombinator.com/item?id=48403953", "by": "kiwicopple", "date": "2026-06-04", "stance": "recommend", "quote": "we have released Multigres v0.1", "excerpt": "Hey HN, Supabase CEO The main highlight here is that we have released Multigres v0.1: https://supabase.com/blog/multigres-v0-1-alpha This is open source and self-hostable. It\u2019s not production ready yet. That will take a few more months You can find instructions for running the operator in EKS here https://github.com/multigres/multigres/blob/43db3a4873922eeebc463f8e249d0b5f214e93f1/docs/kubernetes/eks.md", "context": "Supabase CEO", "use_case": "Postgres scaling", "switched_from": "", "story": "Supabase Series F"}], "threads": [{"url": "https://news.ycombinator.com/item?id=48819308", "title": "Why we built yet another Postgres connection pooler", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=48476466", "title": "PgDog is funded and coming to a database near you", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49645686", "title": "Neki \u2013 Sharded Postgres", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49432960", "title": "The History of Postgres Sharding", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48930075", "title": "Making 768 servers look like 1", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48403289", "title": "Supabase Series F", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"recommend": 1}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {"neutral": 1}, "2026-06": {"recommend": 1, "neutral": 1}, "2026-07": {"neutral": 1, "recommend": 1}, "2026-08": {"recommend": 1}, "2026-09": {"compare": 1}, "2026-10": {}}, "quotes": [{"id": 794369521, "item_id": 49648095, "url": "https://news.ycombinator.com/item?id=49648095", "by": "xyzzy_plugh", "date": "2026-09-10", "stance": "compare", "quote": "multigres[0], Supabase's equivalent to Neki", "excerpt": "I love how the Planetscale CEO has been shitting on multigres[0], Supabase's equivalent to Neki, and gloating about how superior Neki is, and yet Neki is not even open source! Sam, it feels like you're just playing games. It's hard to take anything you say or do seriously. Are you going to OSS this thing? Or have you decided to backpedal? Congrats on the checks notes closed launch, I guess? 0: https://github.com/mult", "context": "", "use_case": "sharded Postgres", "switched_from": "", "story": "Neki \u2013 Sharded Postgres"}, {"id": 790929200, "item_id": 49433075, "url": "https://news.ycombinator.com/item?id=49433075", "by": "massimodeluisa", "date": "2026-08-25", "stance": "recommend", "quote": "One of my favorite solutions so far is https://multigres.com/!", "excerpt": "I already read the article in your website: https://planetscale.com/blog/the-history-of-postgres-sharding, which I found very interesting. One of my favorite solutions so far is https://multigres.com/!", "context": "", "use_case": "", "switched_from": "", "story": "The History of Postgres Sharding"}, {"id": 782945200, "item_id": 48934075, "url": "https://news.ycombinator.com/item?id=48934075", "by": "hasyimibhar", "date": "2026-07-16", "stance": "recommend", "quote": "Multigres is being built in public since day 1", "excerpt": "I'm surprised no one has mentioned Multigres yet, they are the competitor of Neki. I'm a big fan of both and has been following them since they were announced last year. I think this blog post is the first time they are talking about the internals of Neki. In contrast, Multigres is being built in public since day 1, you can see their high-level architecture here [1], though I'm still waiting for more details on their", "context": "", "use_case": "", "switched_from": "", "story": "Making 768 servers look like 1"}, {"id": 781205857, "item_id": 48825366, "url": "https://news.ycombinator.com/item?id=48825366", "by": "khurs", "date": "2026-07-07", "stance": "recommend", "quote": "Supabase one is open from start", "excerpt": "Looked it up, says 'Will be released as an open source project' but announcement was in July 2025 and no public repo yet which is strange, so time will tell if they will stick to this. https://planetscale.com/blog/planetscale-for-postgres#vitess-for-postgres https://planetscale.com/neki ... Supabase one is open from start: https://github.com/multigres/multigres https://multigres.com/", "context": "", "use_case": "", "switched_from": "", "story": "Why we built yet another Postgres connection pooler"}, {"id": 781171472, "item_id": 48823217, "url": "https://news.ycombinator.com/item?id=48823217", "by": "khurs", "date": "2026-07-07", "stance": "neutral", "quote": "Supabase are launching a Vitess for Postgresql", "excerpt": ">might bringt Postgres finally closer to vitess Supabase are launching a Vitess for Postgresql, they have hired the original creator of Vitess for it https://supabase.com/blog/multigres-vitess-for-postgres", "context": "", "use_case": "Sharding layer for Postgres", "switched_from": "", "story": "Why we built yet another Postgres connection pooler"}, {"id": 776162864, "item_id": 48510179, "url": "https://news.ycombinator.com/item?id=48510179", "by": "znpy", "date": "2026-06-12", "stance": "neutral", "quote": "Maybe it works, maybe it doesn't.", "excerpt": "> What about Multigres[0]? According to they githyb (https://github.com/multigres/multigres) as of today (June 12th, 2026): > Multigres is a Vitess adaptation for Postgres. The project is currently in the early stages of development. Maybe it works, maybe it doesn't. I would start looking into it when it gets released as stable. Otherwise it's unfair.", "context": "", "use_case": "Postgres HA and sharding", "switched_from": "", "story": "PgDog is funded and coming to a database near you"}, {"id": 775767697, "item_id": 48485481, "url": "https://news.ycombinator.com/item?id=48485481", "by": "hasyimibhar", "date": "2026-06-10", "stance": "recommend", "quote": "I'm highly optimistic they will solve a lot of the problems Postgres have.", "excerpt": "What about Multigres[0]? It builds on top of Postgres and adds HA (based on Flexible Paxos[1]), sharding, etc. They're still not production-ready, but I'm highly optimistic they will solve a lot of the problems Postgres have. For example, with Multigres, you should be able to achieve true zero downtime major version upgrade by simply resharding [2]. With vanilla Postgres + pgBouncer, you can only achieve near-zero do", "context": "", "use_case": "Postgres HA and sharding", "switched_from": "", "story": "PgDog is funded and coming to a database near you"}, {"id": 767555728, "item_id": 47972233, "url": "https://news.ycombinator.com/item?id=47972233", "by": "hasyimibhar", "date": "2026-05-01", "stance": "neutral", "quote": "AFAIK that's what Multigres[0] and Neki[1] are trying to solve.", "excerpt": "AFAIK that's what Multigres[0] and Neki[1] are trying to solve. [0] https://multigres.com/ [1] https://neki.dev/", "context": "", "use_case": "Horizontal PostgreSQL scaling", "switched_from": "", "story": "Does Postgres Scale?"}, {"id": 740118768, "item_id": 46257423, "url": "https://news.ycombinator.com/item?id=46257423", "by": "benjiro", "date": "2025-12-13", "stance": "recommend", "quote": "when its complete. From the guy that made Vitess for Mysql.", "excerpt": "https://github.com/multigres/multigres ... when its complete. From the guy that made Vitess for Mysql. And yes, i agree, the PG failover setup (and especially dealing with a failure afterwards, to restore the ex-master is beyond infuriating). But its not pay 10x the amount, while eating easily 10x performance infuriating :)", "context": "", "use_case": "", "switched_from": "", "story": "Indexing 100M vectors in 20 minutes on PostgreSQL with 12GB RAM"}]}