How Cursor beat Git's scalability shortcomings
- ID
- 17049
- Status
- summarized
- Published
- 23 Aug 2026, 9:45 PM
- Fetched
- 23 Aug 2026, 10:18 PM
- Provider
- The Register
- Category
- technology
- Original URL
- https://www.theregister.com/devops/2026/08/23/how-cursor-beat-gits-scalability-shortcomings/5291421
- Source URL
- https://www.theregister.com/headlines.atom
Summary
- Score
- 7.0
- Created
- 23 Aug 2026, 10:18 PM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Cursor principal systems engineer Vicent Martí detailed how Cursor built its own Git repository service called Origin, powered by an internal engine called Continuity, using S3 object storage as the source of truth and local NVMe repositories for latency-sensitive operations. The approach addresses Git's fundamental scalability problem—servers must traverse the entire commit DAG to assemble packfiles for fetches and clones—which GitHub's Spokes architecture (three synchronized NVMe replicas) only partially solves and worsens as replica count grows. A beta of Origin is available with paid Cursor plans.
Why it matters
If you're shipping AI agents that generate high volumes of code, PRs, and CI runs against Git repositories, traditional Git server architectures become a bottleneck. Cursor's S3-as-source-of-truth model is worth studying if you're building or selecting Git infrastructure for agent-heavy workflows, and the Origin beta is available now on paid Cursor plans for teams already in that ecosystem.
Discussion angle
How AI agents multiplying PRs and CI runs expose Git's architectural limits—and whether S3-backed object storage as the source of truth is a pattern smaller teams should adopt or wait for tooling to catch up on.