AI on Your Own Terms: Anaconda Acquires Kilo Code

This was originally published on Anaconda’s blog.
There’s an old public service announcement from a generation ago: It’s 10 p.m. Do you know where your children are?
The question was designed to make people stop and reckon with something they’d been assuming was fine.
Every CIO, CTO, and CISO in the world should be asking a version of that question about AI right now: Do you know where your data is?
Not according to your company’s internal AI policies. Actually, in practice. Builders are running AI agents today on personal accounts, with their own API keys, across five different tools, routing an organization’s most sensitive context through external services no one is monitoring.
For most enterprises, the honest answer is: no.
Today, there is a solution. Anaconda is acquiring Kilo Code.
The Tokenpocalypse Is Here
The global AI economy now processes hundreds of trillions of tokens every month, according to OpenRouter. Kilo alone orchestrates almost 10 trillion tokens per month across more than 3 million developers. These AI-native development workflows are operating at a scale that would have been unimaginable 12 months ago.
Meanwhile, 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.
There’s been no real answer to token-maxxing. Organizations are spending enormous sums, with very little visibility into where the risk is and if they are getting an ROI.
The harder question underneath the spend is one of dependency. Would any organization accept a single source dependency on anything else this critical to its business? If a cloud provider had downtime, there would be a failover plan that included an alternate cloud provider. If there is a chance your company’s law firm could have conflicts on the business you need from…