The IDE Wars Have a New Front Line
Cursor, the AI-native code editor built by Anysphere, started as a tool for indie developers and solo engineers who wanted something faster and smarter than their current setup. It has since moved well past that demographic. Enterprise software teams – the kind that run on JetBrains IDEs like IntelliJ IDEA, WebStorm, and PyCharm – are increasingly running Cursor evaluations, and in some cases, full migrations. The shift is quiet but accelerating, driven not by marketing but by word-of-mouth inside engineering orgs.
JetBrains has spent two decades building the professional developer market. Its tools are embedded in the workflows of large financial institutions, healthcare tech companies, and Fortune 500 engineering departments. The loyalty to JetBrains has always been earned – deep language support, reliable refactoring, mature plugin ecosystems. Cursor is not trying to beat JetBrains on any of those traditional dimensions. It is winning on a different axis entirely: the quality and speed of AI-assisted development at the level of individual productivity.
What Cursor Is Actually Selling
Cursor is built on a fork of VS Code, which means it inherits a familiar interface and a massive extension library. But the product differentiation is almost entirely in how its AI layer behaves. The tab-complete is context-aware across files. The chat interface can read the full codebase, not just an open file. And the agent mode can autonomously execute multi-step coding tasks – editing across files, running terminal commands, and iterating on errors – without the developer manually directing every step. For engineers accustomed to JetBrains AI Assistant, which feels like a polished add-on rather than a native capability, the contrast is stark.
The pricing model also plays a role. Cursor’s Pro tier runs at $20 per month, which is competitive with what many teams pay per seat for JetBrains subscriptions alone – before any AI tooling is added. Enterprise teams stacking JetBrains licenses on top of GitHub Copilot or a separate AI coding assistant are paying considerably more per developer. Cursor collapses that into a single tool at a lower combined cost. For budget-conscious engineering leaders managing headcount pressure, that math is attractive even before the productivity argument is made.
Why Enterprise Is the Real Prize
The enterprise developer market is where the real revenue concentration sits in the IDE space. Individual developers make tool decisions impulsively, based on hype or habit. Enterprise engineering leads move slower, but when they move, they move entire teams. A single procurement decision at a mid-size fintech or a software consultancy can mean hundreds of seats shifting at once. Anysphere understands this, which is why Cursor’s recent product updates have been oriented heavily toward team features – shared context, admin controls, audit logging, and SSO support. These are not features that solo developers ask for.
JetBrains is not standing still. The company has been expanding its AI Assistant across its IDE lineup and has deepened integrations with major language models. But there is a structural problem: JetBrains’ AI features are built on top of an existing product architecture that was not designed around AI-first workflows. Cursor, built from the ground up to treat AI as the primary interaction layer rather than a helpful add-on, does not carry that same architectural debt. That gap is difficult to close quickly, and engineering teams are starting to notice it during evaluations.
There is also a cultural dimension to what is happening. Younger engineers entering the workforce now have often learned to code with AI assistance built in from the start. Their mental model of what an IDE should do is different from a senior engineer who learned on IntelliJ in 2012. When these developers join enterprise teams and advocate for their preferred tools, they advocate for Cursor. Engineering managers who dismiss that pressure risk losing hiring leverage with a demographic that treats tooling quality as a proxy for whether a company takes engineering seriously.
The competitive pressure Cursor is exerting mirrors what has happened in other corners of the developer tools market. Supabase’s backend platform followed a similar trajectory – starting with indie developers before pushing into teams that had previously committed to established infrastructure providers. The pattern is consistent: an AI-native or developer-experience-native tool earns grassroots credibility first, then converts that into enterprise pipeline. Cursor is at the inflection point where grassroots credibility is converting into procurement conversations.
JetBrains’ deepest moat has always been language-specific depth – the kind of refactoring intelligence and static analysis that takes years to build for a single language, let alone a dozen. Cursor has not matched that depth, and for teams writing highly complex Java or Kotlin at scale, the gap still matters. But for a growing number of enterprise teams working in Python, TypeScript, and Go – where JetBrains’ advantage is narrower – the calculus is shifting. The question for JetBrains is whether its AI roadmap can accelerate fast enough to close the experience gap before more enterprise accounts start treating Cursor not as an experiment, but as the default.
