East River Source Control has disclosed the architecture behind a source-control platform intended to address repository growth and heavier development workloads without forcing teams to abandon existing Git clients. The company is not launching the product yet, but says its system will accept the Git protocol while storing code in a custom backend rather than conventional Git repositories.
That compatibility-first approach is central to the proposal. Git is embedded throughout development tools and operational practices, making an abrupt move to another version-control system risky. ERSC says users will continue to connect with ordinary Git software, allowing organizations to change the server architecture without simultaneously retraining every developer or replacing integrations.
The company argues that AI-assisted development is exposing scaling pressures that were previously concentrated in very large engineering organizations. Agents can produce more changes and branches, increase merge contention and favor monorepositories because broad code access provides useful context. Cloud-based, isolated development environments also make fast cloning and predictable repository access increasingly important. Those are the company’s assessments of the market, not independent performance findings.
On the server, ERSC plans to replace disk-based Git repositories as the system of record with a horizontally scalable storage engine. Deployments would be isolated by customer rather than sharing one global platform, a design the company says should improve control and reduce the risk that another customer’s workload affects availability. A GraphQL interface is also part of the broader architecture described by the company.
ERSC is additionally considering Jujutsu, or jj, as a bridge to future protocols. Jujutsu already lets developers use its workflow with a Git backend, so an individual can adopt it while colleagues continue using Git. ERSC proposes mirroring that gradual transition on the server: customers could begin with Git clients, then potentially use a different protocol against the same underlying storage engine.
Important parts of that vision remain prospective. There is no upstream native Jujutsu protocol today, and ERSC explicitly says it is not claiming that such support already exists. The company says any protocol work would be documented and that necessary client modifications would be open source if developed with the community.
The disclosure is therefore an architectural statement rather than a finished-product announcement. It identifies a practical adoption strategy—preserve the interface developers already use while changing the storage beneath it—but provides no production benchmarks, customer deployments or launch date. Those details will determine whether the proposed system can deliver the reliability and scale ERSC describes.
