East River Source Control Challenges Git to Solve Agentic Scaling

Steve Klabnik, representing East River Source Control (ERSC), has declared that Git is no longer sufficient for the technical demands of 2025 and beyond. The company is developing a next-generation version control system (VCS) designed to handle the scaling pressures of modern software engineering without forcing developers to abandon their existing workflows.

To achieve this, ERSC is building a system that speaks the Git protocol but replaces the standard Git repository storage on the server with a custom, horizontally scalable storage engine. This architectural shift allows the system to maintain compatibility with existing tools while removing the bottlenecks inherent in Git's original design. Additionally, ERSC intends to support multiple protocols over this single storage engine, specifically highlighting Jujutsu (jj) as a primary path for incremental adoption.

The Pressure of Agentic Development

Git has remained the industry standard since the mid-2000s, but its architecture was built for a different era of collaboration. While massive organizations have long struggled with performance in multi-billion line monorepos, a new catalyst is accelerating the need for change: agentic development.

According to ERSC, the rise of AI agents is a primary driver for new VCS requirements. Because agents can produce code significantly faster than humans, they increase repository sizes and create higher levels of merge contention. "Agents are bringing big company problems to the rest of us," Klabnik wrote in a recent blog post, noting that the volume of commits generated by AI is pushing traditional systems to their limits.

Industry Implications

If ERSC successfully bridges the gap between the ubiquitous Git protocol and a more scalable backend, it could fundamentally change how enterprises manage their code. The primary hurdle for any new VCS has always been the "network effect"—the massive ecosystem of CI/CD pipelines, IDE integrations, and developer habits built around Git.

By maintaining protocol compatibility, ERSC aims to lower the barrier for companies to move away from Git's architectural limitations. This approach allows organizations to gain the benefits of a horizontally scalable engine without requiring a total rewrite of their infrastructure or a disruptive migration for their engineering teams.

The Path Forward

As the industry shifts toward cloud-based environments and AI-driven coding, the demand for faster clone times and higher commit throughput is expected to grow. While alternatives like Perforce and Mercurial exist, ERSC's strategy focuses on coexistence rather than total replacement.

For now, the industry will be watching to see if ERSC's custom storage engine can deliver on its promise of horizontal scalability while remaining invisible to the end user. "Put plainly, we do not believe that Git is the future of source control," Klabnik stated, signaling a broader push toward a more flexible, protocol-agnostic future for version control.