Invest1 distinct publisher3 min readUpdated
Origin keeps GitHub as the source of truth. That is both the reason engineering orgs can try it this quarter and the reason it is not yet an exit.
The Investor · Invest desk

Compiled by The InvestorSomething wrong?How this is made
Cursor began shipping Origin, its GitHub-interoperable code-hosting platform, to paying customers on Monday morning [1]. About three and a half hours later GitHub's incident log opened a global degradation that ran 6h42m [2][3], which matters less as a coincidence than as a data point: according to Cryptopolitan, GitHub logged 257 outages over the past year [4].
That works out to a mean of roughly one logged incident every 1.4 days [5]. Monday's was not a mild one. Error rates across pull requests, issues and the API sat near 20%, pushing errors on archive and raw file downloads toward 50% [6], and it took down enterprise sign-on along with SAML, OIDC, SCIM provisioning, Team Sync and Copilot [7]. Identity and provisioning are the part enterprises actually price when they sign a hosting contract.
The interesting thing about Origin is how little it asks. Pushes still go to GitHub, which remains the definitive source for anything that originated there [8]. Permissions are identical to GitHub's read/write model [9]. Pull request comments sync both directions, so a comment written in Cursor shows up in GitHub and the reverse [10], and Cursor says GitHub-hosted repositories can sit alongside Cursor-hosted ones [11]. Existing GitHub Actions workflows run without rewriting [12], with Vercel generating a preview per pull request and Depot and Buildkite running builds [13]. The product pitch is agents, code and review in one place: send the agent a review comment and it edits the pull request [14].
Read that as a switching-cost strategy rather than a replacement. There is no migration, no permission remodelling, no CI rewrite, which is why a platform team can pilot it inside a sprint. It also means Origin does not route around a GitHub failure, because by design the writes still land there [8]. Guillermo Rauch, Vercel's chief executive, said on X that developers could host on Origin and deploy to Vercel, which was online unlike GitHub, then conceded he was making light of the fact that Vercel itself was stuck because of the GitHub outage [15]. Cursor's Matt Palmer quote-tweeted the launch and said the team had wanted to ship earlier, but GitHub was down [16]. Launches are booked weeks ahead and there is no evidence Cursor engineered the overlap [17].
The incumbent's scale is the counterweight. GitHub's Octoverse 2025 count reported 180 million developers, 630 million repositories and 43.2 million pull requests merged monthly, up 23% year over year [18], and it remains the largest source code host, owned by Microsoft [19]. Those merge volumes work out to about 1.4 million a day, meaning a 6h42m degradation covers a window in which roughly 400,000 merges would normally clear [20].
Cursor bought the code-review company Graphite in December 2025 at a price well above its $290 million Series B valuation [21], and Graphite co-founder Tomas Reimers now runs Origin [22], having first shown it at Cursor's Compile conference in June [23]. The stated premise leans on Google's 2025 DORA report, drawn from almost 5,000 professionals: writing code requires extensive reviewing [24].
Watch for the moment Origin offers to be the source of truth rather than a mirror, because that is when the switching cost stops being zero and the procurement conversation starts. Watch enterprise identity, since SSO and SCIM were what broke on Monday [7]. And watch whether 23% merge growth [18] or 257 logged incidents [4] is the number engineering leaders quote in their next renewal.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Cursor opened Origin, its GitHub-interoperable code-hosting platform, to paying customers on Monday morning.
About three and a half hours after Cursor's Monday morning rollout, GitHub's incident log listed a global degradation.
GitHub logged 257 outages over the past year, a series of failures the report ties to a visible exodus of high-profile users.
During the outage, error rates across pull requests, issues and the API were around 20%, driving the error rate on archive and raw file downloads toward 50%.
The outage brought down enterprise sign-on, as well as SAML, OIDC, SCIM provisioning, Team Sync and Copilot.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Single-publisher relay of unlinked primary artifacts
Every claim traces to one secondary article. It cites checkable primaries — GitHub's incident log, Cursor's blog, Octoverse 2025, Google's 2025 DORA report, X posts — but links none, and no second publisher corroborates the outage metrics, the 257-outage count, or the Graphite deal terms. Product-mechanics claims (source of truth, permission parity, Actions compatibility) are vendor-stated and untested by the reporter. The article does earn credit for disclaiming coordination between launch and outage.
Day-one paid availability with ecosystem hooks, no usage data
There is real, dated adoption signal — Origin is shipping to paying customers, and named third parties (Vercel previews, Depot and Buildkite builds, unchanged GitHub Actions) are wired in — but zero usage evidence: no customers, repo counts, migrated teams, or seat numbers. The counterweight is that GitHub's incumbency is quantified at 180M developers and 630M repositories, and Origin by design keeps GitHub authoritative, so what exists is trial-grade availability rather than displacement.
Exodus framing overshoots a keep-GitHub-authoritative product
The narrative pairs a 257-outage count and a 'visible exodus of high-profile users' with a launch that explicitly retains GitHub as the source of truth — the architecture contradicts the migration story the framing implies. Outage drama is amplified by a Cursor employee's quote-tweet and a Vercel CEO pitch delivered while Vercel was itself blocked. The article partially self-corrects by noting launches are booked weeks ahead with no evidence of engineered timing, and the incident metrics themselves look specific, which keeps the gap moderate rather than severe.
Vendor and partner amplification around a rival's bad day
The named voices all gain from the framing: a Cursor employee amplifying the launch against GitHub's downtime, and Vercel's CEO directing developers to host on Origin and deploy to Vercel while conceding Vercel was stuck on the same outage. Cursor has just spent above a $290M valuation acquiring Graphite and installed its co-founder over Origin, so it needs the review-layer thesis to land. The publisher is a crypto-focused outlet running newsletter promotion and a boilerplate disclaimer, which signals traffic incentives, though no undisclosed sponsorship is evidenced.
Low: one publisher, undefined key metric, ambiguous dating
Confidence is limited by structure, not plausibility. One publisher, no corroboration, no links to the cited logs and reports, an undefined 'logged outage' unit behind the headline number, an unnamed acquisition price, and relative dating ('Monday', 'in June', 'last October') that the publication timestamp does not resolve. Product-mechanics claims are internally consistent and the reporting flags its own coincidence caveat, which supports a floor above the minimum.
build
GitHub's autoscaler watched the wrong meter, and auth, CI and Copilot fell together3 distinct publishers
build
Claude Code now outruns Copilot roughly two to one in JetBrains' survey of 15,000 developers1 distinct publisher
build
Agent Plugins 1.0.0 standardises file paths. Anthropic still owns the behaviour.1 distinct publisher
build
AI-written code fails the same four ways, and every gate you own reports green1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 19, 2026