When we finally decided to rip our Postgres graph engine out of our codebase and open-source it, we needed a name. No clever branding. No missing vowels. Just raw, unadulterated infrastructure naming conventions. We settled on pgGraph.
The Goal
Our goal is simple and entirely unreasonable: We want to do to graph what pgvector did to RAG.
But before we could unleash this upon the world, we needed a domain. This is usually the part where you start screaming.
The Domain Problem
If you are building infrastructure in 2026, you do not expect to get the exact .com for your product. You expect it to be held hostage by a guy who registered it in 2004 and now wants fifty grand. Combine 'pg' with 'graph' and the odds of the .com being available are the same as C++ memory safety. Zero.
We sat down, cracked our knuckles, and prepared for war. We fully expected to settle for a .io, a .dev, or some cursed hyphenated variant. We typed pggraph.com into the registrar just to see how much the squatter was going to extort us for.
It wasn't parked. It wasn't listed at a premium.
It was just available. For $10.
We stared at the screen. We refreshed the page. We checked if we were hallucinating from sleep deprivation. Still available. We slammed the 'Buy' button so hard I think my mouse switch broke.
The Signal
Building infrastructure is a miserable grind. You fight the compiler, you fight the benchmarks, you fight the query planner, and then you fight your own architecture. But every once in a while, the simulation breaks and gives you a clear, blinding signal that you are building the exact right thing at the exact right time.
Finding the absolute most definitive .com for Postgres graph infrastructure sitting completely empty for ten dollars? That's a glitch in the matrix.
The documentation is now live. You can read it at pggraph.com. Let's build.