OpenAI's Pando swaps out the Git backend while engineers keep using Git as before — and pushes get nearly 80% faster. In its November 2 engineering post, "Scaling Git at OpenAI," OpenAI unveiled Pando, a homegrown backend that keeps the Git protocol and client and replaces only the service behind the repository, built to absorb the parallel development load Codex has created. It matters not because it is another internal tool, but because it shows that the version-control bottleneck of the agent era does not have to be solved by replacing Git; replacing the backend can work too.
OpenAI engineers built Pando with Codex in about 10 weeks: one engineer designed the core, agent teams implemented it, and a handful of engineers deployed it, all in Rust. It began carrying production traffic in April 2026. According to OpenAI, Pando now serves nearly 1 PB of Git data per day, peaks at 57 TB of packs in a single hour, and cuts median push latency nearly fivefold. The pressure came from Codex: engineers and agents pushing, fetching, cloning, and merging across many branches at once, until merge reliability at times fell below 90%.
How Pando speeds things up without changing workflows
Pando gives up repository-wide, point-in-time consistency in favor of causal consistency: updates to unrelated branches proceed in parallel, while the order of changes within a branch is preserved. It also reuses stored packs to serve heavy repeated fetch traffic, and compacts small packs into larger ones in the background so clients catching up do not have to fetch every fragment. The two goals are stated plainly: writes must scale horizontally with the number of branches, and reads must saturate network bandwidth. For teams, the change lives on the server; local push, pull, and clone commands stay exactly as they are.
Pando is an internal system — the Anthropic contrast clarifies the boundary
Pando currently serves only OpenAI's own monorepo; it is not a public product. OpenAI says it is studying how to offer the technology to outside users, and has already contributed its Git fixes upstream. Anthropic faced the same problem and chose a different path in October: Anthropic's homegrown Scion replaces Git outright. Side by side, the practical conclusion is clear: once agents push commit volume up, the work that matters is how the server coordinates concurrency, not forcing every developer to switch tools.
