GitHub: the pricing arc

The SPP read

When GitHub moved Copilot to usage-based billing, existing Business and Enterprise customers received elevated promotional monthly AI credit allotments for a fixed three-month window. That window closes on September 1, 2026, reverting both plans to their standard included credit allotments against unchanged seat prices.

The SPP read

GitHub restated Copilot's included allowances across its Pro, Pro+, and Max plans, replacing raw credit quantities and Pro-relative multipliers with dollar-denominated totals as the canonical way allowances are presented. The restatement also rebased the Max tier's comparative multiplier from Pro to Pro+, reflecting the growing distance between tiers. The change landed the day before a promotional included-usage uplift for Business and Enterprise plans expired, making the dollar framing the first thing buyers see when that uplift closes.

The SPP read

GitHub extended its downloadable AI usage report to expose token consumption at the per-model level, splitting activity into four distinct categories. For enterprise buyers, the observable unit moves from aggregate model usage to the input, output, and cache dimensions that underlie Copilot billing. The change sits on the governance arc: the meter itself did not move, but the buyer's ability to read and act on it materially expanded.

The SPP read

GitHub has added Kimi K3 to Copilot and placed it on a per-token consumption meter covering input, output, and cached-input traffic. This is the first published rate for this model inside the Copilot marketplace, establishing a new entry on GitHub's model-selection price surface. Buyers choosing between Copilot-available models now have a stated token cost for Kimi K3 to weigh against alternatives.

The SPP read

The value metric does the work here: per active committer prices the people whose code the product touches, not the whole seat roster. It self-scopes to usage, which softens procurement pushback, and it rides the metric Copilot already trained GitHub's buyers to accept. The exposure is the agent question: when AI agents commit code, the definition of an active committer becomes a licensing decision, and today's metric language decides whether that expansion arrives priced or free.

The SPP read

Budgets and usage caps attach to the cost center giving more finely grained controls on variability. Rather than change the pricing architecture, GitHub is gearing more tools for customers to manage their own spend. Expect this trend to continue until a breakout vendor’s alternative model is to absorb the risk, ditch the tools (and the requirement for customers to have staff managing these tools) and make it easier for customers to handle variability.

The SPP read

An open-weight model entering the picker puts a lower-priced option on the same menu as the frontier models, and GitHub hosts this one itself while still describing the charge as provider list pricing. That phrase does quiet work: it frames the credit draw as a relay of someone else's price even where GitHub is the provider, which makes the rate read as arithmetic rather than a decision. Once customers pay by consumption, the model picker stops being a quality control and becomes a price list they operate. The vendor that writes the menu sets the spread, whatever the menu says about who set the price.

The SPP read

BYOK routes inference through the customer's own provider account three weeks after credits went live, moving the token bill off GitHub's meter entirely. What stays billable is the harness: the agent loop, the client, the repository context, the governance. That splits what a Copilot subscription had been selling as one product, and it hands the largest buyers a lever they will eventually pull at renewal. A vendor that lets you bring your own tokens has told you which half of the product it believes is defensible.

The SPP read

The effective date is where the architecture sharpened: multipliers rose the same day billing went live, and code review began drawing on two meters at once, Actions minutes and AI Credits. Notice what is absent: a legacy conversion. The pattern that holds across our engagements runs new-logo pricing first, with the installed base following on a modeled schedule. GitHub instead repriced the installed base in place on a date, cushioned by promotional and flex credits that expire on a calendar. A flash-cut of the base is the most damaging path a repricing can take, and doubly so in a competitive market where the smallest customers carry the lowest switching costs. The cushions soften the first invoice, not the decision to leave.

The SPP read

The announcement did the heavy lifting a quarter early: plan prices held still while the unit underneath them changed from requests to AI Credits, and promotional credit cushions bought the installed base a quiet first quarter. Swapping the meter while the visible price stands still is the least-resistance path through a repricing, and the cushion is its anesthetic. The bill arrives when the promo expires, not when the announcement ships.

The SPP read

The annual cohort was not migrated. It was left on the old meter with its multipliers raised, then dropped to the free plan at expiry unless it re-bought. That turns a renewal into a fresh purchase decision at the moment the customer has the least leverage and the vendor has the most: mid-arc, on a repriced surface, with the prior contract already gone. The cohort that had been paying annually was the one asked to buy again at the new rates.

The SPP read

GitHub stopped selling the individual plans, tightened their limits, and pulled the most expensive model out of Pro, then said why in pricing terms: a handful of requests could now cost more than the plan itself. The stated reason is the mechanism: a flat monthly fee with per-request costs the fee did not bound, and the model pulled from Pro was the one carrying the largest of those costs. The repricing followed one week later. The sequence on the record: access tightened first, with the cost reason stated, and the repricing dated one week later.

The SPP read

Auto bills at whatever model it picks, and at launch it picked only from the low end of the menu: models carrying a zero-to-one multiplier. Choosing auto then cost ten percent less than choosing the same model directly. The discount prices a decision rather than a resource. The customer gives up model choice, GitHub keeps the spread between the model the task needs and the model the customer would have reached for, and the router is bounded so that spread can only run one way. Paying customers to stop choosing is how a reseller manufactures a margin the meter does not hand it.

The SPP read

Enforcement is the move, not the announcement: on June 18 the allowance became a wall, and passing through it cost four cents a request. Two design choices sit underneath. The overage tap shipped switched off, so a developer had to opt into a variable bill rather than discover one, and completions stayed unmetered so the daily experience never felt counted. Meter the frontier, leave the habit free, and the bill lands only on work the buyer already believes is expensive.

The SPP read

The plan split the product surface in two: unlimited use of the base model, and a counted allowance of premium requests for everything else. That is a new metric introduced under cover of a new top tier, where a higher price presents the unit as generosity rather than a meter. Every later step in GitHub's arc runs through that unit. The first time a vendor counts something, the number is almost never the point; the habit of counting is.