The Multigres team writes about its Postgres scaling project, covering sharding architecture, consensus, replication, and formal verification with TLA+.
HN commenters mention Multigres as the Postgres counterpart to Vitess, built by Vitess's creator, and link its TLA+ post on a pg_rewind bug.
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 sharding model.
[1] https://multigres.com/docs/architecture
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/
> Side node: The guy that wrote Vitess for Mysql, is also working on multigress (https://multigres.com/), a solution that does the same. Aka Vitess for postgres.
And also was the founder of planetscale
> It's infamously hard to exhaustively unit-test concurrency.
a useful example from last week where TLA+ found a bug in pg_rewind:
https://multigres.com/blog/2026/05/04/tla-pg-rewind
Your probably better off with the original flavor (the guy that made Vitesse)
https://multigres.com/
He is making a open source version of porting Vitesse to Postgres.