Enterprise admins can now set a cost center user-level budget: one per-user AI credit budget on a cost center that applies to every individual in it. As membership changes, the budget follows. Anyone added to the cost center, directly or through an enterprise team, picks up its per-user budget, and anyone removed is no longer covered by it. You do not reconfigure budgets monthly or when people move teams. This removes the need to create thousands of individual budgets to control spend across teams with different AI needs.

Using this tool, you have more granular options when funding teams. For example, you could put your platform engineering team in one cost center at $250 per user and keep everyone else on a $40 universal budget, without setting budgets one user at a time.

A cost center’s user-level budget counts every AI credit a member consumes, from the included usage pool and from additional usage, if enabled. Because it counts included usage, it can stop a user before the pool is exhausted and before any metered charges begin. This is what sets it apart from a cost center budget, which caps a team’s total additional usage only after the pool is exhausted.

Precedence runs from most specific to least specific. An individual user-level budget overrides a cost center user-level budget, which overrides the universal budget. As of June 30th, creating a cost center user-level budget is only available through the REST API. Billing UI support for creating this budget type is coming soon.

Key details

  • Add enterprise teams or individual users to a cost center, then create a per-user budget scoped to that cost center via the REST API.
  • Membership stays in sync. As people join or leave the cost center or its enterprise team, budget coverage updates automatically.
  • Give different cost centers different per-user budgets to match how each team uses GitHub Copilot.
  • A cost center user-level budget overrides the universal budget for its members. An individual user-level budget override takes precedence over both.

To learn more, see Budgets for usage-based billing and Control GitHub costs at scale.

Join the discussion or submit feedback within GitHub Community.