GitHub added Kimi K2.7 Code to Copilot Business and Copilot Enterprise on July 7, expanding the model beyond the Pro, Pro+, and Max plans announced on July 1.
GitHub describes Kimi K2.7 Code as an open-weight model and says it is the first open-weight model offered as a selectable option in the Copilot model picker. The model is hosted by GitHub on Microsoft Azure and billed at provider list pricing under usage-based billing.
For Business and Enterprise plans, Kimi K2.7 Code is off by default. Administrators must enable the policy before users can select it.
Model choice now comes with budget and measurement controls
The Kimi release landed the same day as two enterprise-management updates.
GitHub Enterprise Cloud admins can now create cost-center user-level budgets directly in the billing UI. The feature lets admins add teams or individual users to a cost center, set one per-user AI credit budget, and keep coverage synced as membership changes.
GitHub also added two code-review velocity fields to the Copilot usage metrics API: median minutes from pull request creation to first review, and median review submissions before merge. Both are reported by AI adoption phase and scoped to merged pull requests.
Taken together, the July 7 updates move Copilot model choice into a governed operating layer. Admins are not only choosing whether a model appears in the picker. They are also being given tools to cap spend and measure whether deeper AI adoption changes review flow.
The open-weight label does not remove enterprise review
The open-weight part of Kimi matters because it introduces a different model provenance into Copilot’s enterprise picker. But GitHub’s own default is cautious: off until an admin enables it.
That is the right posture. Enterprise teams still need to review data handling, model hosting, pricing, allowed repositories, and whether the model fits the tasks developers will assign to it.
The practical test is not whether Kimi is cheaper or more open in the abstract. It is whether it completes the team’s coding workflows at an acceptable cost, under a policy the organization can explain.
