GitHub’s Rubicon Git Architecture Targets Concurrent AI Agents
GitHub announced Rubicon, a next-generation Git storage architecture designed for high-volume agentic development. In company-reported internal testing, it supported 5,000 concurrent agents working on one repository and 7,200 pushes per second while maintaining consistently low read latency. The architecture is currently available in a limited private preview, with broader rollout planned for early next year.
Rubicon separates Git object storage, request handling, and reference updates so repositories can scale concurrent agent activity without changing standard Git workflows.
Last week at GitHub Universe, we announced our new Git storage architecture, capable of handling thousands of writes per second with reads that scale on demand. Through internal testing, we’ve demonstrated the ability to support 5,000 concurrent agents working on a repository, sending 7,200 pushes per second to a repo, all while serving read traffic with consistently low latency. This new architecture is the foundation for GitHub to support agentic development for hundreds of millions of developers, and we’ve been building it underneath GitHub while it keeps running.
Over the past year, agents changed what a busy repository looks like on GitHub. In our first post in this series, we laid out the two principles behind our next-generation Git storage architecture: minimize coordination, and decouple storage from compute. In our last post, we covered the bridge: moving 99.99999% of repositories into Azure, scoping the write quorum to individual references, and standing up virtual replicas backed by Azure Blob Storage.
We also left off with an observation: very little of a write needs to be ordered. Git objects are immutable and named by their contents, meaning two writers can store them at the same time without agreeing on anything. The part of a push that needs agreement is the reference update, and a reference update is tiny in comparison. Virtual replicas were the first step toward building around that, and the means by which we onboard repositories to the new architecture.