Skip to main content
CursorIntegration

How Cursor beat Git's scalability shortcomings

What happened

Cursor built its Git repository service, Origin, on Amazon Web Services' S3 object storage to manage scalability.

Source

Article excerpt

DEVOPS S3 keeps the source of truth while local NVMe repositories do the latency-sensitive work Developers recently burned by GitHub’s system outages should take note that there are other ways to manage Git at scale. One approach, recently put into action by Cursor, is to build the distributed version control system on object storage. A recent post from Cursor principal systems engineer Vicent Martí explains how the SpaceX subsidiary worked through its scaling issues with the notoriously fickle Git distributed version control system. The post explains how Cursor arrived at an architecture for its own Git-based repository service called Origin, which is powered by an internal engine called Continuity. A beta of the service is available with paid Cursor plans. “Agents have fundamentally changed the way we work with software, and in many ways they've made this situation worse. More code, more PRs, more CI runs. Version control is at the core of all of this, and it is possibly the hardest thing to change overnight,” Martí wrote. Martí speaks from experience, having worked at GitHub through much of the last decade when the company arrived at its own current architecture for managing Git. Git creator Linus Torvalds designed his software to work as a content-addressable data store, where all the objects are stored and indexed by the SHA-1 hash of their contents. Git sees a...

Keep reading with a free account

The rest of this article, and every signal for Cursor, is in your free account.

Extracted from this sentence

With Origin, pushes are uploaded into S3 in a write-ahead log (WAL), capturing all changes as immutable objects.

Extracted by Autobound

From the Signal API record
Event
Integration

What this signalsA new integration often shows which tools the company builds around.

Product
Origin

Companies

  • Amazon Web ServicesPartneraws.amazon.com

More integration signals at other companies

The full record

From the Signal API record

Topics and mentions

Product tags

  • online technology
  • general technology

Extraction

Confidence
90%
Detected
Aug 23, 2026
signal_type
news
signal_subtype
integrates_with

Use this data

Get every integration signal for Cursor and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Cursor this week?”

  2. Send it to your own tools

    The Signal API returns integration signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full news record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/0875d0ee-9600-1918-5ee8-ccf635250fd8 returns this record as JSON. POST /v1/companies/enrich returns every signal for cursor.com.

{
  "signal_id": "0875d0ee-9600-1918-5ee8-ccf635250fd8",
  "signal_type": "news",
  "signal_subtype": "integrates_with",
  "detected_at": "2026-08-23T13:45:00+00:00",
  "company": {
    "name": "Cursor",
    "domain": "cursor.com"
  },
  "data": {
    "url": "https://www.theregister.com/devops/2026/08/23/how-cursor-beat-gits-scalability-shortcomings/5291421",
    "title": "How Cursor beat Git's scalability shortcomings",
    "excerpt": "DEVOPS S3 keeps the source of truth while local NVMe repositories do the latency-sensitive work Developers recently burned by GitHub’s system outages should take note that there are other ways to manage Git at scale. One approach, recently put into action by Cursor, is to build the distributed version control system on object storage. A recent post from Cursor principal systems engineer Vicent Martí explains how the SpaceX subsidiary worked through its scaling issues with the notoriously fickle Git distributed version control system. The post explains how Cursor arrived at an architecture for its own Git-based repository service called Origin, which is powered by an internal engine called Continuity. A beta of the service is available with paid Cursor plans. “Agents have fundamentally changed the way we work with software, and in many ways they've made this situation worse. More code, more PRs, more CI runs. Version control is at the core of all of this, and it is possibly the hardest thing to change overnight,” Martí wrote. Martí speaks from experience, having worked at GitHub through much of the last decade when the company arrived at its own current architecture for managing Git. Git creator Linus Torvalds designed his software to work as a content-addressable data store, where all the objects are stored and indexed by the SHA-1 hash of their contents. Git sees a repository...",
    "product": "Origin",
    "summary": "Cursor built its Git repository service, Origin, on Amazon Web Services' S3 object storage to manage scalability.",
    "planning": false,
    "image_url": "https://image.theregister.com/5291465.jpg?imageId=5291465&x=0&y=0&cropw=100&croph=100&panox=0&panoy=0&panow=100&panoh=100&width=1200&height=683",
    "confidence": 0.9,
    "product_data": {
      "name": "Origin",
      "full_text": "Git-based repository service called Origin",
      "fuzzy_match": false
    },
    "product_tags": [
      "online_technology",
      "general_technology"
    ],
    "published_at": "2026-08-23T13:45:00Z",
    "article_sentence": "With Origin, pushes are uploaded into S3 in a write-ahead log (WAL), capturing all changes as immutable objects.",
    "related_company_name": "Amazon Web Services",
    "related_company_domain": "aws.amazon.com"
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.