What you need to know
- It is an acquisition, not a raise. SpaceX has entered a definitive agreement to buy Anysphere Inc. — the parent of Cursor — in an all-stock deal valued at $60 billion, announced on 16 June 2026.
- Cursor folds into xAI. On close, Cursor becomes a wholly owned subsidiary and joins the SpaceX/xAI AI division. SpaceX merged with Elon Musk's xAI in February 2026.
- Close is expected in Q3 2026, pending regulatory approvals. Until then, nothing changes for paying users day to day.
- The builder question is lock-in. If you standardised your team on Cursor, the things to watch are model choice, pricing, roadmap, and data governance under new ownership.
You do not need to rip Cursor out today. The single most useful thing you can do this week is make your setup portable: keep your rules, prompts and tool configuration in editor-agnostic files, and standardise on the Model Context Protocol (MCP) for tool access so the same context works in any client.
What actually happened
On 16 June 2026, SpaceX announced a definitive agreement to acquire Anysphere Inc., the company that makes Cursor, in an all-stock transaction valued at $60 billion. Per reporting from TechCrunch, CBS News and Yahoo Finance, the deal is expected to close in Q3 2026 subject to regulatory clearance, after which Cursor becomes a wholly owned subsidiary and is absorbed into the combined SpaceX/xAI artificial-intelligence division.
The timing is striking. The announcement landed just days after SpaceX's own initial public offering — reported by CBS News and Yahoo Finance as the largest IPO in history, raising roughly $75 billion. Per the same reporting, SpaceX had already merged with Elon Musk's xAI in February 2026, so the acquisition is best read as xAI buying its way to the front of the AI-coding market with freshly minted public-company stock.
This was not entirely out of the blue. As TechRepublic and Quartz reported, back in April 2026 SpaceX posted on X that it was working with Cursor to build the "world's best coding and knowledge work AI". The same reporting noted that Cursor had granted SpaceX an option either to buy the company for $60 billion or to pay $10 billion simply to "work together". SpaceX took the larger door.
This is a different story from the one many builders remember. Earlier in 2026 we covered Cursor's roughly $2B raise at a $50B valuation — that was a funding round that kept Anysphere independent. The $60B figure here is an outright acquisition. Do not conflate the two.
How big is Cursor, really?
Cursor (built by Anysphere) was founded in 2022 and became one of the fastest-revenue-growth stories in software. The annual recurring revenue figures quoted in the press climb steeply: around $100 million in annualised revenue in early 2025, rising past $2 billion by early 2026. By June 2026, reported figures sit in a range — roughly $2.6 billion on a business-to-business basis up to about $4 billion annualised, depending on which DevOps.com and Quartz numbers you read and how each is defined.
We deliberately quote that as a range rather than a single number, because the sources do not agree and the definitions differ. What is not in dispute is the trajectory: a four-year-old company commanding a $60 billion acquisition price tells you how central AI-assisted coding has become to how software gets built.
The numbers at a glance
| Item | Figure (as reported) | Status |
|---|---|---|
| Acquisition value | $60 billion, all-stock | Definitive agreement, 16 Jun 2026 |
| Expected close | Q3 2026 | Pending regulatory approval |
| SpaceX IPO raise | ~$75 billion | Reported as largest in history |
| Cursor ARR, early 2025 | ~$100 million | Reported |
| Cursor ARR, June 2026 | ~$2.6B (B2B) to ~$4B (annualised) | Reported range, sources differ |
Why this matters for India and UK builders
For a great many engineering teams in Bengaluru, Hyderabad, London and Manchester, Cursor is not just one tool among many — it is the default integrated development environment that the whole squad standardised on. That is exactly what makes a change of ownership worth taking seriously, even before anything visibly changes in the product.
Three concrete concerns are worth naming plainly.
Model lock-in. Cursor today lets you pick from several model providers. Once it sits inside xAI, there is an obvious commercial incentive to favour in-house Grok and xAI models — through defaults, pricing, or feature gating — over rivals such as Claude, Gemini and the open-weight options. None of that has been announced. But the incentive is structural, and structural incentives tend to win over time. If your output quality depends on a specific model behind Cursor, that dependency is now downstream of a competitor's roadmap.
Pricing and roadmap uncertainty. Acquisitions reset priorities. A team that built its unit economics around Cursor's current per-seat or usage pricing should assume the pricing surface can move after close, and budget with a margin of safety. The roadmap may also tilt toward whatever serves the parent company's strategy rather than the standalone product's previous direction.
Data governance. If your organisation cleared Cursor through procurement, security and DPDP or UK GDPR review on the basis of how Anysphere handled code and telemetry, that approval was for the old entity. New ownership can mean new sub-processors, new data flows, and new places your code context travels. UK and India teams in regulated sectors — fintech, health, public sector — should plan to re-run that review when the deal closes.
"We love Cursor and it is not going anywhere this quarter. But the day a competitor owns your default editor is the day you write down an exit plan — not because you intend to use it, but because having one is what keeps your negotiating position honest."
— A Verified Builder · Bengaluru, INWhat to actually do about it
The right posture here is calm, not reactive. Cursor remains an excellent product and the deal has not closed. The goal is simply to make sure that whatever xAI decides next, your team is never trapped. A few practical moves:
Keep your AI-coding workflow editor-agnostic. Store rules, prompts and project conventions in plain files in the repo. Use MCP for tool and context access so the same servers work whether you are in Cursor, Claude Code or another client. Portability is cheap to maintain now and expensive to retrofit later.
- Audit your dependency. Write down exactly what your team relies on Cursor for — autocomplete, agent edits, codebase chat, PR review — and which underlying model each step assumes. That document is your migration map if you ever need it.
- Evaluate at least one alternative in anger. Spend a sprint with Claude Code alongside Cursor on real tickets, not toy tasks. Knowing how a second tool performs on your codebase is the difference between a real option and a theoretical one.
- Keep a self-hostable path open. If model choice is your biggest worry, the open-weight coding models from Kimi, GLM and MiniMax are now strong enough to back a serious workflow you control end to end. Even if you never deploy them, validating that they work on your stack is leverage.
- Confirm your contract and data terms. Check renewal dates, price-lock clauses and data-processing terms now, while you still have a clean independent counterparty.
- Watch the close. Treat Q3 2026 as the trigger date. Set a calendar reminder to re-assess model defaults, pricing and data terms the week the acquisition completes.
Do not panic-migrate your whole team this week on the strength of a headline. A rushed switch costs you velocity for a change that has not happened yet. The deal still needs regulatory approval, and a forced move now is its own form of lock-in — to whatever you scramble onto.
Every article here is written by a Verified Builder. Want your name on the next one?
AI Tech Connect lists AI engineers, founders and researchers across India and the UK — and the people hiring browse it to find them. Adding your profile is free.
Become a Verified Builder →The bigger picture
Step back and the acquisition is a marker of where the AI-coding market is heading: consolidation under the largest, best-capitalised players. SpaceX used the proceeds of the biggest IPO on record to fold the leading AI editor into a company that also builds frontier models. That vertical integration — models, editor, and distribution under one roof — is powerful, and it is exactly why builders should keep an independent line of sight on their own tooling.
For the wider stack, the strategic read matters more than the dollar figure. If owning the editor becomes a way to steer developers toward a particular model family, then the choice of coding tool stops being a neutral productivity decision and becomes a bet on a vendor's whole AI strategy. Builders who keep their workflow portable get to make that bet deliberately, on their own timeline, rather than having it made for them by an acquisition they did not vote on.
None of this is a reason to abandon a tool that works. It is a reason to know your alternatives, keep your context portable, and watch the Q3 2026 close. For most India and UK teams, that is the whole to-do list. The companies that come out of this comfortably will be the ones who treated their editor as a choice they can revisit — not a destination they are stuck with.
Reporting referenced in this piece: TechCrunch, CBS News, Yahoo Finance, TechRepublic, Quartz and DevOps.com. Figures attributed as "reported" reflect ranges across those sources and should be read as such.