JetBrains Fleet

Overview

JetBrains Fleet was a next-generation polyglot code editor and IDE from JetBrains (makers of IntelliJ IDEA, PyCharm, WebStorm, and Rider). Product home: jetbrains.com/fleet. Announced in November 2021 and opened to a public preview in October 2022, Fleet was built from scratch—not on the classic IntelliJ Platform UI stack—with a distributed architecture: a lightweight client, optional smart backend, and support for local, remote, collaborative, and containerized workspaces.

Status (mid-2026): Fleet is discontinued. On December 8, 2025 JetBrains published The Future of Fleet: starting December 22, 2025, Fleet is no longer available for download from the Toolbox App or other official channels, and further updates stopped. Existing installs may keep running offline-capable features, but server-backed pieces (including AI Assistant) can degrade over time. A May 2026 update on that same post states that Fleet’s platform direction evolved into JetBrains Air—an agentic development environment for multi-agent task loops—while JetBrains reaffirmed IntelliJ-based IDEs as the primary general-purpose coding products.

While it lived, Fleet’s pitch was simple: start as a fast, clean multi-language editor; turn on Smart Mode when you need IntelliJ-class completion, navigation, inspections, and refactorings; collaborate and develop remotely without a separate product family. It never left multi-year public preview as a fully commercial GA product, and JetBrains later wrote that rebuilding full IntelliJ capability inside Fleet did not create enough standalone value to justify two overlapping IDE families.

Key features

The following describes Fleet as shipped during public preview (roughly 2022–early 2025 releases such as 1.19–1.47). These capabilities matter for historical comparison and for understanding what Air and modern JetBrains IDEs inherited conceptually—not as a shopping list for a current download.

• Editor-first, Smart Mode on demand — Default mode focused on fast open, syntax highlighting, and essential editing. Smart Mode started a separate code-processing backend (IntelliJ engine lineage) for project-aware completion, go-to-definition/usages, on-the-fly inspections, quick-fixes, and refactorings. Later builds added Smart Mode for single files and automatic language detection on scratch/untitled buffers.
• Polyglot workspace — One tool marketed for Java, Kotlin, Python, JavaScript/TypeScript, Go, PHP, C#/.NET, Rust (via rust-analyzer style tooling), Zig (from ~1.44), and other languages without switching product brand names. Depth varied by language and never fully matched specialized IntelliJ-family IDEs for every stack.
• Distributed architecture — Client/UI separated from language intelligence and workspace backends. Supported local folders plus remote targets such as SSH hosts, Docker, WSL, and (at launch era) JetBrains Space-style remote environments. Aimed at “edit here, compute there” workflows similar in spirit to VS Code Remote, with JetBrains’ own packaging.
• Collaboration — Built-in multi-user editing sessions for pair programming and mentoring, positioned as a first-class feature rather than only a plugin bolt-on. Community reports mixed: useful for mentoring, less ubiquitous than screenshare for many teams.
• AI Assistant integration — From mid-2023 releases onward Fleet gained JetBrains AI features: chat, context retrieval, slash commands, and AI-oriented completion (including Java-focused completion work in 1.37-era notes). These depended on JetBrains cloud services and accounts—the same class of features JetBrains warned may stop working after sunset.
• Modern UI experiments — Minimal chrome, later the “Islands” UI refresh (late 2024), VS Code-compatible keymap options, structure tool window, file compare, Markdown/AsciiDoc soft wraps and previews, color previews in completion, improved Git branches menu, run-single-file without full project scaffolding, Vitest/run-config macros, Anaconda virtualenv support, and other editor ergonomics shipped across 1.3x–1.4x blogs.
• Plugins (late, limited ecosystem) — Early preview lacked third-party plugins; support arrived later via in-product plugin UI and a Fleet plugin SDK (Gradle plugin on GitHub). The marketplace never approached VS Code’s breadth—one of the structural reasons community comparison favored VS Code for extensibility.
• Run/debug and project tooling — Run configurations, debuggers, terminals, Git, Gradle auto-import improvements, and language-specific interpreters (Python, npm, rust-analyzer config) aimed to reduce “toy editor” stigma while staying lighter than a full IntelliJ window by default.

Pricing

Fleet never became a long-running paid SKU with stable public list prices comparable to IntelliJ IDEA Ultimate. Through public preview it was effectively free to download and use for evaluation (Toolbox distribution). JetBrains staff and community threads indicated a future model with a free/hobby tier for non-commercial or limited criteria and a commercial subscription similar to other JetBrains products—but that commercial GA packaging was not the durable story: the product was withdrawn from distribution instead.

Period / option	Cost	Notes
Public preview (2022–Dec 2025)	Free	Download via Toolbox while distributed; no general paid Fleet-only storefront that defined the product’s life
Hobby / free tier (planned messaging)	Intended free subset	Community/HN discussion of non-commercial criteria (local/public GitHub/small private teams); never the lasting commercial center of gravity
Commercial subscription (planned)	Never mature GA list price	JetBrains said Fleet would be commercial/subscription-like; sunset happened before a stable standalone price table defined the brand
Post-Dec 22, 2025	N/A (no downloads)	No new installs; existing binaries unsupported; server features may die
Successor: JetBrains Air	Preview packaging	Air marketed free to try via air.dev; agent usage tied to JetBrains AI subscriptions and/or third-party agent providers/API keys—check Air’s current docs for seat and credit rules
Practical JetBrains alternatives	IDE list prices	Individual All Products Pack and single-IDE yearly plans on jetbrains.com/store; AI Pro credit packs on JetBrains AI buy pages; non-commercial free options for several IDEs

Starting price for this profile: $0 while Fleet was obtainable (preview freemium positioning). There is no current paid Fleet seat to buy in 2026. Budget for replacements: free VS Code/Cursor Hobby for editors; JetBrains individual IDE or All Products Pack if you need classic JetBrains depth; separate AI subscription if you use JetBrains AI / Air agents heavily.

Limits & gotchas

• Product is sunset — No official downloads after December 22, 2025; no security/feature updates; AI and other server features may fail silently over time.
• Never left perpetual preview branding — Multi-year “public preview” eroded trust. Teams that need multi-year vendor commitment correctly stayed on IntelliJ IDEA or VS Code.
• Identity crisis vs IntelliJ — Official post-mortem: two general-purpose IDE families confused buyers. If you already paid for IntelliJ/WebStorm/PyCharm, Fleet rarely justified switching.
• Incomplete VS Code replacement — Extension ecosystem, remote container maturity, and community snippets lagged VS Code. “VS Code killer” headlines from 2021–2022 did not hold up.
• Smart Mode resource cost — Turning on full intelligence reintroduced heavy indexing and RAM characteristics closer to JetBrains IDEs; lightweight claims applied mainly with Smart Mode off.
• Language depth uneven — Polyglot surface area was real, but specialists often preferred dedicated JetBrains IDEs (e.g. Rider for.NET, GoLand for Go) or VS Code + best-in-class language extensions.
• Feature cuts eroded confidence — Community reaction to moves such as reduced Kotlin Multiplatform focus in Fleet reinforced the sense that IntelliJ remained the investment priority.
• Plugin story late and thin — Early inability to install third-party plugins (Stack Overflow era) and a small marketplace thereafter limited sticky customization.
• Collaboration underused — Real-time multi-caret editing existed; many teams still used video + screen share or Code With Me inside classic IDEs.
• Migration tax now — Anyone still on a leftover Fleet install should export settings/keymaps mentally to IntelliJ, VS Code, or Air; do not depend on Fleet-specific plugin state.

Community sentiment

Launch era (2021–2022): Hacker News and Reddit treated Fleet as JetBrains’ answer to VS Code—distributed architecture, collab, and “editor that becomes an IDE.” Excitement mixed with skepticism: architecture diagrams looked familiar to VS Code remote users, and “why not improve IntelliJ?” was an immediate refrain.

Middle years (2023–mid-2025): r/Jetbrains threads asked “what is Fleet for?” and “is anyone using it daily?” Common answers: interesting tech demo; fine for light multi-language browsing; not enough reason to leave a tuned IntelliJ or VS Code setup. Complaints included bugs after long preview, incomplete plugins, and unclear licensing. Positive notes praised clean UI, Smart Mode quality when it worked, and keymap familiarity for VS Code migrants.

Sunset (Dec 2025): r/programming and HN cancellation threads largely reacted with “not surprised.” Narratives: lack of focus, preview purgatory, and dual-IDE maintenance cost. Some praised JetBrains for an honest post-mortem and for reusing Fleet technology toward Air rather than quiet abandonment with zero explanation. Others read the Air pivot as chasing Cursor-class agent workflows after the editor war was already lost.

What people liked when it worked: fast cold start in editor mode; JetBrains-smart assistance without opening a heavyweight project window first; multi-language folders; collab demos; progressive AI chat/slash-command work in later builds.

What people disliked: endless preview; weaker extensions; Smart Mode heaviness; “use IntelliJ instead” as the real advice from JetBrains veterans; then the hard stop on downloads.

Who should use it

• Nobody for new production work in 2026 — Fleet is not available for new installs and is unsupported.
• Historians / tool researchers — Useful case study in distributed IDE architecture, dual-product cannibalization, and how AI shifted JetBrains’ roadmap from “lightweight IDE” to “agentic ADE.”
• Users with an old local install — May open offline files temporarily, accepting broken cloud AI and zero patches; plan a migration.
• Teams that wanted Fleet’s pitch should evaluate instead:
  • Deep JetBrains language intelligence → IntelliJ IDEA or the language-specific IDE
  • Lightweight + extensions → VS Code
  • AI-native IDE → Cursor, Windsurf, or JetBrains AI inside classic IDEs
  • Multi-agent task loops under JetBrains branding → Air
• Less ideal even when it existed: regulated enterprises needing long support horizons; plugin-heavy VS Code shops; pure IntelliJ power users with mature workflows.

Alternatives

• JetBrains IDEs (IntelliJ family) — Default migration path for Fleet users who wanted Smart Mode depth; mature plugins, debuggers, and commercial support.
• Visual Studio Code — Free, dominant editor; extensions, remote SSH/containers, and huge community; the product Fleet was most often compared against.
• Cursor — AI-first IDE on a VS Code foundation; common 2025–2026 choice when the goal is agentic editing rather than classic JetBrains inspections alone.
• Windsurf — Competing AI IDE; alternative when evaluating paid AI editors.
• Zed — Fast native collaborative editor for teams prioritizing performance and multiplayer over JetBrains inspections.
• GitHub Copilot — Assistant inside VS Code/JetBrains without switching entire IDE platforms.
• JetBrains Air (air.dev) — Official successor direction: agentic development environment on Fleet-platform learnings; multi-agent runs (e.g. Codex, Claude Agent, Gemini CLI, Junie) with review-first workflows—not a drop-in Fleet editor clone.
• Sublime Text / Vim-class editors — When you only needed Fleet’s lightweight mode, not Smart Mode.

Verdict

JetBrains Fleet is a closed chapter: a free public-preview polyglot editor/IDE (2021 announce, 2022 preview, discontinued December 22, 2025) that did not win a lasting niche against IntelliJ IDEA or VS Code. Its real legacy is technical and strategic—distributed client/backend design, UI experiments, and a pivot of the team/platform into JetBrains Air for agentic development—rather than a tool you should adopt in 2026.

Bottom line: treat Fleet as historical context on VersusTools, not as a purchase decision. If you need JetBrains code intelligence, buy or renew the appropriate IntelliJ-family IDE (and JetBrains AI if you want assistant/agent features there). If you need a free extensible editor, use VS Code. If you need multi-agent workflows under JetBrains’ new ADE branding, evaluate Air on air.dev with eyes open about preview maturity and AI credit costs. Fleet itself: starting price was $0 in preview; current availability is none.