Cursor just announced Origin, a code storage and Git hosting platform. In one line: a direct competitor to GitHub. It ships this fall, and for now there's only a waitlist. So far, nothing wild in a market where everyone wants a piece. What makes it interesting isn't the what. It's the when.

From editor to platform

Some context first. Cursor, made by Anysphere, started as a fork of VS Code with AI built in. In a few years it went from a toy to the editor a lot of us open every morning.

In December 2025, Cursor bought Graphite, a startup focused on code review: stacked pull requests, merge queues, structured reviews. With Origin, the last piece falls into place, which is hosting. Cursor doesn't just want to be the place where you write code. It wants to be the place where it's stored, reviewed, and merged.

They're blunt about the pitch. GitHub was built for humans: one developer, a few commits a day, a pull request, a coworker who reviews it. Origin starts from a different assumption. Soon, Cursor says, it won't be one person pushing code. It'll be dozens of agents at once, cloning, branching, merging, and fixing their own mistakes in parallel. Origin is built to handle that load, and it throws in AI-powered automatic merge conflict resolution on top.

The numbers they showed on stage make the point: about 22 commits per second in a single repo, close to 300,000 clones and tens of thousands of pushes an hour. Numbers that make no sense at human scale, and all the sense in the world if you point an army of agents at the same repo.

You could call the bet early. Most of us don't have fifty agents running around the same project. But the idea isn't crazy, and it explains why Cursor dropped so much money on Graphite six months ago.

The detail that changes everything

Here's where it gets interesting. Just a few days before Origin, SpaceX signed a deal to buy Cursor for $60 billion, all in stock. Cursor becomes a wholly owned part of SpaceX once the deal closes, which is expected this fall. And it's worth remembering that SpaceX absorbed xAI, Musk's AI company, earlier this year.

So by the time Origin ships, it'll belong to the same group as xAI. A group that already trains its own models: Cursor and xAI have confirmed they're working together on one that's coming soon, described as trained from scratch on more than a hundred thousand GPUs.

The question all this raises

Line up the pieces. You write your code in Cursor. You host it on Origin. And the whole thing belongs to a company that trains top-tier AI models.

I'm not saying it's a trap, and I'm not assuming anyone has bad intentions. But the question is worth asking plainly: where does my code live, and who gets to use it? We already ask it about GitHub and Copilot, and the answers aren't always reassuring. The difference with Origin is that the whole chain ends up under one roof: the tool that writes, the place that stores, and the model that learns.

When one company controls all three links, the line between "hosting your code" and "learning from your code" comes down to the terms of service. And terms of service get rewritten.

What this means for a freelancer

On the practical side, I mostly work on client projects: Symfony, Laravel, PrestaShop, APIs. Not all the repos are mine, and several clients have strict rules about where the code can live. Switching platforms isn't a technical tweak you knock out on a Friday afternoon. It's a decision that touches confidentiality, compliance, and sometimes the contract itself.

For now I'm staying on GitHub. Not out of loyalty: GitHub has its own problems, and its recent outages made that clear. But trading a dependency on Microsoft for one on SpaceX isn't a win. It's just another giant, with its own priorities.

What I'd do in your shoes

Origin is worth a look, especially if you're starting to run agents in production and GitHub is choking at scale. I'll probably join the waitlist, if only to see how it actually works. There's still a lot we don't know: pricing, importing and exporting repos, how it plays with GitHub and GitLab, what it offers companies. What's up right now is a landing page, not documentation.

But before I move a single serious repo, I want to read those terms, know what happens to the data, and wait for the deal to actually close. You don't get control of your code back after the fact. You protect it before you click "migrate."

Originally published on my blog. Read more of my writing on PHP, freelancing, and dev tooling at jatniel.dev.