Cafiyn Pulse
← Startup Signals
5 min readUpdated 2026-08-31Issue 1

One Copilot code review costs 13 requests. Here is the rest of the maths.

Copilot now bills on usage rather than seats. The headline change is simple. The multipliers underneath it are where teams get surprised.

ByKarthik KumarCafiyn Innovations
At a glance
Changed
All plans moved to usage-based billing on 1 June 2026
Unit
Monthly allotment of GitHub AI Credits
Reasoning models
Can bill at 5x or 20x a standard request
Copilot code review
13x per pull request or IDE review
Auto model selection
10% discount, e.g. 1x becomes 0.9x
Enterprise Cloud
Data residency or FedRAMP adds a further 10%

The change, and the number that matters

All Copilot plans moved to usage-based billing on 1 June 2026, replacing the previous premium-request model with a monthly allotment of GitHub AI Credits.

Per-seat pricing is predictable and usage-based pricing is not, which is the entire story. But the part that catches teams out is not the model itself, it is that a single interaction does not necessarily cost one request.

Copilot code review carries a multiplier of 13. Every time it reviews a pull request, or reviews code in your IDE, your allotment drops by 13. If you wired Copilot review into CI on every PR, work out your monthly PR count and multiply. For a team merging ten pull requests a day, that is a meaningfully different number than the one on the pricing page.

Where the multipliers stack

Advanced reasoning models can consume 5x or 20x a standard request. This is defensible, since a reasoning model genuinely does more work, but it makes model choice a budget decision rather than a preference.

There are discounts too, and they are worth taking. Using auto model selection in Copilot Chat, Copilot CLI, or the Copilot cloud agent earns a 10% multiplier discount, so a model that would bill at 1x bills at 0.9x instead. Letting the platform pick is cheaper than pinning a model, which is the opposite of the instinct most engineers have.

On GitHub Enterprise Cloud, requests processed with data residency or FedRAMP enforcement carry an additional 10% multiplier. If you are in a regulated environment, that is a compliance cost showing up as a line in your AI budget, and it is worth naming it as such when someone asks why the number moved.

Why unattended agents change the risk

Under per-seat pricing, the worst case was bounded: you paid for the seats you had. Under usage-based pricing with agents that run without a human waiting, the worst case is bounded by whatever loop you wrote.

This is the same shape as any metered cloud resource, and the same discipline applies. The reason it surprises people with AI tooling specifically is that the previous model trained everyone to think of it as a fixed cost, so nobody instrumented it.

What to do

  1. 1Count your monthly pull requests and multiply by 13 before deciding whether Copilot code review runs on every PR or only on ones above a size threshold.
  2. 2Turn on auto model selection where you can. The 10% discount applies for doing less work, not more.
  3. 3Treat reasoning models as a deliberate choice per task rather than a default, given the 5x to 20x range.
  4. 4Set a spend alert now. The first genuinely surprising invoice under a metered model is almost always the one nobody was watching for.
  5. 5If you are on Enterprise Cloud with data residency or FedRAMP, budget the extra 10% explicitly so it is not mistaken for drift.

Common questions

When did Copilot billing change?

All plans moved to usage-based billing on 1 June 2026, shifting from premium requests to a monthly allotment of GitHub AI Credits.

How much does a Copilot code review cost?

It carries a model multiplier of 13, so each pull request review or IDE code review reduces your monthly allotment by 13 rather than 1.

Is there a way to reduce the cost?

Auto model selection in Copilot Chat, Copilot CLI, or the cloud agent earns a 10% multiplier discount, so a 1x model bills at 0.9x. Beyond that, the levers are choosing reasoning models deliberately and scoping automated review rather than running it on everything.

Does data residency cost extra?

On GitHub Enterprise Cloud, requests processed with data residency or FedRAMP enforcement carry an additional 10% multiplier.

Sources

Read against the primary documentation rather than secondary coverage. Where a figure comes from a provider's own docs, it is quoted as published on 2026-08-31.

Related

What a code assistant costs per developer →Model your own AI bill →

More from Signals

OpenAI removes o1, o3-mini, o4-mini and GPT-4 Turbo on 23 October. The replacements it names run from 5.5 times the price to 97 percent less.
Eleven models and six fine tuned models go dark in four days. Here is OpenAI's own mapping, what each landing costs on a typical month of traffic, and the places where the named replacement is not the cheapest or cannot be used at all.
OpenCode says a breach hit 1.4 percent of Console users who linked an AI provider. Rotate those keys before the root cause is published.
OpenCode has confirmed the breach and has not said how it happened or what was taken. Here is what the vendor said, who is exposed, the order to work in, and how to limit the damage next time.
GitHub Actions workflow lockfiles are in public preview. Here is how to turn them on, check them in CI, and what they do not protect.
A tag can move after you reviewed it. A lockfile makes the runner use the commit you reviewed. Here is the setup, the CI check, the policy, and what a lockfile cannot tell you.
Next.js 16.4.1 and 15.5.28 fix two critical remote code execution flaws. For one of them there is no workaround.
Two of the three fixes were postponed from September. Here is what each flaw needs in order to be reachable, the one workaround that exists, and what the announcement leaves out.
A poisoned npm release that punishes you for revoking the stolen token. The order of your response is the whole defence.
Most incident guidance starts with revoking the leaked token. Here that is the trigger. What StepSecurity found, the order it recommends, and why a valid provenance attestation did not help.
Claude Haiku 5.5 costs a tenth of Haiku 4.5 per token. One token past 100,000 it costs half.
The rate card is a tenth of Haiku 4.5. The footnote is a threshold that moves the price fivefold and that a tokenizer change pushes you toward.
Gemini 4 Argon launched at $2 and $10 and goes to $4 and $20 on 1 December. Price your product on the second number.
Every tier on the pricing page doubles on the same date. What changes, what the number includes, and what to do if you are building on the launch rate.
Claude Haiku 5.5 is not a model id swap. Five things that worked on Haiku 4.5 now return a 400.
The model id is the easy part. The requests that now fail, the response parsing that changes, and the details that fail quietly.
Next.js shipped 16.3.7 and 16.3.8 a day apart. Only one of them is the security release.
Two patch releases a day apart, one of them a decoy if you are not reading carefully. And the 15.5 line does not get the high severity fix at all.
The EU AI output marking rule is not a December deadline. For most teams it started in August.
Almost every summary of this gives one date. There are two, and which one applies to you depends on when you shipped, not on how big you are.
Sonnet 5.5 cut the rate by a third and the token count went up by about 30 percent.
A third off the per-token rate is not a third off the bill when the same text now costs more tokens. Here is the arithmetic, and the five ways your code can break.
Your AI gateway holds every provider key you have. A 9.9 just landed in LiteLLM.
An AI gateway concentrates every upstream key into one process. That is the point of it, and it is why a privilege escalation there is worse than it looks.
The table your coding agent created does not have row level security on it.
Dashboard-created tables get row level security by default now. API-created tables do not, and API is how your coding agent works.
A 9.5 in next/og. Whether it reaches you depends on one line in your OG route.
The advisory rates it 9.5, but it only fires if your OG image route puts attacker-controlled text into SVG. Here is how to find out which side of that line you are on.
OpenAI and Anthropic both cut prices on 22 September. One of them costs you a refactor.
Two frontier price cuts in one day is a good week for anyone paying a token bill. The migration cost is not evenly distributed, and one of the two prices comes with an expiry hedge.
A package install reads your home directory. This week two of them did it on purpose.
The implant did nothing clever. It read the files your shell reads, in the place your credentials live, and sent them somewhere else. That is the whole attack, and it works.
GitHub is switching off SHA-1 SSH keys. Find out now whether yours is one of them.
The keys at risk are the old ones, on the machines nobody logs into, in the pipelines that have run untouched for three years. Those are also the ones that will fail loudest.
Every third-party script tag is a standing grant to run code on your visitors.
A marketing form, a chat widget, an analytics snippet. Each one is permission for someone else's server to execute whatever it sends, on every page it sits on, forever.
1.8 million Android apps were scanned for hardcoded keys. Here is how to check yours.
Finding secrets in shipped apps is now a cheap, automated pipeline. Anything compiled into an APK, an IPA or a JavaScript bundle should be treated as already published.
OpenAI's Agents API will hold your agent state. What breaks if you ever need to leave.
Two major providers moved into the agent state layer in the same week. A managed harness is a real shortcut, as long as you keep a copy of what it holds.
Meta's Muse agent can now check out at your store. What merchants should change.
Agent purchases are arriving through wallets and single-use cards, not through merchants adopting a new protocol. Many merchants will receive them without choosing to.
What Brevo's SSO incident teaches about multi-tenant SAML and hijacked sending accounts.
One incident, two lessons: why email authentication did not help, and the tenant-scoping mistake anyone shipping SSO can make.
Cloudflare now sorts bots into Search, Training and Agent. What it means for your site and your agent.
The same change lands on two audiences. Site owners can now accidentally block search; agent builders will find more doors closed.
OpenAI has announced ten dated deadlines between 23 October 2026 and 1 April 2027. Here is the calendar.
Ten dated deadlines in six months, every one announced in public. The failure mode is never the notice. Updated 19 October with the entries added since September.
Nvidia bought Hugging Face. Your open-weight fallback is now a vendor relationship.
The commitments say nothing breaks. The structural change is that "we can always self-host" is now a dependency on one vendor rather than on a neutral commons.
The Videos API goes away on 24 September and OpenAI names nothing to move to.
Every other deprecation on OpenAI's page offers a migration target. This one does not, which makes it a different kind of problem.
Whisper shuts down on 26 February. The risk is not the deadline.
Five months is a generous window. Whisper is also typically wired into a background job that fails into a queue rather than into a user's face.
The Assistants API is gone. Your app may not have told you yet.
It shut down on 26 August 2026. The replacement is not a drop-in, and the most common migration mistake changes your model's behaviour without throwing an error.
Row-level security is on by default now. That is not the same as being protected.
Lovable fixed the default. The gap that actually leaks data was never the default, it was the policy, and no platform can write that for you.
Your model comparison is measuring the wrong number.
Every price list is per token. Your bill is per finished piece of work. Those two numbers can rank models in opposite orders.
An agent with production log access is a new identity. Treat it like one.
Always-on agents that read production logs are arriving fast. The access-control question they raise is old and well understood, which is the good news.

Open the tool.

Ten production categories, three minutes, and a ranked list of what to fix first.

Check your own stack