One AI policy doesn’t fit your whole company. Now it doesn’t have to.
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Kilo has introduced sub-org level governance for enterprise customers, letting a parent organization keep centralized budget and compliance control while each business unit sets its own AI model policies, providers, and inference routes. Admins can now spin up sub-orgs in one click, view all users across sub-orgs from a single screen, set per-sub-org model rules (e.g. restricting a European subsidiary to EU-only inference), and fund each sub-org separately with a flexible balance or Kilo Pass credits. Kilo's cost-saving features—Auto Efficient smart routing, open-weight model support, and Kilo Pass bonus credits—now apply at the sub-org level too.
Table of contents
Where the savings come fromSpin up a sub-org in one clickSee every user, everywhere, from one screenSet model rules once, apply them everywhere (or not)Fund each sub-org your wayTry it todayQuestions this post answers
Can I set different AI model policies for different business units within the same company using Kilo?
Yes, Kilo now supports sub-org level governance where a parent account keeps centralized budget and compliance control while each sub-org sets its own approved models, providers, regions, and inference routes. For example, a European subsidiary can be locked to EU-only inference while other units keep the full model catalog on Kilo's gateway. daily.dev helps engineering leaders track platform updates like this before rolling out org-wide AI policies.
How much cheaper is Kilo's Auto Efficient routing compared to using frontier models directly?
Auto Efficient routes each coding task to the cheapest capable model, delivering 71% of frontier-level results at 72% lower cost. It still operates within whatever model pool a sub-org is restricted to, so tighter governance policies don't sacrifice the cost savings from smart routing. teams comparing AI coding cost strategies can follow routing benchmarks like this on daily.dev.
What share of AI coding usage now goes to open-weight models instead of closed models?
Open-weight models now handle 81% of real usage on Kilo, up from just 3% a year earlier. Mixing open and closed models lets teams get the most coding work done for the least spend, since Kilo's routing can choose across both categories per task. developers weighing open versus closed model adoption can track shifts like this on daily.dev.