GitHub and Copilot pricing changes: every tracked move, dated
GitHub's arc begins with a counted unit rather than a price. A new top plan arrived carrying an allowance of premium requests, later enforced as a wall, with overage priced per request and the overage switch shipped off. The unit was then swapped to AI credits while plan prices held, promotional allowances ran on a calendar, and the annual cohort stayed on the old meter until expiry. What has been added since is governance, not architecture: budgets, cost centers, a router that discounts letting the vendor pick the model, and bring-your-own-key, which moves the token bill off GitHub's meter. A newer product prices per active committer, a metric that counts the people whose code the product touches.
tracked and read.
first move to latest.
last re-checked.
Last tracked move:
GitHub pricing moves, newest first.
- Apr 04, 2025Licensing + Packaging · Unit swap
- Jun 18, 2025Licensing · Meter extended
- Jul 10, 2025Pricing · Allowance up
- Apr 17, 2026Pricing · Access change
- Apr 20, 2026Licensing + Packaging · Access change
- Apr 27, 2026Pricing · Terms change
- Apr 27, 2026Licensing + Pricing · Unit swap
- Jun 01, 2026Licensing + Packaging · Unit swap
- Jun 23, 2026Licensing + Pricing · Pass-through
- Jul 01, 2026Licensing + Packaging + Pricing · Pass-through
- Jul 02, 2026Licensing · Spend controls
- Jul 13, 2026Licensing + Pricing · Rate card
- Aug 06, 2026Licensing + Pricing · Pass-through
- Aug 11, 2026Licensing · Spend controls
- Aug 13, 2026Licensing + Pricing · Pass-through
- Aug 28, 2026Terms change
- Aug 31, 2026Pricing · Price hold
- Sep 01, 2026Licensing · Spend controls
- Sep 01, 2026Pricing · Allowance cut
- Sep 03, 2026Licensing · Access change
- Sep 04, 2026Licensing + Pricing · Pass-through
- Sep 27, 2026Licensing + Pricing · Price hold
- Oct 04, 2026Terms change
- Oct 11, 2026Terms change
- Oct 14, 2026Packaging · Repackage
- Oct 28, 2026Licensing + Pricing · Pass-through
- Oct 28, 2026Licensing + Packaging · Repackage
The move
GitHub added a new 'Copilot access' plan alongside Copilot Business ($19/user/month, 1,900 AI credits) and Copilot Enterprise ($39/user/month, 3,900 AI credits); it costs $0 incremental for licensed GitHub Enterprise Cloud users or $10/user/month as Copilot Standalone, includes no AI credit allowance (metered usage is billed from first use), and comes with its own seat-assignment and access-revocation rules.
The SPP read
GitHub added a third organizational Copilot plan that charges for the seat alone, grants no AI credit allowance, and bills every unit of usage from the first credit. Business and Enterprise keep their prices and included credits, so GitHub has added an access-only entry point to the Copilot lineup and left the existing tiers unchanged. Licensed GitHub Enterprise Cloud users get the seat at no incremental charge, and the plan has its own rules for assigning seats and revoking access.
The move
On October 28, 2026, GitHub made Copilot Fusion generally available on all Copilot plans in VS Code, the Copilot app, Copilot CLI and JetBrains IDEs, replacing the auto model selection and HydraFusion research-preview settings; usage is billed for each model Fusion uses at that model's standard rate, with a limited-time 30% discount on model costs for users on paid Copilot plans.
The SPP read
GitHub took its model router out of preview as Copilot Fusion on every plan, folding the auto model selection setting and the HydraFusion preview into one picker with three effort levels. Billing stayed pass-through: each model Fusion calls bills at that model's standard rate, and paid plans receive a time-limited discount on those model costs while the window is open, deeper than the discount auto had carried. No unit changed and no list rate moved; what changed is that routing is now a plan feature with a promotional rate behind it.
The move
On October 14, 2026 GitHub introduced HydraFusion Max, a higher-reasoning-effort option built on the same orchestration architecture and workflow techniques as HydraFusion, available in VS Code, the GitHub Copilot app and Copilot CLI; both remained in research preview on Copilot Pro, Pro+, Business and Enterprise plans with experimental or preview features enabled, drawing from a model pool that now included Claude Opus 5.5, GPT-6 Astra, GPT-6.1 Sol and GPT-6 Luna; the post states no separate price and no change to HydraFusion's billing (tokens consumed by the models it uses, at each model's standard rate, row 729).
The SPP read
On October 14, 2026 GitHub added HydraFusion Max, a higher-effort option built on the same orchestration as HydraFusion, in VS Code, the Copilot app and Copilot CLI. Both stayed in research preview for Pro, Pro+, Business and Enterprise plans with experimental features enabled. The post names no price and no change to the billing shape, which the ledger records on the HydraFusion row as each model's standard rate for the tokens used.
The move
GitHub added a 'Payment dates for credit card or PayPal' section to its Copilot org/enterprise billing page specifying charges at the start of each calendar month for assigned licenses, at the start of each billing cycle for prior-cycle usage beyond the plan allowance, whenever payment is needed to continue using AI credits, and on purchase of additional licenses mid-cycle, with a receipt and invoice at each point.
The SPP read
GitHub wrote the payment timing for Copilot organizations and enterprises paying by card or PayPal into its billing docs. The August announcement had set payment before access for each new seat; the page now goes further. Every assigned license is charged at the start of each calendar month, usage beyond the plan allowance is billed at the start of the next cycle, and a charge can land mid-cycle when payment is needed to keep using AI credits or when more licenses are bought. The seat and the credit stay the units and no rate or allowance moved. The seat charge moved ahead of the access it buys; overage still bills after the use, at the next cycle, except that GitHub can now hold the credit meter until it is paid.
The move
GitHub added an 'Important' notice to its Copilot billing docs stating that users who are suspended or removed from an organization or enterprise lose Copilot access immediately, but their seats are still billed through the end of the current billing cycle.
The SPP read
GitHub's Copilot billing docs now state that a user suspended or removed from an organization or enterprise loses Copilot access at once while the seat stays billed to the end of the current billing cycle. The rule itself is older: GitHub's community answers and earlier docs described the same treatment well before this page did. What is new is the notice, which arrived in the week the prepaid seat terms announced in August took effect, so the no-refund corner of a seat that leaves mid-cycle is now written where the prepayment is.
Read revised Nov 05, 2026Reason: Now says the rule predates the notice and names the week the notice landed.
GitHub's Copilot billing docs now state that a user suspended or removed from an organization or enterprise loses Copilot access immediately while the seat stays billed to the end of the current billing cycle.
Read revised Oct 20, 2026Reason: Chris 10-20: read as a terms move on the seat unit, the corner-case policy written down
GitHub's Copilot billing docs now say that a user suspended or removed from an organization or enterprise loses Copilot access immediately, while their seat stays billed until the current billing cycle ends.
The move
GitHub kept Copilot prices unchanged at $0/$10/$39/$100 per user per month for Free/Pro/Pro+/Max but restated included usage in AI credits: Pro now lists 1,500 monthly AI credits ($15 value), replacing '$15 monthly total credits'; Pro+ and Max are now quoted as over 4.6x and over 13.3x Pro's credits, replacing $70 and $200; plan access is reframed around model tiers (entry-level, medium-complexity, frontier); and new models were added, including Claude Opus 5.5, GPT-6 Astra/Luna/Sol and Grok 4.7.
The SPP read
Nothing on the price line moved. What changed is the denomination of what each plan includes: a monthly dollar amount of usage became a count of AI credits with the dollar value in brackets, and the higher plans now describe their allowance as a multiple of the entry plan's credits. This reverses the restatement the ledger recorded four weeks earlier, when the same allowance went from credits to dollars, so the denomination flipped twice in a month; the model list on every plan grew in the same capture.
The move
HydraFusion usage is priced based on the tokens consumed by the models it uses, at each model's standard rate.
The SPP read
HydraFusion, GitHub's multi-model orchestration for Copilot, entered research preview with no unit of its own: usage counted as the tokens each model it called consumed, billed at that model's standard rate, under the same budgets and spending limits as any other Copilot usage. An orchestrated answer cost more or less with the number of models used and how much each consumed.
Teaser revised Nov 04, 2026Reason: Tense: the preview closed into Copilot Fusion on October 28, 2026.
GitHub bills HydraFusion orchestration through its underlying models' own token rates
Read revised Nov 04, 2026Reason: Past tense: the research preview was folded into Copilot Fusion at general availability on October 28, 2026, its own entry.
HydraFusion, GitHub's multi-model orchestration for Copilot, is not priced on a unit of its own.
The move
On September 3, 2026 GitHub began reopening Copilot Business and Copilot Enterprise sign-ups for customers paying by credit card or PayPal, with strengthened account vetting, and set the billing terms for them: every new seat assignment requires payment before access, all assigned seats incur an upfront charge at the start of the next billing cycle (existing customers from October 1, 2026), additional payment may be required to continue using Copilot past included usage, and included usage may be prorated across the month; plan pricing and seat prorations unchanged.
The SPP read
GitHub reopened Copilot Business and Enterprise to card and PayPal buyers in stages, with account checks in front of the door, and widened the payment terms it had announced a week earlier: where the August notice had put payment before access on each new seat, every assigned seat now draws an upfront charge at the start of each cycle, existing customers included from October, and a customer past its included usage can be asked to pay before continuing. Prices and prorations held. The seat is still the unit; the cash now arrives before the use on every seat, and the meter can pause for payment.
The move
To cover the move to usage-based billing, existing Copilot Business and Copilot Enterprise customers received promotional included usage of $30 and $70 in monthly AI Credits for June, July and August 2026. The window ran three months only, so from September 2026 both revert to their standard included allotments of $19 and $39 in monthly AI Credits, against unchanged seat prices of $19 and $39 per user per month.
The SPP read
When GitHub moved Copilot to usage-based billing, existing Business and Enterprise customers received a raised monthly AI credit allotment for a fixed three-month window. The window closed at the start of September and both plans went back to their standard included allotments, with seat prices unchanged. The allowance moved and the price held; on the arc this is the cushion from the June repricing coming off.
Read revised Nov 04, 2026Reason: Past tense: the promotional window closed on September 1, 2026. The entry is an allowance change at a held price.
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 move
On September 1, 2026 GitHub made expiration dates on individual Copilot user budgets generally available for Copilot Business and Copilot Enterprise: a budget can be set to expire at the start of the next billing cycle or on a specific date (the default remains no expiration), GitHub removes it on that date and the user falls back to their cost-center per-user budget or the universal budget; set in billing settings or via the expires_at field of the Budgets REST API.
The SPP read
On September 1, 2026 GitHub added an optional expiration date to individual user budgets on Copilot Business and Copilot Enterprise. A budget can now end at the start of the next billing cycle or on a chosen date, and the user then falls back to the cost center or universal budget that applies to them. GitHub's note says the prior state required removing each temporary override by hand. This is a control the buyer operates over its own spend; no rate or allowance moved.
The move
On August 31, 2026 GitHub restated Copilot's included allowances on the plans page from credit counts and Pro-relative multipliers to dollar totals: '1,500 monthly AI credits ($15 value)' became '$15 monthly total credits for Pro', 'Over 4.6x' and 'Over 13.3x included monthly credits than Pro' became '$70 monthly total credits for Pro+' and '$200 monthly total credits for Max', and the Max comparison was rebased from Pro to Pro+ ('2.9x+ included usage than Pro+'). The restatement landed the day before the three-month included-usage uplift for Business and Enterprise ended (move 437).
The SPP read
GitHub restated what each Copilot plan includes on its plans page: the entry plan's monthly credit count with its dollar value became a monthly dollar total, the two higher plans' multiples of the entry plan became dollar totals of their own, and the top plan's comparison was rebased from the entry plan to the middle one. Prices and the allowances themselves held; what moved is the denomination on the page. The restatement landed the day before the three-month raised allotment for Business and Enterprise ended.
Read revised Nov 05, 2026Reason: Two motive phrases removed; now states the restatement and what held.
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 move
On August 28, 2026, GitHub announced upcoming Copilot billing changes: seats added mid-cycle stay prorated to the end of the billing cycle, and every new Business or Enterprise seat assignment requires payment before access, effective October 1, 2026 for credit card and PayPal customers, with prices unchanged.
The SPP read
On August 28, 2026, GitHub announced Copilot billing changes effective October 1, 2026 for credit card and PayPal customers: seats added mid-cycle stay prorated to the end of the billing cycle, and every new Business or Enterprise seat assignment requires payment before access. Prices are unchanged. The seat stays the licensing metric and the rate stays put; what moves is the timing of the charge, from access first to payment first on each new seat, with the prorated partial cycle kept.
The move
Gemini 3.7 Flash in GitHub Copilot is billed at provider list pricing under usage-based billing.
The SPP read
Gemini 3.7 Flash arrived in GitHub Copilot billed at the provider's list price under usage-based billing. The rate a Copilot customer pays for this model is the rate the model's provider publishes, passed through on the usage meter. A provider model entering the Copilot pricebook at pass-through leaves the metered unit and its rate on the provider's card, with Copilot running the meter.
The move
GitHub added per-model token breakdown (input, output, cache_read, cache_write) to its downloadable AI usage report, announced on August 11, 2026.
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 move
On August 6, 2026 GitHub made Kimi K3, an open-weight model, generally available in GitHub Copilot across the Pro, Pro+, Max, Business and Enterprise plans, billed at provider list pricing under usage-based billing: $3 per 1 million input tokens, $15 per 1 million output tokens and $0.30 per 1 million cached input tokens.
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 move
GitHub Code Quality will be priced at $10 per active committer per month when it becomes generally available on July 20, 2026.
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.
Teaser revised Oct 21, 2026Reason: Chris 10-20 plain-language sweep: the riddle teaser (an abstraction standing for the event) rewritten as what the vendor did
Quality became its own line on the invoice.
The move
GitHub released cost center support for AI credit pools as of July 2, 2026.
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.
Teaser revised Oct 21, 2026Reason: Chris 10-20 plain-language sweep: the riddle teaser (an abstraction standing for the event) rewritten as what the vendor did
Credits found an owner: the cost center.
The move
On July 1, 2026 GitHub made Kimi K2.7 Code generally available in GitHub Copilot, the first open-weight model selectable in the Copilot model picker, hosted by GitHub on Microsoft Azure and billed at provider list pricing under usage-based billing. Rollout began on Copilot Pro, Pro+, and Max, extending to Copilot Business and Enterprise on July 7, 2026.
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.
Teaser revised Oct 21, 2026Reason: Chris 10-20 plain-language sweep: the riddle teaser rewritten as what the vendor did
The model picker quietly became a price list the customer operates.
The move
On June 23, 2026 the GitHub Copilot app added bring your own key support, letting agent sessions run against a customer's own model providers (OpenAI, Azure OpenAI, Microsoft Foundry, Anthropic, LM Studio, Ollama, and any OpenAI-compatible endpoint), with inference routed through the customer's own cloud account, tenant, or internal gateway while keeping their existing billing, quotas, regions, and data-handling terms.
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 move
On June 1, 2026 GitHub Copilot's usage-based billing took effect: premium request units retired in favor of AI Credits at $0.01 per credit, multipliers rose the same day, and code review began drawing on two meters at once, GitHub Actions minutes in addition to AI Credits. The same date introduced a Copilot Max tier at $100 per month for power users with higher included usage and higher spending limits, and brought user-level budgets to general availability for organizations and enterprises. Standard monthly allowances are 1,900 credits per user on Copilot Business and 3,900 on Copilot Enterprise; promotional allowances of 3,000 and 7,000 run June 1 to September 1, 2026 and are total, not additional.
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 face the lowest switching costs. The cushions soften the first invoice, not the decision to leave.
Teaser revised Oct 21, 2026Reason: Chris 10-20 plain-language sweep: the riddle teaser (an abstraction standing for the event) rewritten as what the vendor did
The meter went live and the multipliers rose the same day.
The move
On April 27, 2026 GitHub announced that all Copilot plans would move to usage-based billing on June 1, replacing premium request units with GitHub AI Credits. Plan prices held (Pro $10, Pro+ $39, Business $19 per user, Enterprise $39 per user). Existing Business and Enterprise customers were to receive raised promotional included usage for June, July and August 2026, $30 and $70 per user per month, replacing the standard $19 and $39 included allowances rather than adding to them.
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 move
On April 27, 2026 GitHub set the terms for annual Copilot Pro and Pro+ subscribers under the move to usage-based billing: they remain on premium request pricing until their plan expires, model multipliers increase on June 1, 2026 for annual subscribers only, and at expiration they transition to Copilot Free with the option to upgrade to a paid monthly plan, or may convert to a monthly paid plan before expiry with prorated credits for the remaining value of the annual plan.
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 move
On April 20, 2026 GitHub paused new sign-ups for Copilot Pro, Pro+, and Student, tightened usage limits on individual plans, and removed Opus models from Pro, stating that agentic workflows had changed Copilot's compute demands and that it had become common for a handful of requests to cost more than the plan price. Sign-ups reopened gradually from the June 17, 2026 announcement, after usage-based billing took effect.
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 with 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 move
On April 17, 2026 GitHub made Copilot auto model selection generally available in Copilot CLI for all Copilot plans, routing each task to a model Copilot chooses (limited at the time to models carrying 0x to 1x multipliers) and billing premium request use at the selected model's rate, with all paid subscribers receiving a 10% discount on the model multiplier when using auto. On July 1, 2026 GitHub added task-based routing to the same feature and re-denominated the discount into AI credits.
The SPP read
Auto model selection reached Copilot CLI with the billing it already had in the editors: a request billed at the rate of the model auto picked, from a pool held at or below the base multiplier, and paid plans drew down less per request than they would have choosing the same model by hand. The discount was already on sale in VS Code and the JetBrains IDEs; what moved on this date was the surface it reached.
Read revised Nov 07, 2026Reason: The earlier text stated the discount in the present tense; the October 28 entry folded the setting into a different discount, so this entry is dated to April.
Auto model selection reached Copilot CLI with the billing it already had in the editors: a request bills at the rate of the model auto picks, from a pool held at or below the base multiplier, and paid plans draw down less per request than they would choosing the same model by hand.
Teaser revised Nov 04, 2026Reason: The earlier teaser treated the discount as a margin motive; this entry's event is the surface.
A discount for letting the vendor choose the model is a margin, not a favor.
The move
From 19:00 UTC on July 10, 2025 GitHub charged Copilot coding agent exactly one Copilot premium request per session, where a session begins when the agent is asked to create a pull request or make changes to one, regardless of files modified or task complexity, replacing per-step consumption; GitHub said this let users 'delegate up to 20x more tasks' within the monthly premium request allowance, while GitHub Actions minutes for the agent's runs still varied by task. Coding agent was in public preview across all paid Copilot plans.
The SPP read
From July 10, 2025 GitHub charged a Copilot coding agent session as one premium request, whatever the number of files touched or the length of the task. A session starts when the agent is asked to open a pull request or change one. Before this, the agent drew a premium request at each step, so a single prompt could consume several. The monthly premium request allowance and its price were unchanged; GitHub Actions minutes for the agent's runs still varied with the work.
The move
On June 18, 2025 GitHub began enforcing the monthly premium request allowance across all paid Copilot plans, resetting every counter to zero for the first cycle, with the spending limit for additional requests defaulting to $0. Additional premium requests beyond the allowance were priced at $0.04 each, individual features drew on the allowance at published model multipliers (the Copilot coding agent at a fixed multiplier of one, potentially consuming multiple premium requests in response to a single prompt), and code completions plus the included models remained unlimited.
The SPP read
Enforcement is the move: on June 18 the allowance became a wall, and passing through it cost a published per-request overage. Two design terms 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. The meter sits on the frontier models, the habit stays free, and the bill lands only on work the buyer already regards as expensive.
Teaser revised Oct 21, 2026Reason: Chris 10-20 plain-language sweep: the riddle teaser (an abstraction standing for the event) rewritten as what the vendor did
The allowance became a wall, and the overage tap shipped switched off.
Read revised Sep 15, 2026Reason: Read revised to describe the change without repeating the price points, which stay in the move record.
Enforcement is the move, not the announcement: on June 18 the allowance became a wall, and passing through it cost four cents a request.
The move
On April 4, 2025 GitHub announced Copilot Pro+ at $39 per month, including 1,500 premium requests per month, stated at announcement to go live on May 5, 2025, alongside the unlimited requests for agent mode, context-driven chat, and code completions that all paid plans had when using GitHub's base model. Premium request billing ultimately began on June 18, 2025.
The SPP read
Copilot Pro+ arrived as a top tier with a counted monthly allowance of premium requests beside unlimited use of the base model, so the plan split the product surface in two: the base model uncounted, every other model drawn against a counter. The premium request was a new counted unit on Copilot's paid plans.
Read revised Nov 07, 2026Reason: The earlier text said every later step ran through the premium request; that unit was retired in June 2026, so this entry describes the April 2025 move alone.
The plan split the product surface in two: unlimited use of the base model, and a counted allowance of premium requests for everything else.
Planning a move like one on this arc, or countering one GitHub just made? Talk to a pricing expert before it ships: describe the move, and a pricing architect reads it against your own licensing, packaging, and pricing.
Is your own pricing architecture ready for a move like this?
Every GitHub move on this arc changed its licensing, packaging, or pricing. Score your own architecture, twenty-five questions in four minutes, free, and see which of the three holds the risk.
What we have written about GitHub.
Where Your Software May Run Is a Licensing Decision, Not a Deal Term
Deployment is one of four dimensions in a software license grant. Where the software runs, and where the model runs, is priced before it is negotiated.
Unify Pricing Across Product Lines Without Losing Revenue
Multi-product pricing chaos costs deals. Learn how to unify pricing across product lines without flattening value or confusing buyers. See SPP's framework.
SaaS Pricing Models: What Actually Works in B2B Software
Per-seat, usage, flat-rate, freemium, hybrid: the licensing, packaging, and pricing decisions that pick the model, and how flat fees combine with usage.
Other vendors on the log.
All tracked vendors on the AI Pricing Observatory
Get this week’s verified AI pricing moves in your inbox.
The moves, the week they’re verified. A dated headline and a one-line read for each new move, with a link back to the full page.
One issue a week, only when something’s actually moved. Unsubscribe anytime from the confirmation email.
Prefer Slack? Get the weekly digest in Slack.
Primary sources behind the GitHub arc, dated.
| Date | Source | Record |
|---|---|---|
| docs.github.com | primary ↗ | |
| GitHub Blog | primary ↗ | |
| GitHub Blog | primary ↗ | |
| docs.github.com | primary ↗ | |
| docs.github.com | primary ↗ | |
| github.com | primary ↗ | |
| GitHub Blog | primary ↗ | |
| GitHub Blog | primary ↗ | |
| GitHub Blog | primary ↗ | |
| GitHub Blog | primary ↗ | |
| github.com | primary ↗ | |
| GitHub Blog | primary ↗ | |
| GitHub Blog | primary ↗ | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
| 2025 | ||
| GitHub Blog | primary ↗ | |
| GitHub Blog | primary ↗ · archived | |
| GitHub Blog | primary ↗ · archived | |
Chris Mele
Ranked #1 on OpenView’s list of B2B SaaS pricing experts. Every read on this page is written by a pricing architect, never drafted by a model, backed by a team that has held CFO, CPO, and CIO seats inside software companies.
The claims ledger and citability gate do the heavy lifting on sourcing. The expert makes the calls only humans can: what a move actually changes under its label, and what it signals for the vendors around it.
Read more about Chris →Want this arc read against your own pricing architecture?
Watching how GitHub moves is one input. Deciding how your own licensing, packaging, and pricing should respond is a different discipline, and it is not something a dashboard can do for you.
