Saturday Aug 22
PRODUCTCursor

Cursor Launches A GitHub Rival

22AUG
GITHUB DOWNORIGIN OPEN

GitHub went down for six hours. That same day Cursor launched Origin, its own code hosting platform. Repos, pull requests, browsing, plus agent features it says are coming.

GitHub has had 257 outages in the past year, per LeadDev. The August 18 one hit a 20% global error rate. Cursor shipped Origin into that window.

Origin does not ask you to leave. It syncs with GitHub and passes code both ways. Low switching cost is the whole pitch, and it is a smart one.

Cursor closed its SpaceX acquisition three days before this launch. GitHub still has 180 million developers. The editor company is now coming for the repo.

full brief & sources

⚡ Why this matters

  • The editor company is moving into the repo. That changes who owns the developer workflow.
  • GitHub's reliability record is now a competitive opening, not just an annoyance.
  • Low switching cost is the design. Origin syncs with GitHub instead of demanding a migration.

🔍 What happened

  • Cursor launched Origin to paid users on Monday, August 18.
  • It covers repository storage, pull requests, code review and collaboration, with day-one integrations from Vercel, Depot and Buildkite.
  • GitHub went down globally the same day for roughly six hours and forty minutes, with error rates near 20%.
  • LeadDev counted 257 GitHub outages in the past year.
  • Origin syncs existing GitHub repos both ways rather than forcing a move.
  • SpaceX closed its acquisition of Cursor three days before the launch.

💬 Smart takes

  • Cursor changelog: "Your GitHub repos can sit alongside the ones Cursor hosts. Connect GitHub to Cursor, pick your org, and you'll see the repos you can sync."
  • Cursor's team: says the outage timing was coincidence, not strategy.
  • Skeptic: GitHub has 180 million developers, Actions, Codespaces and a decade of org permissions. A sync feature is not a migration path.

🧭 Where this goes

  1. LikelyOrigin lands with small teams already all-in on Cursor, not with enterprises.
  2. LikelyGitHub ships a reliability post and an agent feature within the quarter.
  3. Possiblethe agent-native features Cursor promised become the real differentiator, not hosting.
  4. Possibledual hosting becomes normal and neither side wins outright.
  5. Wild CardSpaceX ownership becomes a procurement blocker for some enterprise buyers.

🥄 The Spoon Take

Hosting is not the product here. The repo is where agents need to live, and Cursor wants that surface before GitHub locks it down. Shipping into a six-hour outage was luck. Building it to sync rather than migrate was the actual strategy, and it is a good one.

🤔 Pushback

GitHub has 180 million developers and a decade of enterprise plumbing. One bad outage does not move any of them.

·TechCrunch - launch and outage·VentureBeat - AI coding race·Cursor - Origin changelog