GitHub's replacement is now
under SpaceX.
Cursor shipped a beta of its own Git hosting platform, Origin, to paid users on August 17-18, 2026 — the same day a major GitHub outage hit. It's on by default for paid users, and reports say its data-handling terms were unpublished at launch.
The beta landed the
same day GitHub went down
Cursor rolled out a beta of Origin, a new service it positions as "Git hosting for the AI-agent era," to paid users on August 17-18, 2026. VentureBeat reports this shipped ahead of the originally planned "fall 2026" timeline. It's designed around AI agents reading and writing code, not human review, and ships with native Cursor integration, a CLI, and GitHub sync.
The launch date happened to coincide with a major GitHub outage. VentureBeat frames it as GitHub's outage "exposing an opening" in the AI-coding race — the timing of Origin's launch itself read as a jab at a rival's weak moment.
Where your code lives is also a choice
about whose company it lives under.
Owning the hosting layer
means escaping GitHub
SpaceX's acquisition of Cursor (Anysphere) formally closed on August 14, folding it into a new "SpaceXAI" division. Origin shipped right after.
SpaceX signed the all-stock deal to acquire Cursor for roughly $60B on June 16, and it formally closed on August 14, with about 391 million shares of SpaceX Class A stock issued to Anysphere as consideration, TechTimes reports. SpaceX had already absorbed xAI earlier this year, so Cursor now sits in the same corporate family. Origin's launch is being framed as the capstone of a vertical-integration strategy: owning code hosting, the backbone of developer infrastructure, instead of depending on an outside party (GitHub, owned by Microsoft).
GitHub belongs to Microsoft, which also runs a competing coding AI, GitHub Copilot. From Cursor's perspective, staying dependent on a rival-owned company for where its users' code lives was a long-term liability. Origin folds that hosting layer into Cursor's own corporate group to close that gap.
Different by
design, not just by name
| Origin (Cursor / SpaceXAI) | GitHub (Microsoft) |
|---|---|
| Designed around AI agents reading/writing | Designed around human review |
| On by default for paid users | Existing workflows continue unchanged |
| Same corporate family as SpaceX, xAI | Also ships its own AI via Copilot |
Who this matters to,
and how
Engineers
Simply being on a Cursor paid plan could mean your code starts flowing into Origin without you noticing. It's worth checking the on/off state in settings.
Business and procurement leads
GitHub's near-monopoly on dev infrastructure now has a SpaceX-and-xAI-backed alternative — reduced vendor lock-in is a real upside, but it's still a beta with a thin track record.
Security and legal teams
The state of the published data-handling terms, discussed below, is a real issue for internal code-management policy — not one to wave away.
"On by default" plus
"terms not yet published"
This is the part that deserves the most caution. According to TheNextWeb, Origin is on by default for paid users — anyone who doesn't want it has to actively opt out. TechTimes further reports that Origin's data-handling terms were not yet published as of the beta launch, framing it as SpaceX effectively holding paid developers' code without those terms in place.
Handing over code hosting — a piece of core developer infrastructure — to a freshly-acquired corporate group, on by default, before the data terms are finalized, isn't something to wave off as pure upside. Teams using Cursor at a company should check whether Origin is enabled, and it's reasonable to hold off using it on new projects until the data-handling terms are formally published.