Anaconda Acquires Kilo Code to Govern 10 Trillion Tokens a Month

Anaconda has acquired Kilo Code, the open-source, model-agnostic AI coding agent used by more than 3 million developers. The deal is a direct bet that the next big enterprise AI problem is not capability, but governance: who controls the models, the spend, and the data flowing through them.

Zero to 3 million in 16 months

Anaconda, a company that provides governed, open-source packages and environments for enterprises, has acquired popular open-source coding agent Kilo. Kilo grew its agentic engineering platform from zero to a thriving open-source community of 3 million developers in only 16 months. That kind of organic growth, driven entirely by developer word-of-mouth, is what made Kilo an attractive target.

Kilo itself is a fork of Roo Code, an open source AI coding agent for VS Code. When Roo Code sunset its IDE extension in favor of a cloud-only agent, it sent a wave of its user base looking for alternatives, with Kilo positioning itself as a landing spot. The project now has more than 26,000 GitHub stars and 3,000 forks, and Kilo alone orchestrates almost 10 trillion tokens per month across more than 3 million developers.

The people behind the deal

The key executives are:

• David DeSanto, CEO of Anaconda, who joined in October 2025 after six years as GitLab's chief product officer
• Scott Breitenother, CEO and co-founder of Kilo Code, who will continue leading the Kilo team post-acquisition
• Sid Sijbrandij, Kilo co-founder and GitLab co-founder and executive chair, who championed the deal

Kilo's numbers go some way toward explaining why Anaconda wanted it: more than 3 million developers routing close to 10 trillion tokens a month through the platform, across 500-plus models from over 60 providers. That scale, combined with Anaconda's existing enterprise reach, is the core logic of the acquisition.

The enterprise AI governance crisis

The strategic rationale is rooted in a problem that is getting worse fast. Enterprise AI spend is growing faster than anyone's ability to account for the spend. AI builders are being told to move fast, and the token consumption accumulates invisibly, spread across dozens of tools, work accounts, and personal accounts. It leaves no single view of where it all goes.