Three million developers found this tool on their own. Nobody ran a bake-off, nobody filed a purchase request, and in most of those companies nobody in procurement has heard the name. Kilo Code went from zero to three million users in sixteen months because developers told other developers about it (Anaconda, 2026). On July 15, Anaconda bought it.
If you are a chief information officer, the useful part of that sentence is the buyer. Anaconda already has a contract with 95% of the Fortune 500 (Anaconda, 2026). A tool your teams adopted without you now belongs to a vendor you pay.
That is a better position than most shadow adoption stories end in.
Your developers made a good call, and it came with a vendor relationship you never signed
Kilo lets a developer pick from more than 500 AI models, and it can pick the best one for a given task on its own (Anaconda, 2026). Developers love that. It is also the part worth a second look, because every one of those models belongs to somebody, runs somewhere, and bills by usage.
Anaconda names the pressure plainly: as AI use scales, token costs are outpacing return (Anaconda, 2026). The company also opens its announcement with 80% of AI projects falling short of production (Anaconda, 2026). That is Anaconda's framing of the problem it sells against, and the shape of it matches what most technology leaders are seeing on their own invoices.
Kilo's answer is choice with a floor under it. Run it on your own infrastructure if you want to. Let it choose models for cost as well as quality. Anaconda's answer is the decade of enterprise trust it already sells you, extended to cover the moment an agent writes something.
Anaconda is assembling one contract where you currently hold several
Kilo is Anaconda's second acquisition this year. Outerbounds came earlier and brought the machinery for running AI work in production (Anaconda, 2026). Kilo covers the other end, where the work starts. David DeSanto, Anaconda's chief executive, put the enterprise question as letting builders move at the speed AI allows without losing control of what ships or failing a compliance audit (Anaconda, 2026).
Here is where Anaconda earns some credit. Most acquisition announcements let you assume the pieces already fit together. This one says the opposite. Connecting Kilo to Anaconda's governed environments is a direction the company is building toward, not a capability available today (Anaconda, 2026). Kilo also keeps running exactly as it does now, with no changes to products, plans, or support for current users (Anaconda, 2026).
Anaconda has told you what it is building and has not told you when.
Sid Sijbrandij, who co-founded Kilo and co-founded GitLab, described the two companies as a rare fit with almost no overlap, each holding what the other lacks (Anaconda, 2026). He is right about the fit. The date is the open item, and it is the one that decides what you do in the next two quarters.
Find out how many of your developers are already running Kilo, then ask your Anaconda account team when your existing agreement will cover them. Anaconda has said the connection is coming and has not said when. Get the date, and decide whether you formalize what your teams already chose or wait and buy it once.
Kilo Code. Kilo, 2026, kilo.ai.
