From Saint Petersburg to Prague — and Back
Sergey Dmitriev co-founded JetBrains in 2000 with Valentin Kipyatkov and Eugene Belyaev, all three veterans of the Saint Petersburg software scene. The company incorporated in Prague — a practical choice for a European legal base — while its engineering centre remained in Saint Petersburg, Russia. That split geography became a structural feature of the company rather than a transitional arrangement: JetBrains still maintains a distributed development model across European offices decades later, with the original Russian engineering culture visibly embedded in the product line's rigour.
The timing was aggressive. IBM was preparing to open-source Eclipse, which it released in November 2001 under the Common Public Licence, with stewardship later passing to the Eclipse Foundation. Free tools were the trend; charging for a Java IDE required a pointed argument. JetBrains made one.
The Refactoring Menu as Commercial Proposition
IntelliJ IDEA 1.0 shipped in January 2001 with automated refactoring — rename, extract method, inline variable, introduce parameter — baked into the editor rather than bolted on. At the time, most Java developers performed these transformations by hand, cross-referencing usages across files and hoping the search-and-replace held. IDEA's refactoring engine understood the type system; it traced every reference, updated every call site, and previewed the changes before applying them. The argument was not that refactoring was a new idea — Martin Fowler's 1999 book had already catalogued it as a discipline — but that automating it correctly was genuinely hard, and that developers who cared about code structure would pay for the tool that did it right.
The initial list price was several hundred dollars per seat, which positioned IDEA firmly in the professional market. The bet was that Java shops with large codebases and real maintenance costs would see the licence fee as smaller than the engineering time saved. That bet proved correct. IDEA built a devoted user base among Java professionals throughout the early 2000s, even as Eclipse accumulated plugins and market share. The two products competed on different grounds: Eclipse offered a platform you could extend into almost anything; IDEA offered a coherent, opinionated experience that required less configuration to be useful.
The technical foundation of IDEA's refactoring was a persistent, incrementally updated model of the codebase — closer to a compiler's internal representation than to a text index. Incremental compilation and live error detection were consequences of the same architecture, giving IDEA its characteristic sense of knowing the code rather than merely displaying it. Autocompletion drew on the same type-aware model, offering context-sensitive completions that outpaced the simpler token-matching approaches in rival editors.
One Codebase, Twelve IDEs
The lasting strategic decision was treating IntelliJ IDEA not as a finished product but as a platform. JetBrains extracted the core — the editor, the project model, the refactoring infrastructure, the debugger framework — into what the company calls the IntelliJ Platform, then built language-specific IDEs on top of it. PyCharm for Python arrived in 2010, WebStorm for JavaScript the same year, RubyMine, CLion for C and C++, GoLand, and others followed. Each product carries the same keyboard model, the same settings structure, the same plugin system, and the same refactoring philosophy applied to a new language.
The strategy answered the pricing question a second time: instead of selling one IDE to Java developers, JetBrains sold twelve IDEs to twelve developer communities, each at a professional price point, each sharing the same engineering investment. By the mid-2010s the company had extended that logic further still, publishing MPS, a tool for language engineering and eventually acquiring or building tools across the development lifecycle. The refactoring argument had become a company.