Cursor's official account @cursor_ai revealed the storage design of its own Git hosting service, Origin, at 1:57 a.m. KST on August 19, 2026. The post said, "We're making Git hosting more reliable, faster, and more scalable," and that it "traces 20 years of Git infrastructure history and explains how that history led us to design and run Origin like a database." The full explanation is in Cursor's official blog post, "Git at any scale."
Why build Git hosting as a database?
According to Cursor's official explanation, the core of Origin is a write-ahead log (WAL). Every push is first written as a WAL entry to S3-compatible object storage and counts as complete only once it is fully stored. Copies of repositories also live on the servers' fast NVMe disks, but they are a reproducible cache for actual Git operations, not the source of truth. If a repository disappears from a particular server, it is immediately rebuilt on another server from the WAL. Which server owns which repository is decided by rendezvous hashing rather than a separate database, and if routing is briefly wrong, the system responds by rebuilding the repository on another server instead of failing.
What does 22.6 commits per second mean?
Cursor said it demonstrated a throughput of 22.6 commits per second on a single repository with this design. Cursor's argument is that Git hosting from the era of humans committing by hand was never designed with this kind of throughput in mind. Origin is compatible with the Git protocol and can be extended through an API and MCP (Model Context Protocol). This figure, however, comes from Cursor's own published demo environment and has not been validated by an independent benchmark. Origin is currently rolling out in early beta to the Pro, Teams, and Enterprise paid plans, and no general availability date has been announced.
The timing, and mixed reactions so far
The announcement drew attention because it coincided with a major GitHub outage. According to Cryptonomist's report, Origin's reveal overlapped with a spike in GitHub error rates. Replies to the official post also captured practitioners' real reactions. Questions like "How is this different from GitHub?" and "Does a two-person team need this?" followed, and one user pointed out, "How many people will actually read a post this long?" These are anonymous individual opinions with no statistical representativeness, but they show that Origin is still in beta, and that it's safer to hold off on an adoption decision until you've compared it with GitHub in real use.