JetBrains Ends Support for Its Fleet IDE
JetBrains has announced it will be discontinuing its Fleet IDE, citing the challenge of maintaining two similar products. The company’s main focus remains on IntelliJ IDEA, its flagship IDE. Fleet, which was introduced as a lightweight, modern alternative, did not gain enough traction as a standalone product. Starting December 22, users will no longer be able to download Fleet, and the IDE will no longer receive updates. Existing users can continue to use Fleet, but some features depending on server-side services, such as the AI Assistant, may stop working over time.
Why JetBrains Decided to Discontinue Fleet
JetBrains explained that trying to rebuild the full capabilities of IntelliJ-based IDEs within Fleet did not create enough value. Maintaining two overlapping products caused confusion and distracted from their core focus. Fleet was designed to be a lighter, architecture-driven IDE with a modern user interface and more flexibility. While it was seen as a worthwhile experiment, it ultimately didn’t serve as a strong replacement for IntelliJ IDEA.
Many elements of Fleet contributed to other JetBrains products. Several components and user experience concepts developed for Fleet have been adopted across JetBrains’ suite of IDEs. However, the company found that Fleet could not replace IntelliJ or carve out a unique niche. The idea of Fleet as a second flagship was considered, but user feedback showed most developers preferred sticking with IntelliJ IDEA or other existing JetBrains tools like Rider, WebStorm, or PyCharm.
The Evolution and Market Challenges of Fleet
Fleet was first previewed in November 2021. Initially, it was positioned as a lightweight, multi-language IDE with smart coding assistance. Later, JetBrains envisioned it as an editor with advanced AI features. The company even explored whether Fleet could become a second flagship IDE, similar to IntelliJ IDEA. But as the product developed, it became clear that convincing users to switch was difficult, especially since many developers already relied on established JetBrains tools.
JetBrains also considered making Fleet an AI-first editor. However, after conducting extensive user research and developing new workflows, they concluded that another AI-based editor would not stand out enough. The market was already crowded with AI-enhanced editors, especially those based on Visual Studio Code. As a result, JetBrains decided to focus on integrating its AI workflows into existing IDEs rather than pushing Fleet as a standalone product.
Moving forward, JetBrains plans to develop these AI features as part of a new product, which will have a different name and identity. This approach allows the company to refine its AI offerings without the constraints of Fleet’s original form. The new environment aims to better serve user needs and adapt to evolving market demands.















What do you think?
It is nice to know your opinion. Leave a comment.