What OpenAI’s Pando Means for Small Business Git Workflows

What OpenAI Built and Why

OpenAI created Pando, a new backend for Git repositories, to handle the staggering growth of its monorepo over the past year. According to OpenAI’s own report, the size and demands on their monorepo increased at a pace that made it clear they needed to revamp their source control system to scale to the level of concurrent work that Codex AI makes possible.

Pando is fully Git-compatible, meaning engineers and AI agents can keep using Git exactly as they always have. OpenAI deployed it without interrupting any engineering work or changing how their team uses Git. The result: Pando now powers all development in OpenAI’s monorepo, cutting median push latency by nearly 80% and serving close to a petabyte of Git data per day.

For small businesses, the key takeaway isn’t that you need to build your own Git backend. It’s that AI can dramatically increase the volume of code your team produces, and that existing tools like Git can be adapted to handle that growth without forcing your team to learn new workflows.

How Pando Works (In Plain Terms)

Pando achieves horizontally scalable writes and high read throughput by using a causal consistency model. In simpler terms, it allows multiple writers—whether human engineers or AI agents—to push code simultaneously without slowing each other down. It reuses Git’s packfile-uri mechanism to let clients pull precomputed packs from cache-friendly services, and regional caches allow it to saturate 10 Gbps links.

The system uses commit mappings recorded at push time to look up what a client has and needs, then returns download links through Git’s packfile-uri mechanism. This means that even when thousands of AI agents are pushing code every minute, the system can quickly tell each client exactly what they need to fetch, rather than forcing them to download everything.

For a small business, the architectural lesson is about separating concerns: Pando doesn’t change how Git works on the client side. It only changes the backend storage and retrieval. This means you can adopt new infrastructure without retraining your team or changing your daily workflow.

What This Means for Small Business Codebases

OpenAI’s experience shows that AI can write thousands of lines of code daily. For a small business using AI coding tools like Codex, this means your codebase can grow much faster than before. That growth can strain traditional Git setups, especially if your team is small and your infrastructure is minimal.

The good news is that you don’t need to build Pando yourself. The principles it demonstrates—caching, parallel writes, and client-side simplicity—are already available in many modern Git hosting services. Services like GitHub, GitLab, and Bitbucket have been adding similar features for years, such as partial clones, sparse checkouts, and improved caching.

What matters for a small business is planning ahead. If you’re using AI to generate code, expect your repository size and commit frequency to increase. Make sure your Git hosting service can handle that growth. Consider enabling features like shallow clones or blobless clones to keep clone times fast. And ensure your team understands how to manage a growing monorepo, even if you’re not at OpenAI’s scale.

Practical Steps You Can Take Today

First, audit your current Git workflow. How many commits do you make per day? How large is your repository? If you’re using AI coding tools, project how those numbers might change in the next six months. OpenAI’s report notes that the size and demands on their monorepo increased at a staggering pace—yours might too.

Second, enable Git performance features. Most modern Git hosting services support partial clones, which let you fetch only the files you need. Sparse checkouts let you work with a subset of your repository. These features can dramatically reduce clone and fetch times without changing how you use Git day-to-day.

Third, consider your team’s workflow. Pando was designed so that engineers and agents could keep using Git without any changes. Your tools should work the same way. If you need to upgrade your Git infrastructure, choose solutions that are backward-compatible and don’t require retraining. The goal is to let AI accelerate your development without adding complexity.

Takeaways

• AI can dramatically increase code volume, so plan for faster repository growth and more frequent commits.
• You don’t need to build custom infrastructure—modern Git hosting services already offer performance features like partial clones and caching.
• Choose tools that are backward-compatible so your team can keep using Git without retraining or workflow changes.