Tabnine now under Tricentis

On July 30, 2026, Tricentis officially announced its acquisition of Tabnine. Tabnine started life as Codota in 2013 — years before GitHub Copilot existed — and took its current name after acquiring the Canadian startup Tabnine in 2019, making it one of the oldest AI coding-assistant brands still standing. Terms were not disclosed, but Israeli tech outlet CTech reports the deal was valued in the tens of millions of dollars. On paper, the world's largest test-automation vendor buying a code-completion company looks like an odd pairing.

The point of the deal isn't code completion. Tricentis wanted Tabnine's Enterprise Context Engine — technology that models enterprise systems as a combined graph-and-vector representation, so AI agents can reason about architecture instead of just searching documents. On its own blog, Tabnine says this engine will now be folded into the Tricentis Agentic Quality Engineering Platform. In test automation, deciding what an AI agent should even test requires understanding the target system's structure first — and Tricentis is repurposing technology Tabnine spent years refining for code generation to solve exactly that problem.

For anyone managing a Tabnine contract, the renewal window is now the moment to ask hard questions about its future as a standalone product. Tricentis's core business is test automation, so it's plausible that investment in Tabnine-as-a-coding-tool gets deprioritized over time. It's also worth noting Tabnine cut 18% of its staff in a February 2025 restructuring — its independent footing wasn't rock-solid even before the deal, and this acquisition may partly reflect how hard it had become to keep competing alone.

For product managers, at least part of Tabnine's existing roadmap is likely to get absorbed into Tricentis's QA-agent priorities. New coding-assistant features may slow down, while testing/QA integration features could actually accelerate — how you read this deal depends on which side of that line your workflow sits on. Teams that already wire Tabnine into their CI/CD pipeline are arguably well positioned to benefit if testing integration deepens.

It's not all upside, either. The acquisition announcement is written from Tricentis's vantage point, with thin detail on what standalone Tabnine users can expect going forward. Tabnine's own "new chapter" post doesn't commit to specifics on continued feature support, either. Given the February 2025 layoffs, how the pace of Tabnine-as-a-standalone-product development holds up simply isn't answered by what's been published so far.