What changed
On November 2, 2026, OpenAI described Pando, the new Git-compatible backend serving its monorepo. Rather than serialising unrelated branch updates through a repository-wide manifest or replicated coordination, Pando stores incoming packfiles as immutable blobs and tracks versions and dependencies for each ref in scalable metadata storage. It reuses packs across fetches. OpenAI reports that Pando now serves its entire monorepo, cut median push latency nearly fivefold and delivers nearly a petabyte of Git data per day. These are internal production measurements, not independently audited benchmarks.
Why it matters
AI coding agents increase simultaneous branches, pushes and CI fetches per engineer, stressing Git infrastructure designed for fewer concurrent writers. Pando illustrates a practical architecture choice: preserve standard Git workflows while accepting causal rather than repository-wide snapshot consistency to scale independent branches. Operators evaluating similar systems should ask what consistency guarantees their builds, release automation and cross-branch tooling actually require.
Why conventional approaches struggled
OpenAI describes replicated Git services that coordinate ref updates across nodes and object-store WAL designs that contend on a single shared manifest. Both create coordination points even for independent branch pushes. These are architectural comparisons and illustrative simulations, not a universal benchmark against every hosted Git provider.
Branch-level ordering instead of a global snapshot
Pando tracks immutable packfiles and ref versions with dependencies, serialising conflicting updates to a single ref while allowing unrelated refs to progress independently. A fetch can reconstruct the causal history needed for a requested ref, but simultaneous reads of multiple branches need not represent one global instant. Automation requiring a repository-wide atomic view must account for that limitation.
Packfile reuse changes the read path
Traditional fetches may generate client-specific packs based on objects the client already has. Pando serves reusable packfiles from storage and caches, potentially transferring some redundant objects in exchange for much less server-side computation. That is especially relevant when many agent sandboxes and CI workers fetch overlapping histories.
What the reported results establish
OpenAI reports a nearly fivefold improvement in median push latency and almost one petabyte of daily Git delivery in its own production environment. The article does not establish that other teams can reproduce those numbers with different repositories, network patterns, hardware or client behaviour. The architecture is not presented as a generally available hosted product.