Skip to main content

Research

Tabnine in Practice: What 2025 and 2026 Public Evidence Shows

Who wrote publicly about Tabnine in 2025 and 2026, what their 47 accounts praise and fault, and what an enterprise pilot should measure before you sign.

Reading time
4 min read
Sources
14 cited

Key findings

  1. Stability draws the most complaints. All 15 sources that discuss it report sign-in failures, crashes, or plugins that stop working.
  2. Price and plan changes come up in 14 sources, and 10 raise them as a complaint, mostly about Dev and Pro subscriptions that ended or did not deliver what was paid for.
  3. Chat and agents draw praise in 6 of the 15 sources that discuss them, mostly for the choice between Claude, GPT, and other models.
  4. Only 3 of 47 accounts speak for a team, and no company has published a named account of a Tabnine rollout from 2025 or 2026. The newest named account is CI&T's 2023 case study, which describes autocomplete Tabnine no longer sells. Ask Tricentis for two reference customers on your deployment model and call them before you sign.

An enterprise Tabnine pilot has to produce its own evidence. GILD read public developer accounts from January 2025 to August 2026, and they mostly report plugin failures and the end of the self-serve plans. Almost none describe the private, governed platform Tabnine sells today.

What the record contains

The record holds 25 JetBrains plugin reviews, 16 GitHub issues on Tabnine plugin repositories, 4 Hacker News comments, a Reddit post, and a personal blog post. Forty-four describe individual use and 3 describe small teams. GILD left out posts by Tabnine and Codota staff, and accounts from before 2025, which describe the discontinued local autocomplete product.

GitHub issues lean toward failures, so GILD capped them near a third of the record and dropped bare crash reports first. A bug report counts as mixed unless its author canceled, so the GitHub issues run 2 negative and 14 mixed, with none positive. JetBrains reviews include 15 negative verdicts, 5 mixed, and 5 positive. Hacker News has 2 negative, 1 mixed, and 1 positive. The Reddit post reports charges on a free plan. The blog post is mixed: its author worked around the end of Sublime Text support to keep Tabnine running.

Figure 1Developer accounts by source
Source
JetBrains Marketplace reviews
GitHub issues
Hacker News comments
Reddit posts
Personal blog posts

GILD's Tabnine records, 47 public developer accounts, Jan 3, 2025 to Aug 13, 2026

What 2025 and 2026 accounts describe

Thirty-seven accounts date from 2025, when Tabnine sold Dev and Pro plans with chat, model choice, and agents. They praise model choice and documentation generation. The failures they report include sign-in problems, edits that did not apply, rate limits on paid plans, undocumented usage limits, charges on a free plan, and the end of Sublime Text support.

The 10 accounts from 2026 mostly describe the end of the self-serve plans. They report a Dev cancellation without a refund, a charge days before a plan was removed, and the end of new sign-ups through the legacy plugin. Enterprise users report a Neovim Agent window that never loaded, broken shared commands, and crashes in a current IntelliJ build.

Where developers see value

Praise is rare and names specific features. Six accounts praise chat and agents for comparing Claude with GPT, for answers more informative than Copilot's, or for hours saved on documentation. Two developers regret losing Tabnine, including one who ranked it best in PhpStorm.

Six accounts discuss completion quality, once Tabnine's main function, and four are critical. They describe references to code that does not exist, code that does not compile, and poor results on a large Java codebase.

Where developers hit problems

Fifteen accounts report stability failures, including sign-in loops, disconnects, edits that did not apply, and crashes in current IDE builds. Five raise resource use, including 40 GB of RAM and a 30-minute IDE freeze on a large project. Five report output that needed cleanup, such as unrelated edits, ignored indentation, and a change written to the wrong directory.

Main assistant or moved away

Eight accounts use Tabnine as their main assistant, and eight removed it, canceled, or moved to another tool. On net time, 2 report savings and 3 say that checking intrusive or wrong suggestions took longer than the tool saved.

What this means for an enterprise pilot

None of the accounts test what Tabnine sells in 2026, an enterprise platform with private deployment, administered models, provenance checks, a Context Engine, and cost caps. Run the pilot on the deployment model you would buy, in the IDE versions your engineers use, with the models your security team would approve. Measure plugin stability, accepted completions, agent changes merged, reviewer time, and token spend by team.

Methodology

GILD collected public sources on October 12, 2026 through the Hacker News Algolia API and the Arctic Shift Reddit archive. It also used the GitHub issue trackers of Tabnine's public repositories and the JetBrains Marketplace reviews API. It kept sources dated 2025 or later, capped GitHub issues near a third of the total, and recorded each account's author type, sentiment, and the themes it supports. Arctic Shift rate limits ended the Reddit search early. G2 and TrustRadius block automated reading, so their reviews are not in the record. On October 25, 2026, GILD searched blogs, newsletters, talks, research papers, and X again and added the one first-hand, dated blog post it found. The other results were affiliate or generated review pages, Tabnine's own posts, or partner case studies, so GILD left them out. The same day, GILD searched Tabnine's customer-stories blog, the Tricentis acquisition release, conference talks, and company engineering blogs for a named 2025 or 2026 customer account. The newest result was the 2023 CI&T case study. Every count on this page comes from the records on the Tabnine Signals page.

Products in this piece

Sources

Official documentation
5
Public source
9
  1. Tabnine docs: Supported IDEsOfficial documentationdocs.tabnine.com
  2. Tabnine docs: PrivacyOfficial documentationdocs.tabnine.com
  3. Tabnine docs: ArchitectureOfficial documentationdocs.tabnine.com
  4. Tabnine docs: Release NotesOfficial documentationdocs.tabnine.com
  5. VS Code Marketplace: (Legacy) TabnineOfficial documentationmarketplace.visualstudio.com
  6. Ruslan Sukhikh, JetBrains Marketplace review: a team purchase on a large Java project (Jul 25, 2025)Public sourceplugins.jetbrains.com
  7. Ollymid on GitHub: shared team commands on Tabnine Enterprise (Jun 11, 2026)Public sourcegithub.com
  8. the-isz on GitHub: Tabnine Agent stuck loading on Tabnine Enterprise (Apr 22, 2026)Public sourcegithub.com
  9. Vitasfor4af on GitHub: an undocumented usage limit on the Tabnine Dev plan (Sep 8, 2025)Public sourcegithub.com
  10. voilentKiller0 on GitHub: RAM use climbs to 40 of 42 GB when Tabnine starts (Jul 10, 2025)Public sourcegithub.com
  11. Mind Print, JetBrains Marketplace review: the legacy plan gone days after a charge (Jan 9, 2026)Public sourceplugins.jetbrains.com
  12. Derak Kilgo, JetBrains Marketplace review: Pro and Dev subscriptions closing (May 26, 2026)Public sourceplugins.jetbrains.com
  13. lordrebel on GitHub: Tabnine Dev subscription stopped (Jan 26, 2026)Public sourcegithub.com
  14. Google Cloud blog: How CI&T accelerated development by 11% with AI from Tabnine and Google Cloud (May 11, 2023)Public sourcecloud.google.com