A 3-person startup raised $5.5M to make Postgres shard without touching your code
PgDog is a Rust proxy that shards, pools and load-balances PostgreSQL — and claims 2M queries per second in production across dozens of deployments. The thread is full of people who already run it, and one who asks how three people will QA all this.
You change only your connection string, not your app. The open-source version has 1.4M Docker pulls; the round is from Basis Set, YC and Pioneer Fund.
Simon Willison's request was the most telling product feedback: ship a plain binary, because he won't fire up Helm or Docker just to kick the tires.
What PgDog is, and what it claims
The funding post is the source, so the claims come straight from it. PgDog raised $5.5M from Basis Set, YC, Pioneer Fund and other investors. It's a proxy layer that makes PostgreSQL horizontally scalable — "a sharding solution, connection pooler, and load balancer" written in Rust — and its pitch is that you only change your database connection string, "no application code changes required."
The traction numbers are concrete: "more than 2M queries per second, in production, across dozens of deployments," and it has "sharded over 20 TB." The open-source build has passed 1.4M Docker pulls, with a new release weekly. The team is three people with Postgres-scaling experience from places like Instacart, and there's an AWS-targeted Enterprise edition with SLA support in the works.
The thread is a reference check, and it mostly passes
What makes this more than a press release is that production users showed up unprompted. One reported a clean migration off the standard pooler:
"I've moved from pgbouncer to pgdog a few months ago without issue. Huge fan." — ParadisoShlee
Another named a feature that earns its keep in a specific failure mode:
"It really helped us scale our connection proxy needs pretty substantially and it has great features like auto mode to support Aurora failovers neatly. It's infra that just works." — maherbeg
The most useful product feedback came from a name worth listening to. Simon Willison, creator of Datasette and co-creator of Django, flagged the adoption friction directly:
"have more than just helm and Docker in your quickstart documentation. I'd like to try this out … Is there a binary I can run directly?" — Simon Willison
The skeptics: positioning gaps and a QA worry
Not all of it was applause. A high-karma engineer flagged a missing competitive frame — why this over the established sharding extension:
"It's surprising they don't mention advantages over other sharding systems like Citus. Maybe it's just the fact that it's only a proxy and not core extensions? But that could limit capabilities." — jeremyjh
Someone caught what looked like an undersell, suggesting the "20 TB" figure is conservative: "20TB isn't that big. I would imagine they've sharded a lot more than that." And the bluntest concern was about headcount versus surface area — a proxy sitting in the hot path of everyone's database is a scary place for bugs:
"How are 3 developers going to QA this properly?" — 999900000999
The real question the money answers
A connection pooler is undifferentiated plumbing; sharding-without-code-changes is not. The bet $5.5M is making is that a meaningful number of teams have outgrown a single Postgres box but can't face rewriting their data layer — and will pay for a proxy that hides the sharding. The thread's mix of "it just works" testimonials and "how will three people maintain it" doubts is exactly the tension that funding is meant to resolve: turning a beloved open-source proxy into infrastructure people trust in the write path.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
Eric Ries on why good companies rot: it's not corruption, it's 'financial gravity'
The Lean Startup author ran an AMA for his new book, Incorruptible. His sharpest line: he's 'sick and tired of helping people become rich and miserable, creating great companies only for them to be destroyed out of the gates.'