An update on East River Source Control availability

# An update on ERSC availability | East River Source Control Source: [https://ersc.io/blog/ersc-availability](https://ersc.io/blog/ersc-availability) East River Source Control is building a code hosting platform to meet the needs of modern development environments\. Our version control model is based on[Jujutsu](https://docs.jj-vcs.dev/latest/), with first class conflicts, fine\-grained ACLs, and backwards compatibility with git\. Taking inspiration from how Google, Meta, and others have done code hosting, we've built a storage engine that performs at scale\. We're building for a world where machines and humans are iterating and writing code faster than ever\. That means a distributed system that can land thousands of commits per second, instant checkouts, and support for arbitrarily sized files\. Our storage engine speaks git and "jj"[1](https://ersc.io/blog/ersc-availability#user-content-fn-1), so you can adopt it*today*, with new capabilities being available when you need them\. Rather than building a better git server, we've opted to build the substrate that comes next\. We're currently trialing the product with early partners and are onboarding more teams in the near future\. Our focus is on best in class code collaboration for teams, not social features\. Code review coming soon, and yes, there will be stacked diffs[2](https://ersc.io/blog/ersc-availability#user-content-fn-2)\. [Request Early Access](https://ersc.io/cdn-cgi/l/email-protection#7f1c10110b1e1c0b3f1a0d0c1c511610400c0a1d151a1c0b423a1e0d13065a4d4f1e1c1c1a0c0c5a4d4f0b105a4d4f3c171e11181a0c1a0b) 1. jj does not have an official native protocol yet, but we intend to work with upstream on something great[↩](https://ersc.io/blog/ersc-availability#user-content-fnref-1) 2. There is no other reasonable way to review code\. Stacked diffs are table stakes\.[↩](https://ersc.io/blog/ersc-availability#user-content-fnref-2)