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 …

AI Accelerator Depreciation: The Assumption Nobody Audits

AI accelerator depreciation

An A100 with 80GB of HBM2e still computes exactly as well in 2026 as it did when it was installed. Nothing has degraded. It passes every diagnostic.

It is also increasingly hard to justify running, and the reason has almost nothing to do with its arithmetic throughput. A model that fits comfortably in 141GB on an H200 must be sharded across two A100s, halving effective utilisation and doubling the interconnect traffic. A context window that one newer accelerator holds in its KV cache does not fit at all.

The hardware works. The workload moved.

That gap — between an accelerator that functions and one that earns — is the subject of this article, and it sits directly on top of an accounting assumption that carries tens of billions of dollars of reported profit across the industry. AI accelerator depreciation is the allocation of an accelerator’s cost across its estimated useful life, and the estimate is exactly that: an estimate, chosen by management, disclosed in a sentence, and rarely examined against the physics of the workloads the hardware actually has to serve.

Key takeaways
  • AI accelerator depreciation is an accounting allocation, not a measurement of hardware lifespan. The disclosed figure is an estimate of economic benefit, and the hyperscalers apply it to “servers and network equipment” as a category rather than to accelerators specifically.
  • Four different lifetimes hide inside one number: physical, accounting, economic and competitive. They rarely coincide, and the shortest one determines when replacement actually happens.
  • The hyperscalers no longer agree. Microsoft and Alphabet moved servers to six years in 2022–23 and have held there; Amazon shortened a subset back to five effective January 2025, citing the pace of AI development; Meta extended to 5.5 years the same month.
  • Changing a four-year assumption to three raises annual depreciation on the same asset by roughly a third, which flows straight into cost per accelerator-hour and cost per token.
  • Memory capacity is the underexamined obsolescence driver. Accelerator HBM has gone from 40–80GB on A100 to 141GB on H200, 192GB on B200 and up to 288GB on B300-class parts, while models, context windows and KV caches grew to match.
  • An accelerator becomes economically obsolete when the workload outgrows its memory envelope, not when it stops computing. We call this obsolescence by memory footprint — an analytical framing, not an accounting term.

Quick Navigation


AI Accelerator Depreciation Starts With an Accounting Assumption

Depreciation spreads the cost of a long-lived asset across the periods that benefit from it. For an accelerator bought outright, the mechanics are simple:

Annual depreciation = (asset cost − salvage value) ÷ estimated useful life

The cost is known. Salvage value for accelerators is usually assumed to be small or zero. Useful life is the judgement call, and it is the only input management chooses.

That choice does three things at once. It sets reported operating income, because depreciation is an expense. It sets the capital recovery burden built into internal transfer pricing and cloud rate cards. And it signals to investors how long management believes the hardware will produce economic benefit.

One structural point deserves emphasis before any of the numbers below. None of the major operators discloses a useful life specifically for AI accelerators. They disclose useful lives for categories such as “servers and network equipment” or “technical infrastructure”, which bundle accelerators with CPUs, memory, storage, chassis and switches. Treating a disclosed six-year server life as a statement about GPU lifespan is an inference, not a reading of the filing.


AI Accelerator Depreciation Hides Four Different Lifetimes

The same physical accelerator has four expiry dates, and they are set by different forces.

LifetimeWhat ends itWho decides
PhysicalComponent failure — HBM faults, VRM degradation, thermal damagePhysics and operating conditions
AccountingThe end of the disclosed useful lifeManagement estimate, audited for reasonableness
EconomicThe point at which running it costs more than the value it producesPower prices, utilisation, alternatives
CompetitiveThe point at which it cannot serve the workload at acceptable throughput, latency or memoryModel architecture and customer requirements

Physical life is usually the longest. Well-cooled data-centre hardware runs for many years, and the secondary market for previous-generation accelerators exists precisely because they still work.

Accounting life sits in the middle by construction, since auditors want an estimate that reflects expected economic benefit rather than either extreme.

Economic life turns on operating cost against output. An older accelerator drawing 400W to produce a fraction of what a newer part produces at 700W can lose on performance per watt badly enough that electricity alone justifies replacement, before any capital consideration.

Competitive life is usually the shortest, and it is the one nobody discloses. It ends when the accelerator can no longer hold what the workload needs it to hold.

The practical consequence: a fleet can be fully depreciated and still valuable, or carry substantial book value while being commercially unusable for current workloads. Neither situation is visible from the depreciation schedule.


What Major Operators Disclose About AI Accelerator Depreciation

Between 2022 and 2024 the major operators moved in one direction. In January 2025 they stopped agreeing.

CompanyDisclosed changeStated scopeReported effect
Microsoft4 → 6 years, effective FY2023 (July 2022)Servers and network equipment~$3.7bn lower depreciation, ~$3.0bn higher net income in FY23
AlphabetServers 4 → 6 years; certain network equipment 5 → 6, effective January 2023Servers and certain network equipment~$3.9bn lower 2023 depreciation, ~$3.0bn higher net income
Amazon5 → 6 years, effective January 2024Servers~$3.2bn lower 2024 depreciation, ~$2.5bn higher net income
Amazon6 → 5 years, effective January 2025A subset of servers and networking equipmentRoughly $0.7bn lower operating income, with accelerated depreciation on early retirements
MetaMost assets → 5.5 years, effective January 2025Servers and network assets~$2.9bn lower 2025 depreciation, ~$2.6bn higher net income
OracleExtended to 5 years, 2023Servers and related equipmentDisclosed in that year’s filing

Four points about how to read that table.

  1. The direction reversed, once. Amazon is the only operator in the group to have shortened, and its stated reason is specific: the increased pace of technology development, particularly in artificial intelligence and machine learning. That is a company statement about AI hardware turnover, from the operator with the largest cloud footprint.
  2. The categories are not comparable. Microsoft’s disclosure covers servers and network equipment together as a range of two to six years. Alphabet separates servers from certain network equipment. Amazon’s January 2025 change applies to a subset it does not size. Lining these up in one column is convenient and slightly misleading, which is why the scope column is there.
  3. Sources disagree on some figures. Alphabet’s 2023 effect appears in coverage as both a ~$3.9bn actual reduction and a ~$3.4bn estimate made at the time of the change. Those are different things — an estimate disclosed in the 2022 10-K versus the outcome reported later — and the difference is a good illustration of why the primary filing matters more than the summary.
  4. Nothing here is about GPUs. No line in that table tells you how long a specific accelerator generation remains useful. It tells you what period management chose to spread the cost over for a category of equipment.

The analyst commentary around these disclosures has been vocal, and it should be labelled as commentary. In November 2025, investor Michael Burry argued publicly that hyperscalers were overstating earnings by extending useful lives beyond what two-to-three-year product cycles justify, putting the understatement at $176bn across 2026–2028. That is an outside estimate built on assumptions about true economic life, not a company disclosure, and it depends entirely on whether the accelerators concerned really do lose their economic value that fast.

Management has not been entirely silent on the tension. Satya Nadella has described not wanting to be “stuck with four or five years of depreciation on one generation” when a supplier’s migration pace increases — an acknowledgement that generational turnover, not hardware failure, is the pressure on useful life.


Why AI Accelerator Depreciation at Three Years Differs From Four

The arithmetic is simple enough to do in your head, which is part of why the assumption escapes scrutiny. The consequences are not simple at all.

The figures below are illustrative assumptions chosen for round numbers, not vendor prices or disclosed costs.

Take an accelerator server costing $300,000, assume zero salvage value, and assume 8,760 hours in a year at 100% availability.

Useful lifeAnnual depreciationDepreciation per hourChange vs 6 years
6 years$50,000$5.71—
5 years$60,000$6.85+20%
4 years$75,000$8.56+50%
3 years$100,000$11.42+100%

Moving from four years to three raises the hourly capital recovery burden by a third. Moving from six to three doubles it. No hardware changed, no electricity was consumed differently, and no workload got slower.

Now push it through to the number that matters operationally. Depreciation is only part of the cost of an accelerator-hour, but it is the largest part for recently purchased hardware. Assume power, cooling, networking and facility costs add $4.00 per hour:

Useful lifeDepreciation/hrOther costs/hrTotal/hrAt 60% utilisation, cost per useful hour
6 years$5.71$4.00$9.71$16.18
4 years$8.56$4.00$12.56$20.93
3 years$11.42$4.00$15.42$25.70

The last column is the one to sit with. Two variables — an accounting estimate and a utilisation rate — move the cost of an hour of useful compute by roughly 60% between the top and bottom rows. Neither is a property of the hardware.

This is why the assumption is not a footnote. It determines the floor under every internal chargeback rate, every cloud price built on cost-plus logic, and every build-versus-rent comparison. A team that models its costs on a six-year life and then replaces hardware after three has been systematically understating what its inference actually costs.

The converse is equally true, and worth saying because the commentary rarely does: an operator that depreciates over three years and then runs the hardware profitably for six has been overcharging its own product teams and understating its own margins. Conservative is not automatically correct.


The Accelerator Can Still Compute, But the Workload Has Moved

Everything above concerns the numerator of the cost equation. The rest of this article is about the denominator, which is where the interesting failure happens.

An accelerator becomes economically difficult long before it becomes technically incapable, and several forces push in the same direction at once:

  • Performance per watt. Newer parts do more work for the same power. In a facility with a fixed power envelope — which is most facilities now — every rack slot occupied by older hardware has an opportunity cost measured in the throughput a newer part would have produced from the same watts.
  • Rack density and cooling. Older air-cooled deployments cannot always be upgraded in place, so the constraint is the building, not the card.
  • Interconnect. Model and tensor parallelism depend on inter-GPU bandwidth. An older interconnect generation caps how effectively multiple accelerators can be combined, which matters most precisely when you are combining them to compensate for insufficient memory.
  • Software support. Kernel optimisation follows the current generation. New attention implementations, quantisation formats and serving features arrive tuned for recent hardware, and older parts receive them late, partially, or not at all.
  • Numerical formats. FP8 and FP4 support is architectural. An accelerator that cannot execute the format a model was quantised for either runs a less efficient variant or does not run it.

None of these makes the hardware stop working. They make it progressively less attractive than the alternative, which is what economic obsolescence means.


HBM Changes the AI Accelerator Depreciation Clock

The memory story is the one that deserves more attention than it gets, because it produces a hard boundary rather than a gradual decline.

Here is how accelerator memory has moved across generations, using vendor-published specifications:

AcceleratorMemoryTypeBandwidth
A100 (2020)40GB or 80GBHBM2e1.55–2.0 TB/s
H100 SXM (2022)80GBHBM33.35 TB/s
H200 (2023)141GBHBM3e4.8 TB/s
B200 (2024)192GBHBM3e8 TB/s
B300-classup to 288GBHBM3e~8 TB/s

Capacity roughly tripled from A100’s 80GB to B200’s 192GB, and bandwidth rose about fourfold. Compute throughput rose faster still in raw terms, but compute and memory are not interchangeable, and that is the point.

Three things compete for accelerator memory during inference:

  1. Model weights. A 70B-parameter model at FP16 needs roughly 140GB before anything else — which is why the H200’s 141GB is frequently described as the point where 70B-class models fit on a single accelerator, and why the same model on 80GB parts requires either quantisation or sharding across two.
  2. KV cache. Attention state for every token in every active sequence, growing linearly with context length and with batch size. Long-context serving is a KV cache problem before it is anything else. We went through the economics of this memory in our breakdown of AI memory costs.
  3. Activations and working space. Intermediate results, communication buffers, and whatever the serving framework reserves.

Memory capacity is therefore a feasibility constraint, while compute throughput is a speed constraint. Insufficient compute makes a workload slow. Insufficient memory makes it impossible without changing the deployment — and the changes available all cost something.


Obsolescence by Memory Footprint

Hardware does not need to stop computing to become obsolete. The workload can simply outgrow its memory envelope.

Obsolescence by memory footprint is our analytical framing, not an accounting term or an industry standard. It describes the case where an accelerator retains sufficient compute capability for a workload but lacks the memory capacity to hold that workload efficiently — and where every available workaround degrades the economics rather than restoring them.

The workarounds, and what each costs:

WorkaroundImmediate effectEconomic consequence
Reduce batch sizeFits in memoryLower throughput per accelerator; weights re-read for fewer tokens
Shard across more acceleratorsModel fitsTwo devices doing one device’s work; interconnect traffic and synchronisation overhead
Shorten contextFits in KV cacheA product limitation, not a technical fix
Offload to host memoryFitsPCIe-bound transfers at a fraction of HBM bandwidth
Quantise more aggressivelySmaller footprintPossible quality loss; may need formats the hardware lacks

Each of those paths ends in the same place: more accelerator-hours per unit of useful output, and therefore a higher cost per token on hardware whose hourly cost was fixed the day it was installed.

Work through the arithmetic informally. If a model requires two 80GB accelerators where one 141GB accelerator would serve it, the older deployment needs twice the devices, pays two sets of hourly costs, and absorbs the interconnect overhead of tensor parallelism. Even if the older accelerators were fully depreciated and cost nothing in capital terms, they still consume power, rack space and operational attention — and in a power-constrained facility, they consume the scarcest resource of all.

What makes this form of obsolescence distinctive is that it arrives as a step, not a slope. Performance-per-watt disadvantages accumulate gradually. Memory capacity either holds the model or it does not, and the moment a workload crosses the boundary, everything downstream changes at once: the parallelism strategy, the device count, the utilisation, the cost per token.

Four trends push workloads across that boundary, and all four are moving in the same direction:

  • Context windows lengthened. Frontier models moved from tens of thousands of tokens to hundreds of thousands and beyond, and KV cache scales linearly with context.
  • Reasoning models generate more tokens per task, which means longer sequences held in cache for longer.
  • Agentic workloads accumulate context across many turns within a single task.
  • Multimodal inputs consume far more tokens per unit of content than text.
AI accelerator depreciation

None of these trends required more FLOPS specifically. All of them required more memory, and the demand pressure this creates across the accelerator market is part of what we examined in our analysis of what pacing the frontier does to AI chip demand.

The implication for depreciation policy is uncomfortable. An accounting useful life is chosen partly on the assumption that the hardware remains productive across the period. Memory-footprint obsolescence means that productivity can end abruptly, for reasons entirely external to the asset, when the models being served grow past what it can hold.


A Practical Test for an Aging AI Accelerator

There is no universal answer to how long an accelerator lasts, and anyone offering one is selling something. Useful life depends on workload, generation, memory capacity, utilisation, electricity price, cooling efficiency, whether the work is training or inference, software support and what the replacement would cost.

What can be built is a test. Five layers, in order — and the accelerator’s economic life ends at the first layer it fails.

Layer 1 — Can it still run the workload? Does the model fit, with its KV cache, at the context length your product promises? A no here is memory-footprint obsolescence, and it is binary.

Layer 2 — Can it run it efficiently? What batch size does it sustain? How much sharding is required? Every extra device is an efficiency tax on the older generation.

Layer 3 — Can it hit the required throughput and latency? Tokens per second, TTFT and p95 against your actual SLA rather than a benchmark.

Layer 4 — Does it compete economically? Cost per useful token, including power, cooling and rack space, against the same figure for current hardware. Fully depreciated hardware often wins this comparison, which is exactly why it stays in service.

Layer 5 — Does replacement create enough additional capacity to justify the capital? The relevant question is not whether new hardware is better but whether the throughput gain per watt and per rack unit, in a facility with fixed power, repays the spend.

The metrics to gather for that test:

SignalWhat indicates approaching obsolescence
HBM capacity pressureFrequent OOM, forced sharding, capped batch sizes
Memory bandwidth utilisationSustained near ceiling while compute sits idle
Achieved throughputFalling well short of what newer parts deliver per watt
Batch size ceilingConstrained by memory rather than by latency targets
Context length supportedBelow what the product now requires
Power per useful tokenRising against the current generation
UtilisationFalling because the hardware cannot take the current workload mix
Replacement cost per unit of added capacityThe decision variable at layer 5

A fleet failing at layer 1 or 2 should be redeployed rather than retired — older accelerators remain genuinely useful for smaller models, embeddings, batch scoring, fine-tuning and development environments. Economic obsolescence for one workload is not obsolescence generally, which is the strongest argument the hyperscalers have for longer useful lives.


What AI Accelerator Depreciation Should and Should Not Tell You

Depreciation tells you how a company has chosen to allocate cost across periods, and by extension what management believes about the duration of economic benefit. Read across a group of filings, it tells you whether that belief is converging or diverging — and since January 2025 it has been diverging.

It does not tell you how long the hardware physically lasts, how long a specific accelerator generation stays competitive, what the fleet would fetch on the secondary market, or whether the assets are impaired. Those are separate questions with separate evidence, and the disclosure of useful life answers none of them.

The most useful reading of a change in useful life is as a signal about management’s expectations rather than as a fact about hardware. Amazon shortening a subset while Meta extended, in the same month, tells you two large operators looked at similar hardware and reached different conclusions about how long it would keep earning.

For anyone reading filings closely, the disclosures worth tracking are the scope statements rather than the headline numbers — what equipment the estimate covers, and whether the company breaks out accelerators at all. We looked at how much a detailed filing can reveal about AI cost structure in our analysis of what an Anthropic S-1 would disclose; the same reading applies here, and the answer is usually that the category is broader than the question.


Conclusion: Useful Life Is Not Competitive Life

An accelerator’s accounting life is a management estimate applied to a broad equipment category. Its competitive life is set by model architecture, context length and memory capacity, and nobody discloses it.

The gap between them is where the risk sits. If competitive life is shorter than accounting life, depreciation is understated and the reported cost of AI compute is too low. If it is longer — because older accelerators find second lives serving smaller models — the schedules are conservative and the hardware keeps earning after its book value reaches zero.

Both outcomes are happening simultaneously, on different parts of the same fleets. That is the honest answer, and it is why a single industry number has never made sense.

What operators can do is stop treating depreciation as the measure of how long hardware stays useful. It was never that. Measure the memory envelope against the workload, and you will know when an accelerator’s competitive life is ending long before its depreciation schedule notices.


FAQ

How long does an AI accelerator typically last?

Physically, well beyond the period it is depreciated over — data-centre accelerators commonly run for many years without failure. Economically, it depends on workload, memory capacity, power costs and what replaces it. There is no single industry figure, and the disclosed accounting lives of five to six years are estimates for equipment categories rather than measurements of accelerator lifespan.

Why do companies depreciate AI accelerators over different periods?

Because useful life is an estimate of expected economic benefit, and companies have different fleets, workloads, refresh patterns and judgements. Amazon cited the increased pace of technology development in AI when shortening; Microsoft cited software efficiency improvements when extending.

Can an older GPU still be economically useful?

Yes, frequently. Fully depreciated accelerators carry no capital cost, and older parts remain well suited to smaller models, embeddings, batch scoring, fine-tuning and development. Obsolescence for frontier inference is not obsolescence for every workload.

How does HBM affect GPU obsolescence?

Memory capacity determines whether a model, its KV cache and its activations fit on the device. When they do not, the workload must be sharded, batched smaller or offloaded, each of which raises cost per token. Capacity has risen from 40–80GB on A100 to 141GB on H200, 192GB on B200 and up to 288GB on B300-class parts.

What is the difference between GPU depreciation and GPU obsolescence?

Depreciation is an accounting allocation of cost over an estimated period. Obsolescence is the economic event of hardware no longer being worth operating relative to alternatives. They are independent: an accelerator can be fully depreciated and still productive, or carry book value and be commercially unusable.

Does more GPU memory increase useful life?

It extends competitive life, which is usually the binding constraint. A higher-memory accelerator stays able to hold larger models, longer contexts and bigger batches as workloads grow, which is why capacity has become a differentiator independent of compute throughput.

How can companies determine when to replace AI accelerators?

Test in order: does the workload fit in memory, does it run efficiently, does it meet throughput and latency targets, does it compete on cost per useful token, and does replacement add enough capacity per watt to justify the capital. The first failure in that sequence marks the end of economic life for that workload.


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 …