AMD’s Hybrid AI Math: What the 40–60% Savings Model Assumes

Hybrid AI TCO

AMD says a fleet of 500 AI PCs running half their AI work locally can cost 40 to 60% less over three years than doing all of it through cloud APIs. The company built a calculator to show the arithmetic, which is more than most vendors do.

So the number is checkable. The question is what had to be true to produce it.

Run AMD’s Tokenomics Calculator at its defaults and three assumptions carry most of the weight: a daily token volume that only heavy agentic users reach, prompt caching switched off on the cloud side, and a local model whose quality the tool explicitly declines to compare. Change any one and the percentage moves substantially.

None of that makes the model dishonest. AMD discloses its assumptions more thoroughly than the headline suggests, including a frank exclusions list. But a modeled result under stated assumptions is not a property of hybrid AI, and the useful exercise for a buyer is working out which of those assumptions describe their own workload.

Key takeaways
  • The 40–60% figure is a modeled outcome for one scenario: 500 users at the Medium workload tier, 50% hybrid mix, three-year horizon, July 2026 cloud prices. It is not a general property of hybrid deployment.
  • The Medium tier assumes 5.74 million input and 574,000 output tokens per user per day — roughly 200 input tokens per second sustained across an eight-hour day. That is continuous agent activity, not assisted office work.
  • Prompt caching is supported in the calculator but off by default. Enabling it on a repetitive agentic workload can cut cloud input costs dramatically, which is the single biggest threat to the headline result.
  • At a 50% hybrid mix the calculator buys hardware for every user and runs half the tokens locally. The capital cost is full; the local utilisation is not.
  • AMD states plainly that the calculator does not consider performance needs and excludes model-quality differences, software licensing, IT management, migration, taxes, financing and egress.
  • Local throughput is measured on a quantised 35B open model. Comparing its cost against Claude Opus or GPT 5.5 pricing compares two different things.
  • The defensible conclusion: hybrid AI TCO can produce real savings for high-volume, repetitive, quality-tolerant workloads. Whether it does for you is a measurement question, not a percentage you can inherit.

Quick Navigation


What AMD’s Calculator Actually Models

Hybrid AI TCO is the total cost of running AI workloads across a mix of local hardware and cloud APIs, counting hardware, electricity and token charges over a defined period. AMD’s Tokenomics Calculator models three paths — cloud only, local on AMD devices, and a hybrid split — and reports three-year totals, monthly run rates and break-even months.

The inputs it takes:

InputOptions
Team size25, 250, 1,000 or custom
Analysis period1, 3, 4 or 5 years
Workload tierLight, Medium, Heavy or custom, as tokens per user per day
Cloud model mixGemini Pro $2/$12, Claude Sonnet $3/$15, Claude Opus $5/$25, GPT 5.5 $5/$30, or custom, per million tokens
Hybrid mix0% to 100% local
HardwareRyzen AI 9 HX 470, Ryzen AI Max+ 395, Radeon AI PRO R9700, with editable price, throughput, power and hours per day
EnergyElectricity rate and powered days per month
Cloud modifiersPrompt caching, batch discount, regional multiplier, long-context premium, monthly API surcharge

That is a more complete model than the headline implies, and the advanced panel exposes nearly every assumption for editing. Credit where it is due: the caching, batch and long-context controls exist, and most vendor calculators do not have them.

Three mechanics in the fine print matter more than anything on the main panel.

  1. Cloud cost is API tokens only. AMD states there is no seat, subscription or flat monthly price in the cloud figure. For an organisation actually paying per-seat for a coding assistant, this models a different cost structure than the one on their invoice — sometimes higher, sometimes lower.
  2. Hybrid buys hardware for everyone. At 50% mix, all users get a device and half the token volume runs on it. The hardware line is identical to a full local deployment.
  3. Hardware life equals the analysis period. Choose three years and the full device cost lands inside three years, adjusted by an end-of-life value percentage. There is no refresh cycle and no residual beyond that field.

AMD also prices local throughput from a specific measurement: Qwen 3.6 35B A3B at Q4_K_M quantisation, 262,000-token context prefilled to 128,000, sustained throughput under Vulkan llama.cpp. That is a real benchmark configuration, disclosed, and it is the quiet centre of the whole comparison — because it is the model whose cost is being compared against Claude Opus pricing.

The Token Assumption Does Most of the Work

5.74 million input tokens per user per day sounds abstract. Convert it and it stops being abstract.

Our calculations from AMD’s stated tier, using an eight-hour working day and 260 working days.

UnitInput tokensOutput tokens
Per day5,740,000574,000
Per hour (8h day)717,50071,750
Per second sustained~199~20
Per year~1.49bn~149m
Per 500-user fleet, per year~746bn~75bn

Two hundred input tokens per second, sustained, for every second of every working hour. That is not a person typing prompts. That is an agent running continuously, reading a repository, re-sending context and looping through tool calls.

For scale, 5.74 million tokens is in the region of four million words of input per person per day. No human reads or writes that. Only a machine loop produces it.

Three workload profiles, to show the spread. These are illustrative sketches, not measured data.

ProfileWhat it looks likeRough daily input tokens
Light office AIDrafting, summarising, occasional questionsTens of thousands to low hundreds of thousands
Knowledge worker with AI assistanceRegular use, document context, some retrievalHundreds of thousands to low millions
Continuous agentic codingCoding agent with large repo context, long sessionsMillions to tens of millions

AMD’s own Light tier sits at 574K input, a tenth of Medium. The gap between those two tiers is roughly the gap between a typical office deployment and a developer running a coding agent all day.

Why this dominates the result: cloud cost scales linearly with tokens while hardware cost is fixed. At the Medium tier on Claude Sonnet pricing, one user’s input tokens alone come to roughly $4,470 a year, with output adding about $2,240 — call it $6,700 per user per year, or $20,000 over three years. That is our arithmetic at AMD’s stated tier and prices. Against an AI PC costing one to three thousand dollars, the comparison is not close.

Drop to the Light tier and the same arithmetic yields roughly $670 per user per year. Now a $2,000 device takes about three years to pay for itself before counting electricity, management or anything AMD excludes, and the 40–60% headline does not survive.

The lesson is not that AMD picked an unfair number. It is that tier selection, more than hybrid mix, determines the answer. A buyer starting from the default tier rather than their own metered token volume is reading somebody else’s workload.

Where Prompt Caching Changes the Cloud Side

Here is the tension at the centre of the model. The workload that justifies the Medium tier — a continuous agent re-sending large context — is precisely the workload that prompt caching was designed for.

An agent turn is mostly repetition: the same system instructions, the same tool schemas, the same repository or document context, plus a small amount of genuinely new input. Providers price reused prefixes far below fresh input, and the discount is steep. On current frontier pricing, cached reads land near $0.20 per million tokens against input rates of $2 to $5. We worked through what that does to real bills in our analysis of the cache line that decides agentic costs.

AMD’s calculator supports this. The advanced panel has cache write share, cache read share, a write multiplier (1.25x for a five-minute window, 2x for an hour) and a read multiplier. The controls are there and they are correctly specified.

They are also off by default.

What that means in practice: the following is our illustrative arithmetic, not a calculator output. Take the Medium tier’s 5.74M daily input tokens on Claude Sonnet at $3 per million.

Cache-hit rateEffective input cost per user per dayAnnual input cost per user
0% (calculator default)$17.22~$4,477
50%$9.47~$2,462
80%$4.82~$1,253
90%$3.27~$850

At a 90% hit rate, the cloud input bill falls by roughly 80%. Since input dominates this workload’s token volume, that reshapes the entire comparison — and it reshapes it in the direction that hurts the local case.

The honest counterweight: high cache-hit rates are not automatic. They depend on prefix stability, on how the agent structures its context, on cache window duration against request frequency, and on provider implementation. An agent that rebuilds its context every turn gets little benefit and pays cache-write premiums for the privilege. Assuming 90% is as wrong as assuming zero.

So the correct criticism of AMD’s default is narrow and fair: for the specific workload profile that makes the Medium tier plausible, zero caching is the least likely assumption, and it is the one the tool ships with. Any buyer running this calculator should turn caching on and enter their own measured hit rate before reading the savings number.

The Utilisation Problem on the Local Side

The cloud side of this comparison is perfectly elastic: you pay for tokens consumed and nothing else. The local side is the opposite. You buy a device, and whether it earns its price depends entirely on how much work passes through it.

The calculator handles this more carefully than most. It has an “hrs/day running AI” field per device, it sizes capacity from throughput times that window, and it warns when fleet capacity falls short of token demand. Those are the right mechanics.

What the default scenario still implies is worth making explicit. At a 50% hybrid mix, every user gets a device and half the token volume runs on it. The device’s economic output is therefore half what the same hardware could produce — while its cost is unchanged. In utilisation terms, a 50% hybrid mix is a 50%-utilised fleet, at best.

Hybrid AI TCO

The gap between purchased and productive capacity has several sources, and they compound:

  • AI-active hours are not working hours. A device powered for eight hours may run inference for two.
  • One device per user caps sharing. The calculator states a hard ceiling of one device per user. A heavy user cannot borrow a colleague’s idle capacity.
  • Nights and weekends are free capacity nobody uses. Unless batch or background agent work is scheduled into them, two thirds of each day is idle.
  • Provisioning follows the peak. Hardware sized for the busiest user is over-provisioned for everyone else.
  • Adoption is uneven. Fleet-wide deployment assumes fleet-wide usage. Actual AI adoption inside organisations is famously lumpy.

This is the same economics we set out in our analysis of accelerator utilisation: once capacity is bought rather than rented, idle time stops being an efficiency question and becomes a cost-per-unit question. Every hour the device does not run inference raises the effective cost of the hours it does.

The flip side deserves equal weight, because it is the strongest argument for the local case. A device that runs background agents overnight, processes batch jobs on weekends, or serves a developer who genuinely saturates it can reach utilisation a cloud buyer pays dearly for. Local capacity has no marginal token cost. If you can fill it, you should.

The practical test is simple: measure AI-active hours per user, not headcount. A fleet where ten per cent of staff generate ninety per cent of token volume should not be deployed uniformly, and uniform deployment is exactly what the calculator’s hybrid model assumes.

The Missing Variable: Model Quality

AMD says this plainly, twice, and it deserves to be quoted rather than discovered: the calculator does not consider your performance needs, and model inference quality differences are excluded.

That exclusion is doing a lot of work, because of what is on each side of the comparison. The cloud column is priced from Claude Opus, GPT 5.5, Claude Sonnet or Gemini Pro. The local column is throughput-measured on Qwen 3.6 35B A3B at four-bit quantisation. Both are real. They are not the same capability, and the calculator compares their costs without comparing their outputs.

The economic principle is the one that matters here, and it generalises well beyond AMD:

Cost per token is not cost per completed task.

A cheaper model that needs more attempts can cost more in total. Work the chain through:

  • A task that takes two attempts instead of one doubles the token volume for that task
  • A task that needs human review consumes the most expensive resource in the building
  • A wrong output that reaches a downstream system costs far more than either
  • A longer reasoning path to the same answer burns more tokens on cheaper hardware

The arithmetic that follows is unforgiving. If a local model completes 70% of tasks that a frontier model completes at 95%, the effective cost per completed task rises by roughly a third before counting retries — and that is before anyone prices the human time spent on the failures.

None of this says local models are inadequate. Open models at 30B-class sizes have become genuinely capable, and for classification, extraction, summarisation, routing and structured transformation they are often indistinguishable from frontier models at a fraction of the cost. That is a real and growing category of work.

The point is narrower: a TCO model that excludes quality is answering “what does this cost?” rather than “what does this deliver per pound spent?” For the tasks where the two models are equivalent, AMD’s comparison is fair. For the tasks where they are not, the cost column is measuring the wrong thing — and the calculator cannot tell you which tasks are which. Only your own evaluation can.

Why 50/50 Is a Modeling Choice, Not a Strategy

The hybrid mix slider defaults to 50%. It is a reasonable midpoint for a demonstration and a poor description of how workloads actually divide.

Real routing is decided by task characteristics, not by percentages:

Route locallyRoute to cloud
Classification, extraction, taggingComplex multi-step reasoning
Summarisation of routine documentsNovel problem-solving
Privacy-sensitive or regulated dataTasks needing the newest model capabilities
High-volume repetitive transformationBurst workloads above local capacity
Offline or air-gapped workAnything where a wrong answer is expensive
Draft generation before human editingFinal output that ships unreviewed

Run that split against a real workload and the local share lands wherever it lands — 15%, 40%, 80%. The number is an output of the routing policy, not an input to it. An organisation doing mostly structured data work might route 80% locally. One doing mostly open-ended analysis might manage 20%.

This also explains why the calculator’s “max potential savings at 100% hybrid” figure should be read carefully. Full local means no access to frontier capability at all, which is a product decision rather than a cost optimisation.

What AMD’s Model Gets Right

Credit where it is earned, because the tool is better than the headline it generated.

  • It discloses its assumptions. Token tiers, model prices with a date, electricity rate, throughput test configuration, device specs — all visible and editable.
  • It publishes an exclusions list. Model quality, licensing, IT management, migration, taxes, financing, egress, volume discounts. Most vendor calculators omit this entirely.
  • It includes the modifiers that matter. Caching, batch discounts, long-context premiums and regional multipliers are all present, even if off by default.
  • It flags capacity shortfalls. If the fleet cannot serve the token demand, it says so and routes the overflow to cloud.
  • It states its own limitation on performance. “This calculator does not consider your performance needs” is an unusually honest sentence to put in a sales tool.
  • The underlying economics are sound. For sufficiently high, sufficiently repetitive token volumes, local inference genuinely is cheaper. That is not marketing; it is arithmetic.

What It Leaves Out That Could Matter

The exclusions are disclosed, but not all of them are equally consequential. Ranked by how much they could move a real result:

ExclusionWhy it mattersDirection
Model qualityChanges cost per completed task, not cost per tokenUsually favours cloud
Caching, when left offOverstates cloud input costs on repetitive workloadsFavours local as shipped
IT management and supportManaging local inference across a fleet is real workFavours cloud
Software licensingLocal serving stacks, management tooling, model licencesFavours cloud
Migration and deploymentOne-off but substantial for a 500-device rolloutFavours cloud
Hardware refreshLife is set to the analysis period; a 5-year window assumes 5-year devicesFavours local as shipped
Volume discountsEnterprise cloud agreements rarely pay list priceFavours cloud
Seat and subscription pricingMany organisations pay per seat, not per tokenDepends
Utilisation below 100%Capacity bought is not capacity usedFavours cloud

Notice the pattern. Most of the exclusions push in the same direction, and it is not the direction that makes local hardware look better.

A Better Hybrid AI TCO Calculation

Ten steps. The first four are measurement, and skipping them is how buyers end up with somebody else’s answer.

  1. Meter your actual token consumption. Pull it from provider dashboards or your gateway logs, not from headcount multiplied by an assumption.
  2. Separate input from output. They price differently and they scale differently. Input dominates agentic work; output dominates reasoning work.
  3. Measure your cache-hit rate. Most providers report cached-token usage. This single number may move your cloud bill more than any hardware decision.
  4. Measure AI-active hours per user, not working hours, and look at the distribution rather than the average.
  5. Classify tasks by quality requirement. Which actually need a frontier model? Test, do not assume.
  6. Calculate realistic local utilisation. Include nights, weekends and the users who barely touch AI.
  7. Add the omitted costs. Management, support, licensing, migration, refresh.
  8. Compute cost per completed task for both paths, including retries and human review.
  9. Test several routing mixes — 0%, 25%, 50%, 75%, 100% — rather than accepting the default.
  10. Run sensitivity on your two or three largest variables and see how wide the range gets.

Sensitivity: Which Assumptions Move the Answer

Directional, based on the model’s structure rather than on outputs we cannot reproduce exactly.

If this changesLocal and hybrid TCOWhy
Token volume risesImproves sharplyCloud scales linearly, hardware does not
Token volume fallsDeteriorates sharplyFixed hardware cost spread over less work
Cache-hit rate risesDeterioratesCloud input cost falls, sometimes by 80%+
Local utilisation risesImprovesSame capital, more output
Cloud API prices fallDeterioratesThe savings baseline shrinks
Electricity price risesDeteriorates mildlyPower is a small share at these volumes
Hardware price fallsImprovesLower capital to amortise
Quality requirements riseDeterioratesMore work must route to cloud regardless of cost
Refresh cycle shortensDeterioratesCapital amortised over fewer years
Hybrid mix rises toward 100%Improves on cost, narrows on capabilityFewer tokens billed, less frontier access

The two largest levers are token volume and cache-hit rate, and they pull in opposite directions on the same workload. That is the central tension in AMD’s model: the workloads with enough tokens to justify local hardware are the workloads most likely to benefit from caching.

FAQ

What is hybrid AI TCO?

The total cost of running AI workloads across both local hardware and cloud APIs over a defined period, counting hardware purchase, electricity and token charges. It differs from cloud-only TCO because part of the cost becomes fixed capital rather than metered usage.

Can hybrid AI really reduce AI costs by 40–60%?

AMD’s calculator produces that result for a specific scenario: 500 users at 5.74 million input and 574,000 output tokens per user per day, a 50% local mix, a three-year horizon and July 2026 cloud prices with prompt caching off. Under those assumptions the arithmetic holds. Whether it holds for a given organisation depends on whether its workload resembles that profile.

Is local AI cheaper than cloud AI?

For high-volume, repetitive, quality-tolerant workloads on well-utilised hardware, frequently yes. For light or intermittent usage, usually no, because fixed hardware cost is spread across too little work. The crossover point is set by token volume, utilisation and the cache-hit rate on the cloud side.

How does prompt caching affect hybrid AI TCO?

Significantly, and against the local case. Cached input tokens are priced far below fresh ones, so a repetitive agentic workload with a high hit rate can cut its cloud input bill by most of its value. AMD’s calculator supports caching but ships with it disabled, which prices every input token at full rate.

How much does AI PC utilisation affect TCO?

Proportionally. A device used half as much has roughly double the effective cost per unit of work, since the purchase price does not change. At a 50% hybrid mix the calculator buys hardware for every user and runs half their tokens locally, which is a 50%-utilised fleet by construction.

What costs are missing from AMD’s AI cost calculator?

AMD lists them: model inference quality differences, software licensing, IT management, migration effort, taxes, financing fees, network and egress costs unless entered manually, and provider-specific volume discounts. Most of these, if included, would favour the cloud side.

Is a 50/50 local and cloud split optimal?

It is a default, not an optimum. The right mix follows from task routing — which work genuinely needs frontier capability and which does not — and lands anywhere from 15% to 80% local depending on the workload.

How should businesses calculate AI TCO?

Start by metering actual token consumption split into input and output, measure the cache-hit rate and AI-active hours per user, classify which tasks need frontier models, then compute cost per completed task for several routing mixes rather than cost per token for one.

Does AMD’s calculator compare equivalent models?

No, and it says so. Local throughput is measured on Qwen 3.6 35B A3B at four-bit quantisation, while cloud costs are priced from Claude, GPT and Gemini models. AMD states explicitly that the tool does not consider performance needs.


Keep reading

AGI vs superintelligence

AGI vs Superintelligence: A New Name Isn’t a New Intelligence

Facts checked against official documents and reporting on 18 November 2026. On 29 September, the White House told federal agencies to stop writing “artificial intelligence” …
AI Coding Agent

AI Coding Agents Are Getting Expensive. Who’s Paying for the Tokens?

Pricing checked on official vendor pages on 17 November 2026. All USD. Cost scenarios are illustrative and labelled as such. On 28 October, TechCrunch published …
Model Weights

Verify Model Weights: 7 Checks Before You Download

Checked against the burner22/numbat repository and its discussions, Hugging Face and PyTorch documentation, and Moonshot AI’s announcement on 2 November 2026. On 1 November, a …
Agentic AI Statistics

30 Agentic AI Statistics for 2026: Adoption, Spending and Risk

Last updated: 15 November 2026. This page is updated monthly; each figure keeps its original publication date. Agent traffic at one healthcare booking platform rose …

Anthropic’s $518B Compute Commitment: The Obligation Behind It

Anthropic compute commitments

The number everyone repeated last week was $518 billion. The number that actually matters is 80%.

That is the share of Anthropic’s future compute and infrastructure commitments described as non-cancelable or payable regardless of usage, according to a confidential IPO prospectus reviewed by Reuters. Strip out the second number and the first is just a large purchase order from a company that needs a lot of chips. Keep it, and the commitment changes category: from a plan to spend into an obligation to pay.

Those are different things, and the difference is the whole story.

Having access to compute solves what has been the binding constraint on frontier AI development for three years. Being contractually obligated to pay for compute, on a schedule set in advance, converts a supply problem into a utilisation problem — and utilisation is something a company controls only partly, because it depends on customers showing up on the timetable the contracts assumed.

Key takeaways
  • A confidential IPO prospectus reviewed by Reuters shows Anthropic committed to at least $518 billion over roughly a decade across six infrastructure partners, with about 80% non-cancelable or payable regardless of usage.
  • The largest reported components: approximately $161.2bn in Broadcom-related equipment leases, $111.1bn with Google, $110bn with Amazon, $31.4bn with Microsoft, about $84.5bn for Nvidia-based capacity and about $20bn with AMD.
  • The commitments are not uniform. Reporting describes shortfall payments for Google and Amazon, cancellation only on uncured material breach for Microsoft, and leases cancelable only on default for Broadcom. One percentage covers four different contract types.
  • Anthropic spent $7.33 billion on compute and infrastructure in 2025 — more than half of $12.65 billion in total operating expenses — against revenue of $4.59 billion and $20.28 billion of cash and short-term investments.
  • Broadcom has reportedly agreed to lend up to $42 billion through a convertible note that could fund about a third of a five-year, $125.2 billion TPU lease, making one company supplier, lessor and lender at once.
  • Long-term commitments buy capacity certainty in a market where capacity has been the constraint. The cost of that certainty is financial rigidity if demand arrives later or smaller than contracted.
  • The exact terms remain unverifiable while the prospectus is confidential. That uncertainty is part of the story, not a gap in it.

Quick Navigation


What the $518 Billion Actually Represents

Anthropic’s compute commitments are contractual obligations to buy cloud services, computing capacity and AI infrastructure from named partners over a defined period. They are not a debt balance, not a cash payment, and not a single contract.

The reported breakdown, all from the prospectus as described by Reuters:

PartnerReported amountWhat it coversPeriod
Broadcom~$161.2bnEquipment lease obligations, largely non-cancelableIncludes a five-year TPU capacity lease of $125.2bn
Google~$111.1bnInfrastructure servicesApril 2026 – July 2033
Amazon$110bnInfrastructure servicesMay 2026 – April 2036
Nvidia-based capacity~$84.5bnCompute capacityThrough 2029
Microsoft$31.4bnInfrastructure servicesNovember 2026 – May 2033
AMD~$20bnAI computeNot reported

Those six figures sum to roughly $518 billion, which matches the headline. Note the composition: the single largest line is not a cloud contract at all but equipment leases, which behave differently from service agreements in both accounting and cancellation terms.

Three distinctions matter before anyone compares this to a balance sheet.

  1. Commitment is not cash. A ten-year obligation is paid over ten years. Spread evenly — which it will not be, since these ramp — $518 billion is roughly $50 billion a year, against the $7.33 billion Anthropic actually spent on compute and infrastructure in 2025.
  2. Commitment is not debt. It does not sit on the balance sheet as borrowing, though lease obligations are capitalised under current accounting. It is a future purchase obligation, disclosed in the commitments note rather than counted as leverage.
  3. The period is long and the ramp is steep. Contracts running to 2033, 2036 and beyond assume a company much larger than today’s. Reuters reported an annualised revenue run rate above $65 billion by the end of July and earlier reporting put Anthropic’s own 2028 revenue projection at roughly $190–200 billion. Those projections are the company’s, not forecasts anyone has validated.

The useful comparison is not $518 billion against $4.59 billion of 2025 revenue — that ratio is dramatic and tells you almost nothing. It is annual contracted spend against annual revenue in each future year, which is where the question of whether the commitments are comfortable or binding actually gets settled.

The Obligation Hidden Inside the Headline

The 80% figure is a summary statistic covering several different contractual mechanisms, and the mechanisms matter more than the average.

From the reporting:

  • Google and Amazon: Anthropic must pay the difference if its actual spending falls short of the minimum commitment. This is a shortfall provision — you can buy less, but you pay the same.
  • Microsoft: the agreement is described as non-cancelable through May 2033 absent an uncured material breach.
  • Broadcom: the equipment leases are largely non-cancelable except after default, and certain payment or performance defaults could make a substantial portion of the lease obligations immediately payable.
  • The Nvidia-based capacity arrangement: described as giving Anthropic more room to retreat than the others.

So “80% non-cancelable” bundles a minimum-volume commitment, a breach-only termination clause, a lease default provision and at least one more flexible arrangement under a single number.

That distinction has a practical consequence. A shortfall provision caps your downside at the committed spend — you lose the optionality, not more. A lease acceleration clause is different in kind: default can pull future payments forward into the present, which turns a long-dated obligation into an immediate one at exactly the moment a company would least be able to meet it.

The prospectus itself flags this. Reporting describes a warning that certain defaults could accelerate a substantial portion of lease obligations while also restricting Anthropic’s ability to draw on the $42 billion Broadcom facility to cover them. A financing facility that becomes unavailable precisely when it is needed is a standard credit structure and a real risk factor.

What cannot be verified: the actual contract language, the ramp schedules, the definitions of “minimum commitment”, any price-adjustment or technology-refresh provisions, and whether the agreements contain renegotiation mechanisms that reporting has not described. The prospectus remains confidential. Anyone asserting precision about these terms is working from the same journalism everyone else is.

Take-or-Pay Changes the Utilisation Equation

Take-or-pay means the buyer pays for a contracted quantity whether or not it takes delivery. The structure comes from energy and shipping, where suppliers build expensive dedicated capacity and need revenue certainty to justify it. It is appearing in AI infrastructure for exactly the same reason: someone has to fund the data centre before the demand shows up.

For the buyer, take-or-pay converts a variable cost into a fixed one. That is the entire economic consequence, and it cuts both ways.

Anthropic compute commitments

Here is what it does to the unit economics. The following is a hypothetical illustration, not a description of any Anthropic contract or price.

Suppose a company commits to $10 billion of compute capacity for a year under a take-or-pay arrangement.

ScenarioCapacity usedCost incurredEffective cost per unit used
Demand as planned100%$10bn1.0x
Demand arrives late70%$10bn1.43x
Demand disappoints50%$10bn2.0x
Usage-based contract, same shortfall50%$5bn1.0x

Under a usage-based contract, a demand shortfall is a revenue problem. Under take-or-pay, the same shortfall is a revenue problem and a margin problem, because the denominator shrinks while the numerator does not.

This is why utilisation stops being an engineering concern and becomes a financial one. When capacity is elastic, running accelerators at 60% is an optimisation question — you are leaving efficiency on the table. When capacity is committed and paid for regardless, 60% utilisation means 40% of a contracted dollar produced nothing, and that gap flows directly into gross margin. We worked through the mechanics of where idle capacity comes from in our analysis of accelerator utilisation, and every source of idle time in that piece becomes more expensive under this contract structure.

The pressure this creates is directional and predictable. A company with committed capacity has strong incentives to fill it: push inference volume, expand enterprise contracts, launch workloads that consume compute, price aggressively to drive usage. None of those are irrational responses. They are what the contract structure rewards.

The honest caveat: none of this establishes that Anthropic is underutilising anything. Its reported run-rate growth suggests demand has been the easier half of the equation so far. The point is structural — take-or-pay raises the cost of being wrong about timing, for anyone who signs it.

Why Compute Certainty Can Be Worth Paying For

It would be easy to write this as a cautionary tale. That reading ignores why a competent management team signs these contracts, and the reasons are good ones.

For the past three years, the binding constraint on frontier AI has been access to compute, not demand for it. Accelerators have been allocated rather than sold. Memory has been contracted years ahead. Data-centre power has become a multi-year procurement problem. In that environment, a company without secured capacity does not get to choose how fast it grows.

What a long-term commitment buys:

  • Capacity that exists. Suppliers build against contracted demand. An uncommitted buyer competes for whatever is left.
  • Price certainty in a rising market. If compute costs rise, a fixed contract becomes an asset. The hedge runs both directions.
  • Planning horizon. Model development schedules depend on knowing what hardware will be available and when.
  • Priority on new generations. Being a large committed customer affects allocation when the next accelerator ships short.
  • Scale economics. Volume commitments buy better unit pricing than spot purchasing.

There is also a competitive dimension. If frontier capability tracks compute, then capacity secured is capability secured, and capacity your competitor cannot buy is capability they cannot build. Commitments of this size take supply off the market.

The trade-off is clean enough to state in one sentence: Anthropic has exchanged financial flexibility for compute certainty. Whether that was a good trade depends entirely on which constraint turns out to bind — and that will not be clear for years.

The Partners Behind the Anthropic Compute Commitments

The prospectus, as reported, identifies Amazon, Google and Microsoft as simultaneously investors, customers, cloud providers, distributors and competitors. That is not a conflict the company is hiding; it is one it is disclosing as a risk.

Each role pulls differently. As an investor, a partner benefits from Anthropic’s success. As a supplier, it benefits from Anthropic’s spending. As a distributor, it takes a margin on Anthropic’s models. As a competitor, it builds models that compete with them. The same counterparty occupies all four positions at once.

The Broadcom structure is the sharpest version. Reuters reported on October 1 that Broadcom agreed to lend Anthropic up to $42 billion through a convertible note that could fund roughly a third of the five-year, $125.2 billion TPU compute lease, with Broadcom permitted to designate a financing partner and the debt convertible into Anthropic equity. Anthropic is expected to become the largest customer in Broadcom’s chip design business next year.

So one company supplies the hardware, leases it, lends the money to pay for the lease, and may end up holding equity. The prospectus reportedly flags potential conflicts of interest directly, warning that Broadcom’s decisions on pricing and hardware could affect Anthropic’s ability to procure enough computing infrastructure.

Broadcom’s own public filings describe a structure of this shape without naming a customer. Its 10-Q for the quarter ended August 2, 2026 discloses an “AI XPV platform” launched in June 2026 with an initial $35 billion tranche led by a financial partner, enabling deployment of more than a gigawatt of compute infrastructure for a customer, with Broadcom providing a backstop on that customer’s five-year lease obligations and maximum potential liability of roughly $29 billion. Broadcom does not identify the customer, and no public source establishes that these are the same arrangement.

The economic observation, offered as analysis: vendor financing linked to future demand for the vendor’s own product is not new — it is how equipment vendors have supported large customers for decades, and Nvidia has done versions of it recently. What is different here is the concentration. The same relationship carries supply risk, credit risk and equity exposure, and a stress event in one leg propagates to the others. Rothschild’s Robert Leitao put the market’s version of this concern plainly, questioning whether the revenue base can keep pace with the scale of financing that has been arranged.

Leases, Depreciation and the Technology Risk in a Long Contract

Three concepts get conflated whenever AI infrastructure costs come up, and they are related but not interchangeable.

ConceptWhat it isWhere it shows up
Contractual commitmentA promise to buy capacity or services in future periodsCommitments note; lease liabilities on the balance sheet
DepreciationAllocation of an owned asset’s cost across its useful lifeOperating expenses, for hardware you own
Operating expenseCash cost of running the business in a periodIncome statement

For a company leasing capacity rather than buying accelerators, depreciation largely sits with whoever owns the hardware — but the economics do not disappear. They arrive embedded in the lease rate, because the lessor priced in the asset’s expected useful life when setting it.

That is where the technology risk lives. A five-year lease on a specific accelerator generation assumes that generation stays economically competitive for five years. Hardware improves on a roughly annual cadence now, and what ends an accelerator’s economic life is usually not failure but the arrival of something that does more per watt and holds more memory — the pattern we examined in our piece on AI accelerator depreciation.

Follow that through. If performance per dollar improves sharply in 2029, a lease signed in 2027 at 2027 rates becomes expensive relative to what the market then offers. The capacity still works. It is simply worth less than it costs, and the contract does not care.

This is the structural reason long compute contracts carry risk that long property leases do not. A building is still a building in year seven. An accelerator generation may be two or three generations behind by then, and the memory capacity that made it viable for a given model size may no longer fit the models being served.

The counterweight, in fairness: the TPU capacity in question reportedly starts coming online in 2027 and the lease runs five years from there, which is roughly in line with how hyperscalers depreciate their own fleets. These are not exotic terms. They are standard terms applied at an unusual scale, and the scale is what makes the technology-refresh assumption consequential.

What Could Make the Anthropic Compute Commitments Work

The bull case is not complicated, and it is mostly about one variable arriving on schedule.

If enterprise AI demand grows as projected, contracted capacity gets consumed, and the commitments look like foresight rather than exposure. Reuters reported an annualised revenue run rate above $65 billion by the end of July, against $4.59 billion for full-year 2025. A company growing at that rate does not have a utilisation problem; it has a capacity problem, which is what the contracts solve.

Several things reinforce that outcome:

  • Compute stays scarce. If accelerators, memory and power remain constrained, fixed-price contracts signed earlier look cheap later.
  • Agentic and reasoning workloads consume more per task. Demand per customer rises without needing more customers.
  • Enterprise contracts lengthen. Multi-year customer commitments on the revenue side offset multi-year obligations on the cost side, which is the natural hedge.
  • Scale lowers unit cost. Large committed volumes buy better pricing than anyone purchasing on demand.

The cleanest version of the bull case: the commitments convert an unpredictable supply risk into a predictable cost, in a business where supply has been the thing that limited growth.

What Could Make Them Expensive

The bear case does not require AI demand to collapse. It only requires the economics of compute to move faster than the contracts.

  • Efficiency improves faster than demand grows. Better quantisation, more efficient architectures and cheaper serving reduce compute per unit of output. The same revenue then needs less capacity, and contracted capacity goes unused.
  • Performance per dollar jumps. A new accelerator generation that is substantially more efficient makes older contracted capacity expensive relative to what is available, exactly as described above.
  • Price competition compresses margins. If model API prices keep falling — and they have fallen steeply — revenue per unit of compute falls with them, while the cost per unit is fixed by contract.
  • Demand arrives late rather than never. This is the underrated scenario. Contracts ramp on a schedule. If adoption lands two years behind the schedule, the capacity is paid for during the gap.
  • Customer concentration bites. Reporting indicates two customers supplied nearly a quarter of 2025 revenue. Concentrated revenue against distributed fixed obligations is an asymmetry worth noting.
  • Capital markets tighten. Much of this structure assumes continued access to financing, including the Broadcom facility. The prospectus reportedly warns that certain defaults could both accelerate lease obligations and restrict access to that facility.

None of these is a prediction. They are the variables that would determine whether a commitment of this size reads as strategic or as overextended, and they are the ones worth tracking.

The Valuation Connection

A valuation above $2 trillion — against a self-estimated $965 billion in May — is a statement about future cash flows. Those cash flows depend on revenue growth, gross margin, capital intensity and how much compute each dollar of revenue requires.

What the $518 billion does is make one of those variables visible. Infrastructure spending is normally a forecast assumption that investors argue about. Here, a large portion of it is contracted, dated and disclosed. The spending is no longer a question mark; what remains uncertain is the revenue that has to arrive alongside it.

This is not an argument that the valuation is right or wrong, and this article offers no view on that. The structural observation is narrower: when costs are contractually fixed and revenues are not, the equity absorbs the variance. That is true of any capital-intensive business, and it is unusual to see it at this scale in a company five years old.

The 2025 figures give a sense of the starting point. Revenue of $4.59 billion, operating loss of $8.06 billion, compute and infrastructure spending of $7.33 billion within $12.65 billion of total operating expenses, and $20.28 billion of cash and short-term investments at year end. The headline $42 billion net loss is mostly a non-cash charge of roughly $34 billion tied to the rising estimated value of convertible financing instruments — a number that grows precisely because the company’s valuation grew, and which tells you nothing about operations.

A Note on Governance

Briefly, because it is a separate question from the economics.

Reporting describes a newly created “Founder LLC” comprising Anthropic’s seven co-founders, holding a single Class F share carrying 50.1% of voting power on certain matters including some director elections. The founders direct that share by majority vote. The structure is not permanent: a founder who leaves, dies, sells below a threshold or is removed for cause drops out, and the super-voting class begins to sunset once few enough founders remain.

That is the factual position. Dual-class structures are common in technology listings, and whether this one is appropriate is a judgement for investors rather than for this article. The relevant connection to the rest of the piece is simply that financial scale and governance structure are independent: the commitments would have the same economics under any voting arrangement.

What AI Infrastructure Buyers Should Take From This

Most organisations will never sign a contract with nine zeros. The structural lessons scale down anyway.

  • Know which of your compute spend is committed. Reserved instances, savings plans, minimum commitments and capacity reservations all behave like small take-or-pay contracts. The percentage of your bill that is committed is the percentage where utilisation becomes a margin issue.
  • Model the shortfall, not just the spend. The question is not what the commitment costs. It is what it costs if you use 60% of it.
  • Match contract duration to demand visibility. A three-year commitment against six months of demand visibility is a bet, however good the discount.
  • Price the flexibility you are selling. Vendors discount committed volume because certainty is worth something to them. Work out what it is worth to you before trading it away.
  • Watch counterparty concentration. If the same vendor supplies, finances and distributes, your exposure to them is larger than any single contract suggests.
  • Treat utilisation as a financial metric. Once capacity is committed, the operations team’s efficiency work shows up in gross margin. That changes who should be in the room when it is discussed.

The question this story leaves open is a genuine one. Does committing $518 billion remove Anthropic’s biggest risk — not being able to get compute — or substitute a different one, being obligated to pay for compute whether or not demand arrives on schedule? The answer is that it does both, and which dominates depends on variables that will take years to resolve: utilisation, revenue growth, contract terms nobody outside has seen, compute prices, model efficiency and how quickly hardware generations turn over.

Anyone offering a confident verdict today is working from the same confidential document nobody has read.

FAQ

What are Anthropic’s compute commitments?

Contractual obligations to purchase cloud services, computing capacity and AI infrastructure from named partners over fixed periods. According to a confidential IPO prospectus reviewed by Reuters, they total at least $518 billion over roughly a decade across six partners.

What is the $518 billion figure?

The sum of Anthropic’s disclosed infrastructure commitments: approximately $161.2bn in Broadcom-related equipment leases, $111.1bn with Google, $110bn with Amazon, about $84.5bn for Nvidia-based capacity, $31.4bn with Microsoft and about $20bn with AMD. It is a multi-year obligation, not a current debt or a cash payment.

What does take-or-pay mean here?

That the buyer pays for contracted capacity whether or not it is used. Reuters reported that about 80% of Anthropic’s commitments are non-cancelable or payable regardless of usage, though the specific mechanisms differ by counterparty.

What happens if Anthropic does not use the contracted compute?

Based on the reported terms, it would still owe the money in most cases — through shortfall payments to Google and Amazon, or through lease obligations to Broadcom. The exact provisions cannot be verified while the prospectus stays confidential.

Why would a company commit so much compute?

Because compute availability, not demand, has been the binding constraint on frontier AI development. Long-term commitments secure capacity, lock in pricing, support planning and give priority on new hardware generations — at the cost of financial flexibility.

Who provides Anthropic’s compute?

Six partners per the reported prospectus: Broadcom, Google, Amazon, a provider of Nvidia-based capacity, Microsoft and AMD. Amazon, Google and Microsoft are described as simultaneously investors, customers, cloud providers, distributors and competitors.

What is the Broadcom financing arrangement?

Reuters reported that Broadcom agreed to lend Anthropic up to $42 billion via a convertible note that could fund roughly a third of a five-year, $125.2 billion TPU compute lease. Broadcom may designate a financing partner, and the debt could convert into Anthropic equity.

How do compute commitments affect AI company economics?

They convert a variable cost into a fixed one. That reduces supply risk and increases operating leverage: if capacity is fully used, unit economics improve with scale; if it is not, the unused portion still has to be paid for and effective cost per unit rises.


Keep reading

AGI vs superintelligence

AGI vs Superintelligence: A New Name Isn’t a New Intelligence

Facts checked against official documents and reporting on 18 November 2026. On 29 September, the White House told federal agencies to stop writing “artificial intelligence” …
AI Coding Agent

AI Coding Agents Are Getting Expensive. Who’s Paying for the Tokens?

Pricing checked on official vendor pages on 17 November 2026. All USD. Cost scenarios are illustrative and labelled as such. On 28 October, TechCrunch published …
Model Weights

Verify Model Weights: 7 Checks Before You Download

Checked against the burner22/numbat repository and its discussions, Hugging Face and PyTorch documentation, and Moonshot AI’s announcement on 2 November 2026. On 1 November, a …
Agentic AI Statistics

30 Agentic AI Statistics for 2026: Adoption, Spending and Risk

Last updated: 15 November 2026. This page is updated monthly; each figure keeps its original publication date. Agent traffic at one healthcare booking platform rose …