On Friday, June 12, at 5:21 pm Eastern, Anthropic received a letter from the U.S. Commerce Department. By that evening, Fable 5 and Mythos 5 — the company’s two most capable models, launched three days earlier — were gone. Not throttled. Not region-locked. Gone, for every customer Anthropic has, including the banks and agencies that had been using Mythos-class capability for vulnerability discovery. [1]

The mechanism is worth getting right because most of the coverage has it slightly wrong. Nobody flipped a remote kill switch. The government issued an export-control directive citing national security authorities, ordering Anthropic to suspend access for any foreign national, whether outside the United States or within it, including Anthropic’s own foreign national employees. [2] That last reach is the sharp part: under the deemed-export doctrine, giving a controlled technology to a foreign national on US soil counts as an export to their home country, so the order swept in Anthropic’s own non-citizen staff alongside every user abroad. A company cannot filter foreign nationals from US citizens in real time across a consumer product, so the only way to comply was to disable the models for everyone. The order's reach did the work. The global takedown was the side effect.

In April, in an internal briefing for the CEOs of portfolio companies I help oversee, I argued that the defining feature of the AI security landscape is an asymmetry: defenders are governed, and attackers are not. Procurement rules, compliance regimes, and data-sovereignty constraints dictate which models a defender may run. Attackers self-host abliterated open-weight models — models with the refusal behavior surgically removed from the weights — and answer to none of it. June 12 is that asymmetry rendered in a single week.

Here is the sharpened version. The week the most heavily safeguarded frontier model on the market was withdrawn from the entire planet over a narrow, non-universal jailbreak, a bypass that unlocks one sliver of capability in one circumstance. The abliterated open-weight models on Hugging Face stayed exactly where they were. The platform’s own “obliterated” tag now returns over 7,000 of them. [3] No export order reaches those. There is no account to suspend, no API to revoke, and no US-jurisdiction entity in the chain to serve. The governed model can be removed from hundreds of millions of users by one letter. The ungoverned model cannot be removed from anyone by anything.

Abliteration is not a jailbreak, and the difference is the whole argument. A jailbreak is an input attack — a crafted prompt that tricks an aligned model into complying — and the provider can patch it, filter it, or ban the account that sent it. Abliteration is surgery on the model itself. In 2024, researchers showed that a chat model’s willingness to refuse is mediated by a single direction in its internal activations: erase that direction from the weights, and the model loses the ability to say no while keeping nearly all its other capabilities. [4] The edit is baked into the file. Once those weights are on a hard drive, there is no refusal left to bypass and nothing for a vendor to fix. A jailbreak is a lock that can be picked. Abliteration removes the door.

What changed since 2024 is not the idea but the cost. The original technique required a researcher who understood transformer internals; the current tooling takes a command line — one openly published tool decensors a small model in under an hour on a single consumer GPU, no expertise required — and a single registry now hosts more than 200 ablated models. [5] The tempo asymmetry is the part defenders underweight: a frontier lab spends months red-teaming a release — Anthropic says thousands of hours on Fable — while the community publishes the de-safetied counterpart of a comparable open-weight release within a day or two of launch.

The honest objection is that some models try to resist this, but it does not hold. Published defenses — circuit breakers, extended-refusal training — work in the lab. But the labs don’t ship them inside the frontier open weights that actually get downloaded, the strongest results are on small models, and by 2026, public tooling already claims to defeat them, driving even Google’s hardened Gemma 4 to single-digit refusal rates. [6] Hardening raises the price of the operation. It does not close it.

The readers of this newsletter will see this as the activation of the coercion stack described in Access, Disable, Destroy, but through a route the original map didn’t draw. The off switch was not held by the model provider, nor by a sanctioning authority pointed at a foreign adversary. According to the Wall Street Journal and The Information, the finding that triggered the order came from Amazon — Anthropic’s largest investor and its primary cloud partner, on whose Bedrock platform the model most likely ran. Amazon’s researchers found the bypass; CEO Andy Jassy raised it with senior officials, including Treasury Secretary Scott Bessent; Commerce Secretary Howard Lutnick sent the letter. [7]

Reporting a live cyber bypass is defensible: a researcher who finds one should disclose it, whoever signs their checks. The hazard is not Amazon’s motive. It is that one firm now bankrolls the vendor, hosts its models, and supplies the findings behind the federal action against it: three chairs, one occupant, a governance problem, whether anyone acted in bad faith. That row did not exist on the original coercion-stack table. It does now.

Concede the government’s strongest case: Mythos is a genuinely dangerous capability. Anthropic itself withheld it from public release and lobbied for Mythos-class models to be treated as cyberweapons. A jailbreak that unlocks even a sliver of that capability on a model deployed to hundreds of millions of people is a real finding, not a clerical one. David Sacks, the administration’s former AI czar, put the case bluntly: a bypass “allowing operability of a cyber weapon” is hard to call anything but serious, and Anthropic’s minimizing language was “not consistent with Anthropic’s brand as the AI safety company.” [8] That last clause is the hinge, and it is where the story turns from a regulatory dispute into something closer to a Greek tragedy.

Anthropic supplied the moral framing that took its model down. On or around June 10 — a day after Fable 5 launched, two days before the letter arrived — Dario Amodei published an essay titled Policy on the AI Exponential. In it, in his own boldface, he argued that frontier models “should be required to go through technical testing and auditing, and their release should be blocked or reversed as a threat to public safety if they do not meet high standards of safety.” He named the analogy himself: the FAA grounding an unsafe aircraft. He called, in the same essay, for export controls on the AI supply chain to be “expanded, tightened, and coordinated.” [9] Two days later the government blocked his release, citing safety, using an export control.

Here is the cruelty in it. Amodei did not receive the apparatus he requested. He proposed a deliberative, statutory process: a third-party technical evaluation and explicit protection against “political favoritism or arbitrary decisions.” What arrived was a verbal directive on roughly ninety minutes’ notice, with no specific national-security detail and no third-party finding shared, the opposite of the process he described. Anthropic’s own statement says so: “This action does not adhere to those principles.” [10] But the principle the administration did use — that government may block or reverse a frontier release on safety grounds — is the one Anthropic spent years legitimizing. Sacks then turned the company’s safety branding back on it, arguing that it should have complied without argument. The lab supplied the moral framework; the government supplied a blunter instrument than the lab wanted; and the safety reputation Anthropic built became the lever its own funder’s disclosure pried.

The asymmetry is what makes something load-bearing, and it should change how you price a dependency. The durability of a closed frontier model is not a function of the vendor's uptime or balance sheet. It is a function of a regulatory surface the vendor does not control and cannot predict — and that surface, as of June 12, can be activated by the firm that funds and hosts the vendor. The substitute sitting one tier down — the abliterated open-weight model an attacker runs on a few GPUs at most — lacks such a surface. The best open-weight models now trail the closed frontier by about four months, not the chasm that gap used to be; abliteration is a separate operation layered on top, stripping refusals from a model that is already near-peer. [11] So the substitute is not as capable as Mythos, but it is close, it is permanent, and it is — in the only sense that matters to whoever is probing your systems — more reliably available than the safety-first product it imitates.

The model built to refuse can be withdrawn from everyone. The model built to refuse nothing cannot be withdrawn from anyone.

Notes

[1] Anthropic, “Statement on the US government directive to suspend access to Fable 5 and Mythos 5”, June 12, 2026; launch date (June 9) and enterprise-customer impact per MarkTechPost, June 13, 2026, and MLQ News, June 13, 2026.

[2] Anthropic statement, June 12, 2026 (full text of the scope language, including foreign-national employees); corroborated by Axios, “Trump admin blocks foreign access to Anthropic’s most powerful AI”, June 12, 2026.

[3] Hugging Face’s abliterated tag filter returned roughly 7,500 model repos as of mid-June 2026. The “over six thousand... against roughly six hundred two years ago” figure is from NPR, citing University of Nebraska Omaha (NCITE) research, “These AI models are free, private, and will never say ‘no,’” May 31, 2026. The tag count includes quantizations and mirrors, not solely unique base-model abliterations, and is rising — retrieve a current figure at publication.

[4] Andy Arditi et al., “Refusal in Language Models Is Mediated by a Single Direction”, arXiv 2406.11717 (submitted June 2024; NeurIPS 2024). The paper demonstrates across 13 open chat models up to 72B that refusal is mediated by a one-dimensional subspace; ablating that direction from the weights (weight orthogonalization) removes refusal while preserving other capabilities. The permanence-once-distributed characterization follows from the edit being to the weights themselves.

[5] Heretic (Philipp Emanuel Weidmann, “p-e-w”), released late 2025 (PyPI heretic-llm), automates directional ablation via an Optuna/TPE optimizer; its README reports ~45 minutes to decensor Llama-3.1-8B-Instruct on an RTX 3090 (20–30 minutes for Qwen3-4B), corroborated by NPR (n.3) for the “few minutes,” no-expertise characterization. Registry scale: huihui-ai hosted 235 models with 7,406 followers as of June 15, 2026. Speed-of-appearance (abliterated builds within ~24–72 hours of a major release) per huihui-ai’s published Gemma 4 / Qwen abliterations and activity feed. Anthropic’s “thousands of hours” of Fable red-teaming is from its launch posture as summarized in its June 12 statement (n.2).

[6] Defenses and the offense’s response: circuit breakers / Representation Rerouting per Zou et al., “Improving Alignment and Robustness with Circuit Breakers”, arXiv 2406.04313 (NeurIPS 2024); extended-refusal training per Abu Shairah et al. (KAUST), “An Embarrassingly Simple Defense Against LLM Abliteration Attacks”, arXiv 2505.19056 (May 2025), reporting treated models retaining >90% refusal under abliteration versus 70–80% drops for baselines — demonstrated on small/older models. Offense keeping pace: Abliterix, a Heretic derivative, claims to defeat circuit breakers and to reach a ~7% refusal rate on Google’s Gemma 4 (E4B) via direct weight editing. These refusal-rate figures are self-reported by the abliterating parties and are highly method-dependent; treated as directional, not measured.

[7] Wall Street Journal, “Amazon CEO’s talks with U.S. officials triggered crackdown on Anthropic models”, June 13, 2026 (WSJ names Bessent as one of several officials Jassy contacted); The Information, “Amazon’s Jassy raised concerns about Anthropic model, Trump crackdown”, June 13, 2026. Lutnick (Commerce) sent the directive per Anthropic’s statement and Axios. Amazon’s investment ($8B deployed to date, plus an up-to-$25B commitment agreed April 2026) and AWS cloud partnership per CNBC, Nov 22, 2024 and April 20, 2026; the same CNBC reporting confirms “Amazon does not have a seat on Anthropic’s board.” Bedrock as the likely test surface is inference, flagged as such.

[8] David Sacks, post on X, June 13, 2026.

[9] Dario Amodei, “Policy on the AI Exponential”, dated “June 2026” on the primary page; secondary trackers place publication on or around June 10, 2026. The “blocked or reversed” sentence and the FAA analogy are in Section 1 (Regulation and public safety); the “expanded, tightened, and coordinated” export-control language is in Section 5 (Securing leadership by democracies) and refers to chips and semiconductor manufacturing equipment. The essay’s separate “off switch” phrasing appears in Section 4 and refers to autonomous-weapons oversight, not model release — not conflated here.

[10] Sacks, X, June 13, 2026 (as n.8).

[11] Epoch AI, "Open models lag state-of-the-art closed models by 4 months" (Jack Edwards and Luke Emberson), data covering Jan 1–May 28, 2026: the most capable open-weight models trailed frontier closed models by an average of four months, or 8 points on Epoch's composite Capabilities Index — up slightly from the ~3-month average Epoch measured for Jan 2023–Oct 2025. This is a capability gap (open vs. closed frontier); abliteration is a distinct operation that removes refusals without adding capability, applied on top of an already-near-frontier open model. The two are not the same axis and are not conflated here.

On June 8, Amazon signed a $17.5 billion loan it can draw at will, with no financial covenants attached. Two days later, Oracle told investors it would raise roughly $40 billion more and unveiled a new accounting measure to explain why its capex is not quite its capex. The same day, Bloomberg reported that SoftBank could not borrow $6 billion against its OpenAI stake.

The volume itself is no longer news. Morgan Stanley estimates nearly $236 billion of AI-linked debt has been issued globally through May, four times last year’s pace, and expects close to $570 billion for the full year [1]. UBS estimates that hyperscaler capex will consume close to 100% of operating cash flow in 2026, compared with a ten-year average of 40% [2]. Everyone now knows the buildout runs on debt. What last week revealed is who gets to borrow it, on what terms, and against what.

Start with the cheapest money. Amazon’s facility is a senior unsecured delayed-draw term loan led by Citibank: the company can pull funds as needed through September 30, each draw repayable over three years, at 0.625% to 0.875% over SOFR, the floating benchmark rate, depending on ratings [3]. It landed days after Amazon priced the largest Canadian-dollar corporate bond in history, a C$14 billion deal that drew more than C$28 billion in orders [4]. This is for a company whose trailing free cash flow has collapsed to $1.2 billion from $25.9 billion a year earlier, on the way to roughly $200 billion of capex this year [5]. The banks looked straight past the AI bet. Unsecured borrowing with no financial covenants is routine at Amazon’s rating — and that is the point. What stands behind the loan is the retail engine and AWS’s operating cash flow: businesses already earning, whatever the GPUs return tomorrow.

Oracle got the conditional money. Its fiscal Q4, reported June 10, beat the headline estimates: $19.2 billion in revenue, $2.11 in adjusted EPS, and remaining performance obligations — contracted future revenue — of $638 billion, up 363% in a year and up $85 billion in a single quarter [6]. The stock fell anyway, not the first time this fiscal year, a headline beat has been sold [7]. The funding side explains it. Free cash flow for the year was negative $23.7 billion. Oracle raised $43 billion in debt and $5 billion in equity in fiscal 2026, and plans roughly $40 billion more this year, including a previously announced $20 billion at-the-market equity program (new shares sold directly into the market) [8]. The buildout has crossed a line worth stating plainly: reported capex of $90–95 billion next fiscal year, against $90 billion of guided total revenue for the same year [8]. Oracle plans to spend its entire revenue, roughly, on capital expenditures.

And it introduced a new number. “Net cash outlay for capital expenditures” is guided around $70 billion for fiscal 2027, against the same $90–95 billion in reported capex; the gap is due to customers prepaying for GPUs or supplying their own [9]. Those arrangements now total $75 billion across Oracle’s large AI contracts, and the company says they substantially reduce the capital it must raise [10]. Read that twice. Oracle is publishing a table showing lenders which parts of its capex are really someone else’s. The arrangement is genuine — prepaid hardware does reduce Oracle’s funding needs — but it shifts risk rather than removing it. The $75 billion is banked; the rest of the backlog, largely anchored to OpenAI through Stargate [11], still depends on customers being able to pay, quarter after quarter, for years. When a borrower starts inventing measures to reassure the market, the market has started asking questions.

What did Amazon’s lenders see that SoftBank’s couldn’t? The answer is a hierarchy worth understanding before the second half of Morgan Stanley’s $570 billion arrives.

SoftBank asked for the third kind of money and didn’t get it. In May, it sought a $10 billion margin loan backed by its OpenAI stake; lender hesitation cut the target to $6 billion; on June 10, the talks stalled outright [12]. SoftBank may yet revive them. About $5 billion had been lined up, though it was unclear whether those commitments were verbal or written [13]. The sticking point was not OpenAI’s prospects. It was the collateral itself. OpenAI is private; its valuation is set by funding rounds rather than a liquid market, and a margin lender needs collateral that it can price daily and sell quickly. A stake last marked inside a $122 billion round at an $852 billion post-money valuation [14] turned out to be worth, for borrowing purposes, nothing yet. The stall came even though OpenAI had confirmed, two days earlier, a confidential filing for a US listing that could debut as soon as the fall [15]. Some of the same prospective lenders had said the IPO news made the loan more attractive. They still walked. The clock, meanwhile, is real: a $40 billion bridge loan taken on to fund SoftBank’s OpenAI commitments comes due in March 2027 [16]. Shares fell as much as 9.7% on the news, nine days after the company had overtaken Toyota as Japan’s most valuable [17].

Strip away the deal terms, and the three answers reduce to one question: what gets the lender repaid? Amazon’s creditors are repaid from businesses that predate the AI bet and would survive its disappointment. Oracle’s creditors are repaid from backlog: promises from customers whose own funding remains unproven. SoftBank’s would have been repaid from a mark: a number set by the last buyer in a private round, untested by any open market. The week’s pricing followed that gradient without sentiment. Cheapest against yesterday’s cash. Conditional, and increasingly explained, against tomorrow’s contracts. Refused against a number on a page.

None of this says the lending stops. Morgan Stanley expects issuance to accelerate in the second half [1]. It says the lending discriminates, and what it discriminates against is distance from cash. Each rung down the ladder, the borrower pays more, explains more, and pledges more. At the bottom rung, the market said no to collateral with a listing already in motion. A ticker will do what the mark could not; the prospect of one was not enough. This reading would be wrong if SoftBank closes its loan at or near $6 billion before the IPO prices, or if Oracle’s $40 billion raise comes as ordinary investment-grade debt without leaning on equity. Either outcome would mean the market lends against marks and backlog as readily as against cash flow after all.

Until then, the hierarchy stands. Cash flow lends. Backlog negotiates. Valuation waits for its ticker.

Notes

[1] Morgan Stanley research note, June 10, 2026, as reported by Reuters via Tech Startups: ~$236 billion in AI-linked global debt issuance through May 31, 2026, roughly four times the prior-year pace; full-year 2026 forecast of nearly $570 billion. Analyst estimate, not a measured total.

[2] UBS estimate, as reported by TechTimes: 2026 hyperscaler capital spending on pace to consume close to 100% of operating cash flows, versus a 10-year average of about 40%. Analyst estimate.

[3] Amazon Form 8-K, filed June 10, 2026: term loan agreement dated June 8, 2026, Citibank N.A. as administrative agent; $17.5 billion senior unsecured delayed draw term loan facility; commitments expire September 30, 2026; three-year maturity per draw. SOFR margin of 0.625–0.875% depending on ratings and the absence of financial covenants per the filing as reported by Yahoo Finance; the agreement retains customary covenants and events of default. Joint lead arrangers: Citibank, JPMorgan, BofA Securities, HSBC, Wells Fargo.

[4] Bloomberg: C$14 billion (~$10 billion) priced June 8, 2026, the largest corporate debt offering on record in Canadian dollars, with more than C$28 billion in orders. Reuters confirms from the final pricing term sheet filed with the SEC: five tranches, maturities 2029–2056, surpassing Alphabet’s C$8.5 billion record set a month earlier.

[5] Yahoo Finance, per Amazon’s Q1 2026 results: trailing-twelve-month free cash flow of $1.2 billion versus $25.9 billion a year earlier; Q1 2026 capex of $44.2 billion; ~$200 billion full-year 2026 capex plan disclosed with Q4 2025 earnings.

[6] Oracle Q4 FY2026 earnings press release (Form 8-K exhibit, June 10, 2026): RPO of $638 billion, up 363% year-over-year and up $85 billion sequentially. Revenue and EPS beats per Sherwood News: revenue $19.2 billion vs. $19.1 billion expected; adjusted EPS $2.11 vs. $1.96 expected ($2.03 excluding one-time net investment gains). One miss beneath the headlines, per Yahoo Finance: total cloud revenue of $9.91 billion came in below the $9.99 billion consensus, with cloud applications light and cloud infrastructure ahead.

[7] Sherwood News and TheStreet. Shares fell in after-hours trading on June 10 despite the beats. Precedent: in Q2 FY2026, a 32.4% EPS beat was followed by a -10.8% day-of move (24/7 Wall St.). Note the broader tape: May CPI printed at a three-year high the same day, and all three major US indices fell, so the decline was not purely company-specific.

[8] Oracle Q4 FY2026 earnings press release: fiscal 2026 free cash flow of negative $23.7 billion; $43 billion raised in debt financing and $5 billion in equity financing in fiscal 2026; approximately $40 billion in combined debt and equity financing planned for fiscal 2027, including the previously announced $20 billion at-the-market equity issuance; fiscal 2027 total revenue guidance confirmed at $90 billion. The release adds that Oracle “does not expect to issue additional debt in calendar year 2026” — making the near-term portion of the raise equity-led by the company’s own statement. The $90–95 billion reported-capex figure for fiscal 2027 is from the earnings call (see [9]).

[9] Oracle Q4 FY2026 earnings call, June 10, 2026: expected net cash outlay for capital expenditures of around $70 billion in fiscal 2027, with customer prepayments and timing impacts of $20–25 billion raising reported capex above that figure; the press release includes a reconciliation table for the new measure, and CFO Hilary Maxson detailed it on the call (CNBC). Fiscal 2026 net cash outlay was $48 billion after ~$8 billion of prepayment and timing impacts, against $55.7 billion of reported capex — up 162% year-over-year, with depreciation nearly doubling to $7.62 billion.

[10] Oracle Q4 FY2026 earnings press release: prepaid and customer-supplied hardware portions of large AI contracts total $75 billion, which the company states “substantially reduces the amount of capital Oracle must raise” for its AI datacenter buildout.

[11] Sherwood News: the RPO balance is largely anchored by Oracle’s OpenAI partnership under the $500 billion Stargate initiative. Bank of America analysts estimate that over 50% of the remaining performance obligation comes from OpenAI (CNBC); analyst estimate, not a company disclosure.

[12] Bloomberg, June 10, 2026: talks to raise at least $6 billion via a margin loan backed by SoftBank’s OpenAI stake have stalled; the initial $10 billion target was cut by 40% in May after lender hesitation. SoftBank may resume the margin loan later and is considering other fundraising options. A fair objection: SoftBank itself is rated BB+ with a negative outlook from S&P (revised March 3, 2026, on the additional $30 billion OpenAI commitment), so borrower quality may have weighed on the talks. But margin lending looks to the collateral first, and the concern lenders voiced, per Bloomberg’s reporting, was the difficulty of valuing an unlisted company — not SoftBank’s own credit.

[13] Bloomberg via Yahoo Finance: approximately $5 billion had been secured before talks stalled, though it was unclear whether commitments were verbal or written.

[14] OpenAI announcement, March 31, 2026: the round closed with $122 billion in committed capital at a post-money valuation of $852 billion; confirmed by Bloomberg. SoftBank contributed $30 billion of the round. The figure is a private-round valuation, not a market price — which is the point.

[15] Bloomberg via The Edge Singapore: OpenAI said on Monday, June 8, that it filed confidentially for a US IPO and is working with Goldman Sachs and Morgan Stanley on a potential listing as soon as the fall. Some prospective lenders on the margin loan had said they viewed it more favorably after news of the IPO preparation; the talks stalled regardless.

[16] Bloomberg via Yahoo Finance and Quartz: a $40 billion bridge loan taken on to fund SoftBank’s OpenAI commitments comes due in March 2027; SoftBank has indicated it intends to cover it from existing assets plus additional financing. Counterpoint on severity from Hua Cheng, head of Asia credit research at AllianceBernstein, who called the stalled margin loan one piece of a larger puzzle and not a standalone red flag.

[17] Bloomberg via Yahoo Finance: shares declined as much as 9.7% on June 10; SoftBank had overtaken Toyota as Japan’s most valuable company by market capitalization on June 1 (Bloomberg, Nikkei Asia) — the first time in more than two decades. SoftBank’s credit default swaps had narrowed to about 307 basis points from a May 20 peak above 367 — the credit market was already charging for the OpenAI concentration before the loan stalled.

Jensen Huang stood at the Taipei Music Center on the last day of May and announced that Nvidia intended to “reinvent the single most important tool of humanity.”[1] The tool in question is the personal computer, and the product behind the sentence is a laptop chip: RTX Spark, a 20-core Arm processor fused to a Blackwell GPU around a 128-gigabyte pool of memory, co-announced with Microsoft.[2] It ships this fall in machines from Asus, Dell, HP, Lenovo, and MSI, with a Surface Laptop Ultra as the flagship. Shares of AMD, Intel, and Qualcomm fell on the news.[3] The market read the announcement as a land grab in the PC business.

Eight weeks earlier, this publication described the single move that could pull local AI back into Nvidia’s orbit. In “Your Parents Paid,” we documented how Nvidia’s own product segmentation had handed the fastest-growing consumer AI workload to Apple and AMD, and we listed three conditions under which that would reverse. The third: “the CUDA moat extends into inference. If NVIDIA ships inference-specific optimizations — through TensorRT-LLM, NIM, or a CUDA-exclusive quantization format — that make the performance gap too large to ignore, practitioners return to NVIDIA hardware regardless of memory capacity.”[4]

RTX Spark is condition three, shipped as a product line. But it arrived with a twist we didn’t predict: Nvidia isn’t closing the performance gap. It’s making the gap irrelevant.

The spec sheet and the missing number

Start with what Nvidia published. The RTX Spark product page lists up to 6,144 CUDA cores on the Blackwell GPU, up to 20 CPU cores, up to 1 petaflop of FP4 AI performance, and up to 128 gigabytes of unified memory.[2] On stage, Huang claimed the chip runs 120-billion-parameter models locally.[5] That claim deserves a moment of respect. In April, we showed that the 120B model class needed 60-70 gigabytes at usable quantization and therefore did not fit on any consumer Nvidia product. The 32-gigabyte ceiling on the RTX 5090 was the centerpiece of Nvidia’s segmentation, the design choice that pushed private-inference buyers toward a $3,699 Mac Studio.[4] RTX Spark removes that ceiling. The capacity objection is gone.

Now look for the number that isn’t there. The product page lists cores, petaflops, and gigabytes. It does not list memory bandwidth.[6] For local language models, bandwidth is the most important metric: token generation reads the entire working set of model weights from memory for every token, making decode speed a near-linear function of memory throughput. Capacity decides whether a model loads. Bandwidth decides whether you can stand to use it. Nvidia headlined the first number and buried the second, the same disclosure pattern it used for the DGX Spark desktop, whose 273 GB/s figure appeared in technical documentation rather than marketing.[7]

Launch coverage and pre-launch leaks fill the blank and explain the silence. The full-spec N1X silicon inside RTX Spark is, by all accounts, the same configuration as the DGX Spark’s GB10: a 256-bit interface of LPDDR5X (laptop-class memory) delivering roughly 273 GB/s, with launch-day spec coverage citing up to 300.[8] Apple’s M4 Max delivers 546 GB/s. The M5 Max delivers 614. The M3 Ultra delivers 819.[9] On the dimension that determines how fast a local model actually runs, the machine Nvidia just announced trails the machines it was announced to displace by a factor of 2 to 3.

So the puzzle is real. Nvidia came back for local AI without closing the gap that lost it the market in the first place. Why would a company that just reported $215.9 billion in annual revenue enter a fight it has already measured itself losing on the merits?

Because the fight isn’t on the merits. RTX Spark is not a bid for the PC market. It is the recapture of the one AI workload that was escaping Nvidia’s orbit, and the recapture runs on defaults, not on benchmarks. The machinery has four layers, and only one of them is silicon.

Four layers of default

The first layer is the hardware itself, and the most important word on the product page is “natively.” Nvidia’s copy reads: “CUDA, the software that accelerates the world’s AI, runs natively on RTX Spark.”[10] Every prior path to large-model local AI on a thin-and-light Windows machine ran through someone else’s silicon and someone else’s runtime: Qualcomm’s NPU through ONNX, AMD’s iGPU through Vulkan, Apple’s unified memory through Metal. Each of those paths was hardware-agnostic by necessity, which is precisely what made local inference the first workload to slip Nvidia’s gravity. RTX Spark ends the necessity. For the first time, the premium Windows laptop tier ships with the same CUDA stack that runs the datacenter, and 128 gigabytes to feed it.

The second layer is the runtime, where the recapture stops being a hardware story. On RTX AI PCs, Nvidia’s NIM microservices run as containers in Windows Subsystem for Linux, with CUDA acceleration, and package models with everything needed to run them.[11] The quieter announcement is the one that matters: Microsoft’s Windows ML inference stack now automatically routes to Nvidia’s TensorRT for RTX whenever it detects RTX hardware.[12] Read that sentence again at the level of incentives. A Windows application developer who calls the operating system’s standard AI interface does not have to select an inference backend. The operating system selects it, and on this machine, the selection is CUDA. The developer didn’t choose Nvidia. Windows chose it for them. Jensen’s defense writes itself: developers begged for this. Local CUDA parity with the datacenter was among the loudest requests in Nvidia’s developer ecosystem, and the convenience is not an illusion. But convenience is how every default gets built.

That shift, from chosen dependency to ambient dependency, is the difference between the lock-in we described in “Open Source, Closed Orbit” and the lock-in being assembled now.[13] The original Black Hole worked on practitioners: researchers and engineers who chose CUDA because the tools were better, then found the exit priced in switching costs. The new layer works on people who never make a choice at all. The mainstream Windows developer building an AI feature in 2027 will write to Windows ML, ship to machines that route to TensorRT, and acquire a CUDA dependency the way one acquires an accent. Nobody decides to have one.

The third layer is the agent platform, and it explains the timing. RTX Spark’s marketing mentions chatbots only briefly. The page promises a PC where “agents work alongside you — running tasks, generating assets, writing code, on demand,” and pitches the desktop variants as machines “built to run personal AI agents 24/7 right at your desk.”[14] The plumbing has a name: NVIDIA OpenShell, an agent framework coming to Windows on top of Microsoft’s new security primitives, packaging local autonomous agents with guardrails gating what they can touch — alongside NIM containers as local agent endpoints and native NIM support arriving in Azure AI Foundry in July.[15] The agent era re-platforms the PC around continuous local inference, the bandwidth-hungry, always-on workload pattern that decides hardware defaults for a decade. Whoever owns the default runtime when that re-platforming happens owns the next ten years of Windows AI development.

The fourth layer is the funnel, and it is the oldest trick in the catalog. NIM’s developer tier is free and genuinely useful: unlimited endpoints for prototyping, hosted on DGX Cloud. Production is a different conversation. Nvidia’s own product page walks the path in two sentences: prototype freely, then “talk to an NVIDIA product specialist about moving from pilot to production with the security, API stability, and support that comes with NVIDIA AI Enterprise.”[16] The same NIM container that runs on the laptop runs in the datacenter and the cloud, which Nvidia presents as portability and which functions as a ratchet. A team prototypes an agent on a Spark laptop, the prototype works, and scaling it means an enterprise agreement that cross-sells the rest of the stack.

Put the four layers together, and the design is legible. Nvidia fixed the capacity problem, kept the bandwidth problem, and wrapped both in the Windows default. It can concede the benchmark because it is buying the path. A 2x decode deficit against a Mac Studio matters to the practitioner who measures tokens per second. It matters not at all to the Windows developer whose operating system, container catalog, agent framework, and cloud funnel have already agreed on the answer before the question was asked.

There is a precedent for this, and Jensen named it himself two months before the announcement. “GeForce is NVIDIA’s greatest marketing campaign,” he told the GTC crowd in March. “Your parents paid for you to be an NVIDIA customer... until someday you became an amazing computer scientist and became a proper customer.”[17] GeForce recruited the CUDA generation: gamers who became graduate students, who became the engineers who made CUDA the default in the datacenter. The pipeline aged. Gaming now accounts for 7% of Nvidia’s revenue, and the recruits were buying Macs.[18] Spark is that pipeline rebuilt for the agent era. The laptop is the new GeForce, except this time the product being marketed isn’t a graphics card a teenager will outgrow. It’s a default that a developer will never notice.

What the machine actually does

Honesty about the product, because it’s good. RTX Spark’s compute is real: the full configuration matches the 6,144 CUDA cores of a desktop RTX 5070, and on the GB10 silicon it shares with the DGX Spark, prefill — the compute-bound phase where a long prompt is ingested — runs at roughly 2,000 tokens per second on a 20B model.[19] For workloads that are mostly ingestion (summarizing long documents, retrieval over a document base, batch classification), that is a serious machine in a laptop chassis. The 45-to-80-watt envelope, the all-day-battery claim, and the full RTX gaming stack make it the most credible Windows-on-Arm product ever shipped, where Qualcomm’s Snapdragon X struggled to give mainstream buyers a reason to switch.[20] And 128 gigabytes of addressable memory on a Windows laptop is a first. None of this is vaporware.

The decode numbers are equally real, and they cut the other way. On the same GB10 silicon, LMSYS measured the DGX Spark generating just under 50 tokens per second on a 20B model at 4-bit precision — against 215 for an RTX Pro 6000 and 205 for an RTX 5090, a gap of roughly 4x that the reviewers attributed directly to the LPDDR5X memory interface.[19] Decode speed doesn't improve with the laptop’s power envelope because memory bandwidth doesn’t scale with wattage; the laptop will generate tokens at desktop-GB10 speed, which is to say at half to a third the speed of the Apple Silicon machines it shares a price bracket with.[21]

A note on a number you will see misquoted. Nvidia’s specifications include a 600 GB/s figure, and parts of the trade press have already printed it as the memory bandwidth.[22] It isn’t. The 600 GB/s is NVLink-C2C, the interconnect between the CPU and GPU complexes on the package. The memory interface feeding both remains LPDDR5X at roughly 273 to 300 GB/s. Bandwidth between two processors and bandwidth to the memory that holds the model are different numbers, and conflating them doubles the product’s apparent throughput. The confusion is not an accident of complicated engineering. Retail listings may yet publish the figure; the DGX Spark precedent, where the number surfaced in technical documentation after launch, suggests the pattern is policy. A company that headlines its interconnect bandwidth and buries its memory bandwidth knows which comparison it would lose.

So the honest scorecard reads: best-in-class prefill for the form factor, true 120B capacity, decode bandwidth in M5 Pro territory at M5 Max prices, and a marketing sheet built to keep you from computing that last number. Our April verdict — no amount of software makes 273 GB/s faster than hardware with three times the bandwidth — survives contact with the new product. What changed is that Nvidia stopped trying to win the comparison and started making sure the buyer never runs it.

The practitioners who walk away

The recapture has a boundary, and the boundary is choice. Everything in the four-layer machinery operates on defaults: the default premium laptop, the default OS inference path, the default agent runtime, the default scaling story. Nothing in it binds the practitioner who actively chooses a stack. llama.cpp still runs everywhere. Vulkan still outruns vendor stacks on AMD silicon.[4] Apple’s MLX is becoming the default backend of Ollama, the most popular local-model tool, with measured decode gains of 93% on supported models.[23] The buyer who reads benchmarks before purchasing will keep buying the machine with 614 GB/s, and nothing Nvidia shipped last week changes that calculus.

But count the populations. The benchmark-reading tier is a niche. The Windows installed base is more than a billion machines, refreshed through OEM defaults and corporate procurement cycles that have shipped “the premium Intel laptop” for thirty years and will ship “the premium RTX Spark laptop” with equal indifference to memory-bus arithmetic. Distribution decides defaults, and defaults decide ecosystems. Qualcomm proved that distribution alone doesn’t move an ecosystem: two years of Snapdragon X laptops put Arm Windows machines in every retail channel without giving developers a reason to target them. Nvidia inherits the compatibility groundwork Qualcomm paid for and arrives with the developer reason pre-installed: a machine carrying the stack the world’s AI is already written on, an OS that routes to it silently, and an agent platform whose launch partner is the OS vendor itself.

The exception that proves the design: the people most likely to escape recapture are the people Nvidia’s original segmentation already pushed out. The medical practice that bought a Mac Studio in 2025 for private 70B inference has no reason to return; its stack is Metal, its tooling is MLX, and its data never left the building. Nvidia has written them off; the project is making sure the next ten million developers never become them.

The ninth domain

Readers of this publication have seen this architecture before. “Open Source, Closed Orbit” mapped how Nvidia replicated the open-source ecosystem’s eight critical infrastructure functions — model hosting, developer tooling, inference serving, fine-tuning, evaluation, and the rest — each replica routing back to Nvidia hardware.[13] The framework’s gap was geographic: the eight domains lived in the cloud, and the datacenter, and the device on the desk remained contested ground. That contest is what “Your Parents Paid” documented from the other side: at the device tier, where workloads run through llama.cpp and MLX rather than NIM and Triton, the pull was visibly loosening. Local inference wasn't escaping because someone built a better CUDA; it was because the workload didn’t need CUDA at all.[4]

RTX Spark closes the map. The device is the ninth domain, and the replication strategy is identical to the first eight: take a function the open ecosystem performs in a hardware-agnostic way, ship a vertically integrated version that is easier than the agnostic one, and let convenience do what compulsion couldn’t. The two pieces are mirror images. April’s story was segmentation pushing the workload out: a 32-gigabyte ceiling, a missing NVLink, a bandwidth-starved Spark desktop, each a deliberate gap that protected datacenter margins. June’s story is integration pulling the workload back: full capacity, native CUDA, OS-level routing, and an agent platform. Opposite moves. Same gravity. In both directions, the constant is that Nvidia designs the consumer product around what it does to the datacenter business, because the datacenter is 90% of revenue, and the consumer device is, in Jensen’s own framing, a marketing campaign with a motherboard.[17][18]

What would have to break

The recapture thesis is falsifiable, and we’ll state the conditions plainly.

First, it breaks if the default path opens up. If Windows ML’s hardware routing stays neutral in practice — if a developer writing to the standard Windows AI interface gets equivalent first-class treatment on Qualcomm NPUs and AMD silicon, and the TensorRT route confers no meaningful advantage — then the second layer of the machinery never engages, and RTX Spark is just a fast laptop. The incentive structure argues against this. Microsoft has reasons to keep Windows ML formally vendor-neutral; Nvidia has reasons to make the neutral interface perform best on its hardware; and “formally neutral, practically optimized” is how platform defaults in computing have historically worked. Watch the benchmark deltas between Windows ML on Spark and Windows ML on Snapdragon through 2027. If your AI feature had to run on a non-RTX machine tomorrow, would anything break? If you don’t know, the default has already been decided.

Second, it breaks if the agnostic stack holds the mainstream, not just the practitioners. Ollama’s MLX migration, llama.cpp’s ubiquity, and an M5 Ultra refresh give Apple every chance to keep the enthusiast tier and grow it; the M5 Ultra skipped this week’s WWDC and is now expected around October on reported memory-supply constraints, which puts Nvidia’s fall launch and Apple’s 128GB-class answer in the same quarter.[24] If local AI on Windows stalls — if the agent-PC pitch lands as this decade’s 3D TV — then Nvidia will have built a beautiful funnel over a dry riverbed. The third condition is the prosaic one: adoption. Windows-on-Arm carries a decade of compatibility scar tissue, fall launches slip, Morgan Stanley’s channel checks put N1X machines at $2,899 and up, and premium-priced first-generation platforms have a long history of underselling their keynotes.[25] If OEM sell-through disappoints by the end of 2027, the ninth domain stays open.

Here is why we doubt Nvidia loses even then. In September 2025, Nvidia agreed to buy $ 5 billion of Intel common stock, roughly 4% of the company whose RTX Spark franchise it is ostensibly built to attack; the purchase closed in December after antitrust clearance.[26] The equity is the smaller half of the deal. The same agreement commits Intel to build x86 system-on-chips for the PC market “that integrate NVIDIA RTX GPU chiplets” — Intel’s own filing language.[26] Read the two moves together. If Arm-based AI PCs win, Nvidia owns the chip. If x86 holds, the incumbent’s next-generation PC silicon will carry Nvidia’s GPU by contract. The instruction set is a coin flip Nvidia has hedged; the layer it refuses to share in either branch is the one this piece is about: the GPU, the runtime, and the default path between a Windows developer and a model. That hedge is the clearest evidence of the bet. Companies hedge the parts they consider interchangeable. They never hedge the moat.

In April, we ended by noting that the local inference market was growing despite Nvidia’s product line, not because of it, and that the gravity of the Black Hole was measurably weakening at the device tier. Eight weeks later, Nvidia shipped the correction, which tells you how seriously it took the leak. It did not ship more bandwidth. It shipped a default.

Local inference still doesn’t need CUDA. Nvidia just rebuilt the machine it runs on so that the path of least resistance does.

Notes

[1] Jensen Huang, GTC Taipei keynote at Computex 2026, Taipei Music Center, May 31–June 1, 2026 (June 1 local time). “Reinvent the single most important tool of humanity” quoted by Tom’s Hardware.

[2] NVIDIA RTX Spark product page (nvidia.com/en-us/products/rtx-spark, accessed June 10, 2026): up to 6,144-core Blackwell RTX GPU, up to 20-core CPU, up to 1 petaflop FP4, up to 128GB unified memory. Laptop partners: Asus ProArt P16, Dell XPS 16, HP OmniBook X 14, Lenovo Yoga Pro 9n, Microsoft Surface Laptop Ultra, MSI Prestige N16 Flip AI+; desktop partners include Acer and Gigabyte. Announced May 31, 2026 with Microsoft (NVIDIA Newsroom); availability fall 2026. CPU complex: 20 Arm cores (10x Cortex-X925 + 10x Cortex-A725), co-designed with MediaTek, per HotHardware. Nvidia also showed a two-year cadence roadmap with successor chips in 2028 and 2030.

[3] AMD, Intel, and Qualcomm share declines on the announcement: CNBC, June 2, 2026.

[4] “Your Parents Paid,” The AI Realist, April 3, 2026. The three reversal conditions appear in the closing section, “What would have to break.” Companion hardware guide: “What to Buy for Local LLMs (April 2026).”

[5] 120-billion-parameter local model claim: Nvidia keynote and product materials, reported by Notebookcheck. At Q4-class quantization a 120B dense model requires roughly 60–70GB of memory; 120B-class MoE models fit comfortably in 128GB. Vendor claim; independent throughput benchmarks on shipping hardware not yet available.

[6] NVIDIA RTX Spark product page, accessed June 10, 2026. The specifications section lists GPU cores, CPU cores, FP4 throughput, and memory capacity. No memory bandwidth figure appears anywhere on the page.

[7] NVIDIA DGX Spark: 128GB LPDDR5x, 273 GB/s, documented in the DGX Spark User Guide rather than launch marketing. See “Your Parents Paid,” note 18.

[8] N1X full-spec configuration matching DGX Spark’s GB10 (256-bit LPDDR5X-8533, ~273 GB/s): Tom’s Hardware pre-launch specification reporting. Tom’s Hardware’s launch article states “up to 300 GB/s of memory bandwidth” in its spec rundown, suggesting the ceiling figure was briefed to press; it appears nowhere on the product page (note 6). One analysis cites LPDDR5X-9400 (~301 GB/s). The GB10-lineage claim is consistent across sources but not officially confirmed.

[9] Apple memory bandwidth, manufacturer specifications: M4 Max 546 GB/s; M5 Max with 40-core GPU — the only configuration offering 128GB — 614 GB/s (the 32-core variant is 460 GB/s); M5 Pro 307 GB/s; M3 Ultra 819 GB/s (Apple tech specs; Apple Newsroom, M5 Pro and M5 Max). See “Your Parents Paid,” notes 32–34, for pricing at the 128GB tier.

[10] NVIDIA RTX Spark product page: “CUDA, the software that accelerates the world’s AI, runs natively on RTX Spark.” Developer section: “The same NVIDIA CUDA stack the world’s AI is built on, so you can develop and prototype on the same machine... prototype, fine-tune, and inference on the latest models locally.”

[11] NVIDIA NIM microservices on RTX AI PCs run through WSL2 with CUDA acceleration: NVIDIA Developer Blog. That deployment path was established on x86 RTX PCs; Arm-native NIM containers are already in production on the DGX Spark, which runs the same GB10-lineage silicon as RTX Spark.

[12] Windows ML, powered by ONNX Runtime, automatically uses the TensorRT for RTX inference library on GeForce RTX GPUs: NVIDIA blog, Microsoft Build coverage. TensorRT for RTX is natively supported by Windows ML.

[13] “Open Source, Closed Orbit: The Hardware Monopolist’s Guide to Owning Open Source,” The AI Realist. The eight-domain replication framework and the catalog-and-contract lock-in structure.

[14] NVIDIA RTX Spark product page: “Welcome to the PC where agents work alongside you — running tasks, generating assets, writing code, on demand... There’s intelligence on both sides of the keyboard now.” Desktop section: “Built to run personal AI agents 24/7 right at your desk.”

[15] “NVIDIA OpenShell is coming to Windows on top of Microsoft’s new security primitives, giving developers a single, easy-to-deploy package for running autonomous agents safely”: NVIDIA, Computex 2026 announcements, May 31, 2026; OpenShell appears in NVIDIA’s trademark list (NVIDIA Newsroom). NIM containers as local agent endpoints and native NIM support in Azure AI Foundry from July 2026: Microsoft Build 2026 coverage (Windows News); the Foundry date is per Build coverage, not yet confirmed in Microsoft primary documentation.

[16] NVIDIA NIM product page (nvidia.com, accessed June 10, 2026): “Get unlimited access to NIM API endpoints for prototyping, accelerated by DGX Cloud. When ready for production, download and self-host NIM on your preferred infrastructure... Talk to an NVIDIA product specialist about moving from pilot to production with the security, API stability, and support that comes with NVIDIA AI Enterprise.”

[17] Jensen Huang, GTC 2026 keynote, March 16, 2026: “GeForce is NVIDIA’s greatest marketing campaign... Your parents paid for you to be NVIDIA customers.” Full quote and sourcing in “Your Parents Paid,” note 1.

[18] NVIDIA Q4 FY2026 earnings (Form 8-K, filed February 25, 2026, SEC EDGAR): fiscal 2026 revenue $215.9B, of which Data Center $197.3B (91%) and Gaming $16.0B (7%).

[19] LMSYS, “NVIDIA DGX Spark In-Depth Review,” October 2025: GPT-OSS 20B (MXFP4) in Ollama at 2,053 tok/s prefill and 49.7 tok/s decode on DGX Spark, versus 10,108/215 on RTX Pro 6000 and 8,519/205 on RTX 5090. The reviewers attribute the decode gap to the unified LPDDR5x memory interface. Figures are for the GB10 desktop; RTX Spark shares the silicon per note 8 but laptop-specific benchmarks are not yet published.

[20] Power envelope 45–80W and integrated-GPU-only positioning (no discrete pairing planned): Engadget and Tom’s Hardware launch coverage. Qualcomm Windows-on-Arm context: Microsoft’s Windows-on-Arm exclusivity with Qualcomm expired in 2024, as Qualcomm executives publicly confirmed, opening the door to this product.

[21] Decode speed invariance with TDP: token generation is memory-bandwidth-bound, and LPDDR5X bandwidth does not change with the power envelope. Prefill, which is compute-bound, takes a 15–25% reduction at laptop wattage per independent analysis. Community analysis; consistent with the bandwidth-bound decode model established in “Your Parents Paid,” notes 18 and 36.

[22] 600 GB/s NVLink-C2C (CPU-to-GPU interconnect) listed by Nvidia and reported by VideoCardz; misreported as peak memory bandwidth by at least one major outlet (Notebookcheck: “With NVLink, its memory bandwidth peaks at 600 GB/s”).

[23] Ollama’s transition of its Apple Silicon backend from llama.cpp to MLX, with preview decode improvements of 93% on supported models: ollama.com/blog/mlx, March 2026. Methodological caveats in “Your Parents Paid,” note 38.

[24] Apple’s M5 Ultra Mac Studio, widely anticipated at WWDC (keynote June 8, 2026), did not appear; reporting attributes the slip to RAM supply constraints, with October 2026 viewed as the likely window (Macworld, June 8, 2026). Nvidia, for its part, says it does not expect RTX Spark laptop supply to be limited despite the same global memory shortage (Yahoo Finance; vendor claim). The rumored M5 Ultra retains the UltraFusion dual-die design, two M5 Max dies with interconnect bandwidth above 1,000 GB/s (TrendForce, citing Commercial Times) — rumored, not announced.

[25] Pricing per a Morgan Stanley report based on channel checks with PC brands at Computex: “AI PCs with N1X will need to price at US$2,899, while N1 models will be priced at US$1,799” (Wccftech; VideoCardz, June 2–3, 2026). Nvidia has not published pricing. Microsoft confirmed a fall release for the Surface Laptop Ultra while declining to discuss pricing (PCWorld, Build 2026).

[26] Securities Purchase Agreement dated September 15, 2025; announced September 18: NVIDIA purchased 214,776,632 Intel shares at $23.28, a $5.0 billion aggregate price (Intel Form 8-K, September 2025). The FTC, which had examined whether the roughly 4% stake raised antitrust concerns, cleared the deal December 18, 2025; the purchase closed December 26 (The Register; CNBC). The product commitment is in the same announcement: “For personal computing, Intel will build and offer to the market x86 system-on-chips (SOCs) that integrate NVIDIA RTX GPU chiplets” (Intel 8-K Exhibit 99.1). No ship dates for products under the agreement have been announced.

Update: 10 June 2026. Nine days after the summit, the strain is already visible. The margin loan SoftBank wanted against its OpenAI stake has stalled: cut from $10 billion to $6 billion on lender hesitation, then stuck at roughly $5 billion. A loan against the marquee asset is supposed to be the easy money. All of it confirms what the headline number was hiding. Read on.

On the morning of June 1, 2026, in the gilded halls of Versailles, Emmanuel Macron told the assembled chief executives that this year’s Choose France summit would “crystallize a record amount of 93 billion euros of confirmed investments.”[1] The word that mattered was confirmed — confirmés. It is the word that turns a press release into a balance sheet, an intention into a number a finance minister can book.

Strip the SoftBank pledge out of the total, and the record disappears. The Japanese conglomerate’s commitment — up to €75 billion to build five gigawatts of AI data-center capacity across France — would be four-fifths of the headline on its own; even the firm tranche France’s own press counted into the total, €45 billion, is roughly half of it.[2] It is also the reason the number is a record at all: this single edition of Choose France exceeded the announced investment promises of the eight previous summits combined, which together totaled around €87 billion.[3] One pledge, from one company, made one summit larger than eight.

And that pledge is not €75 billion of confirmed money. By SoftBank’s own announcement, issued the day before the summit, only the first phase — €45 billion to deliver 3.1 gigawatts — is a commitment. The remaining €30 billion describes “additional sites” the company plans to develop.[4] The language shift inside a single press release, from “commitment” and “investment” to “plans,” is the whole story compressed into one document.

The last time Masayoshi Son stood beside a head of state and named a number this large, it was $500 billion. Sixteen months later, a fraction of one of its seven sites was running.

The anatomy of a record

A Choose France headline is not a measurement. It is a sum of commitment tiers, each with a different probability of becoming a building, presented to the cameras as a single figure. Disaggregate the €93 billion and five tiers separate cleanly: one firm, one a ceiling, one smaller but real, one barely more than a letter of intent, and one recycled from a previous summit.

At the firm end sits SoftBank’s €45 billion first phase — named sites, a named industrial partner in Schneider Electric, a developer in SB Energy, and a 2031 horizon.[5] This is the most concrete pledge at the summit, and it deserves to be treated as a real intent. Below it sits the €30 billion remainder of the SoftBank ceiling, which exists only as “plans for additional sites.” Below that sits a layer of genuine but smaller data-center commitments: Brookfield’s pledge, Nebius’s €8 billion site on a former Bridgestone plant at Béthune, an Ardian-Verne campus in the Paris region.[6] And below that sits the softest tier — capacity that is announced but not yet sited or committed: the MGX–Bpifrance “imminent selection of a second site,” worth around €7.5 billion, and a Revolut commitment contingent on the fintech obtaining a French banking license.[7][8]

The recycling is not a footnote to this structure; it is part of how the record was assembled. Brookfield’s France AI total is now quoted at €30 billion — but €20 billion of that was announced at the February 2025 AI Action Summit, the same event that produced the €109 billion headline; only €10 billion is new to this summit.[6] The MGX–Bpifrance money is the expansion of Campus AI, the Bpifrance–Mistral–MGX–Nvidia joint venture first unveiled at Choose France 2025, whose flagship campus at Fouju is still in early construction.[7] The €7.5 billion “doubles” a commitment that was itself last year’s announcement. Macron’s own framing conceded the pattern: the summit, he said, represented “20 billion invested, and 20 billion of AI investments as a follow-up to the summit in February.”[9] That February summit — the €109 billion AI Action Summit whose figure France never reconciled to disbursement — is being folded back into June’s total as “follow-up.”[10] A material share of this year’s record is last year’s record, counted again.

This is the Commitment-versus-Spend Gap, the analytical move that separates an announced figure from the capital that actually moves. Summit pledges do convert — France has led European foreign direct investment for years running, and Choose France is not a fiction. But they convert at a rate and with a lag that the headline never discloses, and the disaggregation above is why the headline and the eventual deployment are different numbers. At hyperscaler and sovereign-summit scale, the gap is not an anomaly to be explained away; it is the default structure of the announcement. The headline is the ceiling of what could happen. The filing, eventually, shows the floor of what did. The distance between them is where the analysis lives — and at Versailles, the distance is most of the number.

What the same pledge looks like sixteen months later

To price a SoftBank infrastructure pledge at the moment of announcement, you do not need a forecast. You need the last one.

On January 21, 2025, Son stood in the White House alongside Donald Trump, Sam Altman, and Larry Ellison to announce Stargate: $500 billion over four years to build AI data centers across the United States, with $100 billion to be deployed “immediately.”[11] SoftBank took financial responsibility, and Son took the chairmanship. The structure was familiar to anyone who had watched Son work: of the $500 billion, only around $52 billion was committed equity — roughly $19 billion each from SoftBank and OpenAI, around $7 billion each from Oracle and MGX. The other ninety percent was to come from debt and vendor financing, not yet arranged.[12] A mega-pledge, in the Son method, does not deploy existing capital. It opens a financing campaign.

Sixteen months on, the campaign’s results are measurable. Independent satellite analysis put the flagship Abilene, Texas campus at roughly 0.3 to 0.6 gigawatts operational by April 2026 — four of its eight buildings live — against a site target of 1.2 gigawatts and an announced program of ten.[13] The other six US sites were foundations and steel on 2028 timelines. One site of seven was partially energized; the rest were under construction.

Some of that gap is just physics: gigawatt data centers take three to five years to build, and measuring a ten-year program at month sixteen will always show a low number. Abilene, taken alone, is arguably ahead of a normal curve. So the conversion rate, in itself, is not the indictment. The indictment is what happened around it.

The vehicle itself barely functioned. By early 2026, Stargate LLC — the entity unveiled with such ceremony — had reportedly hired no staff and was developing no data centers; OpenAI had bypassed it for bilateral deals with Oracle, Amazon, and Google, and had come to treat the word “Stargate” as, in one executive’s framing, an umbrella term for its compute strategy rather than a company.[14] The Abilene flagship’s planned expansion was canceled in March 2026; the UK Stargate site was paused in April due to energy costs.[15]

None of this means that nothing was built. This is the point at which the skeptical version of the story has to be disciplined, because the booster version is partly true. Abilene is a genuine, operational AI campus running Nvidia hardware; thousands of tradespeople built it; major lenders — JPMorgan, a Newmark-led syndicate — genuinely closed billions in project finance against it.[16] The accurate claim is not that the money was fake. It is that conversion was slow, partial, debt-heavy, and routed around the very vehicle that gave the announcement its name.

The balance sheet behind the pledge

The deeper reason to discount the €75 billion is not SoftBank’s track record. It is SoftBank’s balance sheet, and specifically the distinction between the money SoftBank actually moves and the money it lends its name to.

SoftBank’s funded AI capital has gone almost entirely into one place: its equity position in OpenAI. It completed a $41 billion round in December 2025 for roughly an 11 percent stake, then in February 2026 agreed a further $30 billion that would bring the cumulative total to $64.6 billion and the stake to about 13 percent — a figure that is reached only when the follow-on completes, in tranches running to October 2026.[17] To fund it, SoftBank sold its entire Nvidia stake, shed T-Mobile shares, and drew on a $40 billion bridge facility, the first $10 billion of it borrowed in April 2026, with the facility’s fee structure deliberately escalating to punish slow repayment.[18]

By early 2026, the position had consequences a rating agency could not ignore. S&P revised SoftBank’s outlook to negative in March, affirming a BB+ rating already below investment grade and describing OpenAI as one of the group’s investments “with the weakest credit quality” — even as Moody’s held a stable view a notch lower, the disagreement itself is a measure of how contested the bet is.[19] Reported leverage was still inside SoftBank’s own 25 percent loan-to-value ceiling at the end of 2025, but the chief financial officer had publicly opened the door to exceeding it “temporarily,” and S&P warned the OpenAI follow-on could push leverage toward the 35 percent line that would trigger a downgrade. The shares fell roughly 45 percent from their October 2025 high; one bank labeled the company a “valuation trap”; and SoftBank paused a separate $50 billion acquisition to preserve capacity.[20]

The bull would correctly object that this is only the liability side. SoftBank also holds one of the most valuable single assets in technology — roughly 90 percent of Arm, a stake worth more than $150 billion at mid-2026 prices — plus some $45 billion in unrealized gains on the OpenAI position itself, and it has shown it can monetize on demand, having sold Nvidia and T-Mobile to raise cash. That is real, and it is the strongest case for SoftBank’s resilience. But it cuts toward the concentration problem, not away from it: by mid-2026, the Arm and OpenAI stakes together made up nearly two-thirds of SoftBank’s assets, and the Arm holding is already pledged — an $8.5 billion margin loan drawn against it, with room for more. The crown jewel is collateral. And the credit market noticed: SoftBank’s five-year credit-default swaps widened to an eleven-month high after the S&P action, the widest among major Japanese corporates — the cost of insuring its debt rising in step with the bet.[20]

There is a circularity worth naming. SoftBank is OpenAI’s largest outside backer and, through SB Energy, a builder of the data centers OpenAI will rent. In France, it would play both roles again: financing the anchor tenant and constructing the capacity that the tenant is expected to fill.

Here is what that balance sheet did not do: fund Stargate LLC. The roughly $19 billion equity tranche SoftBank pledged to the vehicle has no confirmation of ever having been wired, because the vehicle was bypassed.[21] The chief financial officer’s own description of the model is the tell: SoftBank makes an equity investment, but the project itself is “financed as project finance,” so its own commitment is “limited” and “should not be too huge.”[22] Stripped of the jargon: SoftBank lends its name and a sliver of equity, and someone else’s debt builds the thing. The capital that flowed to an actual Stargate site was a $500 million check into SB Energy for the Milam County build. The headline was $500 billion; SoftBank’s verified site-level equity was three orders of magnitude smaller.

This reframes what the French €45 billion actually is. It is not a promise that SoftBank will place €45 billion on its own books. It is a promise that SoftBank will supply catalytic equity and arrange project financing that does not yet exist — Son said as much at the podium, describing the venture as one SoftBank is “aggregating project financing” to fund, against demand from an anchor tenant not yet named, on a balance sheet already carrying the most concentrated single-name bet in the AI buildout.[22] The pledge’s deliverability is downstream of a financing structure that has to be assembled and of an OpenAI liquidity event — an IPO — that has to occur before the bridge facility is repaid. France controls none of those variables.

And here, the two halves of the story close together. Staged commitments and project finance are, on their own, unremarkable — every large data-center developer rings capex into phases and funds it with non-recourse debt, because that is cheaper than equity and isolates the risk. The question is never whether a pledge is staged; it is what the staging rests on. SoftBank will not put €75 billion of its own balance sheet behind this — the balance sheet just described could not absorb it on top of the OpenAI commitment — so it writes a €75 billion option instead: a headline ceiling, a smaller firm tranche, and project finance to be arranged later. What changes with leverage is not the structure but the margin for error within it. A cash-rich sponsor that stages a pledge can absorb a slipped tranche or a delayed financing; a sponsor whose crown jewel is already collateral, whose follow-on runs to October, and whose bridge presumes an IPO cannot.

The more strained the balance sheet, the larger and softer the number it can afford to announce, because softness is free and the announcement is the deliverable. To be precise about where the softness enters: not, mostly, with SoftBank. Its press release was scrupulous — “up to” €75 billion, a firm “€45 billion,” the rest explicitly “plans.” The recharacterization happened at the podium, when a phased pledge with one firm tranche became, in Macron’s telling, €93 billion “confirmed.” SoftBank disclosed an option. The summit booked it as cash.

What France actually brings, and what it doesn’t

The honest counterargument is that France is not Texas, and the difference favors the pledge. This deserves a fair hearing, because it is the strongest case for taking the €45 billion at close to face value.

France’s advantages are real and, unlike capital, not exportable. The grid is roughly 70 percent nuclear, France is, in most years, the world’s largest net electricity exporter, and industrial power prices sit well below those in much of Europe, with EDF long-term pricing around €70 per megawatt-hour from 2026.[23] For a buildout whose binding constraint is increasingly power rather than capital, that is a genuine structural edge, and it is why the first-phase sites cluster in Hauts-de-France near existing grid and nuclear infrastructure, including a former coal site at Bouchain where EDF is the named development partner.[24] It also matters that the prior SoftBank pledges failed precisely on the variable that France has solved: the Saudi solar plan had no offtaker, and the UK Stargate site was paused due to energy costs. France removes the constraint that killed those. If any SoftBank data-center pledge converts close to schedule, the case for this one is better than most — and that concession should be granted in full.

But cheap power is necessary, not sufficient, and it is not the variable that has stalled the buildout this year. What stalled Stargate was not the price of electricity; it was demand discipline and financing — a canceled expansion, a paused site, a vehicle that never funded. France solves the kilowatt-hour. It does not supply the anchor tenant, the assembled debt, or the balance-sheet capacity, and those are the three things the precedent says actually bind. Power is the one layer of the stack that France owns, and it is the bottom layer. Above the kilowatt-hour, the French buildout is foreign at every tier. The capital is Japanese. The chips are American — Nvidia silicon, subject to American export jurisdiction. The most likely offtaker of five gigawatts of French inference and training capacity is American, because the anchor tenant SoftBank builds for is OpenAI, and no European anchor of remotely comparable demand has been named.[25]

Macron said the summit would make France “the leading country hosting data centers and computing capacity in Europe,” and that the country was “closing the gap we had in computing capacity.”[26] Both claims may even come true. But hosting capacity and owning intelligence are different sovereignties, and the gap that closes is the one measured in megawatts, not models. This is the substrate-state position, normally diagnosed in Southeast Asian economies that host hyperscaler data centers without owning any layer of the intelligence that runs on them. It is striking to find a G7 economy with a world-class research base occupying the same structural slot — providing the physical inputs and importing everything above it. The fair counter is that substrate can be a first rung rather than a ceiling: Taiwan and South Korea became chip powers partly by first hosting foreign firms’ manufacturing, and a country cannot build the intelligence layer on capacity it never built. Hosting compute you don’t yet own can be a deliberate developmental bet. But the bet only pays off if value accrues locally over time — if the substrate becomes a ladder.

The SoftBank pledge is built the other way: a foreign sponsor, foreign chips, and a most-likely-foreign tenant, with no disclosed mechanism for the intelligence layer to be handed over to French hands. It is a substrate as a destination, not a substrate as a rung.

There are two genuine exceptions inside the broader French buildout, and honesty requires naming both — because they sharpen the point rather than soften it. The first is Campus AI, the joint venture whose expansion supplied the €7.5 billion tier; its French AI champion, Mistral, secured up to 200 megawatts of capacity there, announced the same day as the summit.[7] But Mistral’s role in Campus AI is principally that of shareholder and board member; the project’s own coordinator described the startup as a “preferred” future client while conceding that, for now, “nothing has yet been done” on a binding tenancy.[7] Campus AI’s own president framed the stakes in terms that could serve as this article’s thesis: the test, he said, is that “every gigawatt must grow value in France, and not simply pass through it.”[7] The second exception, and the more real one, is Mistral’s own data center at Bruyères-le-Châtel — its first debt-financed build, totaling $830 million for roughly 13,800 Nvidia chips and about 44 megawatts of capacity.[27] That is the genuine article: a French company owning its own compute.

And its scale is the whole argument in one number. Forty-four megawatts of sovereign French compute, against SoftBank’s 3,100-megawatt first phase. The champion’s owned infrastructure is roughly 1% of the substrate that the country provides for someone else’s use. For the marquee number — five gigawatts — there is no French anchor. The grid is the moat, and nearly everything it powers belongs to someone else. And even the grid advantage is contingent on RTE, the French grid operator, actually delivering 3.1 gigawatts of new connection capacity to three specific sites by 2031 — an unprecedented load addition on a timeline that grid-connection history does not obviously support, and that no signed connection agreement has yet confirmed.[28]

What would have to be true

The thesis is falsifiable, and it is worth stating the conditions plainly, because they are also the things a serious investor should watch. And there is someone who should watch. An option-shaped pledge harms no one if everyone prices it as an option — but it is not being priced that way. It is being booked as a record by a government building industrial-policy narrative on it, cited by analysts pricing “France is Europe’s AI hub” into datacenter REITs and French-exposure allocations, and folded into the case for a SoftBank credit that already trades below investment grade. The reader who needs the disaggregation is the one about to treat €93 billion of intention as €93 billion of capital.

The skeptical reading is wrong if, within roughly twelve months, SoftBank secures binding project financing — not a memorandum — for at least the Dunkirk site; if a named anchor tenant or binding offtake agreement appears; if an executed lease replaces “preferred bidder” status at Bouchain; and if the OpenAI IPO closes cleanly enough to let SoftBank refinance the March 2027 bridge without forced asset sales. If those happen, the €45 billion converts, and the substrate-state critique becomes a quibble about who owns the value rather than whether the buildings exist.

The thesis is confirmed if the tells repeat: financing perpetually “being assembled,” capacity that “can scale to” rather than “will reach,” a first-operations date that slips past 2028, no anchor tenant disclosed by 2027, a further S&P action, or the same “pause” language that appeared over the UK site in April.

Which is the precise thing the word confirmés was chosen to obscure. Macron did not announce €93 billion of investment. He announced €93 billion of intention, of which the largest single component is a ceiling, two-fifths of that ceiling is merely a plan, and the firm remainder rests on a balance sheet betting its credit rating on a single American startup’s path to an IPO. The number is not false. It is an option — priced, and presented, as a certainty.

Notes

[1]: Emmanuel Macron, remarks at the Choose France summit, Versailles, June 1, 2026: “Cette édition de Choose France à elle seule va permettre de cristalliser un montant record de 93 milliards d’euros d’investissements confirmés.” Reported by franceinfo, June 1, 2026; quote also carried verbatim by Euronews FR. The €93 billion figure spans 71 projects and a French-government-stated ~15,600 jobs; it is an announcer-claimed forward figure, not an audited outcome.

[2]: SoftBank Group Corp., “SoftBank Group to Build 5 GW of AI Data Center Capacity in France,” press release, May 30, 2026. The €75 billion figure is stated as “up to.”

[3]: franceinfo, June 1, 2026, reporting that the single 2026 edition exceeded the cumulative announced totals of the prior eight Choose France editions (~€87 billion combined). Prior editions per Élysée/Business France press dossiers (2023 dossier, diplomatie.gouv.fr): 2023 ~€13B; 2024 ~€15B; 2025 stated variously as ~€20B (Macron, 2026 framing) and €40.8B (2025 press dossier) — the moving baseline is noted as itself indicative of headline elasticity.

[4]: SoftBank press release, May 30, 2026: the first phase is described as “an initial €45 billion investment to deliver 3.1 GW”; subsequent capacity is described as the company “also plans to develop additional sites across France.” The shift in verb from “investment/commitment” to “plans” is within the same document.

[5]: SoftBank press release, May 30, 2026. Named first-phase sites: Dunkirk (Loon-Plage), Bosquel, and Bouchain, all in Hauts-de-France; Schneider Electric named as strategic partner (robotized manufacturing at Dunkirk); SB Energy as developer; first operations targeted 2028, full phase by 2031. Per a separate SoftBank announcement (reported by TechRepublic, June 2026), the Bosquel ~1 GW site is structured as a majority-SoftBank joint venture with Sesterce — i.e. even within the “firm” first phase, the capital structure is partly third-party, not pure SoftBank balance sheet.

[6]: Smaller data-center tier, per Choose France 2026 reporting (Le Monde Informatique, Le Journal des Entreprises, Silicon.fr, June 1, 2026): Brookfield €10B at Escaudain (Nord), with Data4, for a ~1 GW datacenter, bringing its stated France AI total to €30B — of which €20B was announced at the February 2025 AI Action Summit (Brookfield press release, Feb 10, 2025: €15B via Data4 + €5B associated infrastructure, delivery by 2030), so only €10B is new to the 2026 summit. Nebius ~€8B / 240 MW on the former Bridgestone site at Béthune. Ardian/Verne ~€5B for a 500 MW Île-de-France campus, full 500 MW capacity targeted only 2035–2037, itself the first tranche of a broader ~€10B / 1 GW French consortium (Ardian, Iliad, EDF, Orange, Scaleway). Figures are announcer-claimed; several were pre-trailed by Les Echos and final terms may differ.

[7]: MGX–Bpifrance ~€7.5B is the national expansion of Campus AI, the joint venture of Bpifrance, Mistral AI, MGX (UAE), and Nvidia, first announced at Choose France 2025 (May 19, 2025) to build “Europe’s largest AI Campus” (flagship ~1.4 GW, Paris region). Per the Bpifrance press release (June 1, 2026), the expansion targets up to 3 GW nationally and the ~€7.5B second-site selection “doubles the consortium’s initial investment”; the second site selection is described as “imminent,” not yet committed. The flagship campus at Fouju (Seine-et-Marne) was reported still in early construction (”foundations laid, main site not yet begun”) as of April 2026; the flagship’s secured first tranche is reported at ~€8.5B (Le Figaro), a separate figure from the €7.5B second-site expansion. Campus AI is the one summit pledge with a French intelligence-layer anchor (Mistral); the substrate-state exception is noted in the body. The Campus AI president quoted in the body is Thibaud Desfossés (”chaque gigawatt doit faire fructifier la valeur en France, et non simplement la traverser”), per the Bpifrance press release.

[8]: Revolut’s ~€1B France commitment was reported as contingent on the firm obtaining a French/EU banking licence.

[9]: Emmanuel Macron, remarks reported by Reuters, June 1, 2026: characterizing the AI-related portion as “20 billion invested, and 20 billion of AI investments as a follow-up to the summit in February.” Verify verbatim French against the Élysée transcript before publication.

[10]: The February 2025 AI Action Summit in Paris produced a ~€109 billion headline; France published no public reconciliation of that figure to authorized, appropriated, or disbursed capital. See “The King’s New Datacenters” (The AI Realist, March 25, 2026), which audited the €109B pledge to an honest near-term figure of roughly €25B.

[11]: OpenAI, “Announcing The Stargate Project,” January 21, 2025; announced at the White House with President Trump, Sam Altman, Larry Ellison, and Masayoshi Son. Headline: “$500 billion over the next four years … We will begin deploying $100 billion immediately.” Son named chairman.

[12]: Reported equity structure (The Information; corroborated by Bloomberg, WSJ): ~$52B committed equity against the $500B headline — roughly $19B each SoftBank and OpenAI, ~$7B each Oracle and MGX — implying ~90% of the program was to be debt- and vendor-financed and not yet arranged at announcement. WSJ reported SoftBank’s equity share could be as low as ~10%.

[13]: Epoch AI, “OpenAI Stargate: where the US sites stand”, satellite-imagery analysis, April 17, 2026: Abilene operational at ~0.3 GW (April 17 reading; a later cached version of the same page shows ~0.6 GW), ~4 of 8 buildings live, against a 1.2 GW site target; Epoch projects the program to “exceed 9 gigawatts by 2029” versus the $500B/10 GW headline announced January 2025; six other US sites in early construction on ~Q4 2028 timelines. “Operational” capacity is satellite-verified (Airbus DS imagery); OpenAI’s “nearly 7 GW planned / $400B+ over three years” figures (five-new-sites announcement, Sept/Oct 2025: https://openai.com/index/five-new-stargate-sites/) are announcer-claimed. The Abilene ~600 MW expansion was redirected, with Microsoft taking the adjacent 900 MW Crusoe site.

[14]: Reporting by The Information, corroborated by Bloomberg and the Financial Times (early–April 2026): Stargate LLC had hired no staff and was developing no data centers; OpenAI pursued bilateral capacity deals (Oracle ~$300B/4.5 GW, plus AWS, Google Cloud) and treated “Stargate” as an umbrella term for its compute strategy. Bloomberg (Aug 7, 2025) earlier reported CFO Yoshimitsu Goto conceding the effort was “taking longer than anticipated.”

[15]: Abilene expansion (~600 MW) cancelled: Bloomberg, March 6, 2026 (Microsoft took the adjacent Crusoe capacity). Stargate UK paused: Bloomberg, April 9, 2026, citing energy costs.

[16]: Abilene construction: Crusoe/Oracle; JPMorgan project-finance facility (~$2.3B, May 2025) and a Newmark-led syndicate (~$7.1B); Nvidia GB200 racks installed from mid-2025; Ellison stated an ultimate target above 450,000 GB200 GPUs under a 15-year Oracle lease. These are real, closed commitments and are cited to discipline the “headline is empty” overclaim.

[17]: SoftBank completed a $41B OpenAI round in December 2025 for ~11% (comprising ~$30B from SoftBank Vision Fund 2 plus ~$11B syndicated co-investment); on February 27, 2026 it agreed a further $30B follow-on (SoftBank Group Corp. press release), funded through Vision Fund 2 as part of OpenAI’s ~$110B round (the largest private funding round on record, valuing OpenAI at ~$852B), bringing cumulative investment to an expected $64.6B and ~13% stake “upon completion,” subject to closing conditions. The follow-on is staged: first $10B tranche executed April 1, 2026; further $10B tranches scheduled July 1 and October 1, 2026 (SoftBank Group Corp. press release, April 1, 2026). As of the June 1 summit, the $64.6B figure is therefore expected-on-completion, not a settled position.

[18]: Funding via disposal of SoftBank’s entire Nvidia stake (~$5.83B, October 2025) and T-Mobile shares; $40B bridge facility signed March 27, 2026, with the first $10B drawn April 1, 2026 (SoftBank Group Corp. press release). The facility is unsecured and full recourse to SoftBank, with no OpenAI shares or Arm stake pledged as collateral; per IFR / loan syndication reporting, the margin starts at 250bp over SOFR and steps up by 17.5bp from July through end-September 2026, a structure designed to incentivise an early takeout via bonds or term loans ahead of an expected OpenAI IPO (widely reported as targeted for late 2026 / as early as Q4 2026; the 12-month tenor, maturing ~March 25–26, 2027, is read by lenders as a bet on that listing). A separate ~$10B margin loan (arranged by Goldman Sachs, JP Morgan, Mizuho; two-year facility with one-year extension, limited recourse) is distinct from the bridge; SoftBank subsequently scaled this facility back toward as little as ~$6B after creditor hesitation (Bloomberg, via Fortune) — a direct signal of the financing strain the body describes. MST Financial’s David Gibson, via the Financial Times, estimated SoftBank faces “[an estimated] $50bn ... of funding, between OpenAI, investments and refinancing” to arrange over the course of 2026; OpenAI is not expected to reach profitability until 2030.

[19]: S&P Global Ratings, action reported March 2026 (S&P statement via Bloomberg; B-tier link to wire coverage of the agency statement): outlook revised to negative, BB+ affirmed (below investment grade), OpenAI described as “one of its investments with the weakest credit quality”; S&P also flagged the unlisted-asset proportion rising above 50% (from 42%) and warned the $30B follow-on could push leverage toward the 35% level that would trigger a downgrade. Moody’s held SoftBank at Ba2/stable (2025 upgrade). The agency divergence is presented to avoid cherry-picking the bearish view; both keep SoftBank below investment grade.

[20]: SoftBank’s reported loan-to-value ratio was 20.6% at end-December 2025, within its stated financial policy (LTV managed below 25% in normal conditions, 35% emergency ceiling; SoftBank Group Corp. disclosure). CFO Yoshimitsu Goto told the Financial Times (March 2026) the group “does not rule out” temporarily exceeding 25%. ADR down ~45% from its October 2025 high by late March 2026; Jefferies downgraded to “Underperform,” calling the company a “valuation trap”; SoftBank paused a separate ~$50B acquisition (Switch). The piece does not claim the 25% ceiling was breached as of publication — only that the CFO opened the door and S&P flagged the trajectory.

[21]: No A-tier source confirms SoftBank’s ~$19B Stargate LLC equity tranche was wired; reporting (The Information, Bloomberg, FT) indicates the JV was bypassed in favor of bilateral deals. Bloomberg Intelligence estimated SoftBank’s actual Stargate cash requirement nearer ~$40B “given its less-active-than-expected participation” — an estimate, not a disclosure.

[22]: Yoshimitsu Goto, SoftBank Q3 FY2025 earnings call, February 12, 2026 (translated remarks): SoftBank makes an equity investment while the project itself is financed as project finance, so SoftBank’s own size is “limited” and the amount “should not be too huge.” Verify exact translated wording against the SoftBank transcript before publication. Son corroborated the same structure at the Choose France podium, stating SoftBank is “aggregating project financing” for the French venture and that the figure “balloons to roughly $750 billion once the broader system is factored in” (CNBC, June 1, 2026) — the announcer himself confirming both that the financing is not yet assembled and that the headline expands on a “broader-system” basis.

[23]: French grid: ~70% nuclear share of generation; France the largest net electricity exporter in Europe/globally in most years (RTE/IEA data — cite data year at fact-check). Note the 2022 exception: amid widespread reactor-corrosion outages France was briefly a net importer, which is why the body says “in most years.” EDF long-term industrial pricing ~€70/MWh from 2026 per the post-ARENH framework. Replace paraphrase with primary RTE/CRE figures and the specific data year before publication.

[24]: SoftBank press release, May 30, 2026; Bouchain former coal-plant site with EDF as named development partner (described at “preferred bidder/due diligence” stage). Grid-proximity rationale for the Hauts-de-France cluster per company and regional (CC2SO/RTE) materials; Bosquel reported ramping 240 MW → ~1 GW → 1.4 GW per regional authority citing RTE.

[25]: No anchor tenant was named in the SoftBank announcement. The substrate-state characterization (Japanese capital, US chips, likely-US offtake) is an analytical inference from SoftBank’s OpenAI relationship, not a stated offtake agreement; flagged as inference.

[26]: Emmanuel Macron, remarks from the Élysée, June 1, 2026, reported by regional French press (mesinfos/La Semaine de l’Île-de-France): aim to make France “le premier pays accueillant des centres de données et des capacités de calcul en Europe” and “Nous sommes clairement en train de combler le retard que nous avions en matière de capacités de calcul en Europe.” Verify against the Élysée transcript before publication.

[27]: Mistral AI raised $830M in debt financing (its first debt raise since founding) from a seven-bank consortium (incl. BNP Paribas, Crédit Agricole CIB, HSBC, MUFG) to acquire ~13,800 Nvidia GB300 chips for a data center at Bruyères-le-Châtel (Essonne), ~44 MW, operational expected Q2 2026 (TechCrunch, March 30, 2026; also Reuters, CNBC). Separately, on June 1, 2026, Bpifrance announced Mistral secured up to 200 MW of capacity with Campus AI (Bpifrance press release); the Campus AI project coordinator (L’Usine Nouvelle) described Mistral as a “preferred” future client and board member/shareholder while stating no binding tenancy was yet concluded — the distinction between equity partner and committed offtaker is preserved in the body. Scale contrast: ~44 MW of Mistral-owned compute vs. SoftBank’s 3,100 MW first phase.

[28]: RTE 3.1 GW connection feasibility to Dunkirk/Bosquel/Bouchain by 2031: no published binding confirmation as of publication. CRE fast-track connection regime (deliberation 2025-120) implies multi-year (≈3–4 year) connection timelines even when expedited. Press-release language on “abundant, decarbonised electricity” is political framing, not a signed connection agreement.

[29]: SoftBank pledge precedents: (a) December 2016 Trump Tower “$50B / 50,000 jobs,” drawn from the forming Vision Fund, with ~half of deployed capital flowing into WeWork (peak ~$47B valuation; 2023 bankruptcy) — Axios retrospective; (b) March 2018 Saudi PIF “$200B / 200 GW” solar MOU, shelved by ~September 2018 (WSJ); (c) Vision Fund 2 ($108B target, ultimately run largely on ~$38B of SoftBank’s own capital). Each: a head-of-state-adjacent headline converting to a fraction of announced, slower, and structurally different capital. France-specific conversion claims are forecasts based on this precedent, not observed outcomes.

On May 29, a deputy from the president’s party named Éric Bothorel filed twelve amendments to a copyright bill. Three more came from his Renaissance colleague Prisca Thévenot. All fifteen landed the same Friday, three days before the Assembly’s culture commission was due to examine the text, and all fifteen failed the following Tuesday.[1] Asked where the measures came from, Bothorel told Le Point that some had been soufflés par Mistral — whispered by Mistral.[2]

That sentence is the one this newsletter spent four thousand words predicting last week.

“Lobby, Levy, Legislate” argued that Mistral’s moat is not sovereignty or model quality but access: the French president’s contact list, which Arthur Mensch is working to convert into formal law before the 2027 election changes who answers the phone.[3] That was an inference from the customer roster and the lobbying pattern. It did not name this bill; it named the move. A week later, a legislator in the governing party put the move on the public record.

The bill itself is narrow. Proposition de loi n° 2634, adopted by the Senate, would install a présomption d’utilisation: a presumption that an AI provider trained on protected cultural works, unless the provider can document otherwise.[4] It reverses the burden of proof. Today, an author has to prove their work was scraped; under the text, the company has to show what went into the model. The French government’s own civic portal describes it in one line: the bill reverses the burden of proof. [5]

The amendments tell you whom that threatens. One of Bothorel’s amendments inserts two words, de modèles, after “fournisseurs,” narrowing the bill so it binds only model-builders and exempts the French firms that merely deploy AI downstream — the corporates that fill Mistral’s customer list. Its justification is not commercial. It is sovereign: a broad scope, the amendment argues, would halt the sector’s growth and our digital sovereignty. [6] Another strikes the retroactivity clause, reciting the industry’s standard line that documenting training data demands complex technical adaptations. [7] A third went after the bill’s title.[8] Filing amendments against a bill is ordinary politics; a legislator admitting the affected company drafted them is not. The sovereignty argument, deployed to reshape a copyright statute, in the pen of the president’s party. This is not yet the procurement law the long-form predicted — it is the same access doing the simpler job first: shielding the customer list from a bill before writing the law that entrenches it.

Emmanuel Maurel, the deputy carrying the text, attributed the pressure to “certains anciens ministres du bloc central” — former central-bloc ministers now working the building.[9] Readers of the long-form will recognize the address. The piece built its second act on one such figure: Cédric O, the former secretary of state for digital affairs who became a Mistral shareholder and adviser.[3] Maurel, with no framework to grind, arrived at the same door.

The calendar rhymes, too. Yaël Braun-Pivet, the Assembly’s president, received Mensch on May 7. Five days later, the panel that sets the Assembly’s agenda drew up the lineup for a cross-party session and left the copyright bill off it.[10] The Assembly says the meeting was routine. The sequence stands regardless.

Last week’s piece closed on “a calendar that runs out in eighteen months.” This week sharpens why the calendar matters. The lobbying is not the behavior of a company that thinks it has time; it is the behavior of one racing against a deadline. Fifteen amendments filed in a single afternoon are the president’s party spending its access while the access still exists.

There is one scenario where the clock resets: Gabriel Attal. The former prime minister has made AI a central plank of his campaign, vowing to turn France into “la patrie de l’IA,” and a macroniste successor in the Élysée would keep the contact list warm.[11] But Attal is not the favorite, by far. A moat that depends on a trailing candidate is a moat with an expiry date. The base case is the one the long-form named: the access leaves with the administration that built it. That is why Mistral is not waiting. You do not whisper fifteen amendments into a friendly deputy’s hand if you expect the friendly deputies to still be there in three years.

The commission turned back all fifteen, and the bill survived the room. But the surviving committee is not a passage. The text now sits last in the running order of a reserved day claimed by a small opposition group, a slot it may never reach; if it advances with amendments attached, it returns to the Senate to die of scheduling.[12] Mistral does not need to defeat this bill. It needs the bill to never finish, and it has a governing party willing to file amendments to buy time.

Still, time is the one thing Mistral cannot lobby for. The president, whose contact list is the moat, is term-limited and polling in the low twenties; in 2027, he leaves, and the phone Mensch has been calling stops being his to answer.[13] The amendments filed in a single afternoon are not the work of a winning company. They are the work of one racing to pour its access into law before the access walks out of the Élysée. Strip the sovereignty language, and the structure is plain crony capitalism: a national champion whose valuation, customer base, and inner circle of former ministers are all underwritten by one man’s term in office.[3]

The lobbying was the visible part. The confession was the story. The clock is the verdict. Macron’s days are numbered, and everyone on his contact list is counting down with him.

Notes

[1]: Amendments to Proposition de loi n° 2634, Commission des affaires culturelles et de l’éducation, Assemblée nationale. Of sixteen amendments examined June 2, 2026, twelve were filed by M. Éric Bothorel and three by Mme Prisca Thévenot (both groupe Ensemble pour la République); one, by Mme Véronique Ludmann (Horizons), was withdrawn. All were deposited May 29, 2026 and rejected or withdrawn June 2. Amendment list and authors, Assemblée nationale.

[2]: Thomas Graindorge, “« Je n’ai jamais vu un lobbying de cette puissance » : à l’Assemblée, la bataille de Mistral contre le droit d’auteur,” Le Point, June 1, 2026. Éric Bothorel quoted acknowledging certain measures were “soufflés par Mistral.” Erwan Balanant (Les Démocrates) is quoted in the same piece: “Je n’ai jamais vu un lobbying de cette puissance-là sur les domaines culturels.”

[3]: “The President’s Customer List,” The AI Realist, May 2026. The Cédric O biographical detail — his role as Mistral shareholder and adviser following his tenure as secretary of state for digital affairs — is sourced there.

[4]: Proposition de loi relative à l’instauration d’une présomption d’utilisation des contenus culturels par les fournisseurs d’intelligence artificielle, n° 2634, adopted by the Sénat (unanimously) April 8, 2026. Commission text n° 2864-A0 deposited at the Assemblée June 2, 2026. Note: the Sénat title used “présomption d’exploitation”; the version examined at the Assemblée reads “présomption d’utilisation.”

[5]: Vie publique (Direction de l’information légale et administrative), notice of April 10, 2026: the bill “renverse la charge de la preuve de l’utilisation de contenus culturels par les fournisseurs d’IA.”

[6]: Amendement n° AC2, M. Éric Bothorel, Commission des affaires culturelles, rejected June 2, 2026: “À l’alinéa 4, après le mot « fournisseurs » insérer les mots « de modèles ».” Exposé sommaire: “Un champ d’application trop large et non justifié du texte […] mettrait un coup d’arrêt à l’essor du secteur et à notre souveraineté numérique.” The amendment also cites the Munich Regional Court ruling GEMA v. OpenAI (November 11, 2025) — the same enforcement action analyzed in “Register, Disclose, Pay.”

[7]: Amendement n° AC10, M. Éric Bothorel: “Supprimer l’alinéa 5,” removing retroactive application to pending litigation, on the grounds that transparency and traceability compliance requires “des adaptations techniques complexes” that cannot be applied retroactively.

[8]: Amendement n° AC3, M. Éric Bothorel, targeting the bill’s title (TITRE).

[9]: Maurel quote per Le Point (note 2). Maurel, the GDR rapporteur, has publicly championed the text alongside the collecting societies Adami, SACD, and ADAGP.

[10]: Braun-Pivet–Mensch meeting (May 7) per Le Point (note 2). The bill’s absence from the agenda set by the May 12 Conférence des présidents is corroborated by “IA : pas de proposition de loi sur le droit d’auteur à l’ordre du jour de l’Assemblée nationale,” Le Monde, May 12, 2026, and by Décideurs Juridiques, May 12, 2026.

[11]: Gabriel Attal, first major campaign rally, May 29, 2026, per Le Point (note 2), which reports his ambition to make France “la patrie de l’IA” and attributes to him an effort to slow the text. Direct-quote wording to be confirmed against the rally transcript before syndication.

[12]: Procedural posture per Le Point (note 2): the text is placed last in the GDR niche order of June 11; amendments lengthen hémicycle debate and, if adopted, force a return to the Sénat for a conforming vote.

[13]: Emmanuel Macron, in his second consecutive term, is barred by Article 6 of the French Constitution from seeking a third; his mandate ends in 2027. His approval stood in the low twenties as of May 2026 (Ipsos, Elabe, and Morning Consult tracking polls), as detailed in “The President’s Customer List” (note 3).

On May 27, asked at Meta’s annual shareholder meeting whether the company would ever take on Amazon, Microsoft, and Google in cloud computing, Mark Zuckerberg said the idea was “definitely on the table.” [1] Then he added the qualifier that matters more than the headline: Meta hasn’t rented out compute “because we think that we have a use for the compute,” and a cloud business becomes an option only “if we get to a point where we feel that we have overbuilt.” [2]

Read that again with the calendar open. Five weeks earlier, on April 24, Meta had signed a deal making it one of the largest customers in the world for Amazon’s Graviton processors — renting compute capacity from a direct competitor’s cloud, explicitly to get access to the silicon it needs now without waiting on its own data centers. [3] So in the same quarter, the only one of the four U.S. hyperscalers that does not sell cloud services [4] was simultaneously a major buyer of someone else’s compute and a prospective seller of its own. Short and long, on the same balance sheet, at the same time.

That is the contradiction worth chasing. Everyone in AI is supposedly starved for compute — GPUs backordered for months, Amazon’s own training chips shipping slower than it can build them, North American data-center vacancy at 1.4% at the end of 2025. [5] And here is the company building more of it than anyone, raising the possibility that it might have too much. Where does “excess capacity” come from in a world that can’t get enough?

The claim: a put, not a pivot

The answer is that “excess” and “scarcity” are not opposites here. They are the same condition seen from two ends of a balance sheet — and which end you look from determines how you should price Meta.

Meta’s cloud remark is not a product strategy. It is a put option on its own buildout. And the interesting question is whether to read that option as fragility or as optionality. Both readings are live. Both are defensible from the same numbers. The piece that follows is about which one the evidence favors, and why the remark itself is the tell.

The numbers frame the tension. Meta raised its 2026 capital-expenditure guidance to $125-$145 billion, up from a prior range of $115–$ 135 billion, citing higher component prices and “additional data center costs to support future year capacity.” [6] As much as double what it spent in 2025, and even at the floor, more than 2024 and 2025 combined. [7] Yet first-quarter capex came in at just $19.84 billion — below the $27.57 billion analysts expected. [8] The company spent modestly and guided enormously in the same breath, and the market punished the guidance, not the spend: the stock fell roughly 7%. [9]

The exposure is not in what Meta has spent but in what it has promised to spend. The first-quarter filing carries $237.67 billion in non-cancelable contractual commitments — mostly third-party cloud capacity, servers, network infrastructure, and data centers — against $81.18 billion of cash and marketable securities. [10] Separately, it disclosed $182.88 billion of leases not yet commenced, consisting of data centers, colocations, and network infrastructure that begin between now and 2036. [11] The commitment line jumped by $107 billion in the quarter alone, which chief financial officer Susan Li attributed to multiyear cloud deals and infrastructure purchase agreements. [12] The overbuild, if there is one, does not live in trailing capex. It lives in the contracts — and contracts do not flex when demand disappoints.

The first reading — call it the Overbuild Put — holds that Meta is stacking every available lever to make a buildout look affordable whose paying customer it has not yet secured, and that the cloud remark is the final lever: a backstop buyer of last resort for capacity its own products may not fill. The second reading — call it Scarcity Builds the Glut — holds that the overbuild is rational, that an advertising machine of staggering profitability is funding it from cash, that scarcity is real and the surplus will be absorbed, and that the cloud option is genuine upside rather than a distress signal. The rest of this piece develops both, then resolves them.

The mechanism: four levers and a backstop

Start with the paradox, because resolving it is the whole argument.

The compute Meta is renting from Amazon, and the compute it is building is not the same as the compute it is renting. The Graviton deal brings tens of millions of Arm-based CPU cores into Meta’s portfolio — general-purpose silicon suited to agentic inference, the workload that runs after a model is trained, and available immediately. [3] Hyperion, Meta’s flagship campus in Richland Parish, Louisiana, is a five-gigawatt site built for the next generation of frontier training, and it does not come online until 2029. [13] Different silicon, different workload, different clock. Meta is short on the inference capacity it needs this year and long on the training capacity it has committed to for the end of the decade.

That gap — between capacity contracted years ahead and demand demonstrated today — is where “excess” is manufactured. And it is manufactured by the very scarcity panic that justifies the spending. Racing a feared shortage, you commit to gigawatts that arrive in giant, indivisible blocks long before the workloads exist to fill them. The scarcity is what produces the glut. They are the same phenomenon.

Meta’s own answer is that the gap is illusory — that the committed capacity is precisely the inference base it needs to put personal and business agents in front of billions of users, as Li told the call. [14] That may prove right. It is also exactly the demand that has to materialize on schedule for the contracts to pay, and a backstop is what a management team names when it wants insurance against its own forecast.

Now the affordability levers — each of them legal, disclosed, and used across the industry. The question is never whether any one of them is permissible; it is what they add up to. The buildout only proceeds if it can be made to look cheaper than it is.

The first lever is the off-balance-sheet vehicle. Meta financed Hyperion through a joint venture with Blue Owl Capital — Blue Owl owns 80%, Meta 20% — funding construction through a special-purpose vehicle (SPV), Beignet Investor, that raised roughly $27 billion of debt against about $2.5 billion of equity: close to $30 billion in total, the largest private-credit data-center deal on record. [15] The structure keeps the debt off Meta’s books, and the price of that engineering shows in the terms. The bonds, rated A+ by a single agency on the strength of Meta’s backing, priced at a 6.58% yield — roughly 225 basis points over Treasuries, wider than Meta’s own senior notes pay despite the identical credit standing behind them, the premium a charge for the off-balance-sheet structure, and the 24-year tenor — and mature in 2049. [16] This is not a one-off but a template. A second vehicle follows the same logic: a roughly $13 billion structure for a gigawatt campus in El Paso, leaning on the same thin-equity, debt-heavy capitalization that is wildly insufficient if the workloads stall. [17][18] One detail in that deal is its own signal — it has no anchor lender, leaving the banks to syndicate the debt into capital markets rather than place it with a single committed buyer. [17] And these vehicles sit on top of, not instead of, the $58.75 billion of senior notes already on Meta’s own balance sheet. [19]

The second lever is the lease itself. To keep the rating agencies from treating the arrangement as debt, Meta structured the Hyperion lease on a four-year renewable term — short enough that the obligation need not be consolidated onto the balance sheet as a single long-term liability. [20] The debt is real; it simply does not appear where a casual reader of the 10-K would expect to find it.

The third lever is depreciation. Effective January 1, 2025, Meta extended the estimated useful life of a subset of its servers and network equipment to 5.5 years, a change it disclosed would reduce full-year 2025 depreciation expense by approximately $2.9 billion. [21] Lower depreciation flows straight to reported operating income without changing a dollar of cash. The timing is the point: Meta stretched the assumed life of its hardware precisely as it ramped the buildout, flattering the income statement at the moment the spending most needed flattering. The contrast with Amazon is exact. In the same window, Amazon shortened the useful life of a subset of its servers to five years, explicitly citing the rapid pace of AI innovation. [22] Two companies, one hardware reality, opposite accounting choices — and Meta picked the one that defers the reckoning. Michael Burry’s public broadside in late 2025, estimating roughly $176 billion of industry-wide understated depreciation between 2026 and 2028, is the bear case for that choice arriving on schedule. [23]

The defense is real: a GPU’s economic life does cascade — from frontier training down to cheaper inference and eventual resale — so a longer book life can be honest rather than cosmetic. But the cascade has to land somewhere. It presumes a profitable second use for silicon Meta has finished training on, and that second use is either internal inference demand or an outside renter. The depreciation assumption and the cloud option are the same bet wearing different clothes.

The fourth lever is the one Zuckerberg named out loud. Each of the first three makes the buildout look affordable; none makes it pay. The vehicles, the lease slicing, the stretched depreciation all assume the same thing — that the compute, once built, generates revenue. The financing analyst on the Hyperion deal said it plainly: Meta has to build the thing, “put workloads in it,” and operate on the presumption that it will monetize those loads later. [24] The cloud option is the answer to the question every other lever begs. If Meta’s own products do not fill the capacity, Meta rents it to someone whose products will — and the debt gets serviced either way. That is what a put is: the right to sell the underlying when you no longer want to hold it.

This is why the Commitment-versus-Spend gap matters so much. A company that has spent $19.84 billion against $237.67 billion in commitments is not yet overbuilt. [8][10] It is contracted to overbuild, with the spending back-loaded and the demand unproven. The cloud remark is what a management team says when it can see the gap between the contracts it has signed and the demand it can document, and wants the market — and the credit market in particular — to know there is an exit.

The strongest objection is that this is simply how the cloud business was born. AWS grew out of Amazon’s own internal slack in 2006: build for yourself, find you have spare capacity, rent it out. Selling the excess is not a red flag — it is the canonical path to the most lucrative franchise in enterprise computing. The distinction is sequence and leverage. Amazon converted capacity it already owned into a product before anyone had committed a quarter-trillion dollars of debt-financed, off-balance-sheet capacity to the bet. Meta is committing the capacity first, financing it through vehicles built to keep the debt invisible, and presuming the product will follow. AWS monetized a surplus it stumbled into; Meta is pre-committing to a surplus and naming, in advance, its buyer of last resort. One is discovery. The other is a hedge.

What actually exists

Here, the second reading is at its strongest, and honesty requires giving it full weight.

Meta can build models. For a year, that was an open question. Llama 4 launched in April 2025 to a poor reception; Yann LeCun later told the Financial Times that the benchmark results had been “fudged a little bit,” that the team used different models for different benchmarks, and that Zuckerberg lost confidence in the group and sidelined it. [25] Eleven of the fourteen researchers behind the original Llama left the company; LeCun himself departed in November 2025. [26] The flagship “Behemoth” model was delayed due to performance issues and never shipped as promised. [27] If the thesis were “Meta cannot compete at the frontier,” that history would carry it.

But it isn’t, and the history was reversed. On April 8, 2026, Meta Superintelligence Labs — the division built around the $14.3 billion Scale AI investment and chief AI officer Alexandr Wang — released Muse Spark, which scored 52 on the independent Artificial Analysis Intelligence Index — fourth in the world at launch, behind only Gemini 3.1 Pro, GPT-5.4, and Claude Opus 4.6, and far ahead of Llama 4 Maverick’s 18. [28] Meta is, demonstrably, back in the race. But the profile is spiky in a telling way: Muse Spark’s weakest results fall on exactly the agentic, real-world-work benchmarks that enterprise compute is sold against — it trails GPT-5.4 and Anthropic’s Claude models on Artificial Analysis’s GDPval economic-task evaluation and on Terminal-Bench, gaps Meta itself flagged as priorities for further work — while its standout scores cluster in consumer health and multimodal fluency. [29]

What it did with that model is the crux. Muse Spark is closed. Its weights are not published, and at launch, Meta offered no public API, only a private preview to select users — the model was available free through the Meta AI app and website, and rolling out as the default assistant across Facebook, Instagram, WhatsApp, and Ray-Ban glasses, but not sold to developers as a service. [30] Meta deliberately declined to monetize the intelligence layer externally. The model exists to make Meta’s own products better and to be consumed by Meta’s own three-billion-user base, monetized the way Meta monetizes everything — through advertising, supplemented by new $7.99 and $19.99 Meta AI subscriptions. [31]

And the advertising machine is extraordinary. First-quarter revenue rose 33% to $56.31 billion, the fastest growth since 2021; ad impressions were up 19% and price per ad up 12%; operating income reached $22.87 billion; and the company generated $12.4 billion of free cash flow in the quarter even after capex. [32] This is the heart of the optimistic reading. Meta is funding a generational infrastructure bet out of one of the most profitable businesses in the world, not borrowing against hope. It underperformed expectations in the quarter and retains the discipline to throttle. If the buildout is rational, this is why.

That cushion is thinning fast, though. The $43.6 billion of free cash flow Meta generated across 2025 is set to fall steeply in 2026 as capex roughly doubles — far enough that several analysts now model it turning negative within a year or two. [33] The ads engine funds the buildout today; whether it still does in 2027 is the seam the bear case pulls at.

It also sharpens the problem. A closed model that, at launch, sold nothing to outside developers does not generate external compute revenue. Muse Spark fills Meta’s consumer demand, not the commercial demand that would absorb a five-gigawatt training campus and service a thirty-billion-dollar SPV. The model’s success and the buildout’s empty revenue case trace to one decision: Meta chose to keep its best work inside the walls. The capacity outside the walls still needs a tenant.

Whose money builds it

If the advertising machine genuinely pays for all of this, one hire is hard to explain. In January 2026, Meta named Dina Powell McCormick, with sixteen years at Goldman Sachs, where she ran the global sovereign investment banking business, later a deputy national security adviser, with the Gulf relationships to match, president and vice chairman. [34] Zuckerberg’s brief for her was specific: partner “with governments and sovereigns to build, deploy, invest in, and finance Meta’s AI and infrastructure,” and build “new strategic capital partnerships” that “expand our long-term investment capacity.” [35] A company that can comfortably fund its buildout from operating cash flow does not recruit a sovereign-wealth dealmaker to expand its investment capacity.

The move follows a path Microsoft, OpenAI, and Amazon have already worn — courting Gulf sovereign-wealth funds to help underwrite AI infrastructure. [36] It is the logic of the SPVs taken one tier further. Private credit moved the debt off Meta’s balance sheet; sovereign capital would move part of the funding burden off the private-credit market, which — as the El Paso deal’s missing anchor lender hints — is showing early signs of indigestion. Each tier widens the circle of people other than Meta who carry the bet.

And it changes what the capacity costs in something other than dollars. Sovereign money is not neutral money. A loan financed by a foreign government carries strings; private credit does not: preferences about where the capacity sits, who gets access, and what the financier expects in return. Meta has not closed such a deal — it has hired the person whose job is to find one. But the direction is the tell. When the cheapest available capital for a buildout is a sovereign-wealth fund, the buildout has outgrown every conventional source, and the question of who holds leverage over Meta’s compute stops being rhetorical.

The mirror: Amazon built the same trap in reverse

The cleanest way to see what Meta is doing is to set it beside the company it is renting chips from.

Amazon is the canonical case of infrastructure reversion: a company that stumbled repeatedly at the intelligence layer — Titan, Nova, the slow developer uptake of its own silicon — and resolved each stumble by retreating to infrastructure it could sell. The difference is that Amazon has the infrastructure business. When its models underperformed, it had AWS to monetize the compute regardless, and Bedrock to resell everyone else’s models through its own billing relationship. The reversion worked because the floor was already a product.

Meta has arrived at the same place from the opposite direction. It has the intelligence-layer stumbles. It has the infrastructure. What it lacks is a cloud business that would let the infrastructure pay for itself if the models don’t. The two companies even diverge on the accounting of identical hardware, each in the direction its strategy implies: Amazon, which sells compute and lives with hardware honesty, shortened its server life; Meta, which needs the buildout to look affordable, lengthened it. [21][22]

So the Infrastructure Reversion Test produces a Meta-specific verdict. Reversion is a fallback to a business you already run. Meta is contemplating reversion to a business it has never run, against incumbents who own two-thirds of the market between them, [4] as the backstop for a model strategy that, at launch, sold nothing to outsiders. It closed its models and is now weighing whether to sell the floor beneath them. When the intelligence layer is walled off from outside revenue, the only thing left to sell to outsiders is the raw compute — and that is the layer with the lowest margins and the most entrenched competition.

The bear’s favorite analogy belongs here, and it cuts more sharply than the bulls admit. The dark-fiber buildout of the late 1990s did, eventually, become the backbone of the modern internet — vindication, the optimists say, for building ahead of demand. But the surplus enriched whoever bought it cheaply out of bankruptcy, not the companies that financed and laid it. [37] If Hyperion and its siblings are dark fiber 2.0, the relevant question is not whether the capacity is used. It is who is holding the paper when it does. And the paper here sits with private-credit funds, insurers, and — through target-date and core bond funds — ordinary retirement accounts, layered over a thin equity cushion. [18][38]

This also answers the objection that the SPV debt is the lenders’ problem, not Meta’s. It is both, and the split is the point. Meta’s own direct exposure is comparatively contained — the lease payments it owes the vehicles, plus its minority equity. The structure’s fragility — the thin cushion, the long-dated near-junk debt — sits with Blue Owl, the bondholders, and the insurers behind them. The risk sits there by design. Meta engineered it onto someone else’s balance sheet, which is precisely why it can afford to be sanguine about overbuilding, and why “cloud is on the table” costs it so little to say.

What would have to break

The cloud remark serves as the hinge between the two readings, making this a thesis with a falsification date built in.

If Meta never exercises the option — if Muse-series models scaling across three billion users, plus recommendation and ads inference, plus whatever agentic workloads arrive, actually fill Hyperion and El Paso, and the SPV debt is serviced out of the advertising machine’s cash flow — then the optimists were right. The buildout was a rational forward purchase, the cloud line was idle optionality, the levers were prudent capital management. The end-state even has a name: Meta becomes a second Google — billions of users, a wall of apps, a competitive frontier model, and the custom silicon and data centers to run it all in-house. Google built precisely that stack, and it pays.

But the comparison is where the bull case turns on itself. Google’s vertical integration includes the one layer Meta has conspicuously skipped: it monetizes the same silicon and models externally, renting its TPUs and selling Gemini through Google Cloud — the chips that train Gemini and serve a billion users also collect rent from outside customers. [39] Google fills its own fleet and sells the overflow. Meta closed its model, withheld the API, and runs no cloud; and its silicon program, MTIA, is the least-proven leg of the stack, which is why it still leans on Nvidia, AMD, and rented AWS capacity to do the work TPUs do for Google. [3] Follow the optimistic case all the way to its end, and Meta lands as Google minus the cloud — the exact configuration that makes “cloud is on the table” necessary in the first place. The bull and bear cases converge on the same missing layer.

The market has already begun pricing that gap. On near-identical first-quarter beats, Alphabet’s stock rose about 7% the same day Meta’s fell — the difference resting on the cloud layer that turns AI capex into outside revenue. [40] And independent modeling cited by the Financial Times puts most of the hyperscalers, Meta included, at negative implied returns on AI investment through 2030, even on the generous assumption that the systems cost nothing to run; Amazon, the most mature cloud monetizer, is the lone positive, at roughly 7%. [41]

If Meta does exercise it — if it stands up external compute sales because internal demand fell short of the contracted capacity — then the put was the plan all along, and the levers were what they looked like: a structure for sustaining a buildout whose customer Meta had not secured.

The clock that decides it is already running, and three hands move at once. The physical capacity arrives on a schedule — Prometheus at a gigawatt in 2026, El Paso in 2028, Hyperion’s five gigawatts in 2029. [13][17][42] The SPV debt amortizes on another, with refinancing risk concentrating as the late-2020s maturities meet the capacity coming online. And the depreciation assumption reconciles on a third: if the stretched five-and-a-half-year life proves optimistic, the write-downs land in precisely the 2026–2028 window Burry flagged. [23] Demand, power delivery, and refinancing have to line up on the same timeline for the optimistic case to hold. [38] Each runs on its own logic, and none waits for the others.

There is a reason the credit market is already watching rather than the equity market. Meta’s five-year credit-default swaps had no liquid market until November 2025 — there was little to insure, because until then Meta funded itself largely from its own cash rather than from debt. [43] The CDS exists today because Meta became a borrower, and it has widened alongside Oracle’s, the cohort’s weakest credit, whose five-year spread has sat near 200 basis points since the spring — its highest since the 2008–09 financial crisis, and roughly quadruple its mid-2025 level. [44] JPMorgan now sells a hyperscaler CDS basket — Alphabet, Amazon, Meta, Microsoft, Oracle — so institutions can hedge a category of risk that barely existed eighteen months ago, against five names carrying $969 billion in commitments with $662 billion of data-center leases not yet commenced. [45] The instrument to bet against Meta’s buildout was built before Meta finished building it.

Weigh it, and the tension does not fully resolve — but it tips. The advertising business is strong enough that the optimistic case cannot be dismissed, and the first-quarter underspend shows real discipline. Yet a management team that genuinely expected internal demand to fill its capacity would not need to remind shareholders, with the CDS trading and the commitments at a quarter-trillion dollars, that it could always rent out the capacity. You name the exit when you can see the scenario that requires it. The most revealing thing Zuckerberg said in May was not that the cloud is on the table. It was the condition attached: if we feel that we have overbuilt. He is pricing the probability himself.

Meta is the one hyperscaler that built the cathedral before it had a congregation. “Cloud is on the table” is the sound of a company that has noticed, and is letting its lenders know there is a door.

Notes

[1] Mark Zuckerberg, remarks at Meta’s annual shareholder meeting, May 27, 2026, as reported in Jonathan Vanian, “Mark Zuckerberg says a Meta cloud computing business ‘definitely on the table,’” CNBC, May 27, 2026.

[2] Ibid. Zuckerberg: “We haven’t done that yet because we think that we have a use for the compute,” and the option arises “if we get to a point where we feel that we have overbuilt.” The conditional framing is load-bearing for this piece: Meta did not announce a cloud business; it named an option contingent on overbuild.

[3] Meta and AWS press releases, April 24, 2026; see “Meta Becomes One of World’s Largest Customers of Amazon AI Chips,” PYMNTS, April 24, 2026 (Graviton Arm cores, “tens of millions” of cores, positioned for agentic inference). Graviton is an Arm-based CPU, not a GPU; reporting that the deal also covers Trainium/Inferentia is less firmly sourced and is not relied on here.

[4] “Of the four U.S. hyperscalers, Meta is the only one that doesn’t sell cloud infrastructure and services”; AWS holds roughly a third of the market, with Microsoft and Google together holding another third. CNBC, May 27, 2026 (n.1); TechRadar, “Meta cloud computing business ‘definitely on the table,’” May 2026.

[5] North American data-center vacancy fell to 1.4% at year-end 2025, per CBRE’s North America Data Center Trends, H2 2025; JLL’s year-end 2025 read put the primary-market vacancy rate near 1%. On Trainium supply, AWS has stated demand exceeds production: TechCrunch, “An exclusive tour of Amazon’s Trainium lab,” March 22, 2026.

[6] Meta Platforms, “Meta Reports First Quarter 2026 Results,” April 29, 2026 (guidance raised to $125–145B from $115–135B; rationale: “higher component pricing... and, to a lesser extent, additional data center costs to support future year capacity”). SEC / Meta IR.

[7] 2025 full-year capex was $72.2 billion; 2026 guidance is nearly double that figure. Fortune, “Meta just bumped its 2026 capex forecast up to as much as $145 billion,” April 29, 2026.

[8] Q1 2026 capital expenditures (including principal payments on finance leases) were $19.84 billion, below the $27.57 billion StreetAccount consensus. Meta 10-Q / “Meta Q1 earnings report,” CNBC, April 29, 2026.

[9] Shares fell roughly 7% (intraday as much as ~10%) following the capex guidance raise. CNBC (n.8); Yahoo Finance, April 30, 2026.

[10] Non-cancelable contractual commitments of $237.67 billion as of March 31, 2026, described in the 10-Q (Note 8, Commitments and Contingencies) as “mostly related to third-party cloud capacity arrangements and continued investments in servers and network infrastructure, data centers, and consumer hardware products in Reality Labs,” with ~$42.25B due in 2026 and ~$47.65B in 2027; cash, cash equivalents and marketable securities of $81.18 billion. Meta Q1 2026 10-Q, SEC.

[11] Operating and finance leases not yet commenced of approximately $182.88 billion as of March 31, 2026, “consisting of data centers, colocations, and certain network infrastructure,” commencing between the remainder of 2026 and 2036, with terms from greater than one year to 30 years. Meta Q1 2026 10-Q, Note 8, SEC.

[12] Susan Li, Meta Q1 2026 earnings call, April 29, 2026: “These multiyear cloud deals and our infrastructure purchase agreements drove a $107 billion step up in our contractual commitments this quarter.” Meta Q1 2026 earnings call transcript.

[13] Hyperion: Richland Parish, Louisiana; ~5 gigawatts; completion expected 2029. Blue Owl / Meta joint-venture announcement and coverage. PE Insights, “Blue Owl and Meta close record $30bn financing,” 2025.

[14] Susan Li, Meta Q1 2026 earnings call, April 29, 2026: the infrastructure investments “will support our training needs for future models and, most importantly, provide us the inference capacity necessary to deliver personal and business agents to billions of people.” Transcript (n.12).

[15] Meta Platforms, “Meta Announces Joint Venture with Funds Managed by Blue Owl Capital to Develop Hyperion Data Center,” October 2025 (Blue Owl 80% / Meta 20%; ~$27B debt to PIMCO and other investors plus ~$2.5B equity; largest private-credit data-center deal on record).

[16] Bonds issued by the Beignet vehicle were rated A+ by S&P (single agency, reflecting Meta’s backing), priced at a 6.58% yield (~225 bps over Treasuries), fully amortizing, maturing 2049. Yahoo Finance / WSJ, “Meta’s $27 billion bet,” October 31, 2025; PE Insights (n.13).

[17] “Sopaipilla”: ~$13 billion SPV for a gigawatt-scale data center in El Paso, Texas, expected online 2028; Morgan Stanley and JPMorgan leading and, unlike the PIMCO-anchored Hyperion deal, may offer the debt to capital-markets investors rather than place it with an anchor. Bloomberg, via “Meta Taps Morgan Stanley, JPMorgan for New Data Center Deal,” Advisor Perspectives, May 5, 2026.

[18] On the inadequacy of the thin equity cushion in these data-center SPVs — typically on the order of 10% equity against a debt-heavy structure — see Paul Kedrosky, “SPVs, Credit, and AI Datacenters,” June 2025. Reported Meta vehicles, including a triple-net leaseback arrangement involving Apollo, have been described at roughly 90% debt / 10% equity (Covenant Lite, “Meta’s $29 Billion Bet with Apollo,” July 2025); whether that arrangement is distinct from the Blue Owl–led Hyperion financing or an earlier account of the same raise is not independently confirmed, and the body does not treat it as a separate vehicle.

[19] Carrying amount of long-term debt (fixed-rate senior unsecured notes) of $58.75 billion as of March 31, 2026. Meta Q1 2026 10-Q, Note 7, SEC.

[20] Meta structured the Hyperion leases in four-year increments so rating agencies would not treat them as debt. The Information, “The Creative Dealmaking Behind Meta’s $30 Billion Data Center Financing,” reported via Michael Parekh, November 2025.

[21] Meta Platforms Form 8-K, FY2024 results: “In January 2025, we completed an assessment of the useful lives of certain servers and network assets, which resulted in an increase in their estimated useful life to 5.5 years, effective beginning fiscal year 2025... we expect this change in accounting estimate will reduce our full year 2025 depreciation expense by approximately $2.9 billion.” SEC.

[22] Amazon shortened the useful life of a subset of its servers and networking equipment to five years in early 2025, citing the rapid pace of AI and machine-learning innovation — the opposite direction to Meta. DeepQuarry, “Depreciation of GPUs: between useful lives and useful myths,” December 2025.

[23] Michael Burry’s late-2025 argument that hyperscalers understate depreciation by using five-to-six-year lives for hardware with a real economic life closer to two-to-three years, estimated at ~$176 billion of understated depreciation industry-wide across 2026–2028; Nvidia publicly rebutted. WSJ, “The Accounting Uproar Over How Fast an AI Chip Depreciates,” December 8, 2025; CNBC, November 25, 2025. (Burry comparison to Cisco circa 2000, not Enron.)

[24] Paraphrased from the financing analyst quoted on the Hyperion structure: Meta must build the facility, place workloads in it, and presume future monetization of those workloads. WSJ via Yahoo Finance, October 31, 2025 (n.16).

[25] Yann LeCun, interview with Melissa Heikkilä, Financial Times, published January 2, 2026: Llama 4 benchmark “results were fudged a little bit,” the team “used different models for different benchmarks to give better results,” and Zuckerberg “lost confidence in everyone who was involved” and “sidelined the entire GenAI organisation.” FT (subscription); reproduction: Fast Company, “Yann LeCun: Meta ‘fudged’ on Llama 4 testing,” January 2026.

[26] Eleven of the fourteen researchers who created the original Llama left Meta; LeCun departed in November 2025. Maginative, “Meta Goes All-In on ‘Superintelligence,’” June 2025; The Next Web, “Meta hires five Thinking Machines Lab founders,” April 2026.

[27] “Behemoth” (the planned ~2-trillion-parameter flagship) was repeatedly delayed on performance and not released in promised form; the GenAI organization was sidelined ahead of the Superintelligence Labs reorganization. Maginative (n.26); Wikipedia, “Meta Superintelligence Labs” (secondary, for chronology only).

[28] Muse Spark scored 52 on the Artificial Analysis Intelligence Index v4.0, fourth globally behind Gemini 3.1 Pro (57), GPT-5.4 (57), and Claude Opus 4.6 (53); Llama 4 Maverick scored 18. Artificial Analysis was given early access to benchmark independently. Artificial Analysis, “Muse Spark: everything you need to know,” April 8, 2026. Note: Meta’s own claim of 50.2% on Humanity’s Last Exam used a multi-agent “Contemplating” mode with tools; the independent single-agent figure was 39.9%. Treat vendor mode-specific claims separately. The #4 ranking reflects the index at launch (April 8, 2026); the leaderboard has since shifted as newer models posted higher scores.

[29] Artificial Analysis (given early access by Meta) scored Muse Spark 52 on its Intelligence Index v4.0, 4th at launch. On GDPval-AA — Artificial Analysis’s evaluation of economically valuable, real-world office tasks — Muse Spark scored roughly 1,427 Elo (Meta’s own reported figure was 1,444), behind GPT-5.4 (~1,672) and Anthropic’s Claude Opus 4.6 (~1,606) and Sonnet 4.6 (~1,648), though ahead of Gemini 3.1 Pro Preview (1,320); it likewise trailed the leaders on Terminal-Bench Hard. Meta flagged long-horizon agentic systems and coding workflows as areas of continued investment. Most non-composite Muse Spark figures are Meta-reported: because the model is closed (no open weights; Meta AI app and a private API preview only), independent evaluators such as Vals.ai and BenchLM had not posted independent scores as of late May 2026. Artificial Analysis, “Muse Spark: everything you need to know,” April 8, 2026; VentureBeat, April 8, 2026.

[30] Muse Spark launched closed-weight, distributed free through the Meta AI app/website and rolling out as the default assistant across Meta’s platforms and Ray-Ban glasses, with no first-party public API at launch (Artificial Analysis benchmarked it via early access; Bloomberg reported the design and code would not be made public). Artificial Analysis (n.28); aitoolbriefing, “Meta’s Muse Spark Drops — And It’s Closed Source,” April 9, 2026. API availability may change; the claim is specific to launch.

[31] Meta is testing Meta AI subscriptions at $7.99 and $19.99 per month. Intellectia, “Zuckerberg: Meta May Enter Cloud Computing Market,” May 2026.

[32] Meta Q1 2026: revenue $56.31B (+33% YoY, fastest since 2021); ad impressions +19%, price per ad +12%; income from operations $22.87B; free cash flow $12.4B. Net income $26.77B included an $8.03B tax benefit (underlying EPS $7.31). Meta Q1 2026 release / 10-Q (n.6, n.8, n.10); CoinDCX earnings recap, April 2026.

[33] Meta’s full-year free cash flow was $43.59 billion in 2025 (Meta Q4/FY2025 release, SEC 8-K). Sell-side projections for 2026 fall sharply as capex roughly doubles — one widely cited Street estimate has full-year free cash flow dropping toward the high single-digit billions (IND Money, citing Street estimates) — and several analysts now model free cash flow turning negative across the AI-infrastructure cohort in 2026–2028; Barclays specifically projected a roughly 90% decline in Meta’s 2026 free cash flow after the raised guidance. CNBC, “Tech AI spending approaches $700 billion in 2026, cash taking big hit,” February 6, 2026.

[34] Meta named Dina Powell McCormick president and vice chairman, announced January 12, 2026; she spent 16 years at Goldman Sachs, where she led its Global Sovereign Investment Banking business, served as deputy national security adviser in the first Trump administration, and most recently was president at BDT & MSD Partners. She had been a Meta board member from April to December 2025. Axios, “Meta taps Dina Powell McCormick as president and vice chairman,” January 12, 2026; Advisor Perspectives, January 12, 2026.

[35] Zuckerberg said Powell McCormick would focus “on partnering with governments and sovereigns to build, deploy, invest in, and finance Meta’s AI and infrastructure”; Meta added that she would “drive an effort to build new strategic capital partnerships and find innovative ways to expand our long-term investment capacity.” Axios (n.34); AGBI, “Meta hires former Trump adviser to focus on Middle East deals,” January 16, 2026.

[36] Microsoft, OpenAI, and Amazon have made AI-infrastructure investment deals with Gulf-based sovereign-wealth funds, many focused on building data centers in the US and the Gulf. AGBI (n.35).

[37] In the late-1990s telecom buildout, the large majority of fiber laid sat dark for years and bandwidth prices collapsed; the surplus later became the backbone of Web 2.0, benefiting those who acquired it cheaply rather than those who financed it. “The AI Infrastructure Bubble,” Development Corporate, November 2025.

[38] AI-infrastructure debt is reaching retail retirement accounts through target-date and core bond funds; the bull case “requires demand, power delivery, and refinancing to line up on the same timeline.” Seeking Alpha, “Your 401(k) Is Funding AI’s Data Center Buildout,” May 14, 2026.

[39] Google Cloud sells external access to its Tensor Processing Units (TPUs) — the custom silicon that also trains Gemini and serves Google’s own products to over a billion users — through Compute Engine, Google Kubernetes Engine, and the Vertex AI / Gemini Enterprise Agent Platform, and offers Gemini models commercially on the same platform. “Tensor Processing Units (TPUs),” Google Cloud product page, accessed May 2026.

[40] On April 29–30, 2026, Alphabet and Meta both beat first-quarter estimates and both raised capital-expenditure guidance, yet Alphabet’s stock rose roughly 7% while Meta’s fell roughly 7% — a divergence widely attributed to Alphabet (like Amazon and Microsoft) operating a cloud business that converts AI investment into external revenue, which Meta lacks. CNBC, “Investors still trust Google more than Meta when it comes to spending their money on AI,” April 30, 2026.

[41] Modeling by Panmure Liberum, cited by the Financial Times, finds that most major US hyperscalers — Microsoft, Alphabet, Meta, and Oracle — show negative implied returns on AI investment over 2025–2030, even under the generous assumption that building and running the AI systems costs effectively nothing; only Amazon is positive, at roughly 7.2%, reflecting its more mature external cloud monetization. One published account put Meta’s implied figure near −29%. This is forward-looking modeling, not realized return. IBTimes UK, “Big Tech’s AI Gamble Shows Negative Returns Despite Surge in Spending,” May 30, 2026; figure for Meta via Sherwood/Yahoo Finance coverage of the same FT analysis.

[42] Prometheus, a ~1-gigawatt data center, is scheduled to come online in 2026. Trending Topics, “Meta’s Comeback: Muse Spark,” April 12, 2026.

[43] Meta’s (and Alphabet’s) five-year CDS did not begin trading until November 2025; before that these companies funded AI expansion from their balance sheets rather than debt markets, so there was little single-name CDS interest. Mellon Investments, “Record-Breaking AI-Related Debt Issuance in 2025,” December 15, 2025 (Bloomberg data).

[44] Oracle’s five-year CDS has sat near 200 basis points since spring 2026 — its highest since the 2008–09 financial crisis and roughly quadrupled from its mid-2025 level (≈198 bps reported late March–April 2026). BondbloX, “Oracle’s 5Y CDS Spread Hits All-Time Highs,” March 31, 2026; The Motley Fool / Yahoo Finance, April 10–11, 2026. A specific basis-point level for Meta’s own CDS is not independently confirmed here and is deliberately not stated.

[45] JPMorgan launched a hyperscaler CDS basket (Alphabet, Amazon, Meta, Microsoft, Oracle) in March 2026, in $25M blocks with $5M per name; the five issued $121B in bonds in 2025 (vs. a $28B annual average 2020–2024), with total commitments of $969B and $662B in data-center leases yet to commence. Winbuzzer, “JPMorgan Launches CDS Basket to Hedge AI Debt Risk,” March 24, 2026 (citing Fortune).

On May 19, 2026, Sundar Pichai stood on the Google I/O stage and made a claim that would have been science fiction when Google first ran its own AI chip in its data centers a decade ago. Gemini, he said, was now trained across more than a million of Google’s own Tensor Processing Units, distributed across data centers on multiple continents, stitched into a single logical cluster, with no Nvidia hardware anywhere in the loop. The chip that began life as an internal cost-saving project, a way to keep Google’s own search and translation workloads off other people’s silicon, was now training and serving one of the world’s frontier models end to end.

The same week, Amazon was telling a different story about its own decade-old silicon bet, though it was dressed in the same language. Trainium, Amazon’s custom AI chip, had “momentum.” Two of the largest AI labs in the world had committed to it. Andy Jassy told CNBC that “the two largest AI labs are both significantly betting on Trainium.” On paper, the two companies were making the same boast: our AI runs on our chips, not Nvidia’s.

Only one of those statements is load-bearing. The question that separates them is not who built a chip. Amazon and Google both did, starting at almost the same moment a decade ago. It is whose chip pulls its own demand, and whose chip has to have its demand bought for it.

The same bet

The two programs are almost exactly the same age. Google built its first TPU in 2015 to run its own neural networks more cheaply than it could on bought GPUs. That same year, Amazon bought Annapurna Labs, the Israeli design house behind its custom silicon: the Nitro networking chips first, then the Inferentia and Trainium AI chips that followed by the end of the decade. Both companies were chasing the same prize, and it is worth being precise about what that prize is.

Nvidia’s gross margin on AI hardware runs around 75 percent.[1] Every GPU-hour a hyperscaler sells carries that margin, paid to Nvidia. At the scale of AWS or Google Cloud, the arithmetic is brutal: the more AI compute you sell, the more of your customers’ money flows straight through your data centers and out to Santa Clara. Building your own chip keeps that margin instead of passing it along. The logic is identical for both companies.

What differs is what each company had to put on the other side of the equation, and that difference is the whole story. A custom chip is worthless without a workload to run. Silicon matures through use: each generation exposes the bottlenecks that the next generation fixes. The question for any custom-silicon program is: where does that workload come from? Google had an answer that Amazon did not.

Google made it

Google’s answer was Gemini. Because Google builds its own frontier model, it has a workload deep enough, demanding enough, and large enough to pull its silicon up the maturity curve generation after generation. The TPU did not have to win customers in a bake-off. It had to serve Google, and Google made sure each chip generation was shaped by what training and serving Gemini actually required.

The result, several generations in, is a chip line that has split to match the work. Google’s newest TPUs come in two variants: a training-optimized part and an inference-optimized part.[2] The training part is built for compute-bound pretraining, where Google claims roughly three times the per-pod performance of the prior generation, scaling near-linearly toward a million-chip logical cluster. The inference part handles the opposite problem: the memory-bound work of generating tokens one at a time, with 288 gigabytes of high-bandwidth memory and a large on-chip cache, tuned for the latency-sensitive serving that agentic workloads demand. This is the disaggregation of the inference problem into purpose-built hardware, and Google does it inside one chip family, on its own silicon.

The clearest evidence that the bet worked is in the pricing. When Google released Gemini 3.5 Flash in May 2026, it priced the model at $1.50 per million input tokens and $9.00 per million output tokens.[3] That was a threefold increase over the previous Flash generation. The model still undercut comparable frontier models on cost while claiming output speeds several times theirs. A company can only price like that if it owns its cost base. Google is not paying Nvidia’s margin on the tokens Flash generates; it is paying its own fabrication and power costs and amortizing its own chips. The price is proof that the silicon escape succeeded: Google has a cost floor that its GPU-dependent competitors cannot match, and it is beginning to use it as a weapon.

None of this required Google to buy a single customer; the demand was already inside the building. “Made it” means made it for Google’s own purposes — escaping Nvidia’s margin on a cost structure Google controls. Whether the TPU ever becomes a chip that other companies rent in volume is a separate and real question. But escaping the margin was the best, and Google has the receipts.

None of which makes Google’s books innocent. Alphabet booked an even larger markup last quarter than Amazon did: some $36.9 billion in gains on its own private-company stakes, including Anthropic and SpaceX, flattering net income the same way. The accounting game is industry-wide. But it is a separate game from the silicon. The difference is dependence: Google’s markup is gravy on a chip that already works and a cloud business growing fast, whereas Amazon, as the next section shows, leans on its markup to carry a quarter that the operating business did not.

Amazon had to anchor it

Amazon’s problem is that it has no Gemini. It acquired the silicon. Annapurna gave it the design talent, and Trainium is a real chip whose third generation is a genuine step up. What it could not acquire was a workload to pull that chip forward. So Amazon had to buy one. And the way it bought it gives the game away.

Consider the two labs Jassy points to. The first is Anthropic. Amazon has put roughly $8 billion into Anthropic since 2023, and in April 2026 committed up to $25 billion more. In return, Anthropic trains Claude on Trainium and has agreed to consume up to five gigawatts of the chips, housed partly in an $11 billion data center campus Amazon built for it in Indiana.[4] The second is OpenAI. In February 2026, Amazon committed up to $50 billion to OpenAI: $15 billion upfront in preferred stock, $35 billion more contingent on OpenAI completing an IPO or hitting undefined milestones. As part of the same deal, OpenAI agreed to consume 2 gigawatts of Trainium capacity, and AWS became the exclusive third-party cloud distributor for OpenAI’s enterprise platform, Frontier.[5]

Look at what each lab actually received in exchange for betting on the chip. Anthropic’s commitment sits on top of Amazon’s equity. OpenAI’s commitment came bundled with up to $50 billion and exclusive distribution rights to enterprise customers it could not otherwise reach through AWS. Neither commitment is a price-performance verdict on Trainium. Trainium has smaller customers who took no equity. The claim here is narrower and harder to wave away: its flagship, frontier-scale demand, the demand Jassy cites as validation, was bought. The two anchor commitments are the consideration in much larger strategic deals, and in OpenAI’s case, the connection is not interpretive. Amazon’s own regulatory filing states that the equity investment and the cloud partnership are contractually linked: if the collaboration agreement terminates, the $35 billion equity commitment dies with it.[6] The money and the chip commitment are bound together in the contract.

The strongest evidence that this is procurement rather than merit is what these same labs do when money is not attached. OpenAI runs an aggressively multi-cloud strategy: it has a custom-ASIC deal with Broadcom, buys Nvidia GPUs through multiple clouds, and has committed to AMD. In the same round that included Amazon’s $50 billion investment, OpenAI committed to 5 gigawatts of Nvidia’s next-generation systems, more than twice its Trainium commitment.[7] When OpenAI allocates compute on the merits, it goes substantially to Nvidia. The Trainium slice is the one with Amazon’s equity stapled to it.

And salvage it

Anchoring the chip to bought demand is the first move. The second is admitting it cannot finish the job alone. In March 2026, AWS announced a partnership with Cerebras to deliver fast inference through its Bedrock platform. The architecture is revealing. Trainium handles “prefill”: reading and digesting the prompt, the fast-parallel part. Cerebras’s wafer-scale chips handle “decode”: writing the answer back one token at a time, the slow sequential part that determines how fast a response feels. There, Cerebras claims an order-of-magnitude speed advantage over conventional hardware.[8] One industry analyst put the implication plainly: by splitting inference across two companies’ chips, “AWS is betting that no single chip architecture can win alone.” That is a precise description of an admission. Amazon went outside its own silicon for the half of inference that matters most for the agentic, token-hungry workloads everyone is racing toward. Google does not hand the decode stage to a third party’s silicon; it builds its own inference chip.

The third move is in the financials, and it is the one that turns the argument into evidence. If Trainium were winning on merit, Amazon’s chip strategy would show up as cash: customers paying for compute, margin retained instead of forwarded to Nvidia. Instead, the most important number Amazon’s chip strategy produced last quarter was an accounting entry.

In the first quarter of 2026, Amazon reported net income of $30.3 billion, up 77 percent year over year, a headline blowout. But $16.8 billion of the pre-tax income behind it was a non-cash, non-operating gain: the markup on Amazon’s Anthropic stake, triggered when Anthropic’s latest funding round reset the valuation, and Amazon revalued its holding.[9] After tax, that single mark-to-market entry was larger than Amazon’s entire year-over-year increase in net income: the company’s headline profit growth was, in effect, the markup. Strip it out and roughly $23 billion of pre-tax income remains, up from the prior year but unspectacular. The gain itself cost nothing and produced nothing. Under the accounting rule that governs it, the gain reverses only if a future Anthropic transaction reprices the stake downward, or the holding is impaired — not a number Amazon can spend, and one that can run backward as easily as forward.[13]

Now set that against the cash. Over the trailing twelve months, Amazon’s free cash flow fell to $1.2 billion, down 95 percent from $25.9 billion a year earlier. Net capital expenditure over the same period climbed to roughly $147 billion, the overwhelming majority of it AI infrastructure.[10] The company posting record AI-era profit is generating almost no free cash, and the profit growth that made the headline is a revaluation of a startup Amazon itself funds and supplies.

The cash collapse, to Amazon’s credit, is largely a choice, not distress. Free cash flow fell because Amazon elected to spend roughly $147 billion on AI infrastructure, and the operating business underneath is healthy: AWS grew 28 percent year over year, its fastest in several quarters, and segment operating income rose. A company can spend its cash flow into the ground on purpose and be sound. So the depressed cash is not, by itself, the indictment. The indictment is narrower: the profit growth the market celebrated came from none of that operating strength. It came from marking up a private stake. Strip the Anthropic gain and the quarter was solid and unspectacular. The blowout was an accounting event.

This is the circuit that holds the salvage together. Amazon invests equity in Anthropic; Anthropic commits to spend on Trainium and AWS. That spending returns as AWS revenue and as evidence of Trainium “traction”. Anthropic raises its next round at a higher valuation. Amazon marks up its stake and books the gain as profit. Each loop raises the mark. The chip’s flagship demand and the quarter’s profit growth trace to the same root: the roughly $8 billion Amazon had invested in Anthropic by the time the stake was marked. The capital goes out as investment, returns as Trainium and AWS revenue, and then appreciates. The appreciation on that stake, not any cash Anthropic paid out, is what carried net income to a record. The money does double duty: once as evidence of silicon momentum, once as reported profit. It is an unusual position — being able to influence the marked value of your own largest asset by doing business with it.[11]

Why one made it and the other didn’t

The difference between the two companies is not intelligence or execution. It comes down to a single asset that cannot be faked: a captive frontier workload. Google’s TPU is pulled up the maturity curve by a model that uses it on the merits, paid for by Google’s own economics, answerable to no outside buyer — captive-demand pull. Amazon’s Trainium is pushed forward by tenants it bought with equity and distribution — procured-demand push. The two can look identical in a press release (”the largest labs run on our chip”), but one is a workload choosing the best tool it has, and the other is a tool that had to purchase its workload.

This is why the same test that condemns Trainium clears the TPU. Both chips are attractive partly because Nvidia is scarce and expensive, but that is not the distinction. The distinction is the counterfactual. Strip away the scarcity premium, and Trainium loses its rationale. Its demand was assembled to fit the shortage: anchor tenants routed to it by equity, overflow capacity so tight that Jassy says Amazon is considering selling racks directly.[12] Strip the same premium from the TPU, and Google still has a frontier model running on it every day, for reasons that have nothing to do with GPU availability. Captive demand survives the counterfactual. Procured demand does not.

The mirror

This is the inverse of a pattern this newsletter has traced before. In “Compute Equals Commitments,” the dynamic was a chipmaker funding its own customer’s purchases — round-trip revenue dressed as demand. Here the same financial structure appears one layer up: a cloud provider funding the labs that validate its chip, and booking the resulting equity markup as profit. The round trip is the same; only the layer has moved. The Annapurna bet was the right instinct — Amazon was early to see that owning the silicon mattered. It was just never able to feed the chip the way Google feeds the TPU.

What would have to break

The honest case against this verdict rests mostly on OpenAI, and it deserves a fair hearing. OpenAI is not a captive Amazon subsidiary; it is a genuinely multi-cloud lab that could have said no. Its willingness to put two gigawatts on Trainium is a real data point, and if Trainium were worthless, a company with OpenAI’s options would not have agreed to run on it at all. That is true, and the piece concedes it: the chip is not bad. But “not bad” is not “won.” OpenAI’s commitment came stapled to up to $50 billion in Amazon investment — $15 billion of it funded so far, the rest contingent on an IPO that has not happened — and to exclusive enterprise distribution. Its merit allocation, the five gigawatts of Nvidia capacity in the same round, went elsewhere, more than twice the Trainium commitment. Procured is not coerced, but neither is it chosen on the basis of price-performance.

So the verdict is falsifiable and worth stating in terms that could fail. If Trainium wins a large frontier customer that is neither funded by Amazon nor bundled with distribution it cannot get elsewhere, the salvage thesis weakens. If the Cerebras dependency ends because a future Trainium wins the decode stage outright, one of the three tells falls. If Amazon’s free cash flow recovers while the Anthropic markup stays flat — proving the operating business stands on its own — the financial tell dissolves. And if Google’s TPU never escapes its own data centers to win external cloud customers, then “made it” is too strong, and Google has merely built an excellent internal tool rather than a competitive product. Each of those is a real possibility, and each would move the verdict.

But on the evidence available now, the two-decade-old silicon bets have not converged. Google built a chip that its own frontier model pulls forward, prices its products off a cost base it owns, and needs far less outside capital to keep improving. Amazon built a chip that it must supply with purchased tenants, finish with a rented decode engine, and validate with an accounting gain while its cash disappears into the build-out. Both companies can say their AI runs on their own silicon.

Only one of them is telling you the whole sentence.

Notes

[1] NVIDIA Corp, Form 10-Q for the quarter ended April 26, 2026 (Q1 FY2027): GAAP gross margin 74.9%; full fiscal 2026 GAAP gross margin 71.1%. NVIDIA does not separately disclose a Data Center segment gross margin; with Data Center at ~92% of revenue, the consolidated figure is the best available proxy, and the “~75%” in the body refers to that consolidated GAAP margin.

[2] Google Cloud, “Ironwood is here: our eighth-generation TPU for the agentic era” (April 2026). Specifications are vendor-published and not independently benchmarked: ~3× per-pod performance and near-linear scaling toward a million-chip logical cluster (training part); 288 GB high-bandwidth memory and on-chip cache (inference part); up to 2× performance-per-watt. Treat as vendor specifications.

[3] Google, official Gemini API pricing (ai.google.dev, updated May 19, 2026): Gemini 3.5 Flash at $1.50 / million input tokens, $9.00 / million output tokens (incl. thinking tokens), $0.15 / million cached input tokens — roughly 3× the prior Flash generation’s list pricing. The “undercuts comparable frontier models / several times the speed” framing is Google’s own, presented at I/O, and the speed comparison is vendor-claimed.

[4] Amazon’s Anthropic investment: ~$8 billion in tranches from September 2023 (initial $1.25B; $4B completed March 2024; further $4B announced November 2024), initially convertible notes, partially converted to equity. On April 20, 2026, Amazon committed up to $25 billion more — $5 billion immediately (at Anthropic’s $350B valuation), up to $20 billion tied to commercial milestones. The Q1 2026 markup discussed below was on the ~$8B already invested; the additional commitment closed after quarter-end. The up-to-five-gigawatt Trainium commitment and the ~$100B AWS spend are Anthropic commitments to consume AWS/Trainium capacity. Project Rainier (Indiana; ~500,000 Trainium2 chips scaling toward 1 million, $11B site) is the dedicated buildout.

[5] OpenAI, “OpenAI and Amazon announce strategic partnership” (Feb 27, 2026): $50 billion total Amazon investment, $15 billion initial (OpenAI Series C Preferred Stock), $35 billion contingent; OpenAI to consume 2 GW of Trainium; AWS as exclusive third-party cloud distributor for OpenAI Frontier. See also Amazon Form 8-K, EX-99.1 (Feb 2026).

[6] Amazon Form 8-K (Feb 2026) and accompanying agreement disclosure: the equity investment and cloud partnership are contractually linked; the $35 billion contingent equity commitment (stated as $34,999,999,447.98) terminates if the Joint Collaboration Agreement terminates, and is contingent on conditions including an OpenAI IPO or direct listing, expiring if not invested by Dec. 31, 2028.

[7] OpenAI’s $110 billion round (Feb 27, 2026; $730 billion pre-money) included $30 billion each from NVIDIA and SoftBank alongside Amazon’s $50 billion; OpenAI’s NVIDIA commitment in connection with the round was 5 GW of Vera Rubin-generation capacity, versus 2 GW of Trainium. OpenAI’s separate Broadcom custom-ASIC and AMD commitments are company-announced.

[8] AWS and Cerebras, “AWS and Cerebras Collaboration Aims to Set a New Standard for AI Inference” (March 13, 2026): AWS Trainium optimized for prefill, Cerebras CS-3 optimized for decode, connected via Elastic Fabric Adapter, delivered exclusively through Amazon Bedrock. Cerebras’s decode speed advantage is vendor-claimed. The “no single chip architecture can win alone” reading is an analyst characterization, not AWS’s.

[9] Amazon Form 8-K, EX-99.1, Q1 2026 (quarter ended March 31, 2026): “First quarter 2026 net income includes pre-tax gains of $16.8 billion included in non-operating income from our investments in Anthropic.” Income before income taxes was $39.834 billion; $16.8B / $39.834B = 42.2%. (Some contemporaneous reporting characterized the gain as “more than half” of pre-tax income; the filing figure is ~42%.)

[10] Amazon Form 8-K, EX-99.1, Q1 2026. Headline “Free cash flow” line (TTM operating cash flow less purchases of property and equipment): $1.232 billion for the TTM ended March 31, 2026, versus $25.925 billion a year earlier. Amazon publishes alternative FCF measures that differ; the headline line is used here. TTM net property-and-equipment purchases ~$147 billion. AWS Q1 2026 revenue grew 28% YoY with segment operating income up, per the same release.

[11] On the structural point — that a company can influence the marked value of an asset through its own business dealings with the issuer — see the disclosure mechanics in Amazon’s Q1 2026 Form 8-K [9] and the ASC 321 measurement-alternative note [13]. The characterization is the author’s, drawn from the filing’s own description of the Anthropic gain.

[12] Andy Jassy, Amazon Q1 2026 earnings commentary and CNBC interview (Feb 27, 2026): Trainium demand sufficiently high that AWS was considering selling Trainium racks directly; “the two largest AI labs are both significantly betting on Trainium.” AWS reported 28% YoY revenue growth in Q1 2026, per Amazon’s Q1 2026 results.

[13] Equity stakes in private companies such as Anthropic are generally accounted for under ASC 321’s measurement alternative: carried at cost and remeasured to fair value only on an observable transaction (e.g., a new funding round) for similar securities of the same issuer, or on impairment. An up-round markup is unrealized and non-cash; it can reverse on a later down round or impairment, and becomes cash only when realized through a sale or liquidity event.

On Monday in Shanghai, He Tingbo — president of Huawei’s semiconductor business and chair of its Scientist Committee — stood in front of a room at the IEEE International Symposium on Circuits and Systems and told the industry it had spent six decades optimizing for the wrong thing.[1] Her keynote, “New Semiconductor Path in Practice,” proposed retiring the principle that has organized the entire business since 1965: shrink the transistor, double the count, repeat. In its place, she offered the “Tau (τ) Scaling Law” — already nicknamed “Her’s Law” by her peers — which optimizes not for how small a transistor is but for how fast a signal moves through the chip.[2] “I used to think it may take us 10 years,” she told the room, “but six years, we are here.”[1]

The French wire that crossed my desk called it “un nouveau mode de fabrication de puces” — a new way of manufacturing chips.[3] It is not. That distinction is the entire story, and getting it wrong is how a reader ends up either over- or under-pricing what just happened.

Huawei did not announce a manufacturing breakthrough. It announced a design breakthrough, executed on the manufacturing it already has. The company is process-constrained: its chips lean on SMIC’s roughly 7-nanometre-class nodes, several generations behind the 3nm-class processes feeding Apple, Qualcomm, and AMD — and behind the 2nm that TSMC is now ramping.[4] What it claims to have built is a way to extract frontier-class transistor density from trailing-edge fabrication — by changing the layout, not the lithography.

The mechanism is called LogicFolding. In a conventional layout, logic blocks sprawl across a mostly flat plane. The limiting factor is increasingly not how fast the transistors switch, but how long it takes a signal to cross the long, resistive wires between them — a delay that caps the clock and wastes energy driving the interconnect. LogicFolding “folds” the logic — expanding the layout from one layer to two — pulling critical paths closer together, shortening the wiring, cutting propagation delay, and packing more transistors into the same footprint.[5] Huawei says the fall 2026 Kirin gains 53.5% in transistor density, to 238 million transistors per square millimeter, alongside a 40% jump in performance-core power efficiency and a 3.1GHz top clock.[6] That density figure sits, on paper, near Intel’s 18A and TSMC’s 3nm.[7] The phone is only the showcase: Huawei frames the same time-scaling logic running up through its UnifiedBus interconnect to the AI clusters, where it is trying to displace Nvidia.[8]

This is neither vaporware nor a triumph — it is a genuine engineering idea aimed at a real bottleneck. The honest steelman comes from Omdia’s semiconductor research director, He Hui, who calls it a shift from node-driven scaling to “system-level efficiency scaling”—in his view, a credible way to wring more performance out of constrained lithography.[9] Interconnect delay is genuinely the dominant frontier problem, and stacking silicon to address it is not new: HBM has stacked memory since 2015, and TSMC and Intel have stacked finished dies with SoIC and Foveros. What Huawei claims is harder and less proven — folding a single logic block’s own gates across two bonded tiers so signals take a short vertical hop instead of a long planar route. That is logic-on-logic at the cell level, the territory the whole industry has been circling for a decade, because the thermal and yield problems are brutal. The difference from the rivals’ version is that theirs still rides on leading-edge fabs Huawei cannot buy.

But density on a slide is not density at competitive yield, power, and thermals. The most important sentence published all day came from Paul Triolo of DGA Group: a stacked or folded design can produce genuine density gains, he said, but it “does not mean Huawei has solved” the yield, power, thermal, and device-performance problems of true 1.4nm-class manufacturing.[10] Counterpoint’s Neil Shah was blunter on the strategic point: this “parallel semiconductor path is still unproven at scale.”[11] And the headline number — a transistor density “equivalent to” a 1.4nm process — is not a 2026 result. It is a 2031 projection, unaccompanied by any independent performance data.[12] Stacking buys you density. It does not automatically buy you the efficiency that makes density useful at the frontier.

So strip the projection away and look at what actually shipped: a strategic reframe. The export-control regime was architected on the premise of manufacturing. Deny China extreme ultraviolet lithography — the ASML machines no Chinese firm can legally buy — cap it at 7nm, and the density frontier stays out of reach.[13] The wall is real, and it works against the thing it was built to stop. What it cannot do is stop Huawei from deciding that the frontier is no longer defined by the dimension the wall measures. If the goal is signal-propagation time rather than transistor pitch, then a control regime denominated in nanometres is policing a metric the target has stopped competing on. Even Triolo, who doubts the manufacturing claim, reads the move this way: Huawei is “turning an engineering strategy into a quasi-’law’” — shorten wires, stack logic, co-design the whole system.[10]

The reframe does not entirely escape the wall. A folded design still has to be finalized for production on EDA software, where America’s Synopsys and Cadence dominate, and fabricated on SMIC’s constrained base node. Huawei now claims home-grown design tools, but domestic EDA at the leading edge is unproven — and Washington showed in 2025 that it can switch the EDA tap off at will, before it relented.[13] The dependency is real. It simply no longer sits where the lithography rules are pointed.

The market saw the same thing even where the engineering is unproven: SMIC shares rose 7.6% on the news.[14] And the competitive backdrop sharpens it — last week, Nvidia’s Jensen Huang told CNBC his company had “largely conceded” China’s AI chip market to Huawei.[15] The Tau Law is a flag planted in the ground that Nvidia is vacating.

None of this means Huawei has closed the gap. It almost certainly has not, and the skeptics may be entirely right that folding logic across bonded tiers hits a thermal-and-yield ceiling well short of the 2031 target. But the bet is now legible, and it is falsifiable on a clock. The first checkpoint is this autumn, when the new Kirin ships and an independent teardown can confirm or puncture the density claim. The test is not whether the design works on a slide but whether Huawei can build it in volume without the chips failing — the gap, in stacked designs, where ambition usually dies.[16] The second checkpoint is 2031. If either one lands at competitive efficiency without EUV, Washington is left writing its rules in a unit that no longer measures the race.

The wall was built to keep China from making the transistors smaller. Huawei’s answer is to stop trying.

Notes

[1]: He Tingbo delivered the keynote “New Semiconductor Path in Practice” at the 2026 IEEE International Symposium on Circuits and Systems (ISCAS), Shanghai, May 25, 2026. Huawei newsroom, “HUAWEI Presents the Tau (τ) Scaling Law, Enabling Breakthroughs in Transistor Density and System Performance,” May 25, 2026, huawei.com. Vendor-primary source. The “I used to think it may take us 10 years, but six years we are here” remark, and a teaser that Huawei would “bring the surprise” before winter 2026, are reported from the keynote by BusinessToday, businesstoday.in.

[2]: The principle “proposes replacing geometric scaling with time (τ) scaling as a new guiding principle for the evolution of both semiconductors and electronic systems.” Huawei newsroom, ibid. The “Her’s Law” nickname (a play on He Tingbo’s surname and the convention of naming foundational laws after their originators, as with Moore’s Law) is reported by the South China Morning Post, “Huawei unveils new scaling law and tech that narrows gap with TSMC, Samsung,” May 25, 2026, scmp.com. τ (tau) is the time constant engineers use to describe how quickly signals propagate through a circuit.

[3]: “Huawei a développé un nouveau mode de fabrication de puces,” Boursorama (reproducing an AFP wire), May 25, 2026, boursorama.com. The “fabrication” framing is the error this piece corrects.

[4]: On the process gap: “analysts say China remains behind global leaders in the most advanced process technology,” with Huawei’s chips produced on SMIC’s 7nm-class node versus TSMC’s 2nm. Reuters, “China’s Huawei reveals chip design breakthrough amid US sanctions,” May 25, 2026, reuters via rappler.com. The Kirin 9030 (Mate 80 Pro Max) was built by SMIC on an “N+3” process, a scaled evolution of its 7nm node and still behind TSMC and Samsung, per a TechInsights teardown reported by the South China Morning Post, scmp via tech.yahoo.com.

[5]: LogicFolding “would shorten wiring inside chips and considerably improve performance”; Reuters, op. cit. (rappler.com). Huawei’s own description: the architecture “can be used to continuously compress signal propagation delay and steadily improve transistor density.” Huawei newsroom, op. cit. CNBC reported that “Huawei’s new chip architecture expands the layout from one layer to two,” per He Tingbo. CNBC, “Huawei plans new smartphone chips this fall,” May 25, 2026, cnbc.com.

[6]: Per-metric figures (vs. a conventional SoC): +53.5% transistor density to 238 MTr/mm², +40% P-core power efficiency, and +12.7% max clock frequency to 3.1GHz. These figures appear in He Tingbo’s ISCAS presentation slides as relayed by trade press; they are not stated in Huawei’s official press release, which carries only the τ Law framework, the “381 chips” and “Fall 2026 Kirin” claims, and the 2031 target (Huawei newsroom, op. cit.). Slide figures via FoneArena, “HUAWEI presents Tau (τ) Scaling Law,” May 25, 2026, fonearena.com, and Huawei Central, huaweicentral.com. Vendor-claimed presentation data; no independent verification as of publication.

[7]: The 238 MTr/mm² figure has been described as roughly comparable to Intel’s 18A and TSMC’s 3nm-class density. The comparison is density-only and does not establish equivalent power, yield, or performance; nor is it specified whether the figure is logic-only or SRAM-inclusive, which materially affects any cross-foundry comparison. Treat as vendor-claimed slide data pending an independent teardown of the shipping Kirin.

[8]: Huawei describes the τ Scaling Law operating “at the system level” by “redefining interconnect protocols for computing systems with UnifiedBus to achieve unified memory addressing and native memory semantics for SuperPoDs,” reducing system communication latency. Huawei newsroom, op. cit. (huawei.com). This situates the phone-level LogicFolding claim within Huawei’s broader AI-cluster ambition.

[9]: He Hui, director of semiconductor research at Omdia, quoted in Reuters via Rappler, “China’s Huawei reveals chip design breakthrough amid US sanctions,” May 25, 2026, rappler.com.

[10]: Paul Triolo, head of technology, Asia and Americas, DGA Group, quoted in CNBC, “Huawei plans new smartphone chips this fall as rivalry with Nvidia and Apple heats up,” May 25, 2026, cnbc.com. Full quotes: “A stacked/folded design can produce effective density gains, but it does not mean Huawei has solved the full process, yield, power, thermal, and device-performance problems associated with true 1.4 nm-class manufacturing”; and separately, “Huawei is turning an engineering strategy into a quasi-’law,’” which Triolo characterized as “more a systems-level optimization doctrine: shorten wires, stack logic, improve memory semantics, and co-design chips, packages, software, and clusters.”

[11]: Neil Shah, vice president of research, Counterpoint Research, quoted in CNBC, ibid.

[12]: “By 2031, the high-end chips HUAWEI designs based on the τ Scaling Law are expected to feature a transistor density that is equivalent to 14 Å (1.4 nm) processes.” Huawei newsroom, op. cit. “Although Huawei did not provide independent performance data, the target is significant because 1.4 nm is expected to be close to the global frontier for advanced chipmaking around the end of the decade.” Reuters via Investing.com, investing.com.

[13]: China “is widely seen as unlikely to reach that level through conventional manufacturing alone because Washington has restricted its access to advanced lithography tools and other key semiconductor technologies.” Reuters, op. cit. ASML has never shipped an EUV machine to China, and there is no credible domestic alternative — the binding reason SMIC sits several generations behind TSMC and Samsung; see TheNextWeb, “Huawei unveils ‘Tau Scaling Law’ as China’s workaround,” May 25, 2026, thenextweb.com. On the EDA dependency as a demonstrated lever: US BIS ordered Synopsys, Cadence, and Siemens EDA to halt China sales in late May 2025, then rescinded the restriction on July 2, 2025; the three firms hold roughly 80% of China’s EDA market. US Commerce/BIS via Network World, July 3, 2025, networkworld.com; EE Times, eetimes.com. The episode established that the tool dependency is a switch that can be activated, even though it is not active as of publication. At the keynote He Tingbo claimed Huawei had spent six years building domestic capabilities “including electronic design automation (EDA) tools and chip design methodologies”; BusinessToday, May 25, 2026, businesstoday.in. Domestic EDA at leading-edge nodes remains commercially unproven.

[14]: SMIC shares rose 7.6% on Monday following the LogicFolding announcement. South China Morning Post, op. cit.; Reuters via Rappler, op. cit.

[15]: Jensen Huang told CNBC the company had “largely conceded” China’s AI chip market to Huawei. CNBC, op. cit.; corroborated in Modern Diplomacy, moderndiplomacy.eu.

[16]: LogicFolding is described as cell-level “folding” — distributing a single logic block’s gates across two vertically bonded wafer tiers connected by hybrid bonding — rather than the die-to-die stacking used by HBM or by TSMC’s SoIC and Intel’s Foveros. One technical reconstruction puts the Kirin 2026 hybrid-bonding pitch at ~1.5µm (versus TSMC SoIC at <15µm and Intel Foveros at ~25µm TSV pitch), with density scaling roughly as the square of interconnect pitch; the same analysis back-calculates the density gain as 155→238 MTr/mm². These are independent analyst figures, not Huawei-published data: GlobalSemiResearch, “Huawei’s Tau Scaling Law: A Technical Deep Dive,” May 25, 2026, globalsemiresearch.substack.com; pitch comparisons via SemiAnalysis, semianalysis.com. The thermal and yield penalties of logic-on-logic stacking are long-documented; see Semiconductor Engineering, “Stacking Logic On Logic.”

On May 12, in a near-empty hearing room of the French National Assembly, Arthur Mensch did something that tells you everything about how Mistral actually competes.

He didn’t talk about his models. He warned the deputies about someone else’s — and the deputies, mostly, hadn’t bothered to come. He delivered his warning about the fate of European civilization to a scattering of empty benches for ninety minutes, with the cameras running. [1]

The warning itself: Anthropic — the American lab that sits ahead of Mistral at the frontier, and whose restricted-access Claude Mythos Preview model can autonomously hunt down and exploit software vulnerabilities [2] — had been circling the French defense establishment, offering to scan the army’s code bases. Mensch’s counsel to the Republic was to keep them out. Letting a foreign model that deep into French defense, he argued, would create a dependency that is “hard to unwind.” [3]

There’s a real security argument buried in there, and Mensch made the fair version of it himself: you might reasonably not want any vulnerability-hunting model — foreign or domestic — crawling through your defense code, and he conceded in the same breath that Mistral’s own models or Chinese ones could find the same flaws. [3] But notice how neatly the sovereignty case lands on the one outcome that also protects Mistral’s existing contract with the French armed forces — and that it asks France to turn away the strongest defensive tool on the market during the worst run of data breaches in its history, a point we’ll come back to.

That convenience — a principled-sounding argument that happens, every time, to favor Mistral — is the thread running through everything Mensch has said and done this spring.

Once you pull it, the whole confusing season snaps into focus.

The eight days that looked like hypocrisy

Here is the sequence in which French Twitter called Mensch a hypocrite.

May 7. Brussels agrees to the “Digital Omnibus,” delaying the AI Act’s high-risk obligations by sixteen months — from August 2026 to December 2027. Mistral is among the industry voices that lobbied for the slowdown. [4]

May 12. Five days after winning that delay, Mensch sits before the National Assembly and warns that Europe over-regulates, that it has “heavy regulation and a fragmented market,” that the stack of GDPR, copyright rules, and the AI Act is an “empilement“ — a pile-up. [5] Europe, he says, has two years to build its own AI infrastructure or become America’s “vassal state.” [6]

May 15. It’s the front page of the Journal du Dimanche.

A man lobbies to weaken a regulation, wins, and then days later complains that Europe is over-regulated — and lands the front page doing it. The hypocrisy reading writes itself. It’s also wrong, or at least lazy. Mensch isn’t confused. He’s running a press strategy with a clock on it, and the clock matters more than the contradiction.

And the empty room is the proof. If your goal is to persuade legislators, you care whether legislators are in the seats. If your goal is the front page, the seats are set dressing, and the camera is the audience. Mensch wasn’t talking to the handful of deputies who showed up. He was talking, through them, to the JDD, to Bercy — the Finance Ministry — to the Élysée, and to every procurement officer in France who would read about it three days later.

The benches were empty because, on some level, everyone involved understood the room wasn’t the point.

Then there’s the third move people keep filing separately. In March, in the Financial Times, Mensch proposed a 1–1.5% levy on the European revenues of all AI providers — including the American and Chinese ones — to fund a European cultural pot. A tax on AI, from the CEO of an AI company. [7] And back in September, asked about France’s proposed Zucman wealth tax, he offered warm words — “at the risk of disappointing the polemicists, I’m rather convinced we need more fiscal justice in France” — while making clear in the same sentence that he could not and would not pay it himself. [8]

Pro-tax, anti-tax, pro-rules, anti-rules. It looks incoherent. It isn’t. Every one of these positions serves the same end.

Mistral isn’t winning on capability

Start with the thing the sovereignty conversation is engineered to make you forget: Mistral does not make the best models, and its own strategy quietly concedes the point.

This isn’t a knock on the engineering. Mistral’s latest flagship, Medium 3.5, is a genuinely strong model: a dense 128-billion-parameter system that posts 77.6% on SWE-Bench Verified, a respected coding benchmark, and undercuts the closed frontier models on price by roughly half. [9] Mistral does benchmark it against the frontier leaders — and that comparison is exactly the tell. On SWE-Bench, it lands about two points behind Claude Sonnet 4.6 (77.6% versus 79.6%); the pitch is not “we win,” it’s “we come close and cost less, and you can run the weights yourself.” [10] That is a deliberate, coherent position — near-frontier at a fraction of the price — and it is, by design, a second-place pitch. The pace-setting systems on reasoning and agents remain American.

Which is exactly the point. If your strategy is to be the affordable, open, sovereign alternative rather than the best model in the world — and the capex math says it has to be; Mistral’s roughly $400M in annual recurring revenue, with €1bn targeted for the year [11] sits against OpenAI’s $20bn-plus annualized run-rate as of late 2025 [12] — then “best model” can never be your moat. You need a different one.

So what is the moat?

The fashionable answer is “sovereignty.” And there’s a real version of that argument. Europe genuinely should worry about routing every critical digital service through American infrastructure governed by American law. The CLOUD Act is real. Dependency is real. Mensch is not wrong that a continent with no domestic frontier lab has no leverage.

But watch what happens when you ask which kind of sovereignty actually protects Mistral, and you find the real answer is none of the ones he names.

It isn’t technical sovereignty — data-stays-in-Europe. Microsoft, AWS, and OpenAI are all racing to offer EU data residency. That checkbox is being commoditized by the quarter.

It isn’t legal sovereignty — open weights you can self-host. Llama and Qwen are open too. A French integrator could run them on a French cloud under French law and undercut Mistral on price tomorrow.

It isn’t corporate sovereignty, either — the cleanest version of Mensch’s own case. He told the Assembly that US investors hold less than 30% of Mistral and that the founders keep strategic control, aiming for a European listing. [13] That’s true, and it does distinguish Mistral from a Microsoft-funded OpenAI. But a European cap table is a governance fact, not a competitive one. It tells you who controls the company; it tells you nothing about why a customer would choose the product over a cheaper, equally European-hosted open model. Ownership is a moat against acquisition, not against competition.

The moat that’s left, when you subtract the ones that don’t hold, is the customer list. And the customer list gives the game away.

Mistral was born inside the Rolodex

Before we read that list, rewind to where it came from. It’s tempting to picture three research “kids” who somehow assembled a blue-chip roster of backers from scratch. That gets them backward. Guillaume Lample and Timothée Lacroix were core authors of Meta’s LLaMA; Arthur Mensch came from DeepMind with his name on Chinchilla and RETRO. In the frenzied weeks after ChatGPT, they were arguably the most bankable large-model team in Europe — and all three had met years earlier at École Polytechnique, the grande école that functions as the spine of the French establishment. [14]

So they didn’t pitch their way in; the network reached out and pulled them through it. The bridge was the founders of Alan, the French insurtech unicorn: Jean-Charles Samuelian-Werve and Charles Gorintin, who introduced the team around, talked Lightspeed into leading, and worked the phones to fill the round. Gorintin and Cédric O — Macron’s former minister for digital — signed on as founding advisors. [15] The result was €105M one month after incorporation, before a single product: the largest seed in European history. [16]

And look who was already in that first cheque: Bpifrance — the French state’s own investment bank — Xavier Niel, and the shipping billionaire Rodolphe Saadé, whose CMA-CGM would two years later become Mistral’s marquee customer. The customer-patron was present at the founding. So was the political bridge, represented by Cédric O, Macron’s campaign treasurer, whose story I’ve told before.

The point isn’t that any of this was secret. It’s that none of it was. Mistral didn’t earn its way to the French establishment; it was incorporated into it. Which is why the customer list reads the way it does.

There’s a darker reading here for anyone following the question of why national AI ecosystems succeed or fail. The usual diagnosis is exclusion — the most significant builders are outsiders, the system pushed away, or had to be imported. France is the inverse. Its champion was built by the consummate insiders the system produces by design — Polytechnique, DeepMind, the right dinners — and the system’s reward for producing them was to wire them straight into state procurement. The failure mode here isn’t a talent the country couldn’t keep. It’s the opposite: a talent the country captured so completely that the product never had to compete.

For now, the Rolodex is the product

When Mensch defends Mistral’s traction, he names the same flagship customers: France Travail, CMA-CGM, Stellantis, and TotalEnergies. This spring, he added the Caisse des Dépôts, the French state investment bank. [19] Read that list not as wins but as buying decisions:

France Travail is a French government agency. TotalEnergies is a French strategic asset whose CEO doesn’t sneeze without an Élysée check-in. [20] Stellantis carries the French state’s industrial legacy through its old stake in PSA, the Peugeot-Citroën group that merged into Stellantis. [21] Caisse des Dépôts is a French state-owned institution. And CMA-CGM is owned by Rodolphe Saadé — the shipping billionaire whom Macron meets on his trips to Marseille, and who assembled BFM-TV, RMC, La Provence, La Tribune, and Brut into one of the largest newsrooms in France. [22] When La Provence ran a 2024 front page the Élysée disliked, Saadé suspended its editorial director; the journalists’ union called it political pressure. [23]

The CMA-CGM deal is the one to study. In April 2025, Saadé’s group invested €100M into Mistral and signed a five-year, $110M service contract — investor and customer, same party, the same circular structure now standard at hyperscaler scale. [24] And here’s the part that should end the “Mistral is winning enterprise on merit” story for good: the same CMA-CGM had already signed a separate $150M AI deal with Google. [25] Saadé bought Mistral the press release and Google the workload.

Now hold the strongest version of the counterargument. At the same hearing, Mensch noted that 70% of Mistral’s revenue is non-French — proof, he argued, of a genuine export champion rather than a subsidized domestic pet. [26] Take the number at face value. It doesn’t touch the argument because the moat was never part of the revenue base. Wherever that 70% lives — cross-border API calls, seat licenses, partner channels — it isn’t the source of the political moat. That lives in the flagship names, the lighthouse customers Mensch puts on the slide to validate the company to the next investor and the next government. And that list, the one that does the political and fundraising work, is almost entirely the French political-industrial complex. No Volkswagen. No Siemens. No Maersk. No ING. No Telefónica. No European reference customer of consequence outside the French orbit. Mistral may sell tokens to Europe. It anchors its credibility to the French permanent state.

That’s the moat. Not sovereignty — the President’s contact list. Mistral built a product that the most important buyers were always going to choose, and those buyers are a circle who have lunch together.

The game: legislate the Rolodex before it expires

A contact list is a fragile asset. Macron is term-limited; 2027 is coming; a contact list does not survive a change of government. So the genius — and it is genius, in a cold way — of Mensch’s spring is that every policy move converts a perishable relationship into durable law. And the conversion is self-reinforcing: each rule that raises a rival’s cost buys time, and that time is spent deepening the very relationships the rule protects, which in turn supply the political capital to write the next rule. The relationship becomes the law that governs it.

Read the spring’s moves as one design, and they line up. The 1–1.5% levy on all AI providers’ European revenue raises rivals’ operating costs in Europe and falls hardest on high-revenue American companies. A public-procurement “European preference” would codify that European equity beats European hosting — turning the Rolodex itself into a rule. The foundation-model carve-out from the AI Act trims Mistral’s own compliance bill while leaving the application-layer obligations that mostly bite US deployers. The Digital Omnibus delay buys sixteen months before any of it starts charging rent. The “vassal state” rhetoric inoculates against the obvious objection — that the French state is overpaying for a domestically preferred model. And the warning to keep the army off Anthropic’s Claude Mythos defends the single highest-value contract on the list from a stronger rival. Six moves, one direction.

Sam Altman wants to be the CEO of an AI company. Arthur Mensch wants to be the CEO of an AI market — and the difference is that markets are made of rules, and rules can be written. While Altman lobbies against regulation, Mensch lobbies for the right regulation: the kind his competitors can satisfy only at a cost they can’t bear, and he doesn’t pay.

It’s the most sophisticated regulatory game in AI right now. Calling it hypocrisy misses how good it is.

And you’re the one paying for it

A strategy this elegant still sends someone an invoice. Several someones.

French taxpayers buy a domestic-preferred model so a French logo can sit on the contract. European consumers may soon pay a 1.5% levy that, as input taxes typically do, flows at least partly downstream into prices. The French army, if Mensch gets his way, runs on the home-team model rather than the strongest available tool, because the strongest is American. And every European who wants the AI Act’s high-risk protections has to wait until December 2027 for them, courtesy of a delay sold as a boost to competitiveness.

None of that is sovereignty. It’s a subsidy — routed through procurement and regulation instead of a line item, paid to one company, and narrated in the language of national dignity so that questioning it feels unpatriotic.

The bill comes due in breaches

And the steepest cost isn’t measured in euros. France is, right now, among the most cyberattacked countries in the world, and the diagnosed root cause is a “remediation gap” — institutions that keep finding vulnerabilities and keep failing to patch them in time. [27] The identity-document agency ANTS leaked up to 19 million passport and license records; [28] much of the spree was carried out by teenagers. [29] And the marquee name on Mistral’s own customer list, France Travail, is the largest data breach in French history — tens of millions of job-seekers exposed and a €5M regulator fine in January 2026. [30] Sovereignty delivered the French logo on the contract. It did not deliver security.

Which is what makes the Mythos warning go sour. A remediation gap is exactly what a frontier vulnerability-hunting model closes — and within days of the hearing, Bloomberg reported that Mistral is building its own such model for European banks shut out of Mythos. [31] So the warning isn’t “keep dangerous vulnerability-hunters out of France.” It’s “keep the American one out, while we build and sell ours.” There is a strong security case for not allowing any foreign model to crawl through the defense code. But weigh it honestly: a country hemorrhaging data because it can’t find its own holes fast enough is being counseled to refuse the best tool for finding them. Denying France the Mythos audits may be the larger sovereignty risk, and the sovereignty argument and the product roadmap turn out to be the same document.

The bet, and how we’ll know

Here’s the falsifiable part — the thing to actually watch, rather than the rhetoric to argue about.

If Mistral’s strategy is sound, the policy moat buys enough time for the product to close on the frontier and for the company to break out of the Macron orbit into real, arm’s-length European enterprise demand. So the test is simple: by the middle of 2027, does Mistral’s flagship customer list contain names that aren’t tied to the French state or Macron’s circle? A Volkswagen. A Siemens. A bank in Milan or Madrid that chose Mistral in a competitive bake-off and paid full freight.

If yes, Mensch will have pulled off one of the great industrial strategy plays of the decade — using the rulebook to buy time to build a real business.

If no — if in two years the list is still France Travail and friends — then the policy moat was never a bridge to a product. It was the product. And policy moats have a half-life measured in election cycles. A non-Macroniste Élysée could simply stop steering the contracts. Or Brussels could decide that France’s domestic procurement, routed so reliably to one favored national champion, is a selective advantage that runs into EU state-aid rules. That is a separate exposure from the “European preference” now being drafted at the EU level — which, awkwardly for the sovereignty story, is a French-led project Mistral wants. Either way, the moment the political weather changes, the whole structure reprices overnight.

Mensch says Europe has two years to avoid becoming America’s vassal. He may be right. But Europe should be careful not to mistake one clever founder’s moat for a continent’s sovereignty — and careful, too, about who exactly it’s being asked to be sovereign for.

Mensch, in German, means “man.” In Yiddish, it came to mean something better — a person of integrity, someone who does the right thing. Watching Monsieur Mensch this spring, the open question isn’t whether he’s brilliant. It’s the kind of mensch France thinks it’s buying.

Notes

[1] Assemblée nationale (official video) — Vulnérabilités systémiques dans le secteur du numérique: audition de M. Arthur Mensch (May 12, 2026; the near-empty room is visible on the official feed)

[2] Fortune — Anthropic says it’s testing “Mythos,” a powerful new AI model representing a “step change” in capabilities (the model’s full name per Anthropic’s April 7, 2026 system card is “Claude Mythos Preview”)

[3] The Decoder — Mistral CEO Arthur Mensch warns France against letting Anthropic’s Mythos scan military code bases (also the source for Mensch’s concession that Mistral’s or Chinese models could find the same vulnerabilities)

[4] Council of the EU — Artificial intelligence: Council and Parliament agree to simplify and streamline rules (official press release, May 7, 2026)

[5] Le JDD — Fiscalité, énergie, dépendance: le patron de Mistral AI alerte sur les faiblesses de l’Europe (May 15, 2026)

[6] Assemblée nationale (official video) — audition de M. Arthur Mensch, “vassal state” / two-year warning (same hearing, May 12, 2026)

[7] IT Pro — Mistral CEO calls for AI cultural levy (reporting Mensch’s Financial Times op-ed, March 20, 2026)

[8] Boursorama (AFP) — Taxe Zucman: le patron de Mistral demande “plus de justice fiscale” tout en préservant la compétitivité de la France

[9] Mistral AI / Hugging Face — Mistral-Medium-3.5 model card (official benchmarks: dense 128B parameters; 77.6% SWE-Bench Verified)

[10] TechSifted — Mistral Medium 3.5 review (independent comparison: 77.6% vs. Claude Sonnet 4.6’s 79.6% on SWE-Bench Verified; ~half the per-token price; open weights under modified MIT terms)

[11] Maddyness UK — Mistral AI on track to reach one billion euros in revenue by 2026 (Mensch at Davos; ~$400M ARR, €1bn a target for the year, not booked revenue)

[12] Reuters (via Yahoo Finance) — OpenAI CFO says annualized revenue crosses $20 billion in 2025 (ARR and “annualized run-rate” are adjacent but not identical metrics; the orders of magnitude make the comparison regardless)

[13] The Decoder — Mistral CEO Arthur Mensch warns France… (Mensch’s statement that US investors hold under 30% and founders retain strategic control)

[14] Sifted — Meta and DeepMind alumni raise €105m seed round to build OpenAI rival Mistral (founders’ LLaMA / DeepMind pedigree; École Polytechnique)

[15] TechCrunch — Alan’s founder role in Mistral’s origin story (Samuelian-Werve and Gorintin as connectors; Cédric O founding advisor)

[16] TechCrunch — France’s Mistral AI blows in with a $113M seed round at a $260M valuation (full investor roster incl. Bpifrance, Niel, Saadé, Schmidt)

[17] Caisse des Dépôts (official) — Souveraineté numérique: le groupe Caisse des Dépôts s’adjoint les services de Mistral AI (May 2026)

[18] TotalEnergies (official) — TotalEnergies to collaborate with Mistral AI to increase the application of AI in its multi-energy strategy

[19] Stellantis (official) — Stellantis and Mistral AI expand their collaboration to accelerate enterprise-wide AI adoption (Oct 2025)

[20] CMA CGM Group (official) — CMA CGM completes acquisition of Altice Media (BFM-TV, RMC; group also owns La Provence, La Tribune, Corse Matin)

[21] Puremédias / Ozap — “La Provence”: Rodolphe Saadé met à pied le directeur de la rédaction après une Une qui aurait déplu à l’actionnaire (March 2024; “political pressure” is the journalists’ union’s characterization)

[22] The Maritime Executive — CMA CGM Group: new custom-designed AI solutions from Mistral AI (€100M investment + five-year $110M contract, April 2025; figures as reported in mixed currencies)

[23] CMA CGM / PR Newswire (official) — CMA CGM embarks on a strategic partnership with Google to deploy AI across all shipping, logistics, and media activities (the separate $150M Google deal, 2024 — predating the Mistral deal)

[24] Angelo Lima (hearing analysis, cross-checked to the Assemblée nationale feed) — What Arthur Mensch told the French National Assembly (Mensch’s claim that 70% of Mistral revenue is non-French; secondary analysis of the official hearing)

[25] Cybernews — Experts warn France “operationally paralyzed” as cyberattacks mount in 2026 (single-source characterization; “among the most-attacked” softened from “second-most” pending an ANSSI/CNIL primary)

[26] Cybernews — ANTS hack: 19 million records exposed in French ID agency breach (April 2026)

[27] The Record — French police arrest suspected hacker behind dozens of data breaches (HexDex, 21, ~100 breaches incl. sports federations, Education Ministry, SIA)

[28] CNIL (official) — Data breach: France Travail fined €5 million (Jan 22, 2026)

[29] Bloomberg — European Banks Explore Mistral AI’s Alternative to Anthropic’s Mythos Model (May 13, 2026; Mistral developing its own vulnerability-detection model for European banks shut out of Mythos)

The Trump-Xi summit in Beijing on May 14-15 was supposed to trade chips for rare earths. Washington would ease restrictions on advanced AI accelerators heading to China. Beijing would open the licensing gate on the rare earths and functional materials that feed every semiconductor fab on the planet. Two interlocking grips, mutually released.

No deal.

On May 15, the US Trade Representative sat down with Bloomberg Television. Asked whether semiconductor export controls had come up during the summit that had just concluded, Jamieson Greer answered without hedging: “This was not a major topic of discussion at the bilateral meeting. We did not talk about chip export controls at the meeting.”[1]

One side of the trade is denied at the principal level.

Last week, this newsletter previewed the summit with three specific tests.[2]

1. An exemption from China’s case-by-case licensing for the rare earths used in advanced AI chips (sub-14-nanometer logic, 256-layer memory).

2. A Chinese commitment to replace case-by-case review with blanket export approvals for the functional materials flowing through every semiconductor fab: polishing slurries, sputtering targets, and non-military magnets.

3. A mutual rollback of the October 2025 rule under which Beijing can require an export license for any foreign-made product anywhere in the world that contains more than 0.1% Chinese-origin rare earth content.

Three tests. Three strikes. The dependency the trailer described — rare earths as the layer beneath chips, cloud, and models — survived the summit intact.

The two readouts

The White House Fact Sheet of May 17 announced that China would “address U.S. concerns regarding supply chain shortages related to rare earths and other critical minerals, including yttrium, scandium, neodymium, and indium,” and would “address U.S. concerns regarding prohibitions or restrictions on the sale of rare earth production and processing equipment and technologies.”[3] The verbs are “address” and “concerns.” That is the language of diplomatic intention. It is not the language of a regulatory commitment.

The Chinese readouts said nothing about rare earths.

Xi Jinping’s statement, issued by the Ministry of Foreign Affairs on May 14, covered “strategic stability,” agricultural trade, and Taiwan.[4] The MOFCOM follow-up on May 17 discussed tariff reductions and announced two new bilateral bodies: a US-China Board of Trade and a US-China Board of Investment.[5] CNBC noted the gap on May 18: “The Chinese statement also did not mention rare earths, while the U.S. said China would address rare earth shortages.”[6]

This is a pattern, not an accident. At Busan in October 2025, the White House announced that China had committed to “issue general licenses valid for exports of rare earths, gallium, germanium, antimony, and graphite for the benefit of U.S. end users and their suppliers around the world.” Beijing never confirmed that framing in writing. The gate has stayed narrow. The EU Chamber of Commerce in China reported that MOFCOM approved fewer than 15% of rare-earth license applications submitted by EU firms in 2025, leading to seven production stoppages in August and 46 expected in September.[7] As of December 2025, three Chinese exporters held streamlined general licenses: JL Mag Rare Earth, Ningbo Yunsheng, and Beijing Zhong Ke San Huan.[8]

Beijing has now declined twice, at Busan and at Beijing, to confirm in writing the rare-earth language the White House has put out. The licensing gate has stayed closed throughout.

Chips off the table

The first two tests required leader-level negotiated outcomes on chip-specific carveouts.

• Test 1: an exemption from MOFCOM’s case-by-case licensing for the rare earths used in advanced AI chips.

• Test 2: a Chinese commitment to replace case-by-case review with blanket export approvals for functional semiconductor materials.

Greer’s answer closes the path by which either could have happened. If chip export controls were not discussed at the leader level, no carveout for sub-14-nanometer chips was negotiated. No blanket-approval commitment was extracted. The “address U.S. concerns” language in the fact sheet is an aspiration. The rules in force are still MOFCOM Notice 61 of October 9, 2025, with the case-by-case review for sub-14-nanometer logic and 256-layer memory currently sleeping under Notice 70.[9] Neither was rescinded. Neither was modified. Neither was discussed.

Jensen Huang said the quiet part out loud at a Citadel Securities event two weeks before the summit: “In China, we have now dropped to zero. Conceding an entire market the size of China probably does not make a lot of strategic sense, so I think that has already largely backfired.”[10] The remark concerned the H200, the AI accelerator Nvidia is licensed by the US to ship to roughly ten approved Chinese firms. Among the buyers are Alibaba, Tencent, ByteDance, and JD.com; among the distributors, Lenovo and Foxconn. Each shipment carries a 25% remittance to the US Treasury and physical transit through US territory for inspection.[11] Trump told reporters aboard Air Force One that the Chinese firms had “chose not to” buy “because they want to develop their own.”[12]

Three days after returning from Beijing, Huang reversed course. Asked at a Dell event in San Francisco on May 18 whether the Chinese market would reopen to Nvidia, he answered: “My sense is that over time, the market will open.”[13] Reuters framed the H200 file more pointedly: “Nvidia has received licenses from the U.S. government to sell its H200 chips but has not received approval from Chinese officials who are fostering China’s own chip suppliers.”

Huawei Ascend, Cambricon, and Biren are not waiting for Nvidia’s return. They are closing the gap while the H200 file sits in MOFCOM’s review queue.

The gate runs both ways. Beijing can stop delivery of US-approved chips through State Council guidance just as Washington can stop delivery of advanced GPUs through Commerce Department rules. The coercion stack the trailer described is not one-sided. Markets priced it within hours. Nvidia closed at $225.04 on May 15, down 4.20%, erasing roughly $170 billion of market value intraday.[14]

The cliff

The third test asked whether the summit would rescind China’s October 2025 extraterritorial 0.1% rule, the provision under MOFCOM Notice 61 that lets Beijing require its approval to export any foreign-made product anywhere in the world that contains more than 0.1% Chinese-origin rare earth content. The rule was suspended on November 7, 2025 under MOFCOM Notice 70. The suspension expires November 10, 2026.[15]

The summit produced no announcement closing this cliff. No language in the White House fact sheet addresses Notice 61 specifically. No Chinese regulatory action followed the summit. The cliff remains live and is scheduled to re-arm automatically in six months.

This is the deepest finding of the summit. Beijing’s most powerful tool was not given up. It was not contested. It was not even discussed at the leader level, by the USTR’s own account. It was left in place, suspended on a calendar timer. November 10 is when the paper rules catch up to the practice on the ground. MOFCOM has held approval rates below 15% throughout the suspension; the licensing gate has been closing in operation while sleeping on paper. The cliff is when the paper wakes up.

The next signal arrives in September, when Xi is scheduled to visit Washington during United Nations General Assembly week. If he arrives without a renewed suspension already in writing, the cliff becomes the central deal of the cycle. APEC in Shenzhen follows in November, two weeks after the suspension expires. The summit calendar has been arranged around the regulatory calendar, not against it.

What markets read

Lynas Rare Earths fell from A$19.90 on May 13 to A$17.95 on May 15, a 9.8% decline in two trading sessions.[16] MP Materials rallied to $61.27 on May 15, then dropped 7.5% to $56.67 on May 18 as the “tactical truce” reading took hold.[17] The supply-side equities priced the same conclusion the Greer interview made plain: nothing had moved underneath. The rally that built into the summit was unwound by what the summit failed to produce.

The ex-China spot prices tell the same story. Terbium oxide averaged $1,140 per kilogram FOB in late April; dysprosium oxide averaged $292 per kilogram.[18] Inside China, the same materials cleared at roughly $895 and $125 per kilogram, respectively — the Western buyer pays a quarter more for terbium and more than double for dysprosium. That spread is the cost of the licensing gate, what the marginal Western buyer pays when MOFCOM approves fewer than 15% of applications. It did not collapse during summit week. It widened.

The supply-side response continues on its own timeline, indifferent to the summit. MP Materials begins commissioning heavy rare earth separation at Mountain Pass in mid-2026, targeting 200 metric tons per year of dysprosium and terbium combined.[19] Lynas continues its Malaysian expansion. Iluka’s Eneabba refinery is now targeted for 2027 commissioning, slipping from earlier 2026 guidance.[20] Combined Western heavy rare earth capacity at full ramp is on the order of 600 metric tons per year by 2028, a fraction of the heavy rare earth content embedded in the 58,000 tons of permanent magnets China exported in 2024 alone.[21]

The summit did not change any of these timelines. It did not need to. The diversification is happening regardless. The cliff is on the calendar regardless.

What the summit settled

The trailer argued that rare earths form the fourth layer of the AI infrastructure coercion stack, under chips, cloud, and models. The Beijing summit tested that argument against three concrete questions. Each question required a specific regulatory action that would have shown leader-level willingness to ease the rare earth grip. None of the three occurred.

The summit produced agricultural commitments, Boeing aircraft orders, beef market access restoration, and two new bilateral talking shops. These are real diplomatic outputs. A lower geopolitical temperature reduces tail risk; the next confrontation is postponed. But they are the deliverables of a managed-stability summit, not of a rebalancing of the underlying dependence. Greer’s sentence confirms the boundary: leader-level discussions did not reach the rules that hold the rare earth grip in place. Working-level talks may continue. Without principal-level direction, MOFCOM has no political cover to dismantle the rules it issued under leader-level authority five months ago.

Six months from now, on November 10, 2026, MOFCOM Notice 70 expires. Either Beijing extends the suspension before that date, in writing, or the extraterritorial 0.1% rule re-arms automatically. The two scheduled summit appearances — Xi in Washington in September, Trump and Xi at APEC Shenzhen in November — are the venues where that decision will be made.

Last week, this newsletter set three tests for the Beijing summit. The summit returned each test unchanged. The exposure the trailer described was not negotiated away. It was scheduled forward.

The chip war happens in press releases. The war underneath happens on the regulatory calendar.

Notes

[1] Jamieson Greer, US Trade Representative, Bloomberg Television interview, May 15, 2026, as reported by Reuters: “Chip export controls not major topic in China talks, US trade rep Greer tells Bloomberg News”.

[2] “Below the Silicon”, The AI Realist, May 13, 2026.

[3] “Fact Sheet: President Donald J. Trump Secures Historic Deals with China, Delivering for American Workers, Farmers, and Industry”, The White House, May 17, 2026.

[4] “President Xi Jinping Holds Talks with U.S. President Donald J. Trump”, Ministry of Foreign Affairs of the People’s Republic of China, May 14, 2026.

[5] “White House touts deals on soybeans and rare earths after Trump-Xi summit, while China talks up tariff cuts”, CNBC, May 18, 2026.

[6] Ibid.

[7] “False sense of security: European complacency on rare earths is the wrong answer to the US-China trade truce”, European Union Institute for Security Studies, citing EU Chamber of Commerce in China data, accessed May 2026.

[8] “China issues first batch of streamlined rare earth licences”, Mining.com, December 2, 2025.

[9] MOFCOM Notice 61 of October 9, 2025; MOFCOM Notice 70 of November 7, 2025, suspending the extraterritorial provisions until November 10, 2026. Analysis: Pillsbury Winthrop Shaw Pittman, “China Suspends Export Controls on Certain Critical Minerals and Related Items”; Clark Hill, “China Hits ‘Pause’ on Rare-Earth Export Controls and What it Means for Supply Chains”.

[10] Jensen Huang, remarks at Citadel Securities event, early May 2026, as reported by Tom’s Hardware: “Trump says China is blocking Nvidia H200 purchases despite US approval — says country ‘chose not to’ sanction purchases, pushing homegrown chips instead”.

[11] H200 framework details per Implicator, “Nvidia H200 China Deliveries Stalled After Trump-Xi Summit”, May 2026.

[12] Trump remarks aboard Air Force One, May 15, 2026, as reported by Tom’s Hardware (op. cit.).

[13] “Nvidia CEO says he believes China market will open over time”, Reuters, San Francisco, May 18, 2026 (Bloomberg Television interview at Dell event).

[14] “Delayed Chinese approval for H200 chips sends Nvidia stock down 4.20%”, Traders Union, May 15, 2026, citing Google Finance.

[15] Pillsbury Winthrop Shaw Pittman, op. cit.; Clark Hill, op. cit.; MOFCOM Announcement No. 70 of 2025.

[16] Lynas Rare Earths (ASX: LYC) close prices per ASX official data, accessed via StockAnalysis.com.

[17] MP Materials (NYSE: MP) close prices per Morningstar; “Lynas Tumbles as ‘Trump–Xi Truce’ Lifts False Calm Over Rare Earths”, Rare Earth Exchanges, May 18, 2026.

[18] Rare earth FOB spot price data per Rare Earth Exchanges market reports, May 2026; “Rare Earth Market Outlook May 2026: Prices Fall”, Rare-earth-mining.com.

[19] MP Materials Q3 2025 earnings release; “Pentagon-Backed MP Materials to Start Rare Earths Plant in 2026”, Bloomberg, November 6, 2025.

[20] Iluka Resources Q1 2026 financial reporting; “Eneabba Rare Earths Refinery Funding Update”, Iluka Resources ASX release, December 6, 2024.

[21] IEA, “Global Critical Minerals Outlook 2025”, October 2025, citing 2024 Chinese permanent magnet export volumes.

There are exactly two US-listed names with direct HALEU exposure. One of them is the obvious pick — funded by the Department of Energy, owned by ~80% of institutions, up 200% in the last twelve months. The other is a $700M micro-cap whose enrichment subsidiary you’ve probably never heard of.

Thanks for reading! Subscribe for free to receive new posts and support my work.

I think the smaller one is the better trade today. Not because the bigger name is bad, it isn’t, but because the market has already priced its bull case, and the smaller name is the only fundamentally cheap HALEU option in the US public market.

Here’s the work.

The two listed names

Centrus Energy (NYSE: LEU) is the name. It is the only US-owned commercial enricher and one of three companies funded by the DOE’s January 2026 $2.7B HALEU and LEU enrichment award.

Centrus’s American Centrifuge Operating subsidiary received $900M for HALEU production at Piketon, Ohio, and produced the first ~900 kg of US-origin HALEU. Centrus raised 2026 revenue guidance to $450–500M in its Q1-26 print (https://www.prnewswire.com/news-releases/centrus-reports-first-quarter-2026-results-302763250.html), and is sitting on a $3.9B contracted backlog. Market cap $4.37B.

ASP Isotopes (NASDAQ: ASPI) is the optionality name. Its core business is laser-based isotope enrichment for medical (Mo-99 path), semiconductor (Silicon-28), and pharmaceutical applications. The HALEU exposure is via a wholly-owned subsidiary, Quantum Leap Energy (QLE), which holds a long-term HALEU offtake agreement with TerraPower plus a $22M conditional loan, and which signed a non-binding MOU in March 2026 (https://www.stocktitan.net/news/ASPI/) with a major US nuclear power operator for HALEU, LEU+, uranium conversion, and deconversion services. Market cap $690M, of which $333M is cash as of December 2025.

The numbers side-by-side:

If you only look at the top three rows, Centrus is obviously the better company. It has revenue, it has guidance, it has DOE money, and the chart has only gone up. ASP Isotopes is small, loss-making, and the stock has gone nowhere for a year while the rest of the nuclear thematic has rallied.

But the bottom three rows are where the trade actually lives.

Where the value actually is

I built probability-weighted scenario DCFs on both names.

Centrus scenarios (my P-weights):

Probability-weighted fair value: ~$169/share. Current price $222. That gap doesn’t mean Centrus is overvalued in any absolute sense — it means the market is pricing the bull-case outcome at roughly 60–70% probability, versus my 30%. Either I’m wrong about the probabilities, or the market is paying ahead of execution. Both can be true at once.

ASP Isotopes scenarios:

Weighted operating NPV ~$0.74B, plus $333M cash on hand → fair equity ~$1.07B. Current market cap $690M. That’s a +55% asymmetric setup, with the cash backstop providing a soft floor.

Three observations from running these numbers.

First, the asymmetry runs in opposite directions. Centrus’s bear case is –80% from current; ASPI’s bear case is –78%. That looks similar. But ASPI’s bear case still leaves you with $150M of NPV against $333M of cash, so the actual equity floor is higher than the bear-NPV number suggests. Centrus’s bear case has no cash floor — it’s a working business, and the bear case is operational impairment. The shape of the downside is different even when the magnitude is similar.

Second, insider ownership is doing real work. ASPI’s 13.5% insider ownership versus Centrus’s 3.3% (and NuScale’s 0.4%) is the kind of management-alignment signal that tends to matter at exactly the inflection moment ASPI is approaching — the 2026 commercial-shipment year. Founders who own the company tend not to price-collapse it on the first dilutive raise.

Third, the TerraPower offtake is a third-party validation that the market hasn’t internalized. TerraPower is privately held, well-funded, and has every incentive to source HALEU from the most credible producer it can find — including, in theory, from Centrus directly. The fact that TerraPower committed offtake terms and a $22M conditional loan to QLE specifically tells you the market is too pessimistic on QLE’s technical credibility.

The catalysts most people aren’t tracking

Both names have a thick catalyst calendar through the end of 2027. The two that matter most for getting positioning right are very specific.

For Centrus, the binary is the Q2-26 print in August, where management will disclose Piketon HALEU production cadence in kg/month run-rate. The current implied schedule has Piketon ramping toward roughly 6 metric tons per year of HALEU output by 2028. That implies a run-rate around 80 kg/month at maturity. If the August print shows the production cadence tracking below ~40 kg/month — half the implied path — the bear case activates fast and the multiple compresses with it. If it tracks at or above 60 kg/month, the bull case stays alive, and the stock probably runs further before consolidating.

For ASPI, the binary is QLE’s first HALEU pilot output disclosure, expected in Q4 2026. This is the cleanest existence proof the market has been waiting for. If QLE produces enriched material on schedule, the bull-case probability re-weights upward — and at a $690M market cap, the re-rating math is significant. If QLE misses by more than two quarters, the bear-case probability dominates, and the cash floor becomes the only thing holding the stock up.

Two other dates worth flagging:

• The Russia uranium waiver expiry in 2027 — under the Prohibiting Russian Uranium Imports Act is a structurally positive catalyst for both names, but more so for Centrus, which loses Russia LEU revenue but gains tighter pricing on its US-domestic enrichment.

• Centrus’s first commercial HALEU shipments, targeted for Q2 2027, are the bull-case proof point. If those land on schedule with TerraPower, X-energy, or Kairos as the first counterparty, Centrus becomes harder to fade.

Dante

All opinions are mine, not financial advice.

What this means for stock-picking

1. Centrus is the right structural answer to the wrong question. “Which name has the most HALEU exposure?” gets you to LEU. “Which HALEU name offers asymmetric upside at current prices?” gets you to ASPI. Both questions are valid, but only one is a trade.

2. The size discount is doing the lifting. ASPI is small enough that institutional ownership hasn’t yet crowded out the asymmetry — 51.6% versus Centrus’s 79.3%. The same business at $4B of market cap would already be priced in line with Centrus.

3. Optionality positions need explicit exits. I would hard exit if QLE produces no enriched HALEU material by year-end 2026, or if TerraPower offtake terms are publicly restructured downward. The cash backstop makes the position survivable; the falsification triggers make it disciplined.

4. Centrus is a buy on pullback, not a buy on chase. I would build a position below $165, where the implied bull-case probability falls into a range that matches my analytical view. Above $200, the math doesn’t work even on aggressive assumptions.

5. Both names will be revisited together every quarter. The catalyst structure is interlocking — Centrus’s Piketon cadence and ASPI’s QLE pilot are the two existence proofs that determine whether US-owned HALEU is real or theoretical. Watching only one of them gives you half the signal.

What’s coming

• Post 3 — Conversion: the bottleneck nobody can play directly. Why ConverDyn / Solstice’s Metropolis Works is the single tightest commercial chokepoint in the chain, and how an HON Advanced Materials spin (rumored, not confirmed) would unlock the cleanest pure-play if it ever lists.

• Post 4 — *Picks-and-shovels*. The mid-cap that passes the 4-variable filter in two of seven segments simultaneously, and why I think it’s a satellite rather than a core position, despite that.

• Post 5 — *SMR demand*. Why I think the post-CFPP-cancellation reset on NuScale is more advanced than the market recognizes — and why that doesn’t yet mean I’m long.

• Post 6 — *The book*. Five names, position-sized, with explicit falsification triggers for each.

Subscribe if you want this in your inbox over the next weeks.

Further reading

- DOE — *[Awards $2.7B to restore American uranium enrichment](https://www.energy.gov/articles/us-department-energy-awards-27-billion-restore-american-uranium-enrichment)* (Jan 6, 2026)

- Centrus Energy — *[Q1-26 results press release](https://www.prnewswire.com/news-releases/centrus-reports-first-quarter-2026-results-302763250.html)*

- ASP Isotopes — *[Q3-25 10-Q via SEC EDGAR / StockTitan summary](https://www.stocktitan.net/sec-filings/ASPI/10-q-asp-isotopes-inc-quarterly-earnings-report-b8eb89c3dea3.html)*

- World Nuclear News — *[US enrichment funding recipients flesh out plans](https://www.world-nuclear-news.org/articles/us-enrichment-funding-reactions)*

- ANS Nuclear Newswire — *[DOE awards $2.7B for HALEU and LEU enrichment](https://www.ans.org/news/article-7652/doe-awards-27b-for-haleu-and-leu-enrichment/)*

- Prohibiting Russian Uranium Imports Act ([P.L. 118-62](https://www.congress.gov/bill/118th-congress-house-bill/1042), May 2024)

---

*Capacity Factor is a six-part series on US nuclear fuel-cycle equities.

Thanks for reading! Subscribe for free to receive new posts and support my work.

Inside a TSMC fab in Taiwan, at this moment, an Nvidia Blackwell die is being polished flat to within fractions of a nanometer. A few meters away, a lithography scanner is exposing the next wafer with extreme-ultraviolet light generated by vaporizing tin droplets with a 30-kilowatt laser, 50,000 times a second. This is the most precise industrial process in human history.

It runs on rare earth elements. China mines 70% of the world’s supply and refines 91% of it. America refines less than 1%.[1]

On Wednesday, the President of the United States flies to Beijing to negotiate continued access.

The recipe

The first step is the polish. Before a chip can be patterned, the silicon wafer has to be made flat to within fractions of an atom across an area the size of a dinner plate. This is done with a slurry of fine abrasive particles. The abrasive is cerium oxide, a rare-earth compound made almost entirely in China.[2]

Next comes lithography: the printing of the chip’s pattern onto the wafer using extreme-ultraviolet light. Three rare earths appear in the light path. Erbium is doped into the optical fibers that amplify the laser’s pulse. Terbium forms a special crystal — terbium gallium garnet — that lets light through one direction and blocks it in the other, protecting the laser from its own reflections. Thulium will be used in the next generation of these lasers, currently under development at Lawrence Livermore National Laboratory. The lithography machines that will use them are built by ASML — the Dutch company that supplies every advanced fab in the world.[3]

Between exposures, a metrology laser checks that the pattern came out right. The crystal at its heart is often Nd:YAG — yttrium aluminum garnet, doped with neodymium.[4] After exposure, the patterned features are etched into the silicon by corrosive fluorine and chlorine plasmas. To survive the plasma, the etch chamber is lined with yttrium oxide.[5]

Then comes deposition: laying down the metal films that become the chip’s wiring. The way to deposit a metal film is to put a solid block of it (a “sputtering target”) into a vacuum chamber and knock atoms off it with ions. Most sputtering targets are pure metals — copper, tungsten, titanium — but the targets that lay down the high-performance dielectric layers and certain barrier materials contain rare earths, most often yttrium and lanthanum.[6] Finally, the chip is packaged. In a modern AI accelerator, packaging means stacking multiple silicon dies into high-bandwidth memory — the “HBM” the industry talks about — and bonding them with millions of microscopic copper joints. Between each bonding step, the surfaces are polished flat again, with the same cerium oxide slurry that started the process.

Then the chip leaves the fab. It arrives at a hyperscaler datacenter on a server board cooled by spinning fans. The motors driving those fans are made from neodymium magnets — alloys of iron, boron, and neodymium, almost always with a small percentage of dysprosium or terbium added to keep them magnetic at high temperatures.[7] The same magnets power the hard drives, the liquid-cooling pumps that keep modern GPU racks from melting, and every motorized actuator in the rack.

Behind the chip, the tools that fabricated it run on the same chemistry. Every lithography scanner, every ion implanter, every etch tool — the precision motors are all neodymium magnets, with the highest-performance versions in fab equipment carrying up to ten percent dysprosium by weight.[8] The magnetic bearings on many cleanroom and vacuum pumps are neodymium too. So are the robotic arms that move wafers between tools.

A modern AI accelerator is, in material terms, a tightly packed assembly of silicon, copper, and rare-earth elements. The silicon and copper have multiple commercial sources. The rare earths do not. Substitutes exist for some uses but perform worse — there is no commercial alternative to cerium oxide at advanced lithography nodes, and no replacement for the heavy rare earths in high-temperature magnets.

The dependency

China controls roughly 70% of global rare earth mining, 91% of separation and refining, and 94% of the world’s strongest permanent magnets — the kind used in motors, generators, and precision equipment.[9] The geological deposits that yield commercial quantities of the heavy rare earths used in those magnets — dysprosium and terbium — are a specific type of clay-bound ore (geologists call them ion-adsorption clays), found in commercial concentrations only in southern China and northern Myanmar. Together, they account for more than 99% of the world’s heavy rare-earth feedstock, with Myanmar production largely flowing into Chinese refineries.[10]

Last year, every gram of terbium America imported came from China. So did every gram of holmium, and every gram of lutetium. Net U.S. import reliance on heavy rare earths is 100%; the small share nominally sourced from third-country processors in Estonia, Japan, and Malaysia is itself derived from Chinese feedstock.[11]

This is the layer beneath the chip war. “Access, Disable, Destroy” mapped a three-switch model of AI infrastructure coercion: chips at the silicon layer, cloud at the infrastructure layer, models at the application layer.[12] The materials layer sits beneath all three. China has commercial and diplomatic reasons not to embargo rare earths outright — its producers want the revenue, and a formal cutoff would accelerate Western diversification.

The leverage operates instead through individual export approvals: China’s Ministry of Commerce (MOFCOM) requires a case-by-case license for any shipment of rare earths destined for advanced semiconductors. The trigger categories are logic chips at process nodes below 14 nanometers (every AI accelerator made today) and memory stacked with more than 256 layers (the high-bandwidth memory inside those accelerators). This licensing regime remains active throughout the November 2025 suspension.[13] A single review can stall a shipment indefinitely, even without a formal export ban. Diversification at the binding constraint takes time that the AI capex cycle does not have: industry estimates place full onshoring of heavy rare-earth refining at 5 to 7 years.[14]

The response

On February 2, 2026, Donald Trump announced Project Vault — a $12 billion strategic reserve of rare earth elements, modeled on the Strategic Petroleum Reserve that has insulated the United States against oil shocks since the 1970s. The signal: the administration now treats rare earth dependency as a national security exposure on par with energy security. The structure is a $10 billion, 15-year loan from the Export-Import Bank, plus roughly $1.7 billion of private capital, with procurement handled by three commodities trading houses.[15] They buy imported oxides and metals on behalf of civilian-sector manufacturers, who can draw down their allocations in a disruption and replenish them when supply normalizes.[16] At blended heavy rare earth prices — terbium oxide at $1,010 per kilogram, dysprosium at $239 — $12 billion is a serious buffer against price spikes and short interruptions.

It does not address the binding constraint. The United States has no commercial-scale heavy rare earth separation capability operating today.[17] MP Materials’ Mountain Pass heavy rare earth circuit, backed by a $150 million Department of War loan, targets 200 metric tons per year of dysprosium and terbium production from mid-2026.[18] Lynas, the only commercial-scale producer of separated heavy rare earths outside China, is expanding its Malaysia facility to a full suite of heavy rare earths within two years.[19] Combined Western capacity at full ramp is on the order of 600 metric tons per year of dysprosium and terbium by 2028 — a fraction of the heavy rare-earth content embedded in the 58,000 tons of permanent magnets China exported in 2024 alone.[20]

What Project Vault stockpiles is what comes out of the country it was designed to protect against. The reserve relocates the dependency one step upstream — from end-use to inventory — without changing the upstream geography. Meanwhile, the chokepoint is moving. In March 2026, Shenzhen launched a state-coordinated R&D program for domestic rare-earth-based polishing slurries — the same cerium oxide chemistry the wafer polish opens with, currently dominated by U.S. and Japanese suppliers.[21] The pattern is consistent: control raw materials upstream, control separation in the middle, and as Western capacity catches up at the upstream layers, move downstream into the higher-margin functional materials. Each Western response addresses a layer that the chokepoint has already moved past.

What to watch on Friday

The summit will produce announcements. Boeing purchases. Agricultural commitments. A bilateral Board of Trade. Possibly an extension of the November 2025 suspension beyond the November 10, 2026 expiry, framed as continued de-escalation.[22] None of these alters the materials layer.

Three things would. First, an exemption from MOFCOM’s case-by-case licensing for the rare earths used in advanced AI chips — the sub-14-nanometer logic and 256-layer memory categories now requiring individual Chinese approval. This would dissolve the most direct chokepoint. Second, a commitment to blanket licenses rather than per-shipment review for the functional materials flowing through semiconductor manufacturing: polishing slurries, sputtering targets, and non-military magnets. That would turn managed dependency into something predictable. Third, a mutual rollback of China’s October 2025 extraterritorial rule, which lets Beijing license any foreign-made product anywhere in the world that contains more than 0.1% Chinese-origin rare earths. That rule is currently suspended; rescinding it would close the November cliff rather than postpone it.

None of these is on the agenda that the U.S. Trade Representative previewed in April.[23] The summit is one whose success is measured by the absence of breakdown, not by the resolution of substance.

Every Blackwell, every MI300, every TPU, every Trainium, every HBM stack from Samsung and SK Hynix carries this recipe inside it. The rare earths are extracted from Chinese land. The chips are built by TSMC on Chinese land — or so they say.

Beijing claims both halves as Chinese. It controls only one. By Friday, the President will have negotiated with the half it controls. Taiwan, where the chips are made, will be the silence in the room.

Notes

[1] Mining figures: U.S. Geological Survey, Mineral Commodity Summaries 2025: Rare Earths, January 2025. China mined 270,000 metric tons of REO equivalent in 2024, accounting for 69.2% of the world total (390,000 tons); the United States mined 45,000 tons. Refining figures: International Energy Agency, “With new export controls on critical minerals, supply concentration risks become reality,” October 9, 2025. China = 91% of global rare earth separation and refining; 94% of sintered permanent magnet production. U.S. domestic production of refined rare earth compounds and metals in 2024 was approximately 1,300 tons (USGS) — roughly 0.3% of global production. Most U.S.-mined concentrate is exported for refining elsewhere, principally to China.

[2] Cerium oxide is the dominant abrasive in chemical-mechanical planarization slurries used for advanced-node silicon wafer polishing; its abrasive properties at sub-nanometer scales are not matched by available substitutes. Chinese mining accounts for the majority of global cerium supply, and Chinese separation accounts for the overwhelming majority of refined cerium oxide production.

[3] Lawrence Livermore National Laboratory, “LLNL selected to lead next-gen extreme ultraviolet lithography research,” December 23, 2024. Erbium-doped fiber amplifiers are standard in the seed-laser stages of EUV light-source pre-pulse generation. Terbium gallium garnet (TGG) is the standard material for Faraday optical isolators in DUV and short-wavelength laser systems, including those used in lithography, metrology, and inspection. Thulium-doped yttrium lithium fluoride is a candidate gain material for next-generation high-numerical-aperture EUV sources.

[4] Neodymium-doped yttrium aluminum garnet (Nd:YAG) is a long-established laser crystal used in fab metrology, alignment, inspection, and certain marking applications. See Vimaterial industry overview, “Rare earth materials for a brighter future,” February 26, 2026.

[5] Yttrium oxide ceramic coatings are standard for plasma etch chamber liners due to their resistance to fluorine and chlorine plasma chemistries; they reduce particle contamination and extend chamber service intervals. See industry technical literature on plasma etch chamber materials.

[6] Sputtering targets composed of rare-earth metals and oxides are used in physical vapor deposition of barrier layers, electrodes, and functional thin films in semiconductor manufacturing. Yttrium, gadolinium, and other rare earths appear across multiple deposition recipes.

[7] Standard NdFeB permanent magnet formulations contain 1–3% dysprosium or terbium for elevated-temperature applications. Industry-standard composition; see also USGS MCS 2026, Rare Earths (Heavy) chapter.

[8] Higher-performance NdFeB grades used in precision-motion applications (semiconductor manufacturing equipment, certain medical devices, defense applications) can contain heavy rare-earth content of up to approximately 10% by mass, depending on temperature and demagnetization-resistance requirements.

[9] Mining share: USGS MCS 2025, op. cit. (China 270,000 / world 390,000 = 69.2% in 2024). Refining and magnet shares: IEA, op. cit. (91% separation, 94% sintered permanent magnets).

[10] Payne Institute for Public Policy (Colorado School of Mines), “Explainer on the MP Materials–Department of War Partnership,” August 2025. The principal global sources of separated heavy rare earths, such as dysprosium and terbium, are ion-adsorption clay (IAC) mining operations; the only notable IAC operations in the world are in China and Myanmar (>99%), with the Myanmar production typically flowing into Chinese separation facilities.

[11] U.S. Geological Survey, Mineral Commodity Summaries 2026: Rare Earths (Heavy), February 2026. US heavy rare-earth imports in 2025: 100 metric tons of compounds and metals. Net import reliance 100% across 2021–2025. Terbium imports 100% from China; holmium 100% from China; lutetium 100% from China (including Hong Kong); ytterbium 86% from China.

[12] “Access, Disable, Destroy,” The AI Realist.

[13] White & Case LLP, “China imposes extraterritorial jurisdiction and a 50% Rule for export controls on rare earth elements and other items,” October 2025. Article 4 of MOFCOM Notification 61/2025 imposes a case-by-case review for memory chips at 256-layer and above and logic at 14 nanometer and below, plus production and testing equipment. Carra Globe, “China Rare Earth Export Controls 2026,” May 2026: case-by-case review remains active during the November 2025 suspension. MOFCOM original text: Center for Security and Emerging Technology translation of Notice No. 61.

[14] Discovery Alert/industry analyst commentary, November 2025, citing industry consensus on heavy rare earth separation onshoring timelines. (B-tier; consistent with multiple industry sources but no single A-tier confirmation.)

[15] PBS NewsHour / AP wire, “WATCH: Trump announces plan for rare earth elements strategic reserve,” February 2, 2026; Fortune, “New ‘Project Vault’ critical minerals stockpile is ‘first step of many’,” February 3, 2026. Procurement firms named: Hartree Partners, Mercuria, Traxys.

[16] Quest Metals industry analysis, “Project Vault: $12 Billion Critical Mineral Stockpile,” February 5, 2026, describing draw-down and replenishment structure.

[17] Rare Earth Exchanges, “Project Vault: America Wants a Strategic Minerals Reserve — But Can It Stockpile What It Still Can’t Produce?,” May 2026.

[18] MP Materials Q3 2025 earnings release, November 6, 2025; USGS MCS 2026, Rare Earths (Heavy) chapter, citing $150 million Department of War loan in August 2025.

[19] Lynas Rare Earths Q3 FY2026 results; Argus Media, “Lynas rare earth output rises in 3Q,” November 3, 2025; Rare Earth Exchanges, “Lynas Doubles Down on Heavy Rare Earths,” February 25, 2026.

[20] IEA, op. cit. China exported 58,000 tons of rare earth magnets in 2024.

[21] Rare Earth Exchanges, “China Targets Chipmaking Bottleneck: Rare Earth Polishing Project Launches in Shenzhen,” March 19, 2026. (B-tier source; project is announced state R&D, not yet commercial-scale; treat as directional signal.)

[22] Brookings, “What will happen when Trump meets Xi?,” May 5, 2026; Pakistan Today, “Trump-Xi talks to focus on trade, Iran and Taiwan,” May 8, 2026.

[23] Washington Times, “Chinese fentanyl exports, lock on rare earths to top Trump’s agenda at summit with Xi,” April 20, 2026, citing USTR Jamieson Greer testimony to House Appropriations subcommittee.

In May 2026, McKinsey published this report [1] on the US domestic nuclear fuel cycle that put a number on the rebuild: $105–170 billion of capex through 2050, split across mining, conversion, enrichment, fabrication, and reprocessing.

That’s a useful frame, but it’s not the investable number. The investable number is which one or two segments will absorb more than half of the new awards in the next 36 months, because the rest of the chain cannot move without them.

This is the first in a six-part series on US-listed nuclear-fuel-cycle equities. I screened 22 names against four filters — small/mid-cap, off all-time-high, accelerating fundamentals, and early narrative — and by the end of the series, I’ll be down to a five-name long book.

But before any of that, you have to understand where the bottlenecks actually are. They are not where most of the public conversation says they are.

The five segments and what they cost

The fuel cycle decomposes into five sequential nodes plus two adjacencies (reactors and waste/storage). Here’s the McKinsey capex stack:

If you read those numbers naively, reprocessing is the biggest opportunity. It isn’t. Commercial reprocessing has been effectively blocked in the US since Jimmy Carter’s 1977 executive order [2] and remains uninvestable on any horizon shorter than a decade. The capex range is wide because it’s a greenfield-risk number for a thing that probably won’t get built before 2040.

Mining looks underweighted at $15–20B. It is but globally, there is no shortage of uranium-producing capacity. Kazatomprom alone supplies roughly 40% of global production at low cost [3]. Adding US mining is a national-security argument, not a global-capacity argument. The investable angle in mining is uranium-spot beta plus US-specific permitting and ramp execution — not ground-up mine economics.

The interesting numbers are conversion and enrichment.

Where the bottleneck actually is

I’d score the seven nodes like this for severity over the next decade. Severity scale: 5 = single point of failure for the chain; 1 = not a binding constraint.

Three observations from this table that surprised me when I started doing this work.

First, HALEU enrichment is the single tightest knot in the chain.

HALEU — high-assay low-enriched uranium, 5–19.75% U-235 — is what every advanced reactor needs for its first core:

• Oklo Aurora,

• TerraPower Natrium,

• X-energy Xe-100,

• Kairos Power KP-FHR.

Until 2024, virtually all commercial HALEU came from Russia. Today, Centrus Energy has produced the first ~900 kg of US-origin HALEU at Piketon, Ohio. That is the entire commercial Western supply.

Second, conversion is almost as tight — and there is no way to play it directly on the listed US tape.

The single operating US conversion facility is ConverDyn’s Metropolis Works in Illinois, running at roughly 7 ktU/yr against an original nameplate of 15 ktU/yr. Its parent is Honeywell. Honeywell is a $137B mega-cap where conversion is a low single-digit percent of revenue. There is no listed pure-play. This matters for the screen because it means even if you correctly identify conversion as the tightest commercial bottleneck, you cannot express it cleanly through a single name. Anyone who tells you they have a “conversion trade” via Honeywell is overstating their position.

Third, advanced fuel fabrication (TRISO and metallic alloys) is also acute, with similarly thin investable exposure. The NRC granted X-energy the first-ever Category II TRISO fuel fabrication license in February 2026. X-energy is private. The only public direct play in advanced fuel fab is BWX Technologies (NYSE: BWXT) — and BWXT is a $19B mid-cap trading near its all-time high, well-covered, and structurally above the size cap most thematic books carry.

Mining sits below those three in severity. It is a thematic-beta trade with a structural overlay, not a structural trade with a price overlay. That distinction matters: if uranium spot rolls over 25%, mining-name multiples compress fast. The conversion and HALEU bottlenecks don’t decompress that way.

The DOE award everyone should be paying attention to

On January 6, 2026, the US Department of Energy awarded $2.7 billion [4], split evenly three ways:

• $900M to American Centrifuge Operating (a Centrus Energy subsidiary) for HALEU at Piketon, Ohio.

• $900M to General Matter for HALEU at the former Paducah Gaseous Diffusion Plant in Kentucky. General Matter only emerged from stealth in April 2025 and signed its DOE land lease in August 2025.

• $900M to Orano Federal Services for LEU at Project IKE in Oak Ridge, Tennessee — a piece of a roughly $5B greenfield enrichment project.

Plus a smaller $28M supplemental award to Global Laser Enrichment [5] (Silex / Cameco JV) for next-gen technology.

The structure of this award is, to me, the most consequential signal in the McKinsey article. The federal government had a choice: concentrate the bet behind one US-owned producer, or seed three separate efforts. It chose three. That decision compresses per-name optionality versus a winner-take-all outcome, but it converts the question from “will US-owned HALEU exist?” (speculative) to “which of three named producers will execute first?” (handicapping).

Two of the three are private. The only listed name that won a tranche is Centrus Energy (NYSE: LEU). That is why every conversation about US enrichment exposure starts and often ends with Centrus — the math of public-market exposure forces it.

What this means for stock-picking

If you’re a thematic investor with a US-listed mandate, the McKinsey frame collapses to a few hard observations.

1. HALEU enrichment is where bottleneck severity, federal funding, and listed exposure all converge. This is where the work has to be most rigorous, because the names are crowded and the cone of outcomes is wide.

2. Conversion is structurally critical but offers no clean public expression. A future Solstice / Honeywell Advanced Materials spinoff is the most-watched corporate-action catalyst in the cycle.

3. Mining is investable but it is a uranium-price trade with a structural overlay, not the other way around. The order of those words is the difference between a 30% drawdown and a five-bagger.

4. The picks-and-shovels lane — waste handling, dosimetry, decommissioning instrumentation — is its own structural thesis, and there is exactly one filter-compliant mid-cap in it. I’ll come back to that in Post 4.

5. The advanced reactor adjacency (NuScale, Oklo, Nano Nuclear, BWXT, GE Vernova) is the demand engine for the entire chain. But FOAK economics are still unproven and the narrative is loud. Post 5.

The single most important question I’m asking through the rest of this series isn’t “which of these names is great.” It’s “which of these names is great at a price I should actually pay.” Most of them aren’t, today.

What’s coming

• Post 2 — HALEU enrichment. Centrus Energy as the McKinsey anchor name. ASP Isotopes’ Quantum Leap Energy subsidiary as the optionality slot. Why I think one of these is fundamentally cheap right now and the other one isn’t.

• Post 3 — Conversion. The bottleneck nobody can play directly, and the Solstice spin that might fix that.

• Post 4 — Picks-and-shovels. One mid-cap that passes the screen in two of seven segments simultaneously.

• Post 5 — SMR demand. Why I think the post-CFPP-cancellation reset on NuScale is more advanced than the market recognizes — and why that doesn’t mean I’m long.

• Post 6 — The book. Five-name long book, position-sized, with explicit falsification triggers for each.

Subscribe if you want this in your inbox over the next few weeks.

Further reading

[1] McKinsey & Co. — Understanding domestic nuclear fuel production options in the United States

[2] Jimmy Carter’s Executive Order

[3] Kazatomprom - Uranium market

[4] DOE — Awards $2.7 billion to restore American uranium enrichment

[5] ANS Nuclear Newswire — DOE awards $2.7B for HALEU and LEU enrichment

World Nuclear News — US enrichment funding recipients flesh out plans

Prohibiting Russian Uranium Imports Act P.L. 118-62

*Capacity Factor is a six-part series on US nuclear fuel-cycle equities. Next post: HALEU enrichment.*

In January 2025, Sam Altman stood in the White House beside Donald Trump, Masayoshi Son, and Larry Ellison to announce the largest AI infrastructure project in history. Stargate: $500 billion, four years, a network of gigawatt-scale data centers across the United States and eventually the world. Fifteen months later, the project is collapsing from the periphery inward — and the center isn’t holding either.

The scorecard. In March, OpenAI and Oracle scrapped plans to expand the flagship Stargate campus in Abilene, Texas, from 1.2 gigawatts to 2 gigawatts after financing negotiations broke down. [1] Crusoe, the site developer, had already been struggling with reliability problems — a winter storm took liquid-cooling infrastructure offline for days. [2]

Microsoft swept in to rent the abandoned 900 megawatt expansion site from Crusoe. [3] Stargate was supposed to free OpenAI from Microsoft’s cloud. Now, Microsoft is occupying the data center that OpenAI couldn’t fill. Oracle, Stargate’s infrastructure partner, is the landlord to Microsoft at the site OpenAI abandoned. The access moat built a building. Someone else moved in.

On April 9, OpenAI paused Stargate UK entirely, citing energy costs and the regulatory environment — and, per Bloomberg, reining in spending ahead of a planned IPO. [4] The Nscale partnership announced in September 2025 — 8,000 Nvidia processors at Cobalt Park, Tyneside, first quarter 2026 — passed its own deadline without breaking ground. [5] In Abu Dhabi, Iran’s Islamic Revolutionary Guard Corps has threatened to destroy the $30 billion Stargate UAE facility, releasing satellite imagery of the site. [6]

Three sites. Three different failure modes. Financing (Abilene). Energy costs and regulation (UK). Missile threats (UAE). The original Abilene campus is operational — multiple buildings running Nvidia GPUs for OpenAI. But that campus predated the Stargate announcement. The new infrastructure — the expansion, the international sites, the multi-gigawatt network — is what the $500 billion was supposed to buy. None of it has materialized.

Stargate is not an outlier. Thirty to fifty percent of all US data center builds planned for 2026 face delays or cancellation — roughly half the industry’s pipeline. [7] Of the 16 gigawatts of planned capacity, only 5 are under construction. By 2027, it gets worse: 6.3 gigawatts under construction against 21.5 announced. [8] The bottleneck is not money — it is transformers, switchgear, and batteries that nobody can source fast enough. Stargate is just the project with its name on the White House lawn.

The pivot. While the sites were stalling, OpenAI abandoned its plan to build and own data centers altogether. In mid-March, The Information reported that OpenAI is now renting server capacity from cloud providers instead of building its own facilities. [9] The company restructured its entire compute team in response to this shift. [10] Total projected spending dropped from $1.4 trillion through 2033 to $600 billion through 2030. [11] OpenAI signed a $100 billion expansion of its AWS agreement — making Amazon, not Oracle or SoftBank, the de facto third-party infrastructure backbone. [12]

On April 29, the Financial Times reported that OpenAI has “in practice abandoned the joint venture.” [13] One person involved with Stargate said the company had “sidelined first-party data centers.” An insider close to SoftBank put it more bluntly: “People can basically define what ‘Stargate’ is for themselves. To some extent, any compute project involving SoftBank or Oracle can be called ‘Stargate.’” [13] OpenAI itself now calls it “an umbrella for our compute strategy.” In Norway, another Stargate-branded site fell through; OpenAI couldn’t close an offtake deal with Nscale at the Narvik facility, and Microsoft stepped in to lease the capacity instead. [13] Partners are “feeling let down and misled.” One source told the FT they prefer Microsoft as a tenant because “they are more creditworthy.” [13]

On April 11, three of Stargate’s original infrastructure leads — including Peter Hoeschele, who ran the early datacenter effort — left OpenAI for Meta. [14] The people who built the project are leaving. The day the FT story ran, OpenAI published a blog post claiming it had “surpassed” its 10 gigawatt target, with “more than 3 GW added in the last 90 days alone.” [15] The language was careful: “The financing models and partnership structures may evolve, but what matters is capacity coming online at scale.” This is the tell. Three gigawatts of leased capacity from AWS and Oracle is not three gigawatts of Stargate infrastructure. When you rent a hotel room, you don’t get to claim you built a hotel. The pivot may produce better economics for OpenAI — controlling chip decisions while renting the buildings is a defensible strategy. The question is whether the $500 billion investment thesis survives the change.

What the financing reveals. SoftBank, Stargate’s financial partner, took out a $40 billion unsecured bridge loan on March 27 with a twelve-month maturity. [16] The loan’s primary purpose: funding a $30 billion follow-on investment in OpenAI, bringing SoftBank’s total equity exposure to approximately $64.6 billion in a single pre-IPO company. [17] The loan matures in March 2027, before most Stargate sites will produce a kilowatt. SoftBank is financing the equity bet, not the infrastructure. Oracle, the designated builder, carries over $100 billion in debt on $30 billion in equity, with CDS spreads at their highest since 2009 and its own bondholders suing over undisclosed financing needs. [18] Beyond the original Abilene campus, nobody is financing Stargate construction.

OpenAI has also signed chip deals totaling nearly 27 gigawatts — with Nvidia, AMD, Broadcom, and Cerebras. [19] Stargate’s total planned capacity, as of September 2025, is approximately 7 gigawatts. [20] The chip commitments exceed the infrastructure capacity by roughly 4-to-1. Either the chips go into other people’s data centers — which is what “renting from AWS” means — or the commitments are aspirational on both sides.

The sovereign compute casualty. The UK pause is not just about energy costs. OpenAI for Countries — the program extending Stargate to the UK, Australia, Greece, the UAE, Slovakia, Kazakhstan, and others — was a sovereignty product. [21] The pitch: run frontier models locally within your jurisdiction on dedicated infrastructure. That requires physical infrastructure that OpenAI controls. If OpenAI can’t build it in the UK — stable grid, rule of law, English-speaking talent, George Osborne on the payroll — it can’t build it in Kazakhstan or Greece either.

Stargate was the largest AI infrastructure announcement ever made. Fifteen months later, the company that announced it calls it “an umbrella.” No international site has broken ground. The builder is being sued by its bondholders. The financier is providing equity financing through a 12-month loan. The people who ran the project are leaving for Meta. Partners who signed up to build data centers are watching Microsoft take the leases. The $500 billion bought a valuation, not a data center.

What happens next? Two scenarios.

First, Oracle’s balance sheet forces a reckoning. Over $100 billion in debt, negative free cash flow, and a quarter-trillion dollars in off-balance-sheet lease commitments are grounds for a credit downgrade. [18] Oracle can no longer finance the buildout at investment-grade rates. The 4.5 gigawatt agreement with OpenAI shrinks or restructures. SoftBank’s bridge loan matures in March 2027 without the infrastructure to justify a rollover. The Stargate venture is formally wound down or absorbed into existing bilateral cloud contracts.

Second, the sovereign compute product dies. OpenAI for Countries promised governments dedicated infrastructure inside their borders. If OpenAI is renting, not building, the infrastructure is Amazon’s or Microsoft’s — subject to US jurisdiction, not sovereign control. Governments that signed memoranda of understanding on the promise of sovereign AI discover they bought ChatGPT Edu licenses and a press photo with Sam Altman. The dependency on US cloud infrastructure that the sovereign product was supposed to escape remains intact.

For any AI infrastructure deal that follows — Stargate or otherwise — the test is simple: a site under construction, a power purchase agreement in force, and a builder whose balance sheet can finish the job. Anything less is a press release.

Notes

[1] Brody Ford, Edward Ludlow, and Dina Bass, “Oracle and OpenAI End Plans to Expand Flagship Data Center,” Bloomberg, March 6, 2026.

[2] “OpenAI’s massive Stargate data center canceled as firm can’t reach terms with Oracle,” Tom’s Hardware, March 8, 2026. Crusoe liquid-cooling disruption during winter weather is cited in the piece.

[3] Dina Bass and Brody Ford, “Microsoft Rents Data Center Project Developed for Oracle, OpenAI,” Bloomberg, March 27, 2026. Crusoe confirmed approximately 900 MW capacity, with the first building expected in mid-2027. Earlier Bloomberg reporting (March 24) cited approximately 700 MW; the difference likely reflects site capacity vs. initial IT load.

[4] “OpenAI Pauses Stargate UK Data Center Citing Energy Costs,” Bloomberg, April 9, 2026. Bloomberg reports OpenAI is “reining in ambitious spending plans ahead of a highly anticipated public listing.” OpenAI statement: “We continue to explore Stargate UK and will move forward when the right conditions, such as regulation and the cost of energy, enable long-term infrastructure investment.” See also CNBC, April 9, 2026.

[5] “OpenAI’s flagship UK data project delayed in setback for Starmer,” The Telegraph, April 4, 2026. The original September 2025 announcement specified ~8,000 Nvidia processors at Cobalt Park, with a Q1 2026 target.

[6] “Iran threatens ‘complete and utter annihilation’ of OpenAI’s $30B Stargate AI data center in Abu Dhabi,” Tom’s Hardware, April 5, 2026. IRGC Brigadier General Ebrahim Zolfaghari’s statements; satellite imagery of the site included in the IRGC video.

[9] The Information, reporting on OpenAI’s shift from building to renting data center capacity, mid-March 2026. Cited by Data Center Dynamics, The Deep Dive, CNBC, and others.

[10] “OpenAI reorganizes leadership amid data center strategy readjustment,” Data Center Dynamics, March 18, 2026. Sachin Katti appointed to oversee Stargate groups; the compute team split into three divisions.

[11] “OpenAI’s data center pivot underscores Wall Street spending concerns ahead of IPO,” CNBC, March 22, 2026. Total projected compute spending reduced from $1.4 trillion (through 2033) to $600 billion (through 2030).

[12] OpenAI expanded its existing AWS agreement by $100 billion over eight years; AWS was designated the exclusive third-party cloud distribution provider for OpenAI’s enterprise platform. CNBC, February 27, 2026.

[16] SoftBank $40 billion unsecured bridge financing facility, March 27, 2026. Twelve-month maturity (March 25, 2027). Syndicated by JPMorgan Chase, Goldman Sachs, Mizuho, SMBC, and MUFG. Interest rate not publicly disclosed as of publication. Source.

[17] SoftBank’s cumulative OpenAI equity exposure: $19 billion initial Stargate equity + $30 billion follow-on = $49 billion confirmed. Additional Vision Fund 2 positions bring the estimated total to approximately $64.6 billion (~13% ownership). OpenAI’s funding round closed at $122 billion in March 2026 at an $852 billion post-money valuation (initial $110B close in February expanded to $122B by final close). Author compilation from S&P Global, CNBC, CNBC April 15, and SoftBank disclosures.

[19] Nvidia: 10 GW LOI, September 2025. AMD: 6 GW definitive agreement, October 2025. Broadcom: 10 GW custom silicon term sheet, October 2025. Cerebras: $10 billion / 750 MW inference deal, January 2026. Sources: respective company announcements and Tom’s Hardware compilation, February 24, 2026.

[20] OpenAI, “Building the compute infrastructure for the Intelligence Age,” April 29, 2026, confirms the original 10 GW commitment: “When we announced Stargate in January 2025, we committed to securing 10GW of AI infrastructure in the United States by 2029.” September 23, 2025, expansion announcement brought the total to “nearly 7 gigawatts” of Stargate-branded planned capacity.

[21] OpenAI for Countries program: UK, Australia, Greece, UAE, Slovakia, Kazakhstan, and others. OpenAI, September 2025. See also “OpenAI pauses its Stargate UK data center plan,” Engadget, April 9, 2026.

[18] Oracle Corporation Form 10-Q, period ended November 30, 2025 (SEC filing). Total debt: $108.1 billion ($8.1B current + $100.0B non-current). Total stockholders’ equity: $30.5 billion. Off-balance-sheet lease commitments of $248 billion are disclosed in notes to financial statements. Bondholder lawsuit: Ohio Carpenters’ Pension Plan v. Oracle, filed January 14, 2026, NYSC. Bloomberg, January 15, 2026.

[7] Sightline Climate, 2026 Data Center Outlook. Of ~16 GW of US data center capacity planned for 2026 across 140 projects, only ~5 GW is under active construction. 25% of projects have not disclosed their powering strategy. See also Bloomberg, April 1, 2026.

[8] 2027 pipeline: 6.3 GW under construction vs. 21.5 GW announced. Beyond 2028, 37 GW of planned capacity has not broken ground, and only 4.5 GW of that has begun work. Futurism, April 2026; ZeroHedge analysis citing Sightline Climate and Canaccord.

[14] Peter Hoeschele, Shamez Hemani, and Anuj Saharan left OpenAI and are joining Meta. Hoeschele led the early Stargate datacenter effort; Hemani worked on computing strategy; Saharan led within the computing organization. “Former OpenAI Stargate Leaders Plan to Join Meta Platforms,” Bloomberg, April 11, 2026.

[13] Financial Times, reported April 29, 2026. OpenAI has “in practice abandoned the joint venture.” One person involved with Stargate said the company had “sidelined first-party data centers.” OpenAI described Stargate as “an umbrella for our compute strategy.” A person close to SoftBank: “People can basically define what ‘Stargate’ is for themselves. To some extent, any compute project involving SoftBank or Oracle can be called ‘Stargate.’ Norway Stargate site abandoned; Microsoft leased the Narvik facility from Nscale. Partners “feeling let down and misled.” Source preference for Microsoft as tenant: “They are more creditworthy.” Cited via Tom’s Hardware, April 30, 2026. “Define for themselves” quote via BigGo Finance, May 1, 2026, citing FT sources. See also CNBC, April 15, 2026, for details on Norway.

[15] OpenAI, “Building the compute infrastructure for the Intelligence Age,” April 29, 2026. Claims to have “surpassed” 10 GW target with “more than 3GW added in the last 90 days alone.” Note: “capacity” in OpenAI’s usage includes leased capacity from third-party providers (AWS, Oracle, Microsoft), not only self-built infrastructure. The blog’s language — “the financing models and partnership structures may evolve” — is an implicit acknowledgment of the FT reporting published the same day.

Three days in April told the story the earnings calls didn’t.

On Sunday, April 27, Microsoft and OpenAI announced they were ending their exclusivity arrangement. The partnership that defined the first era of commercial AI — Microsoft’s billions in exchange for sole access to OpenAI’s models — was restructured into a looser arrangement: a non-exclusive license through 2032, OpenAI free to serve any cloud, Microsoft no longer paying OpenAI a revenue share. The word “exclusive” became “non-exclusive.” [1]

On Monday, OpenAI’s models went live on Amazon Web Services. Bedrock customers could now access GPT and Codex alongside Anthropic’s Claude, which had been on Bedrock since 2023. Andy Jassy posted on X to celebrate. [2]

On Tuesday evening, all four of the world’s largest technology companies reported quarterly earnings within hours of each other. Amazon, Microsoft, Alphabet, and Meta collectively guided capital expenditures to approximately $700 billion in 2026 — the largest single-year infrastructure commitment in the history of corporate America. [3] Each reported what it called AI revenue. No two defined the term the same way.

The market moved. Microsoft surged after reporting capital expenditure of $3.4 billion below expectations. Meta dropped 6% after raising its capex guidance by $10 billion. [4] Alphabet climbed on Google Cloud’s 63% revenue growth. Amazon beat on every line. [5] The consensus held: AI spending is working.

What the consensus missed is that the spending and the revenue are partly the same money.

The Numbers Everyone Saw

The headline figures are genuinely impressive. AWS grew 28%, Google Cloud crossed $20 billion at 63% growth, Azure hit 40% in constant currency, and Meta’s ad revenue surged 33%. [6][7][8][9] The cloud businesses are performing. The question is what else the earnings showed.

Amazon’s net income surged 77% to $30.3 billion. Buried in the 8-K: $16.8 billion of that came from pre-tax gains on its investment in Anthropic, booked as non-operating income. [10] Strip the Anthropic gain, and Amazon’s net income growth was respectable but unremarkable.

Alphabet’s net income rose 81% to $62.6 billion. The filing disclosed $37.7 billion in gains from nonmarketable equity securities — a category that includes Alphabet’s stakes in both Anthropic (estimated at 14%) and SpaceX (estimated at 6%). [11] The gains alone exceeded Google Cloud’s entire quarterly revenue.

Meta’s earnings included an $8 billion one-time tax benefit from the One Big Beautiful Bill Act — a different kind of inflation, clearly labeled and widely noted. [12]

Of the four companies, only Microsoft reported earnings growth driven primarily by operations rather than investment gains or tax adjustments. Its $4.27 EPS, up 21%, reflected actual growth in cloud and software revenue. [13] This matters for what follows.

The question nobody on the earnings calls asked: how much of the AI revenue driving cloud business growth comes from the same companies whose rising valuations are boosting net income?

The Capital Loop

The financing architecture of frontier AI has converged on a single structure. Call it the round-trip.

Step one: the hyperscaler invests equity in the model company. Amazon has committed up to $33 billion in Anthropic — $8 billion in prior rounds, $5 billion in April 2026, and up to $20 billion more tied to commercial milestones. It also committed $50 billion to OpenAI in February, with $15 billion disbursed initially. [14] Alphabet committed up to $40 billion in Anthropic — $3 billion in prior rounds, $10 billion in April 2026, and up to $30 billion contingent on performance. [15] Microsoft invested $5 billion in Anthropic in November 2025, alongside Nvidia’s $10 billion. [16] Microsoft’s prior investment in OpenAI exceeds $13 billion. [17]

Step two: the model company commits to spend multiples of the investment on the hyperscaler’s infrastructure. Anthropic committed more than $100 billion to AWS over ten years, securing up to 5 gigawatts of Trainium capacity. [18] It committed $30 billion to Microsoft Azure. [19] It signed a deal with Google and Broadcom for 5 gigawatts of TPU capacity. [20] OpenAI committed $250 billion to Azure through 2032 — though that commitment is now non-exclusive. [21] OpenAI committed 2 gigawatts of Trainium capacity on AWS. [22]

Add it up: Anthropic alone has committed at least $130 billion in cloud infrastructure spending to the three hyperscalers that have collectively pledged up to $88 billion in equity to Anthropic. OpenAI has committed over $250 billion to cloud providers that have invested over $63 billion in OpenAI. The committed infrastructure spending exceeds the equity investment by more than 2-to-1.

Step three: the hyperscaler reports the resulting cloud consumption as AI revenue. Amazon cites $15 billion in annualized AI revenue run rate, noting that over 100,000 customers run Claude on Bedrock. [23] Microsoft reports $37 billion in annualized AI revenue, which includes “all revenue from model builders” on Azure. [24] Google Cloud’s $20 billion in quarterly revenue includes Anthropic’s TPU consumption, and the company’s backlog of $462 billion — which nearly doubled quarter over quarter — now includes TPU hardware agreements. [25]

None of the three discloses how much of their reported AI revenue comes from companies in which they’ve invested.

Step four: the hyperscaler books mark-to-market gains on the equity investment. These are unrealized gains — the investment’s value has risen on paper, but the hyperscaler hasn’t sold. Amazon recorded $16.8 billion in pre-tax gains from Anthropic in Q1 alone — gains driven by Anthropic’s valuation rising from $183 billion (September 2025) to $380 billion (February 2026). [26] Alphabet recorded $37.7 billion in gains from nonmarketable equity securities, a category that includes both Anthropic and SpaceX. [27] Both gains are booked as income in the same quarter the hyperscaler reports growing AI revenue from those same companies.

The loop is self-reinforcing. The hyperscaler invests, which funds the model company’s growth. The model company spends on the hyperscaler’s infrastructure, which grows the cloud business. The cloud growth supports the hyperscaler’s stock price. The model company’s valuation rises — driven partly by the revenue it generates, which is partly the hyperscaler’s own infrastructure spend. The hyperscaler books the valuation gain as income.

This is not fraud. It is not accounting manipulation. Every transaction is arm’s-length, audited, and disclosed. But the market is pricing the revenue growth and the investment gains as if they are two independent signals of AI’s value. They are substantially the same signal, measured twice.

The Gains Amplifier

The revenue side of the round-trip is meaningful but bounded. Even if Anthropic’s entire $100 billion AWS commitment were disbursed evenly over 10 years, it would amount to roughly $10 billion annually — significant, but less than 7% of AWS’s current run rate. The round-trip revenue is a growing fraction of cloud revenue, not the majority.

The income statement side is a different order of magnitude.

Amazon’s $16.8 billion gain on its Anthropic investment in Q1 exceeded the company’s entire AWS operating income for the quarter. [28] Strip the gain, and Amazon’s EPS falls from $2.78 to roughly $1.55 — an adjusted figure that barely clears the $1.66 consensus. [29] The disclosure is there. The headline isn’t.

Alphabet’s $37.7 billion in equity gains — which include SpaceX and other private investments alongside Anthropic — exceeded Google Cloud’s combined quarterly revenue and operating income. [30] Alphabet’s reported EPS was $5.11 against a consensus of $2.63. Strip the equity gains: CNBC reported the adjusted EPS at $2.62 — a one-cent miss. [31] The most celebrated earnings beat of the quarter was, on an adjusted basis, not a beat at all. To be precise: not all of Alphabet’s $37.7 billion in gains came from Anthropic — SpaceX is likely the largest single contributor, and the filing doesn’t disaggregate. But the structural point holds for every dollar that did come from AI investments: a substantial portion of the gains that inflated Alphabet’s headline earnings came from private companies whose valuations the hyperscalers’ own capital helped create.

The gains amplifier compounds the revenue story. The cloud business is growing partly because major companies are spending on infrastructure. That growth justifies higher capex. Higher capex builds more infrastructure. More infrastructure attracts more model company commitments. Model company valuations rise. Analysts revise EPS estimates upward. The cycle continues until the model companies either stop growing, go public (crystallizing the gains), or diversify away from the infrastructure that supports the loop.

The OpenAI-Microsoft restructuring is evidence that the third scenario — diversification — is already underway.

The “Primary” Ratchet

The word “primary” appears in every major hyperscaler-model company agreement. It is doing extraordinary financial work.

Amazon calls itself Anthropic’s “primary cloud provider” and “primary training partner.” [32] The April 2026 announcement extended this designation through a ten-year, $100 billion commitment. But Anthropic simultaneously holds commitments from Google (5 gigawatts of TPU capacity), Microsoft ($30 billion in Azure), and Nvidia ($10 billion in an optimization partnership). Claude is available on all three major clouds. “Primary” means first among several, not sole provider.

Microsoft was OpenAI’s exclusive cloud partner. Then, in February 2026, OpenAI signed a $50 billion deal with Amazon — including exclusive rights for OpenAI’s Frontier agent tool on AWS. Microsoft publicly objected, insisting it maintained exclusive API rights. [33] Two months later, the exclusivity was gone. The April 27 restructuring made Microsoft’s license non-exclusive, permitted OpenAI to serve all products on any cloud, and eliminated Microsoft’s revenue share payments to OpenAI. [34] The word “exclusive” became “primary.” Give it two renegotiations and “primary” may become “significant.”

I examined this pattern two weeks ago in the Amazon-Anthropic context: three qualifying axes — contract language, product geography, and access scope — each narrowing with every successive deal. [35] The OpenAI-Microsoft restructuring confirms the pattern is structural, not company-specific. Model companies outgrow exclusivity. The infrastructure commitments survive in the contract, but the revenue concentration doesn’t survive in practice. The market’s reaction was telling: Microsoft’s stock rose on the restructuring. Ending the revenue share and retaining a non-exclusive license through 2032 was priced as discipline, not loss. That may be right — for Microsoft. The question is whether the same logic applies to Amazon and Google, whose round-trips are still deepening.

The financial asymmetry is sharp. The hyperscaler’s infrastructure investment — $200 billion in Amazon’s case, $190 billion for Microsoft — is sunk. Data centers and custom silicon can’t be redeployed to non-AI workloads overnight. The model company’s commitment is contractual: real, binding, but portable across providers in a multi-cloud world. The model company diversifies its supply; the hyperscaler has already poured the concrete.

The Control Case

Meta reported the same week and serves as the experiment’s control group.

Meta’s AI capex is enormous — $125 to $145 billion guided for 2026, raised from $115 to $135 billion this quarter due to higher component pricing. [36] But Meta’s structure is fundamentally different. It doesn’t invest equity in external model companies. It doesn’t receive compute commitments from AI startups. Its AI investment is entirely internal: model training, inference infrastructure, and product integration. The return shows up in one place — advertising revenue.

That return is real. Meta’s ad revenue grew 33% to $55 billion, driven by AI improvements in ad targeting, with impressions up 19% and price per ad up 12%. [37] No mark-to-market gains inflated the earnings. The $8 billion tax benefit was clearly disclosed and widely noted.

Meta’s 33% revenue growth on pure internal AI investment — no round-trip, no circular gains, no mark-to-market windfalls — is what AI spending looks like when the market can see both sides of the ledger. The market punished Meta not for bad results but for spending $135 billion without the gains amplifier that made Amazon’s and Alphabet’s earnings look transformative.

The Revenue That Can’t Be Counted

The round-trip creates a measurement problem that neither the companies nor the analysts have solved.

Microsoft’s $37 billion in annualized AI revenue includes revenue from model builders running on Azure — but also Copilot enterprise seats, GitHub Copilot, and Azure AI services that have nothing to do with the round-trip. [38] The OpenAI-specific component is undisclosed but likely a fraction of the total. Before April 27, that fraction included all of OpenAI’s API traffic. After April 27, OpenAI can run on any cloud. How much of the $37 billion is at risk of migration? Microsoft hasn’t said. Amy Hood noted on the call that Azure could have grown above 40% if the company hadn’t allocated GPU capacity to first-party products like Copilot, framing the growth as supply-constrained. [39] That narrative was credible when OpenAI was exclusive. It reads differently when OpenAI has options.

Anthropic’s $30 billion run-rate revenue is reported on a gross basis — counting total end-customer spend as revenue and booking cloud infrastructure costs as expenses. [40] OpenAI disputes this approach, arguing it inflates Anthropic’s figure by approximately $8 billion relative to a net reporting basis. [41] The dispute matters here because gross reporting means Anthropic’s revenue includes the full hyperscaler infrastructure payment as both a top-line figure and an expense. The same dollar appears in both Anthropic’s revenue and AWS’s or Google Cloud’s AI revenue. This is standard revenue recognition — not double-counting in the GAAP sense — but it means the market is valuing both sides of the same transaction. To be clear: Anthropic’s cloud spending is real compute demand, the same infrastructure purchase any enterprise makes at market rates. The circularity is not in consumption but in financing — the equity investment that funds the model company and the valuation gains that flow from that same company’s growth.

Google’s $462 billion backlog now includes TPU hardware agreements with Anthropic. [42] Alphabet expects to recognize just over 50% of that backlog as revenue within 24 months. [43] When a cloud provider’s backlog includes committed purchases from a company the cloud provider has invested $40 billion in, the backlog is partly a measure of the cloud provider’s own capital commitment cycling through the system.

The aggregate picture: three hyperscalers have collectively pledged over $140 billion in equity to two model companies — over $150 billion, including Nvidia’s $10 billion. Those model companies have committed over $380 billion in infrastructure spending back to the same hyperscalers. The hyperscalers report the resulting cloud revenue as AI growth. They book the rising valuations as income. And the market prices both signals — the revenue and the gains — as independent validation that AI is working.

Most of it is working. The cloud growth is predominantly organic: enterprise AI adoption is real, developer demand for inference is real, and the shift to AI-native workloads is structural. The hyperscalers would argue the round-trip is simply a customer acquisition cost — that anchoring the model company to their infrastructure attracts organic enterprise customers who arrive for Claude or GPT and stay for the platform. That argument has merit. The question is whether the market is pricing AI revenue at the margin of a customer acquisition funnel or at the margin of independent organic demand.

But the gains that turned good quarters into spectacular ones — $16.8 billion at Amazon, $37.7 billion at Alphabet — are the round-trip showing up in the income statement. And those gains are entirely a function of rising private valuations that the hyperscalers’ own investments helped create.

What Breaks

The round-trip is stable as long as three conditions hold: the model companies keep growing, the infrastructure commitments convert to actual spend, and the private valuations keep rising. All three are under pressure.

The capex itself is increasingly debt-funded. Amazon’s trailing twelve-month free cash flow collapsed 95% to $1.2 billion — meaning its $200 billion in 2026 capex requires substantial debt issuance. [44] Amazon would note that its FCF was similarly compressed during the AWS buildout a decade ago, and that investment proved transformative. The difference is structural: the current investment includes $83 billion in equity deployed to companies whose revenue partly cycles back through Amazon’s own infrastructure — a financing loop the AWS buildout did not have. And much of the equity “deployed” to model companies remains on paper: of Amazon’s $33 billion in commitments to Anthropic, roughly $13 billion has been disbursed; the remaining $20 billion is tied to commercial milestones that may or may not be met. The round-trip depends on commitments converting to cash. The commitments are real. The cash is conditional.

Anthropic’s growth is extraordinary — $1 billion in annualized revenue at the end of 2024, $30 billion by April 2026. [45] But OpenAI’s CFO has reportedly said the company cannot afford its promised infrastructure spending, and OpenAI is missing internal targets for users and revenue. [46] If the model companies’ growth decelerates, the infrastructure commitments — which are contractual but demand-paced — may disburse more slowly than the backlog implies.

The IPO question cuts both ways. Anthropic is reportedly considering a listing as early as October 2026 at a potential valuation above $380 billion, with secondary market interest at $800 billion. [47] An IPO would crystallize the hyperscalers’ gains — converting unrealized mark-to-market into a liquid position with a market price. But it would also end the valuation escalation that produces the gains amplifier. A public Anthropic trading at 25 times revenue is a known quantity. A private Anthropic valued on the latest secondary trade between rounds is an appreciating asset every quarter. The hyperscalers benefit more from the IPO approach than from the event itself.

The “primary” ratchet is the structural risk the market has not priced. Every renegotiation loosens the model company’s commitment to a single provider. Microsoft went from exclusive to non-exclusive in seven years. The model companies would frame the diversification differently — not as instability but as leverage. A model company that can serve any cloud sets the terms. But the hyperscaler that poured the concrete can’t repour it. The infrastructure is sunk — Amazon’s $200 billion in 2026 capex is building data centers and manufacturing custom silicon that will be operational for a decade. The model companies’ commitments are real but operate on a different timescale. A $100 billion, 10-year commitment is $10 billion a year. A model company that can serve any cloud will allocate that spend to wherever the price, performance, and capacity are best. “Primary” protects the first call; it doesn’t protect the margin.

The round-trip ratio — equity invested divided by committed revenue, adjusted for mark-to-market gains — connects the spending story to the earnings story. Until the hyperscalers disclose how much of their AI revenue comes from companies they’ve invested in, the market will continue to treat revenue growth and investment gains as independent signals. They’re not.

They are two readings of the same thermometer, and the temperature is partly the hyperscalers’ own heat.

Notes

[1] Microsoft Blog, “The next phase of the Microsoft-OpenAI partnership,” April 27, 2026; OpenAI, “Next phase of Microsoft partnership,” April 27, 2026.

[2] CNBC, “OpenAI brings its models to Amazon’s cloud after ending exclusivity with Microsoft,” April 28, 2026.

[3] Author’s compilation from Q1 2026 earnings reports: Amazon ~$200B (8-K, FY2026 guidance reiterated); Microsoft ~$190B (CY2026, per CFO Amy Hood on Q3 FY2026 earnings call, April 29, 2026); Alphabet $180–190B (raised from $175–185B, Q1 2026 earnings call); Meta $125–145B (raised from $115–135B, Q1 2026 earnings release). Midpoints sum to approximately $700B.

[4] Microsoft Q3 FY2026 capex of $31.9B vs. $35.3B consensus (Visible Alpha); Meta shares fell approximately 6% in after-hours trading following capex guidance increase.

[5] Alphabet shares rose approximately 6% after-hours (CNBC); Amazon beat on revenue ($181.5B vs. $177.3B consensus) and EPS ($2.78 vs. $1.66 consensus) (CNBC).

[6] Amazon 8-K, Q1 2026: AWS revenue $37.59B, +28% YoY. StreetAccount consensus was $36.64B.

[7] Alphabet Q1 2026 earnings release: Google Cloud revenue $20.0B, +63% YoY. Operating income $6.6B, operating margin 32.9%, up from 17.8% in Q1 2025.

[8] Microsoft Q3 FY2026 earnings call, April 29, 2026: Azure and other cloud services grew 40% in constant currency. AI annualized revenue $37B, +123% YoY. Revenue figure includes “all revenue from model builders” per CNBC reporting.

[9] Meta Q1 2026 8-K: Total revenue $56.31B, +33% YoY. Advertising revenue ~$55B. Ad impressions +19%, average price per ad +12%.

[10] Amazon 8-K, Q1 2026: “First quarter 2026 net income includes pre-tax gains of $16.8 billion included in non-operating income from our investments in Anthropic.” Net income $30.3B, +77% YoY.

[11] Alphabet Q1 2026 earnings release: Net income $62.57B, +81% YoY. “Other income” of $37.7B, “primarily the result of net unrealized gains on our nonmarketable equity securities.” Alphabet’s private investments include stakes in Anthropic (estimated 14%) and SpaceX (estimated 6%). The filing does not disaggregate gains by investment.

[12] Meta Q1 2026 8-K: Net income $26.77B. Includes $8.03B income tax benefit tied to the One Big Beautiful Bill Act and U.S. Treasury Notice 2026-7. “Diluted EPS would have been $3.13 lower without this benefit.”

[13] Microsoft Q3 FY2026 earnings release: EPS $4.27, +21% YoY. Revenue $82.89B, +18% YoY. Operating income up 20%.

[14] Amazon-Anthropic: $8B in prior investments (multiple rounds, 2023–2024); $5B in April 2026 at $350B valuation; up to $20B additional tied to commercial milestones. Anthropic blog, “Anthropic and Amazon expand collaboration,” April 20, 2026. Amazon-OpenAI: $50B committed February 2026 ($15B initial + $35B conditional). CNBC, February 2026.

[15] Alphabet-Anthropic: ~$3B in prior investments; $10B at $350B valuation April 24, 2026; up to $30B additional tied to performance targets. TechCrunch, April 24, 2026; Bloomberg, April 24, 2026.

[16] Microsoft-Anthropic: $5B investment, November 2025. Nvidia-Anthropic: $10B, November 2025. Anthropic committed to $30B Azure compute and 1 GW of Nvidia Grace Blackwell / Vera Rubin capacity. Microsoft Blog, “Microsoft, NVIDIA and Anthropic announce strategic partnerships,” November 18, 2025. See also Anthropic announcement.

[17] Microsoft’s total investment in OpenAI exceeds $13B across multiple rounds since 2019. Exact figure is not publicly disclosed in aggregate; $13B is the widely reported estimate. CNBC.

[18] Anthropic blog, “Anthropic and Amazon expand collaboration,” April 20, 2026: “We are committing more than $100 billion over the next ten years to AWS technologies, securing up to 5GW of new capacity to train and run Claude. The commitment spans Graviton and Trainium2 through Trainium4 chips.”

[19] Microsoft Blog, “Microsoft, NVIDIA and Anthropic announce strategic partnerships,” November 18, 2025: “Anthropic has committed to purchase $30 billion of Azure compute capacity and to contract additional compute capacity up to one gigawatt.”

[20] Anthropic blog, “Anthropic expands partnership with Google and Broadcom,” April 7, 2026. Broadcom SEC filing showed the deal includes 3.5 GW of compute. Separately, Google’s $40B investment includes 5 GW of TPU capacity over five years.

[21] OpenAI’s Azure commitment exceeds $250B through 2032, per multiple reporting outlets citing Microsoft deal terms (now non-exclusive per April 27, 2026 restructuring). Exact figure not disclosed in Microsoft’s public filings; $250B is the widely cited estimate. B-tier sourcing. See CNBC for deal history.

[22] CNBC, “OpenAI brings its models to Amazon’s cloud,” April 28, 2026. OpenAI committed to 2 GW of AWS Trainium for training.

[23] Anthropic blog, “Anthropic and Amazon expand collaboration,” April 20, 2026: “over 100,000 customers now run Claude on Amazon Bedrock.” Amazon Q4 2025 earnings call: AI services annualized run-rate revenue of $15B. Reiterated in Q1 context by multiple outlets.

[24] Microsoft Q3 FY2026 earnings call, April 29, 2026. CNBC: “The number includes business from clients running AI services on Azure, including all revenue from model builders, as well as revenue from Microsoft’s own AI tools.”

[25] Alphabet Q1 2026 earnings call: Backlog $462B, CFO Anat Ashkenazi noted increase driven by “strong demand for enterprise AI offerings and the inclusion of TPU hardware sales.” Expects to recognize “just over 50% of the backlog as revenue over the next 24 months.” CNBC.

[26] Amazon 8-K, Q1 2026: $16.8B pre-tax gains from Anthropic investments. Anthropic’s valuation history: $183B (September 2025, Series F); $380B (February 2026, Series G per Anthropic blog, February 12, 2026).

[27] Alphabet Q1 2026 earnings release: $37.7B gains from nonmarketable equity securities. Includes Anthropic and SpaceX among other private investments. CNBC.

[28] Amazon 8-K, Q1 2026: AWS operating income was $11.5B (derived: total operating income $23.9B minus North America $8.3B minus International segment operating income). The $16.8B Anthropic gain exceeds this figure. Note: AWS operating income figure derived from segment data; verify against 10-Q when available.

[29] Author’s non-GAAP adjustment. Amazon Q1 2026 net income of $30.3B included $16.8B pre-tax Anthropic gains. At an assumed ~20% effective tax rate on the gain, the after-tax impact is approximately $13.4B, or approximately $1.23 per diluted share. $2.78 reported EPS minus $1.23 ≈ $1.55 adjusted EPS, compared to the $1.66 consensus estimate. Methodological note: exact tax treatment of the Anthropic gain depends on the structure of the investment and the applicable tax rate, which will be disclosed in the 10-Q. This adjustment is not provided by the company and is constructed by the author for analytical purposes.

[30] Alphabet Q1 2026: Google Cloud revenue $20.0B, operating income $6.6B, combined $26.6B. Equity gains of $37.7B exceed this combined figure. CNBC.

[31] CNBC, “Alphabet Q1 2026 earnings,” April 29, 2026. Alphabet disclosed the equity securities gains added $2.35 to diluted EPS. Adjusted EPS of $2.62 vs. $2.63 expected by analysts polled by LSEG.

[32] Anthropic blog, “Anthropic and Amazon expand collaboration,” April 20, 2026: “We named AWS our primary cloud provider in 2023 and our primary training partner in 2024.”

[33] Microsoft blog, February 2026, day of OpenAI-Amazon announcement: “Microsoft maintains its exclusive license and access to intellectual property across OpenAI models and products. … Azure remains the exclusive cloud provider of stateless OpenAI APIs.” TechCrunch, April 27, 2026.

[34] Microsoft Blog, “The next phase of the Microsoft-OpenAI partnership,” April 27, 2026. Key terms: non-exclusive license through 2032; OpenAI can serve all products on any cloud; Microsoft no longer pays revenue share to OpenAI; OpenAI revenue share payments to Microsoft continue through 2030, capped.

[35] “The Price of ‘Primary,’” published April 21, 2026, The AI Realist.

[36] Meta Q1 2026 8-K: 2026 capex guidance $125–145B, raised from prior $115–135B. “This reflects our expectations for higher component pricing this year and, to a lesser extent, additional data center costs to support future year capacity.”

[37] Meta Q1 2026 8-K: Advertising revenue ~$55B, +33% YoY. Ad impressions +19%, average price per ad +12%.

[38] Microsoft Q3 FY2026 earnings call, April 29, 2026. CNBC: AI annualized revenue of $37B includes revenue from model builders on Azure, Copilot enterprise seats, GitHub Copilot, and other first-party AI tools.

[39] Microsoft Q3 FY2026 earnings call, April 29, 2026. CFO Amy Hood: Azure could have grown above 40% absent GPU supply constraints / allocation to first-party products.

[40] Sacra, “Anthropic revenue, valuation & funding” (accessed April 30, 2026): “Anthropic reports revenue from cloud resellers (AWS, Google, Microsoft) on a gross basis — counting total end-customer spend as revenue and booking partner payouts as expenses — which inflates top-line figures relative to net-reporting peers.”

[41] OpenAI’s position per multiple reports: Anthropic’s gross revenue overstates by approximately $8B vs. net reporting. Cited by Sacra, TNW, Remio.

[42] Alphabet Q1 2026 earnings call, April 29, 2026: Backlog of $462B now includes TPU hardware agreements. CFO Anat Ashkenazi noted the increase was driven by “strong demand for enterprise AI offerings and the inclusion of TPU hardware sales.” CNBC.

[43] Alphabet Q1 2026 earnings call, April 29, 2026: Expects to recognize “just over 50% of the backlog as revenue over the next 24 months.” CNBC.

[44] Amazon Q1 2026: trailing twelve-month free cash flow of $1.2B, down from $25.9B in Q1 2025, a decline of approximately 95%. Operating cash flow declined while capital expenditure (including finance leases and purchase of property/equipment) increased. Multiple outlets citing 8-K data; verify against 10-Q when available.

[45] Anthropic revenue trajectory: ~$1B ARR end of 2024; $9B end of 2025; $14B February 2026 (per Series G announcement); $30B April 2026 (per Anthropic compute announcement). Anthropic blog, April 20, 2026; Sacra.

[46] WSJ report, April 2026: OpenAI missed internal targets for active users and revenue. OpenAI CFO Sarah Friar and CEO Sam Altman disputed the report. CNBC, April 28, 2026, referencing WSJ.

[47] Anthropic IPO discussions: Goldman Sachs, JPMorgan, Morgan Stanley advising; potential October 2026 listing; expected raise exceeding $60B. TNW, April 15, 2026, referencing Bloomberg. Secondary market offers at $800B+.

Twelve hours. That is how long the second political trilogue on the EU AI Act Omnibus lasted on April 28, 2026. When it ended without agreement, the institutions issued statements. Compliance teams updated their Slack channels. Law firms published client alerts by midnight.

Nobody called DeepSeek or MiniMax. Nobody called the teams maintaining the Llama and Qwen download pages on Hugging Face. They were not in the room. They never needed to be.

The AI Act’s original deadlines are now back in force. High-risk AI obligations — employment screening, credit scoring, biometric systems, law enforcement tools — apply from 2 August 2026 as written. A follow-up trilogue is scheduled for 13 May 2026, and a July publication in the Official Journal remains theoretically possible.[1] But five months of negotiation just collapsed over a single unresolved file, and any CTO or General Counsel who has been planning against an assumed delay should stop.

What Actually Failed

The Omnibus collapsed over Annex I — specifically, the conformity-assessment architecture for AI systems embedded in regulated products: industrial machinery, medical devices, and in-vitro diagnostics.[2] The European Parliament wanted AI Act requirements horizontally integrated into the sectoral safety laws governing those products. The Council did not converge on that approach. Twelve hours of negotiation produced no bridge.

This was not a minor procedural dispute. The conformity-assessment architecture determines who certifies what, under which framework, and inspected by which authority. The Standing Committee of European Doctors had already objected to medical devices being moved out of the AI Act’s high-risk framework and into sectoral-only oversight.[3] Sectoral regulators have their own conformity regimes. The Parliament’s proposal to shift AI medical devices into those regimes produced exactly the resistance that a proposal to weaken overlapping safety requirements tends to produce.

The package that failed included the high-risk deadline delay (Annex III systems to December 2, 2027; Annex I systems to August 2, 2028), the nudifier ban, and the reinstated registration requirement for self-assessed non-high-risk systems — a provision the Commission had tried to delete, and both institutions had independently restored.[4] All of it is now on hold until May 13 at the earliest, July at the latest, and August 2 if negotiations fail entirely.

Dutch MEP Kim van Sparrentak put it plainly: “Big Tech is probably popping champagne. While European companies that care about safety and did their homework now face regulatory chaos.”[5] She named the wrong beneficiary. Big Tech was never the problem the Omnibus was meant to solve.

Who Was Never at the Table

Here is what five months of Omnibus negotiations produced: an extended debate among European institutions, industry associations, and member states over how to make compliance easier for European deployers.

The actors who justified the controls were not party to that debate. They are not subject to it.

A US foundation model provider operating under contractual terms of service and API access restrictions faces AI Act obligations primarily at the GPAI layer — Chapter V, Articles 51 through 55, which govern general-purpose AI models. Those provisions entered into force on 2 August 2025 and were never part of the Omnibus dispute.[6] The high-risk deployer obligations that the Omnibus was trying to delay apply to the European companies that deploy those models in employment, credit, and public-safety contexts, not to the labs that built them.

A Chinese open-weight model distributed through Hugging Face, downloaded by a European startup, and deployed in a recruitment pipeline sits in a more ambiguous position. The AI Act claims jurisdiction twice: Article 2(1)(a) covers any provider placing a system on the EU market regardless of location; Article 2(1)(c) extends to any third-country provider whose outputs are used in the Union.[7] And the open-source exemption under Article 2(12) collapses when the system is deployed in a high-risk context, which EU recruitment is, under Annex III. But claiming jurisdiction and exercising it are different operations. Enforcement against a Chinese lab with no EU legal entity, no EU revenue recognition, and no EU contractual relationship is a different exercise from enforcement against a Frankfurt insurance company that bought an HR screening tool from a certified vendor. The Frankfurt company is in the registration database. The Chinese lab is not.

This is the governance paradox the Omnibus negotiations made visible. The five months of debate were about how to adjust rules for the population that was already complying. The population that justified the rules — and that the rules structurally struggle to reach — had no seat at the table because the table has no jurisdiction over them.

The more effective the governance mechanism for the governed, the sharper the line between the governed and the ungoverned. The Omnibus was trying to move the line. It collapsed before it could.

What August 2 Actually Means

Three things are in force regardless of what happens on May 13.

Article 4 AI literacy obligations have been in effect since 2 February 2025. Every provider and deployer must ensure that staff working with AI systems have sufficient AI literacy for their role. No prescribed curriculum; no direct administrative fine attached; liability exposure arises through the revised Product Liability Directive and national tort law when inadequate training contributes to harm.[8]

Article 50 transparency obligations apply from 2 August 2026 for new systems: disclose chatbot interactions, label AI-generated content in public-interest contexts, and mark synthetic audio and video. The watermarking sub-provision — the machine-readable component — is the one provision still genuinely in play at trilogue, with Parliament proposing November 2, 2026, and the Council proposing February 2, 2027.[9] Everything else in Article 50 lands on August 2 as written.

High-risk deployer obligations — conformity assessments, technical documentation, registration, human oversight mechanisms — apply from August 2 under the original law. If May 13 closes a deal and July publication clears, those obligations move to December 2, 2027. If not, they will go live in 94 days. Building a governance architecture that can absorb either outcome is not a delay strategy. It is the only strategy that works in both scenarios.

What May 13 Changes and What It Doesn’t

A deal on May 13 delivers the delay. Compliance teams gain twelve months on Annex III high-risk obligations. Any CTO managing a Q3 sprint against August 2 would welcome that.

What it does not change: the conformity assessment dispute that sank April 28 had nothing to do with foundation model providers, open-weight distributors, or cross-border API operators. It was a dispute between European institutions about European products deployed in European markets. The labs that built the systems the framework was designed to constrain have faced GPAI obligations since August 2025, and enforcement mechanisms that are still being built.

May 13 will determine whether the governed get twelve more months. If it closes and the July publication clears, this piece’s urgency evaporates, but its structural argument does not. The delay arrives; the boundary does not move.

What does not change in either scenario: while the EU institutions were spending five months negotiating compliance architecture for companies that were already in the room, the companies that were never in the room kept building. DeepSeek, MiniMax, Kimi, and others have shipped new models. The open-weight frontier moved. Every month of trilogue is a month the rest of the world does not spend waiting for a conformity assessment framework to resolve. The Act governs the governed. The ungoverned are compounding.

Notes

[1] European Parliament Legislative Train Schedule, Digital Omnibus on AI, updated April 29, 2026.

[2] IAPP, “EU AI Act reform talks stall as key compliance deadline looms,” April 29, 2026. Cypriot Council Presidency official statement: “It was not possible to reach an agreement with the European Parliament.” MLex Chief AI Correspondent Luca Bertuzzi confirmed the specific sticking point: “talks broke down around 2 am, with the expected fault line on the European Parliament’s push to move sectoral legislation from Annex I Section A to B.” See also TNW, April 29, 2026.

[3] CPME, “’Move fast and break things’ must not endanger patient safety: Medical devices must remain under safeguards of the AI Act,” March 25, 2026.

[4] NicFab, “Digital Omnibus on AI: EP Adopts Position (569 Votes),” March 27, 2026. Both Parliament and Council reinstated the registration obligation after the Commission proposed deleting it; EDPB and EDPS Joint Opinion 1/2026 supported reinstatement.

[5] Van Sparrentak quote via IAPP citing Reuters, April 29, 2026.

[6] IAPP, “AI Act Omnibus: What just happened and what comes next?”, April 29, 2026.

[7] EU AI Act (Regulation (EU) 2024/1689), Article 2(1)(a) (providers placing systems on the EU market regardless of location), Article 2(1)(c) (third-country providers/deployers where outputs are used in the EU), and Article 2(12) (open-source exemption collapses for high-risk systems under Article 6(2) and Annex III).

[8] EU AI Act, Article 4 (AI literacy), in force from 2 February 2025 per Article 113(a). The AI Act does not create a standalone civil liability cause of action; liability exposure for AI-related harm arises through the revised Product Liability Directive (Directive (EU) 2024/2853), transposition deadline 9 December 2026, and national tort law. The AI Liability Directive was formally withdrawn by the Commission in October 2025.

[9] CDT Europe AI Bulletin, April 2026; A&O Shearman trilogue analysis. Parliament proposes November 2, 2026 for watermarking; Council proposes February 2, 2027.

AWS European Sovereign Cloud GmbH is 100% owned by Amazon.com Inc.[1] It launched in January 2026 with improved technical isolation, EU-resident operations, and a thinner managed-service catalog than the commercial AWS track.[2] Microsoft’s Sovereign Public Cloud sits in the same architectural category.[3] Neither severed the US parent-company chain. Microsoft France told the French Senate under oath on June 10, 2025, that the company cannot guarantee EU data sovereignty against US authority requests. The CLOUD Act (18 U.S.C. § 2713) and FISA Section 702 (50 U.S.C. § 1881a) apply regardless of where the data sits.[4]

On April 17, 2026, the European Commission awarded framework contracts under its Cloud III procurement, worth up to €180 million, to handle sensitive EU institutional workloads over six years.[5] Four consortia were prequalified. [6] Ten Percent Sovereign surfaced Canadian jurisdiction dependencies in the Proximus and OVHcloud consortia; they are not considered here.[7] The two clean awardees — Scaleway (Iliad/Niel) and StackIT (Schwarz Digits) — clear the SEAL-3 "Digital Resilience" bar and the legal-pathway test cleanly: no US parent, no US technology dependency at the substrate, no extraterritorial chain. The Commission's framework names this divide and prices nothing else. The buyer who reads SEAL-3 as "compliant for sensitive workloads" is also committing to a different architectural stack, one that hyperscalers cannot deliver within the sovereign lane. That commitment is the Builder Tax. It is paid in productivity. It is partially redeemed in portability. The framework prices neither.

What SEAL Is Selecting For, And What It Isn’t

Ten Percent Sovereign examined the April 17 award as a procurement signal rather than a sovereignty signal. This piece extends to the cost of the signal not surfacing.

After member states failed to agree on a European cybersecurity certification scheme for cloud services (EUCS),[9] the Commission needed an internal-market-compatible substitute it could deploy unilaterally. The Cloud Sovereignty Framework methodology, published October 20, 2025,[8] does that work. SEAL — Sovereignty Effectiveness Assurance Levels — runs from SEAL-0 (no sovereignty) to SEAL-4 (full EU supply chain from chips to software).[10] It is the measurable yardstick the Commission applied to the Cloud III procurement track without waiting for Council unanimity.

The framework’s eight objectives cover strategic, legal-and-jurisdictional, data-and-AI, operational, supply-chain, technology, security-and-compliance, and environmental dimensions, weighted to a 100% sovereignty score.[11] SEAL-3 — “Digital Resilience” — is defined as immunity from supply-chain disruption by non-EU third parties.[12]

That is a procurement signal, not a technical one. SEAL-3 says: this provider’s stack would not break if a non-EU government attempted to coerce it. It does not say: "This provider can run the workload you actually have, on the architecture you actually use.”

The framework gets the legal-pathway leg right by design. Scaleway and StackIT have no extraterritorial chain at any layer of the stack. AWS Sovereign Cloud and Azure Sovereign Cloud — the two principal hyperscaler-built alternatives — share the same legal posture: improved technical separation, EU-resident operations, customer-managed encryption. And a US parent that the CLOUD Act and FISA reach, regardless. The two products are technically distinct, legally identical. The clean SEAL-3 pool is genuinely more sovereign in the dimension the framework measures.

That is the leg the framework names. What it does not name is the cost, or what the cost incidentally delivers.

The argument matters now, not in retrospect, because mini-competitions have not yet begun. The April 17 award was the prequalification, not the workload assignment.[13] Before the first sovereign-track workload is committed to a SEAL-3 provider, the Commission will publish an updated Cloud Sovereignty Framework. Member states preparing their own procurement under CADA — the forthcoming Cloud and AI Development Act, expected on May 27, 2026, under Article 114 TFEU[14] — will look to that updated framework as a template.

The Architectural Fork

Sovereignty is a stack philosophy, not a smaller catalog. The buyer who procures sovereignty under the SEAL-3 frame is committing, without the framework saying so, to a different architectural posture. The hyperscaler-sovereign tracks cannot match it inside the sovereign lane. The clean awardees can match it only because the open-source ecosystem they participate in is cross-vendor by definition. SEAL-3 says: this provider’s stack is sovereign. What it does not say is that the architecture the buyer must run on that stack is the cloud-native commodity stack, and only that stack.

Hyperscalers compete on proprietary managed-service depth. AWS Bedrock for managed multi-vendor proprietary-frontier-model APIs. Amazon SageMaker for a full-lifecycle ML platform. AWS Lambda for serverless compute with a deep ecosystem of triggers and integrations. DynamoDB, Aurora, Step Functions, Kinesis. Azure equivalents: Azure OpenAI Service, Azure Machine Learning, Azure Functions, Cosmos DB. Google Cloud equivalents: Vertex AI, Cloud Run, Spanner. The buyer who builds on these primitives captures real productivity gains and accepts lock-in by construction.[15] Migration cost rises with every proprietary primitive consumed, because the application architecture is shaped by the primitive’s API surface rather than by an open standard.

The clean SEAL-3 awardees cannot match that proprietary depth. They do not have the engineering scale, the R&D budget, or the ten-year head start. Scaleway publishes approximately 60 distinct services; StackIT publishes 42.[16] The hyperscalers publish more than 200 each.[17] What Scaleway and StackIT can offer — and offer cleanly — is the open-source commodity stack: Kubernetes, S3-compatible object storage, PostgreSQL-compatible managed databases, Kafka-compatible streaming, OpenSearch, OpenTelemetry, Prometheus and Grafana, vLLM and SGLang for open-weight model inference, Confidential Computing primitives where available. Open standards. Portable workloads. No managed-primitive lock-in.

This is not a smaller catalog. This is a different stack philosophy.

The objection is real and worth answering directly: hyperscalers offer Kubernetes, too. Amazon EKS runs in the AWS European Sovereign Cloud region. Azure Kubernetes Service runs in Microsoft Sovereign Public Cloud. A buyer can, in principle, run pure Kubernetes on AWS Sovereign and capture portability while staying inside the hyperscaler track. The objection collapses on price and rationale. The 15% sovereign premium buys the sovereignty wrapper around the proprietary catalog above the Kubernetes layer — Bedrock, SageMaker, Lambda, the deep managed-service depth that justifies the AWS procurement decision. A buyer paying that premium for pure Kubernetes-and-open-source on AWS Sovereign is paying for sovereignty assurances, the legal pathway analysis already deemed insufficient — the parent-company chain still reaches via § 2713 — to run a workload that commodity infrastructure delivers cheaper elsewhere. The architectural fork cuts both ways.

Lock-in operates through two mechanisms. The catalog constraint: only certain primitives are natively available, and consuming them shapes the application architecture. The contract gate: production at scale requires an enterprise commitment. Hyperscaler proprietary catalogs operate simultaneously. Bedrock shapes the application around its API surface. SageMaker ties productivity gains to the enterprise commitment level. Lambda triggers lock the hardest — applications written against Lambda’s trigger ecosystem cannot be ported without rewriting the trigger logic.

The clean SEAL-3 stack has no equivalent catalog constraint. The application architecture is shaped by the open-source API, which is the same API that the buyer can deploy on Hetzner, on IONOS, on bare-metal infrastructure in a customer-controlled colocation, or migrate to a future SEAL-3 awardee. The architecture is not lock-in-shaped because the open-source standard does the work that the managed-service catalog would otherwise do.

This is what the Commission’s framework implicitly procures without naming. SEAL-3 says: this provider’s stack is sovereign. What the provider can actually deliver, given its scale and its catalog, is the cloud-native commodity stack. So the framework selects providers that — by architectural necessity, not by buyer choice — force a implement a commodity-stack architecture for every workload that lands on them. The framework prices the sovereignty. It does not name that sovereignty equals architectural commitment.

The Productivity Cost

The productivity cost is real, and it falls on the typical sensitive-workload buyer harder than on the frontier-AI workload buyer.

The managed multi-vendor proprietary-frontier-model API category is the sharpest. A buyer wanting to A/B-test Claude against GPT, Mistral, and Cohere through a single API — with managed billing, rate limits, observability, and safety filters — has that capability natively on the hyperscaler commercial track. The clean SEAL-3 pool runs no managed frontier-model service at all. Scaleway runs open-weight LLMs through its own managed inference; StackIT serves open-weight LLMs through AI Model Serving. Neither runs a multi-vendor-through-one-API service.

The European frontier-model precedent worth naming is Mistral itself. In February 2024, Mistral premiered Mistral Large first on Azure, and its frontier deployment posture has historically been multi-cloud, with Azure first.[20] Mistral Compute — restructured around 13,800 NVIDIA GB300 GPUs at the Eclairion-operated Bruyères-le-Châtel site — is now in the planning phase, not yet in commercial operation as of publication date.[21] The CIO who wants a managed frontier-model service in 2026 chooses between a hyperscaler-sovereign service (delivered partially, with US-parent exposure) and a clean SEAL-3 service (open-weight inference, self-managed).

The full-lifecycle ML platform category matches the same pattern. The hyperscaler reference is a managed, end-to-end platform that covers data preparation, training, deployment, monitoring, and governance through a single console. The clean SEAL-3 pool offers IaaS GPU access, managed Kubernetes, and open-source ML tooling (Kubeflow, MLflow, Ray, KServe). The buyer assembles the lifecycle from open-source components rather than consuming a managed abstraction. That cost hits teams shipping their first model in weeks. It disappears for teams running mature ML platforms where the open-source assembly is already in place.

The thinner managed-platform depth across managed-Kafka, FaaS with rich trigger ecosystems, managed-streaming pipelines, and multi-region active-active is the commodity-layer cost. Scaleway can offer managed Kubernetes, but its managed Kafka offering is newer and less feature-rich than its AWS counterpart. StackIT has managed PostgreSQL and managed object storage, but does not run a counterpart to Step Functions or Cosmos DB.[22] Both providers can run workloads that hyperscalers can run. Neither can run every workload. The gap is concentrated in the proprietary layer. Confidential Computing runs asymmetrically: StackIT’s Confidential Kubernetes exceeds what the hyperscaler-sovereign tracks offer in the same form factor, while AWS Nitro Enclaves and Azure Confidential VMs cover the commercial regions in ways the clean awardees do not.[22]

The engineering capacity to operate commodity-stack architecture is the second cost. A team assembling Kubernetes, vLLM, and Kafka on a SEAL-3 provider is doing more architectural work than a team consuming Bedrock, SageMaker, and Lambda on AWS commercial. In practice, this means additional DevOps and platform engineering hires—or retraining existing staff—to manage infrastructure that the hyperscaler’s managed services would otherwise abstract away. That cost falls on engineering organizations that did not budget for it when the procurement decision was made on legal-pathway grounds alone.

The productivity cost is not catastrophic. It is unevenly distributed across workload categories and is absent from the framework’s signal.

The Exit Optionality

The opposite leg of the trade is what re-architecture into the commodity stack delivers: exit from hyperscaler lock-in.

CNCF and FinOps Foundation research on cloud-native architecture has consistently shown that workloads built on standard Kubernetes APIs and open-source data infrastructure carry materially lower migration costs than workloads built on hyperscaler proprietary primitives.[23] The mechanism is straightforward: open API contracts, portable data formats, provider-agnostic observability. Migration from one Kubernetes deployment to another is a redeploy. Migration across hyperscaler proprietary stacks is a rewrite. A streaming pipeline built on Kafka-on-Kubernetes with open-source consumers can move from Scaleway to StackIT by redeploying manifests. The same pipeline built on Amazon MSK with Kinesis triggers and Lambda consumers requires rewriting every integration point.

Sovereign procurement forces commoditization. Commoditization delivers portability. The buyer that lands on Scaleway’s commodity stack today can migrate to StackIT, to a future SEAL-3 awardee, to a Hetzner deployment with BSI credentials, or to a customer-controlled colocation — at redeploy cost, not rewrite cost. The buyer on AWS Commercial who has consumed the hyperscaler-managed service stack has no equivalent path. Even the migration from AWS commercial to AWS European Sovereign Cloud is not free — the Bedrock catalog differs, GPU instances are absent, and the Lambda trigger ecosystem in the sovereign region is a subset of the commercial one.

This is the option value, not the exercise value. Most enterprise migrations do not happen. But every workload carries an embedded option to migrate, and the strike price of that option is the migration cost — a rewrite for hyperscaler-proprietary workloads, a redeploy for commodity-stack workloads. The option does not become more likely to be exercised by being cheaper to exercise. It just becomes cheaper to exercise. Pricing it as if every workload will eventually migrate overstates the benefit; pricing it at zero understates it.

The broader European commodity-stack market makes the optionality concrete. Hetzner Online GmbH operates one of the largest commodity cloud businesses in Europe, is classified by BSI as a critical infrastructure operator under KRITIS, and holds C5 Type 2 certification as of March 25, 2026.[24] IONOS Cloud Solutions generated €177 million in segment revenue in fiscal 2024, holds BSI C5 and IT-Grundschutz certifications, won the federal sovereign cloud contract for ITZBund in April 2024, and signed a strategic cooperation agreement with the BSI in January 2026.[25] Neither was prequalified for the Cloud III award. Both run the same commodity stack as the SEAL-3 awardees. A workload deployed on Scaleway or StackIT can migrate to either platform without rewriting the deployment manifests, only the application.

A company that has re-architected onto the commodity stack is less locked into any individual cloud provider than one running on hyperscaler managed services. Vendor concentration risk is lower. Migration-cost contingencies in the diligence model are lower. Exit optionality at the infrastructure layer is higher. None of this is in the SEAL designation. All of it is in the architectural pattern of the SEAL designation forces.

What Mini-Competitions Will Reveal

The SEAL-3 framework has not yet been operationally tested. The April 17 award was the prequalification. Workload mini-competitions will follow over the coming months and quarters. Three questions arise.

First: Will the productivity cost be operationally confirmed? If more than thirty percent of mini-competitions over the next twelve months produce fewer than two qualifying bids — concentrated in workloads that depend on managed frontier-model APIs, full-lifecycle ML platforms, or Lambda-trigger-shaped serverless architectures — the cost is confirmed and binding.[27]

Second: Will the carve-out volume reveal where the framework selects against itself? Workloads the SEAL-3 pool cannot serve will be granted exemptions to use SEAL-2 providers. If those exemptions accumulate into a parallel track that quietly does most of the high-value work, the framework’s signal is inconsistent with its own selection criteria.

Third: Is the optionality leg empirically real? Workloads that land on a SEAL-3 provider and subsequently migrate to a different SEAL-3 provider — or to a non-prequalified European commodity-stack provider — will demonstrate the migration-cost asymmetry the architectural fork predicts.

If mini-competitions produce competitive bids across all workload categories, if exemption volume stays marginal, and if no observable migration-cost asymmetry emerges between the commodity-stack pool and the proprietary-stack pool, the thesis is wrong and the Builder Tax does not exist.

The Builder Tax

Sovereignty in the EU cloud, on April 28, 2026, is a two-track procurement choice with a trade neither side names.

One track: AWS Sovereign Cloud and Azure Sovereign Cloud. Improved technical separation. US legal chain intact. A thinner version of the proprietary catalog, a 15% premium, and the same parent-company exposure as the CLOUD Act and FISA reach.

The other track: Scaleway and StackIT. Legal-pathway test cleared by construction. A commodity stack — Kubernetes, S3-compatible storage, open-source data infrastructure, open-weight inference — that costs the buyer the proprietary catalog’s productivity gains and delivers, in exchange, exit from the lock-in that catalog enforces. The exit is not theoretical: Hetzner and IONOS run the same commodity stack outside the SEAL-3 pool, and a workload built on open standards can move between any of them at redeploy cost.

The framework names neither side of the trade. It rates the providers and sends a signal — that SEAL-2 carve-outs are equivalent options for sensitive workloads — that flattens the divide the legal-pathway analysis surfaces. Mini-competitions will reveal what the framework has been quiet about.

The Builder Tax is the productivity loss on the managed-service layer that the clean awardees cannot deliver. It is partially redeemed by portability — exit from hyperscaler lock-in — that the commodity-stack architecture delivers. The Tax falls harder on CTOs running mature managed-service platforms, where the productivity cost is the binding constraint, than on CISOs, who should weigh the legal-pathway leg more heavily and treat the productivity cost as cost-of-compliance. Diligence should weigh exit optionality even more heavily.

I would recommend applying two tests to any SEAL-tier vendor evaluation. First, evaluate which managed primitives the provider can deliver natively, which require rearchitecture, and which are unavailable. Second, clarify the legal-pathway exposure of the proposed architecture — parent-company chain, supplier chain, EU-only operational independence — for the workload’s data sensitivity. A SEAL-3 designation that does not answer those questions is a sovereignty score, not a procurement signal.

The Commission’s updated framework will determine whether the Builder Tax becomes a priced cost in EU public-sector AI infrastructure or remains silent inside a procurement signal. The decisions made in the next six months are the decisions that get templated into the regulatory architecture.

The framework scores sovereignty. It does not mention the productivity the buyer loses or the portability the buyer gains. Every company should decide whether the latter is worth paying for the former.

Notes

[1] AWS, “AWS Launches AWS European Sovereign Cloud and Announces Expansion Across Europe,” Potsdam, January 15, 2026. The AWS European Sovereign Cloud GmbH parent structure is detailed in AWS’s own published documentation; the operating entity is wholly owned by Amazon.com Inc. The Brandenburg datacenter region opened with two Availability Zones at GA. See also AWS Security Blog, “Opening the AWS European Sovereign Cloud,” January 15, 2026.

[2] AWS European Sovereign Cloud service catalog at general availability: approximately 90 services with plans to expand. Two Availability Zones at launch. Pricing premium of approximately 15% versus commercial EU regions, per independent benchmarking by tecRacer across EC2, S3, RDS, and Lambda price points (cited and analyzed by Cloudvisor). Bedrock available at GA but limited to Amazon Nova Lite and Nova Pro models — Anthropic Claude, Mistral, Meta Llama, and other proprietary frontier models are absent. No GPU instances. No CloudFront. Source: AWS European Sovereign Cloud documentation; comparative analysis per Cloudvisor, “Sovereignty as a Service: The AWS European Sovereign Cloud is Live,” published shortly after launch. AWS publishes “200+ services” globally; the comparison figure is Cloudvisor’s, not an AWS-published number. AWS European Sovereign Cloud also achieved SOC 2 Type 1 and C5 Type 1 attestation reports plus seven ISO certifications covering 69 services on March 16, 2026 — see AWS Security Blog, “AWS European Sovereign Cloud achieves first compliance milestone.”

[3] Microsoft Sovereign Public Cloud — the Microsoft-operated EU-Data-Boundary track — is generally available across European Azure datacenter regions for European customers, supporting Azure, Microsoft 365, Microsoft Security, and Power Platform. The track adds Data Guardian (EU-resident operator approval), External Key Management (customer-controlled encryption), and Regulated Environment Management to the commercial Azure platform. See Microsoft Learn, “What is Microsoft Sovereign Cloud?”. Distinguish from Microsoft Sovereign Private Cloud (Azure Local-based, customer-deployed) and National Partner Clouds — these are different products. The Sovereign Public Cloud is the AWS European Sovereign Cloud architectural analog for the comparison in this piece.

[4] AWS European Sovereign Cloud GmbH is 100% owned by Amazon.com Inc. per AWS’s published structure. Microsoft Sovereign Public Cloud runs on Microsoft Corporation infrastructure; Microsoft Corporation is a US-incorporated entity. The CLOUD Act’s compelled disclosure provision (18 U.S.C. § 2713) requires US-incorporated providers to produce data within their “possession, custody, or control” regardless of where the data is stored. FISA Section 702 (50 U.S.C. § 1881a) authorizes warrantless collection of non-US persons’ communications by US intelligence agencies. The Court of Justice of the European Union’s Schrems II ruling (Case C-311/18, July 16, 2020) cited Section 702 as incompatible with EU fundamental rights. Microsoft France told the French Senate under oath on June 10, 2025 that the company cannot guarantee EU data sovereignty against US authority requests; the testifying witnesses were Anton Carniaux (Director of Public and Legal Affairs, Microsoft France) and Pierre Lagarde (Technical Director, Public Sector). The hearing was held by the Senate inquiry commission on public procurement and digital sovereignty, chaired by Senator Simon Uzenat. Carniaux’s response to the question of whether Microsoft could guarantee that French citizens’ data would not be transmitted to US authorities without French consent was: “Non, je ne peux pas le garantir.” See SDxCentral, “Microsoft tells French lawmakers it can’t protect user data from US demands,” July 2025; Senate transcript at senat.fr. AWS contests the framing, citing its own Supplementary Addendum and zero-disclosure record since June 2020 (”there have been no data requests to AWS that resulted in disclosure of enterprise or government content data stored outside the U.S. to the U.S. government” — AWS, “Clarifying Lawful Overseas Use of Data Act,”). The legal exposure is statutory, not retrospective enforcement: the absence of past disclosure does not eliminate the possibility of future ones. For broader analysis of the AWS and Microsoft sovereign cloud legal architectures, see Julien Simon, “Two Sovereign Clouds, One Legal Wall,” February 2026.

[5] European Commission, “Commission advances cloud sovereignty through strategic procurement,” April 17, 2026. The Cloud III procurement is structured as a Dynamic Purchasing System with an estimated total value of up to €180 million over six years.

[6] Ibid. The Commission also prequalified two further consortia — a Post Telecom consortium with OVHcloud and CleverCloud, and a Proximus consortium that uses S3NS, Clarence and Mistral. This piece’s analysis focuses on Scaleway and StackIT as the clean reference pool because the other two prequalified consortia carry documented foreign-jurisdictional exposure (the OVHcloud Canadian subsidiary case examined in The Sovereignty Mirage, December 4, 2025; and the Datacenter United ownership structure following the February 28, 2025 Proximus datacenter sale to a Cordiant Capital-managed investment vehicle). The piece’s binary thesis tracks the cleanly comparable cases.

[7] Julien Simon, “Ten Percent Sovereign,” The AI Realist, April 17, 2026.

[8] European Commission, Cloud Sovereignty Framework, Version 1.2.1, October 20, 2025.

[9] On the EUCS deadlock and the Commission’s response, see European Cybersecurity Certification Scheme for Cloud Services (EUCS) drafting history at the Interoperable Europe Portal; ENISA, Cloud Cybersecurity Certification Scheme market and status pages, 2024–2025.

[10] The SEAL scoring scheme — SEAL-0 (no sovereignty), SEAL-1 (Jurisdictional Sovereignty), SEAL-2 (Data Sovereignty), SEAL-3 (Digital Resilience), SEAL-4 (Full Digital Sovereignty: complete EU control across the supply chain) — is documented in European Commission, Cloud Sovereignty Framework, Version 1.2.1 (October 20, 2025). For the April 17, 2026 procurement, the Commission set SEAL-2 as the minimum eligibility threshold; the prequalified Scaleway and StackIT consortia clear SEAL-3.

[11] The eight Cloud Sovereignty Framework objectives, with their published weights summing to 100% of the Sovereignty Score: SOV-1 Strategic Sovereignty (15%); SOV-2 Legal and Jurisdictional Sovereignty (10%); SOV-3 Data and AI Sovereignty (10%); SOV-4 Operational Sovereignty (15%); SOV-5 Supply Chain Sovereignty (20%); SOV-6 Technology Sovereignty (15%); SOV-7 Security and Compliance (10%); SOV-8 Environmental Sovereignty (5%). Source: European Commission, Cloud Sovereignty Framework, Version 1.2.1, October 20, 2025.

[12] European Commission, Cloud Sovereignty Framework, Version 1.2.1, SEAL-3 definition (Digital Resilience).

[13] European Commission, “Commission advances cloud sovereignty through strategic procurement,” April 17, 2026 announcement: “This is the first step. Mini-competitions will follow over the coming months.”

[14] CADA was originally listed for Q1 2026 in the European Commission’s 2026 Work Programme (October 20, 2025) under Article 114 TFEU. The proposal is now expected on May 27, 2026, per techUK’s “Dispatch from Brussels” (March 2026), as a flagship of the Commission’s “tech sovereignty package” — alongside a parallel revision of EU public procurement rules. Stated objectives include tripling EU data centre capacity, EU-wide eligibility requirements for cloud service providers, and a single EU-wide cloud policy for public administrations and procurement. See European Parliament Legislative Train Schedule, “Cloud and AI Development Act”; EPRS briefing, “Cloud and AI Development Act” (PE 779.251, December 2025).

[15] The Catalog-and-Contract Test framework was developed in the AI Tooling vertical of this publication; see Julien Simon, “Open Source, Closed Orbit: The Hardware Monopolist’s Guide to Owning Open Source,” The AI Realist, March 2026. The test originally targeted lock-in mechanisms in the consumer side of the AI ecosystem (model hosting, inference platforms, developer tooling); this piece extends the framework to the build side of the cloud stack, where the same dual-mechanism (catalog constraint + contract gate) operates.

[16] Scaleway product navigation, retrieved April 28, 2026. StackIT product documentation portal, retrieved April 28, 2026.

[17] AWS publishes “200+ services” globally per its corporate communications. Microsoft Azure and Google Cloud publish comparable counts. Counts vary by methodology — distinct services, distinct API endpoints, or distinct billable units produce different numbers. For the purposes of this piece, the order-of-magnitude comparison is sufficient.

[19] AWS European Sovereign Cloud Bedrock catalog at GA: limited to Amazon Nova Lite and Nova Pro, per AWS European Sovereign Cloud documentation and Cloudvisor analysis. Anthropic Claude, Meta Llama, Mistral, and other proprietary or open-weight frontier models from third-party vendors are absent from the sovereign-region Bedrock catalog at GA.

[20] Microsoft Azure blog, “Microsoft and Mistral AI announce new partnership to accelerate AI innovation and introduce Mistral Large first on Azure,” February 26, 2024. Mistral Large premiered first on Azure AI before becoming available on other deployment surfaces.

[21] Mistral Compute press materials, 2025–2026. The original announcement contemplated 18,000 NVIDIA Grace Blackwell systems hosted via Scaleway. The structure was subsequently reorganized around approximately 13,800 NVIDIA GB300 GPUs at the Eclairion-operated Bruyères-le-Châtel site (44 MW), funded through a $830M (~€750M) debt facility from a seven-bank consortium (Bpifrance, BNP Paribas, Crédit Agricole CIB, HSBC, La Banque Postale, MUFG, Natixis CIB), announced March 30, 2026. See DatacenterDynamics, “Mistral AI raises $830m in debt financing for data center in Paris, France.” Operations expected to begin Q2 2026.

[22] StackIT product portfolio, retrieved April 28, 2026; Scaleway product documentation, retrieved April 28, 2026. Confidential Computing detail: StackIT publishes a Confidential Kubernetes offering that the hyperscaler-sovereign tracks do not match in the same managed-Kubernetes form factor; AWS Nitro Enclaves (AWS commercial regions), Azure Confidential VMs, and GCP Confidential VMs (commercial regions) provide managed Confidential Computing that the clean SEAL-3 pool does not match in the hyperscaler-managed-VM form factor. AWS European Sovereign Cloud’s launch catalog at GA does not include managed Confidential Computing as a top-line service offering.

[23] Cloud Native Computing Foundation, Annual Survey, 2024 and 2025 editions — documenting Kubernetes adoption in production at 66%+ of respondents and rising multi-cloud deployment as the dominant pattern. FinOps Foundation, State of FinOps reports, 2024 and 2025 editions — documenting that organizations running multi-cloud commodity-stack architectures report materially lower switching costs than those dependent on single-provider proprietary services. The comparative-cost mechanism is also analyzed in Mompo Redoli & Ullah, “Kubernetes in the Cloud vs. Bare Metal: A Comparative Study of Network Costs,” arXiv:2504.11007, April 2025.

[24] Hetzner Online GmbH, “Hetzner receives BSI C5 Type 2 certification,” March 25, 2026. Hetzner is classified as a critical infrastructure operator under the German KRITIS regime per BSI designation; see Hetzner information security documentation.

[25] IONOS Group SE FY2024 Annual Report: IONOS Cloud Solutions segment revenue €177 million; total IONOS Group revenue €1.56 billion. IONOS BSI C5 attestation achieved November 7, 2023; IONOS BSI IT-Grundschutz certification achieved September 2022. ITZBund framework contract awarded April 2, 2024 — see IONOS, “IONOS builds cloud solution for the German federal administration,” five-year term, €410M ceiling. BSI strategic cooperation agreement signed January 13, 2026, by BSI President Claudia Plattner and IONOS CTO Markus Noga; see BSI press release and IONOS newsroom.

[26] Disclosure: the author serves as AI Operating Partner at Fortino Capital, a European private equity firm whose portfolio includes companies whose cloud architecture decisions are within the scope of this piece’s analysis. This disclosure illustrates the structural diligence question the piece names; it is not an endorsement of any specific provider or procurement choice.

[27] Mini-competition outcome thresholds are derived from comparable EU framework procurement programs and represent an order-of-magnitude observable signal. The “thirty percent” threshold is the author’s calibration, not a Commission-defined metric. Note: the Commission does not systematically publish mini-competition bid counts. The first falsifiability condition depends on whether the Commission or member-state procurement authorities make bid data available — either directly or through parliamentary scrutiny of sovereign cloud procurement outcomes.

On page six of the European Commission’s Cloud Sovereignty Framework (CSF), in a paragraph no one asked for, nothing required, and apparently no lawyer reviewed, the Commission explains why Legal and Jurisdictional Sovereignty counts for only ten percent of the Sovereignty Score. The text reads: “The weighting considers that the procurement procedure already contains significant safeguards in certain domains such as SOV-2 (Legal and Jurisdictional) and SOV-7 (Security and Compliance).”[1]

This is the Commission arguing, in its own document, that it downweighted legal sovereignty because the procurement process was already handling it. It is difficult to produce a more self-incriminating sentence.

Six months after that framework was published, the Commission awarded €180 million in framework contracts under it.[2] The press release notes that one winning consortium “leverages capacities of partners S3NS, Clarence, and Mistral from a technical environment based on Google Cloud technology, exclusively operated by EU companies.”[3] That will certainly raise a few eyebrows.

And did the Commission ignore that the consortium’s Belgian data center footprint is owned, with fifty percent voting control, by a Canadian-managed investment vehicle? And that one month before the Commission published its framework, the jurisdiction that manages that vehicle had issued a ruling from the Ontario Court of Justice — compelling a French sovereign-cloud champion to hand over EU-hosted customer data to Canadian police, and dismissing France’s blocking statute as an “empty vessel”?[4]

Oops.

Either way, the Commission did not relax the definition of sovereignty. It scored it down to ten percent.

The Award

The EU’s Cloud III Dynamic Purchasing System ran the procurement. Four consortia won framework contracts — maximum authorized spend €180 million, six-year term — to provide sovereign cloud services to EU institutions and agencies.[5]

The winners: Post Luxembourg’s data center subsidiary DEEP, in partnership with OVHcloud and Clever Cloud. Schwarz Digits’ StackIT, the cloud unit of the Schwarz Group behind the Lidl and Kaufland retail chains. Iliad’s Scaleway. And a Proximus-led consortium bundling S3NS, Clarence, Mistral AI, and Thales.[6]

No winner reached SEAL-4 (Sovereignty Effectiveness Assurance Level 4), “Full Digital Sovereignty”, defined as “Technology and operations under complete EU control, subject only to EU law, with no critical non-EU dependencies.”[7]

Three of the four — Post/OVHcloud/Clever Cloud, StackIT, and Scaleway — reached SEAL-3, defined as “EU law applicable and enforceable, EU actors exercising meaningful but not full influence; service, technology or operations under marginal control of non-EU third parties.” The Proximus consortium reached SEAL-2, defined as “EU law applicable and enforceable, with material non-EU dependencies remaining; service, technology or operations under indirect control of non-EU third parties.”

The tier progression encodes a distinction that the piece will return to. SEAL-2 permits “material non-EU dependencies remaining.” SEAL-3 permits only “marginal control of non-EU third parties.” SEAL-4 permits no critical non-EU dependencies at all and requires operations “subject only to EU law.” The framework treats these as cumulative steps on a single ladder. They are not. They are three different questions, and a consortium can satisfy the first two while remaining legally exposed on the third.

The Commission drafted SEAL-4 as Full Digital Sovereignty, published it in the framework, and awarded €180 million without using it. Europe’s most credible sovereign cloud providers, competing in a procurement designed by the Commission to measure sovereignty, could not clear the sovereignty tier the Commission itself defined as the goal. SEAL-4 is not a target. It is the placeholder the framework reserves for a future in which European digital sovereignty exists.

The Eight Objectives

The Cloud Sovereignty Framework, Version 1.2.1, was published by the Commission in October 2025, after iterative drafts spanning roughly two years. It organizes sovereignty into eight objectives, each with a weighting that sums to 100%.[8]

The critical ratio, for a PE or procurement reader: supply chain (SOV-5) and technology (SOV-6) together carry 35% of the Sovereignty Score; operational sovereignty (SOV-4) another 15%; strategic sovereignty (SOV-1) 15%. Legal and jurisdictional sovereignty (SOV-2) — the objective that measures exposure to non-EU legal reach — carries a 10% weighting. Security and compliance (SOV-7): another 10; data and AI sovereignty (SOV-3): 10; environmental sustainability (SOV-8): 5.[9]

This is defensible only if physical and operational EU control substantially produces legal EU insulation. The assumption is load-bearing. It is also contestable.

The framework’s SOV-2 scoring rubric enumerates two specific foreign instruments: the United States CLOUD Act and the Chinese Cybersecurity Law, with a residual reference to “non-EU laws with cross-border reach.”[10] The CLOUD Act deserves its prominence. It is the most documented threat to EU data sovereignty, with Microsoft, Google, and Amazon each publishing transparency reports detailing US authority demands for EU-hosted data. The framework was right to center it.

But the framework was published in October 2025. One month earlier, on September 25, 2025, a Canadian court issued a ruling that demonstrated exactly what the framework’s “non-EU laws with cross-border reach” catch-all does not capture—and, materially, does not name.

The Ottawa Ruling

The case is R. v. OVH Group SA and Hébergement OVH Inc., Court File 24-000659, Ontario Court of Justice, before Justice Heather Perkins-McVey.[11]

In April 2024, the Royal Canadian Mounted Police (RCMP) obtained a Production Order under section 487.014(1) of the Canadian Criminal Code, targeting subscriber data and metadata associated with four IP addresses hosted on OVH servers in France, the United Kingdom, and Australia. The investigation is a national security matter; the underlying facts are sealed.

OVH’s defense was triple-layered. The French parent argued it had no physical presence in Canada and that its Montreal subsidiary, Hébergement OVH Inc., was a separate legal entity that did not control the parent’s data. The French Blocking Statute — Loi 68-678 of July 26, 1968, strengthened by Decree No. 2022-207 — prohibited French companies and personnel from disclosing economic or technical data to foreign public authorities outside formal treaty channels, on penalty of six months’ imprisonment and fines up to €90,000 for legal persons. And Canada and France have a Mutual Legal Assistance Treaty (MLAT); France’s Ministry of Justice had offered expedited processing. The lawful channel was sitting open.[12]

The court rejected all three.

On jurisdiction, Justice Perkins-McVey applied what Canadian courts call the “virtual presence” doctrine: a seven-year settled line across four provinces holding that a foreign corporation with a “real and substantial connection” to Canada — data centers, Canadian customers, marketing targeting Canadian users — falls within Canadian jurisdiction regardless of where its data is physically stored.[13] OVH conceded that it controlled the data and was capable of responding to a lawful court order.[14] From there, the question answered itself.

On the blocking statute, the court acknowledged that Article 1 bis of Loi 68-678 applied. France’s SISSE — the Service de l’Information Stratégique et de la Sécurité Économiques, designated as the official enforcement point under the 2022 reforms — had written to OVH in May 2024 asserting that disclosure would violate French law. The court weighed that evidence and dismissed it. Only one conviction had ever been recorded under Article 1 bis in nearly half a century since it was added to the statute in 1980. Expert witnesses could not point to a single case in which the statute had been respected by a foreign court. Justice Perkins-McVey adopted the English High Court’s “empty vessel” characterization — the standard articulated by Butcher J in Tugushev v. Orlov and applied in Joshua v. Renault — concluding that the blocking statute, in practical effect, is an empty vessel.[15]

On MLAT, the court held the treaty process permissive, not mandatory: Canadian courts retain jurisdiction to issue production orders where the target is present in Canada, and the availability of MLAT does not preclude that jurisdiction.[16]

The application to revoke the production order was dismissed. OVH Group SA and Hébergement OVH Inc. were ordered to comply by October 27, 2025. OVH filed for judicial review to the Ontario Superior Court of Justice through Miller Thomson at the end of October 2025. As of this writing, that appeal is pending.[17]

Three facts carry forward from the ruling into the framework analysis.

The “virtual presence” doctrine is not a one-off improvisation by a trial court. It is a seven-year settled line across British Columbia, Alberta, Quebec, and Ontario, anchored by two provincial Courts of Appeal and reinforced by two 2025 Superior Court rulings extending the doctrine to restraint and management orders. A single Newfoundland ruling that pointed the other way was explicitly declared non-binding.

OVH’s own sovereignty marketing was quoted by the Crown as evidence of control. OVH’s corporate website describes the company as “part of an active ecosystem that shares the same values, and a common vision of a sovereign cloud” — language lifted directly into the Crown’s compendium at Tab 4 as proof that OVH operates as a unified global enterprise over which its Canadian subsidiary exercises possession or control.[18] The branding that OVH built to sell sovereignty became the evidence that defeated its sovereignty defense in court.

And a twenty-five-year-old Ontario Superior Court ruling, Wilson v. Servier Canada, had already held in the civil context that French blocking statutes should be given “minimal weight” when they conflict with Canadian proceedings anchored on a real and substantial connection to Ontario.[19] Wilson was a civil class action, not a criminal production order, and the analogy has limits. But the Canadian courts’ general posture toward French extraterritorial protection predates 2024 by decades.

CSF Version 1.2.1 was published one month after Justice Perkins-McVey released her ruling. A Commission drafter scoping the CSF’s SOV-2 risk vectors would have found it on a first search.

The Proximus Consortium

Of the four winning consortia, only the Proximus-led group scored SEAL-2. It also carries the most complex non-EU exposure, and the Commission’s press release names the exposure on both ends of the stack.

The consortium bundles five entities. Clarence is a Luxembourg-based joint venture between Proximus and LuxConnect (a Luxembourg state-owned company) that deploys Google Distributed Cloud in an air-gapped configuration. S3NS is Thales Cloud Sécurisé SAS, a Thales subsidiary licensed to operate Google Cloud technology from three Île-de-France facilities under the French “Cloud de Confiance” framework, qualified SecNumCloud 3.2 in December 2025.[20] Mistral AI provides model services. Thales contributes security infrastructure, including hardware security modules. Proximus is the Belgian telecommunications incumbent — with the Belgian state holding an economic stake of 53.51 percent through SFPI-FPIM (Société Fédérale de Participations et d’Investissement) — and acts as a systems integrator for Belgian federal agencies, covering more than 70,000 users.[21]

Two of the five — S3NS and Clarence — run Google Cloud technology. Both sit within sovereign-cloud qualification constraints intended to insulate the technology from its American owner. The mechanism is corporate and operational: Thales holds a controlling interest in S3NS with Google as a minority partner, and only cleared EU citizens can access production systems. Thales holds the hardware security module keys, and the Google software stack is deployed through a technical quarantine intended to prevent upstream control. The French ANSSI referential for SecNumCloud 3.2 caps non-EU ownership at 24 percent individually and 39 percent collectively, covering both share capital and voting rights, direct or indirect. Google’s stake in S3NS is structurally constrained below these caps by the qualification requirement itself; the exact equity split has not been publicly disclosed by Thales or Google.[22] For its part, the Commission’s April 17 press release accepts the arrangement at SEAL-2 — “Data Sovereignty” in the framework’s own naming. It describes the technical environment as “based on Google Cloud technology, exclusively operated by EU companies.”[23]

The SecNumCloud qualification is real. The personnel, key-custody, and operational constraints it imposes on Google-powered partnerships materially reduce the likelihood that a CLOUD Act demand on the American partner reaches tenant data, the specific threat vector the framework was designed to address. What SecNumCloud does not address is an exposure category involving different actors in the stack: the physical infrastructure owner, the infrastructure owner’s shareholders, and the shareholders’ investment manager. That exposure is not within the qualified entity’s control, nor is it within the framework’s named risk vectors.

The more direct exposure is elsewhere in the consortium’s stack. The integrator workloads Proximus runs for Belgian federal agencies — the logging infrastructure, the operational telemetry, the coordination surfaces — run on Belgian data centers. Proximus itself owned those facilities until March 2025, when it sold them to Datacenter United for €128 million cash, against a combined enterprise value of €200.5 million.[24]

Who owns Datacenter United? TINC NV, a Belgian-listed infrastructure fund, holds 47.5 percent economic / 50 percent voting. Cordiant Digital Infrastructure Limited, together with a second Cordiant-managed vehicle, holds 47.5 percent economic / 50 percent voting, with aggregate equity consideration of €92.3 million. Friso Haringsma, CEO, holds 5 percent of non-voting shares.[25]

Let’s keep digging. Cordiant Digital Infrastructure Limited is a closed-end investment company listed on the London Stock Exchange since February 2021. Its investment manager — the firm that controls investment decisions, allocation, and board representation on behalf of the listed company — is Cordiant Capital Inc., a private markets asset management firm headquartered in Montreal, Quebec, with additional offices in London, Luxembourg, and São Paulo.[26]

The analytical parallel to OVH is imperfect, and the piece acknowledges this. Cordiant Capital Inc. is an asset manager; it does not directly access tenant data, and a Canadian production order to Cordiant would face a higher “possession or control” hurdle than OVH Canada faced. A fund’s management jurisdiction imposes regulatory obligations on the fund, not automatically on the tenants of its portfolio companies.

The objections are real. What they do not close is the structural exposure. Belgium has no equivalent to Loi 68-678. The legal barrier the OVH ruling dismissed is not even in place to be dismissed here. The seven-year Canadian precedent line is still expanding, and In re TD Bank Production Order in 2025 narrowed the “possession or control” test further — the Quebec Superior Court found that a Canadian parent had possession or control over data held by a US subsidiary on the strength of its corporate control, without requiring direct technical access. That test applied to the Cordiant chain is harder than OVH Canada faced, but not categorically different from the one TD Bank lost on.[27]

The exposure is present in the ownership chain, but has not yet been demonstrated in an enforcement event. Risk committees should assess exposure categories that the framework does not name without assuming any specific exposure has materialized.

What Actually Exists

Three of the four winners come closer to what the framework’s SEAL-4 language describes.

The Post Luxembourg consortium runs through DEEP, the data center subsidiary of Post Telecom (itself a subsidiary of POST Luxembourg, 100% owned by the Luxembourg state). DEEP operates three data centers in Luxembourg at Windhof, Kayl, and Betzdorf, carrying Tier IV Uptime Institute certification — Kayl and Betzdorf at Tier IV Constructed Facility level, Windhof at Tier IV Design Documents level — and hosts OVHcloud infrastructure and Clever Cloud workloads on sovereign Luxembourg soil.[28] OVHcloud itself is listed on Euronext Paris; the Klaba family holds approximately 81 percent of shares.[29] Clever Cloud is French and privately held. The full stack runs on EU-owned infrastructure in an EU jurisdiction. This is a genuine sovereignty claim at SEAL-3, and if the framework’s SOV-2 actually tested legal exposure, it could plausibly have scored higher.

StackIT, the cloud unit of Schwarz Digits, runs in data centers the Schwarz Group has operated for decades — DC01 in Neckarsulm, DC08 in Ellhofen, DC10 in Ostermiething, Austria, and a new 200 MW facility under construction at Lübbenau with an €11 billion capex commitment through 2027.[30] Schwarz Group, the privately-held Schwarz family holding that also controls Lidl and Kaufland, reported fiscal year 2024 total sales of €175.4 billion; Schwarz Digits segment revenue was €1.9 billion, with StackIT as one of several business units within the digital segment.[31] No non-EU entity appears in the ownership or operational chain.

Scaleway’s parent is Iliad, the French telecommunications group controlled by Xavier Niel. Its Paris-anchored sovereign-qualified infrastructure — Paris DC2 through DC5, Lyon, Marseille, and facilities in Poland — is operated by OpCore, carved out of Scaleway in July 2024 and converted into a fifty-fifty joint venture between Iliad and InfraVia Capital Partners on March 2025 closing, at an enterprise value €860 million and a €2.5 billion capex commitment over ten years.[32] InfraVia is a French independent private equity firm headquartered in Paris, regulated under the EU’s Alternative Investment Fund Managers Directive.

Three of the four consortium members run infrastructure that the framework was designed to produce. The SOV-5 Supply Chain weight — the heaviest in the rubric at 20% — rewards EU-owned hardware and operations, and the SEAL-2 eligibility floor keeps non-sovereign offerings out entirely. The result: all four winners operate on EU soil with EU-controlled physical layers. Physical sovereignty is genuine at three of the four.

The framework succeeded at physical sovereignty. It was not designed to deliver legal sovereignty, and SOV-2 at 10% never was. The SEAL-4 definition says it plainly: "subject only to EU law."

That is not a question of where servers sit. The question is whether every legal avenue through which a non-EU authority could compel disclosure has been closed. None of the four winners can answer yes.

The Commission has not published individual scoring breakdowns. We know the tier outcomes; we do not know which objectives each winner failed, by how much, or whether the gap was structural or marginal. That opacity is itself a finding.

The Governance Pattern

The Commission’s sovereign cloud framework is the third European attempt in three years to codify cloud sovereignty as a procurement instrument. EUCS — the European Union Cybersecurity Certification Scheme for cloud services — stalled in draft over exactly this question: whether the highest assurance level should require ownership by an EU entity not subject to non-EU law. France pushed for the requirement, with Italy and Spain supporting it. A coalition of Member States, including Denmark, Estonia, Greece, Ireland, the Netherlands, Poland, and Sweden, resisted, signing a joint non-paper in July 2022; by mid-2023, approximately twelve Member States opposed the sovereignty requirement. The final March 2024 draft dropped the ownership requirement in favor of an International Company Profile Attestation.[33] The proposed Cloud and AI Development Act (CADA), announced but not yet tabled as of April 2026, is the Commission’s next attempt.[34]

The CSF filled the gap left by EUCS, and CADA has not closed it. The Commission chose to do what it could procure — a scoring rubric tied to a dynamic purchasing system — rather than what it could not secure politically: a legal definition of sovereignty with binding ownership constraints.

For three years, Paris held the line in the EUCS negotiations: sovereignty meant EU ownership, full stop, no hyperscaler joint ventures, no Cloud de Confiance workarounds. Italy and Spain agreed. Twelve Member States did not. The EUCS draft dropped the ownership requirement in March 2024. The maximalist French demand became a scoring coefficient that the Commission preemptively justified as redundant.

CISPE, the European cloud providers’ trade association, called the outcome six months early. Its October 24, 2025 statement “No Such Thing as ‘75% Sovereign’” warned that the framework’s ten-percent legal weighting would allow hyperscaler-backed offerings to qualify; Secretary General Francisco Mingorance was quoted saying “the big players will be able to achieve very high overall scores that minimize the impact of poor results in legal and jurisdictional sovereignty — which only account for 10% of the total score.” The Commission did not dispute the analysis. It published the award six months later, exactly as described.[36]

What Would Have to Break

The Commission’s April 17 press release announcing the €180 million award also announced the framework revision that would incorporate the lessons learned from the award. In the same press release. The Commission published the awards and the planned fix in a single document, which is either unusual procedural efficiency or a tell about what the Commission expected the reaction to be. Lessons are ordinarily learned after events. Here they were scheduled before the event’s ink dried.

The CSF’s defenders can argue the framework was never meant to be final. SEAL-4 exists in the definition even though no winner reached it; CADA is on the legislative calendar; the Commission stated in its April 17 announcement that it “will publish an updated version of the Sovereign Cloud Framework based on lessons learned from this tender.” True. Insufficient. A lessons-learned revision is a calibration instrument — it adjusts weights and contributing factors. The structural question is whether a future CSF iteration will restructure the SOV-2 weighting and extend the named risk vectors beyond the CLOUD Act and the Chinese Cybersecurity Law, not as an administrative update, but as a political choice.

The real test is whether the ten-percent SOV-2 weight reflects a drafting accident that a later iteration will correct, or a negotiated outcome reflecting a coalition that cannot accept binding legal sovereignty as a procurement requirement. The Commission’s own justification — that procurement procedure “already contains significant safeguards” at SOV-2 — points to the second.

The Proximus consortium’s composite score would fall below what the other three winners achieved. If SOV-2 contributing factors extended beyond the two named threats, Commonwealth extraterritorial doctrines would enter the evaluation matrix. The ten-percent weight and the two named threats are the mechanisms by which the framework was shipped to procurement on its intended timeline. Removing them reopens the EUCS deadlock.

This thesis would be wrong if CADA, when tabled, restructures the SOV-2 weighting and extends the named risk vectors to cover Canadian, UK, and Five Eyes extraterritorial reach, and does so with binding effect. It would be wrong if the Ontario Superior Court of Justice overturns OVH on the pending appeal, unwinding the case on narrow procedural grounds that deny broader doctrinal implications.

None of these seems likely. CADA has been on the European Parliament’s legislative train since 2025 and has not been tabled; the Q1 2026 tabling window closed without a Commission proposal. The OVH appeal, even if successful, unwinds the specific case but not the doctrine — the Canadian precedent line is seven years and four provinces deep, and one reversal does not erase two Courts of Appeal and two 2025 Superior Court rulings. European institutions process data continuously; the framework contracts are live now.

What actually breaks the pattern is an enforcement event. A Canadian production order that reaches a Cordiant-managed Belgian data center; a UK Investigatory Powers Act technical capability notice served under section 253 on a telecommunications operator in the ownership chain of a Commission-awarded tenant’s infrastructure; a CJEU ruling, on preliminary reference under GDPR Articles 44–48, that personal data processed under a CSF-awarded contract fell outside the transfer framework because the CSF’s sovereignty assurance did not substantially block non-EU access. Until one of those arrives, the framework holds.

The CSF’s enforcement failure, like the failures that preceded EUCS and CADA, is not a bug. It is the negotiated outcome. The Commission’s page-six explanation — that SOV-2 is downweighted because procurement procedure “already contains significant safeguards” — is, read strictly, accurate. The procurement process did contain safeguards. They were the ones the Commission chose to put there.

The weights were set, the named threats were chosen, and the SEAL tiers were defined to produce a specific outcome: a procurement the Commission could run, with winners it could defend, under a rubric it controlled. The OVH ruling didn’t fit that rubric. The Cordiant ownership chain didn’t fit that rubric. The Canadian virtual presence doctrine didn’t fit that rubric. So they were not named, SOV-2 was weighted at 10%, and the contracts were awarded on schedule.

The European Commission did not relax the definition of sovereignty on April 17, 2026. It built a scoring matrix that made its preferred outcome look like a sovereignty finding, awarded €180 million under it, and announced the lessons-learned revision in the same press release. The next framework will be more defensible. It will not be more sovereign.

Did you really expect something else?

Notes

[1] European Commission, Directorate-General for Digital Services, Cloud Sovereignty Framework, Version 1.2.1, October 2025, p. 6 (Section 5, Computation of Sovereignty Score). The document cover carries “Version 1.2.1 – Oct. 2025”; external sources (CISERO, Interoperable Europe Portal, CISPE responses) place publication on or about October 20, 2025. Direct quotation from the document’s justification for SOV-2 and SOV-7 weighting.

[2] European Commission press release, “Commission advances cloud sovereignty through strategic procurement,” IP/26/833, April 17, 2026. €180 million is the maximum authorized spend under the framework contract, not a committed disbursement; actual call-offs across the six-year term will determine spend. Mechanism: Cloud III Dynamic Purchasing System. The same announcement states that the Commission “will also publish an updated version of the Sovereign Cloud Framework based on lessons learned from this tender”; this is cited in the body’s Act 6 as the Commission’s own acknowledgment of a lessons-learned revision cycle.

[3] European Commission press release, April 17, 2026, describing the Proximus-led consortium’s technical architecture. Direct quotation.

[4] R. v. OVH Group SA and Hébergement OVH Inc., Ontario Court of Justice (Ottawa), Court File 24-000659, Heather E. Perkins-McVey J., decision released September 25, 2025. Signed final decision available via David Fraser, McInnes Cooper. The “empty vessel” characterization originates in Butcher J’s judgment in Tugushev v. Orlov, [2021] EWHC 1514 (Comm) at paragraph [33], and was applied to Loi 68-678 in Thomas John Joshua et al v. Renault S.A., [2024] EWHC 1424 (KB) at paragraphs [77]–[78]. Adopted in R. v. OVH at paragraph [115].

[5] European Commission announcement, April 17, 2026. The four awardees are identified in the Commission’s release.

[6] Winner composition per Commission announcement. Thales is named as a consortium partner in Commission and Proximus materials; the Commission press release specifically names S3NS, Clarence, and Mistral in describing the Google Cloud technology base.

[7] Cloud Sovereignty Framework, Version 1.2.1, Section 3, page 3. SEAL tier names and definitions verbatim from the document: SEAL-0 “No Sovereignty”; SEAL-1 “Jurisdictional Sovereignty”; SEAL-2 “Data Sovereignty”; SEAL-3 “Digital Resilience”; SEAL-4 “Full Digital Sovereignty.”

[8] Cloud Sovereignty Framework, Version 1.2.1, October 2025. Document cover dated “Oct. 2025”; contemporaneous coverage and Commission register place publication on or about October 20, 2025.

[9] Cloud Sovereignty Framework, Version 1.2.1, Section 5, page 6 weighting table. Per-objective weights: SOV-1 Strategic Sovereignty 15%, SOV-2 Legal & Jurisdictional Sovereignty 10%, SOV-3 Data & AI Sovereignty 10%, SOV-4 Operational Sovereignty 15%, SOV-5 Supply Chain Sovereignty 20%, SOV-6 Technology Sovereignty 15%, SOV-7 Security & Compliance Sovereignty 10%, SOV-8 Environmental Sustainability 5%. SOV-5 is the largest single weight; SOV-8 is the smallest and, notably, the only objective titled “Sustainability” rather than “Sovereignty.”

[10] Cloud Sovereignty Framework v1.2.1, SOV-2 contributing factors. The framework enumerates the US CLOUD Act and the Chinese Cybersecurity Law and adds a catch-all reference to “non-EU laws with cross-border reach” without naming specific Commonwealth jurisdictions.

[11] R. v. OVH Group SA and Hébergement OVH Inc., Ontario Court of Justice, Court File 24-000659, Ottawa, Heather E. Perkins-McVey J., decision released September 25, 2025. Crown counsel: Michael Fawcett; OVH counsel: Scott Spencer (Miller Thomson). The ruling is a statutory review under the Criminal Code s. 487.0193(4) of a Production Order issued under s. 487.014. The underlying Production Order was issued in April 2024; paragraph [1] of the ruling gives April 11, and paragraph [24] gives April 19 with specific IP/date associations, the latter treated as authoritative. Investigation sealed (national security).

[12] Summary of OVH’s position per paragraphs [3]–[9] of the ruling. French blocking statute at Loi 68-678 of July 26, 1968, with Article 1 bis added by Loi n° 80-538 of 16 July 1980, strengthened by Decree No. 2022-207 of February 18, 2022. Statutory penalty scheme under Article 3, as amended: imprisonment up to 6 months and fines up to €18,000 for individuals; for legal persons, the fine is fixed at 5× the individual fine under Article 131-38 of the French Code pénal, producing a maximum of €90,000.

[13] British Columbia (Attorney General) v. Brecknell, 2018 BCCA 5 (CanLII); R v Love, 2022 ABCA 269 (CanLII); In the Matter of textPlus Inc., 2022 ONSC 7413 (CanLII); In re TD Bank Production Order, 2025 QCCS 2094; R v Binance Holdings Ltd., 2025 ONSC 7113. Per R. v. OVH ruling paragraphs [40]–[53]. The Newfoundland authority In the Matter of an application to obtain a Production Order, 2018 Carswell Nfld 19, is distinguished as non-binding at paragraph [55]. The doctrine remains contested within the Canadian privacy bar — see David Fraser, Canadian Privacy Law Blog, December 5, 2025, arguing that Brecknell itself was wrongly decided on its facts (Craigslist had voluntarily accepted jurisdiction, a fact the OVH court did not preserve as a limiting principle). The piece’s framing reflects the doctrine as applied by the courts, not uniform agreement among Canadian commentators.

[14] Ruling at paragraph [60]: “OVH Parent has acknowledged that it controls the data sought and is capable of responding to a lawful court order (OVH Factum at para. 34).” Jurisdictional analysis at paragraphs [56]–[63].

[15] Ruling at paragraphs [79]–[123]. “Empty vessel” standard adopted from Butcher J in Tugushev v. Orlov, [2021] EWHC 1514 (Comm) at paragraph [33], applied to Loi 68-678 in Thomas John Joshua et al v. Renault S.A., [2024] EWHC 1424 (KB) at paragraphs [77]–[78]. Sole reported Article 1 bis conviction is the “Christopher X” case, Cour de cassation chambre criminelle, 12 December 2007, pourvoi n° 07-83.228, addressed at ruling paragraph [85]. Australian authority on the French Blocking Statute: ACCC v. Prysmian Cavi e Sistemi Energia S.R.L. (No 4), [2012] FCA 1323. US authority: Societe Nationale Industrielle Aerospatiale v. US District Court, 482 U.S. 522 (1987). The 2022 SISSE reforms under Decree No. 2022-207 are discussed at paragraphs [86]–[87]. The SISSE letter to OVH dated May 27, 2024 appears as Appendix B to the Barrière Affidavit (ruling at paragraph [108]); secondary press reports reference a further letter in January 2025 not directly quoted in the ruling.

[16] Ruling at paragraphs [97]–[105]. Canadian authority on MLAT’s permissive nature: R v Strong, 2020 ONSC 7528 at paragraphs 103, 112. The court’s conclusion that MLAT is not mandatory and does not preclude Canadian production orders appears at paragraphs [17] and [99].

[17] Ruling disposition at paragraphs [124]–[126]. Appeal filing confirmed by Heise Online, November 26, 2025, citing OVH filings. As of April 2026, no Ontario Superior Court ruling on the judicial review has been released.

[18] Ruling at paragraph [12], quoting OVH Canada’s “About Us” and “Our Values” pages as reproduced in the Crown’s compendium at Tab 4.

[19] Wilson v. Servier Canada Inc., 2000 CanLII 22407 (ONSC), cited at ruling paragraph [95]. An Ontario class action against a French pharmaceutical company, concerning French Civil Code Article 15 (a civil blocking statute asserting exclusive French jurisdiction). Civil procedural context, not criminal production orders; the analogy holds on Canadian judicial posture toward French extraterritorial protection in cross-border contexts, but does not establish criminal production-order precedent.

[20] S3NS (Thales Cloud Sécurisé SAS), RCS Paris 908 211 980, qualified SecNumCloud 3.2 by ANSSI on December 17, 2025. Thales/Google joint venture structure per S3NS General Terms of Use.

[21] Proximus NV, 2025 Integrated Annual Report, capital structure section. The Belgian state economic stake held via SFPI-FPIM (Société Fédérale de Participations et d’Investissement) is stated at 53.51%. Integrator scope: Proximus NXT SECaaS1 press materials reference 10 key government entities and 70,000+ users served under the federal framework; the Commission has not published a specific tender-linked agency count.

[22] SecNumCloud v3.2 referential (ANSSI, 2022) caps non-EU ownership of qualified entities at 24% individually and 39% collectively, applied to both share capital and voting rights, whether held directly or indirectly. Thales is the controlling shareholder of S3NS; the exact Google equity stake has not been publicly disclosed by Thales or Google. ANSSI’s December 17, 2025, qualification of S3NS 3.2 is the formal finding that the referential’s ownership test is met.

[23] European Commission press release, April 17, 2026, describing the Proximus-led consortium’s technical architecture: “Proximus leverages capacities of partners S3NS, Clarenc,e and Mistral from a technical environment based on Google Cloud technology, exclusively operated by EU companies.”

[24] Proximus NV press release, “Proximus sells its data centers to Datacenter United,” March 3, 2025. Transaction structure: €128 million cash consideration to Proximus; combined enterprise value €200.5 million. Post-sale Proximus remainsthe anchor tenant under a 10-year master services agreement with annual pricing review.

[25] Datacenter United ownership structure per TINC NV announcement and Cordiant Digital Infrastructure Limited regulatory disclosure, March 2025. TINC NV: 47.5% economic / 50% voting. Cordiant Digital Infrastructure Limited, together with a second Cordiant-managed fund: 47.5% economic / 50% voting, with aggregate equity consideration of €92.3 million across both Cordiant vehicles. Friso Haringsma (CEO): 5% non-voting.

[26] Cordiant Digital Infrastructure Limited is listed on the London Stock Exchange (ticker CORD) since February 2021. Investment management performed by Cordiant Capital Inc., a private markets asset manager headquartered in Montreal, Quebec, with additional offices in London, Luxembourg, and São Paulo. Per Cordiant Capital Inc. corporate disclosures.

[27] In re TD Bank Production Order, 2025 QCCS 2094 (Quebec Superior Court). The Court found TD Bank Canada had “possession or control” over records held by its US subsidiary on the strength of corporate control, without requiring direct technical access by Canadian employees. See also R v Binance Holdings Ltd., 2025 ONSC 7113, extending Brecknell‘s “real and substantial connection” test to restraint and management orders. Per R. v. OVH ruling paragraph [53].

[28] Post Telecom corporate structure: Post Telecom is a subsidiary of POST Luxembourg, which is 100% owned by the Luxembourg state. DEEP is Post Telecom’s data center subsidiary, consolidating the former EBRC, Digora, Elgon, and POST Telecom cloud units under a single brand. Three data centers at Windhof, Kayl, and Betzdorf; Tier IV certification status per Uptime Institute public database: Kayl (Tier IV Design + Constructed Facility, 2013), Betzdorf (Tier IV Design + Constructed Facility, 2015), Windhof (Tier IV Design Documents only).

[29] OVH Groupe SA, FY2024 Annual Results, October 23, 2024. Klaba family's share capital increased from ~68% to ~81% following the 2024 buyback completion, per OVHcloud's press release and Bredin Prat's deal notes. Voting rights are materially higher through French double-voting loyalty provisions, controlling provision for listed companies at Article L.22-10-46 of the Code de commerce since the 2020 recodification (Ordonnance n° 2020-1142), cross-referencing Article L.225-123; loi Florange (Loi n° 2014-384 of 29 March 2014); voting rights reported at approximately 82% as of late 2025.

[30] Schwarz Group data center operations: DC01 Neckarsulm, DC08 Ellhofen (Germany), DC10 Ostermiething (Austria). Lübbenau facility: 200 MW planned capacity, €11 billion capex commitment cited in Schwarz Group materials, target completion 2027.

[31] Schwarz Group FY24 press communication, May 22, 2025. Group total sales €175.4 billion for fiscal year 2024 (March 1, 2024 to February 28, 2025); Schwarz Group reports on a March–February fiscal year. Schwarz Digits segment revenue €1.9 billion; Schwarz Digits includes StackIT, XMCloud, and other digital operations — StackIT portion not separately disclosed. StackIT’s Lübbenau facility is the fourth German site; additional capacity sites, including Berlin and the Austrian Ostermiething facility, bring the operational footprint to 4–7 data centers, depending on the definitional scope.

[32] InfraVia Capital Partners and Iliad Group press release, “The Iliad Group and InfraVia partner to develop a major European hyperscale data center platform,” December 4, 2024 (announcement); closing March 2025. OpCore was carved out of Scaleway on July 1, 2024, as a standalone Iliad data-center vehicle; the 50/50 Iliad/InfraVia JV structure was announced on December 4, 2024, and closed in March 2025. Enterprise value €860 million at JV formation; capex commitment stated as “more than €2.5 billion” over a decade, structured as joint capital deployment commitments of the 50/50 shareholders rather than a contractually enforceable obligation to a third party. InfraVia Capital Partners registered as an Alternative Investment Fund Manager with the French AMF (GP 08 000018) under the EU’s AIFMD framework.

[33] EUCS (European Union Cybersecurity Certification Scheme for Cloud Services) consultation history per ENISA public records. The High+ assurance level’s “Annex J” sovereignty requirements — EU headquarters, EU ownership, immunity from non-EU law — were contested between 2021 and 2024. A July 2022 joint non-paper opposing the sovereignty requirement was signed by at least Denmark, Estonia, Greece, Ireland, the Netherlands, Poland, and Sweden, with Lithuania sometimes added. France, supported by Italy and Spain, championed the requirement; Germany’s position was mixed. By mid-2023, EUISS reporting cited approximately twelve Member States opposing. The March 22, 2024 ENISA draft dropped sovereignty requirements in favor of an International Company Profile Attestation (ICPA). The scheme had not been formally adopted as of April 2026.

[34] Cloud and AI Development Act (CADA), status “Announced” on the European Parliament Legislative Train as of March 20, 2026. The expected Q1 2026 tabling window closed without a Commission proposal.

[35] Emmanuel Macron, Artificial Intelligence Action Summit, Grand Palais, Paris, February 10, 2025. “France is back in the AI race” per France 24 live coverage, February 10, 2025. “Plug baby, plug” quotation per CSIS analysis, “France’s AI Action Summit”. €109 billion investment figure and €50 billion UAE contribution per contemporaneous summit coverage. The Paris AI Action Summit took place February 10–11, 2025; the EUCS Annex J sovereignty requirements were dropped from the ENISA draft in March 2024.

[36] CISPE (Cloud Infrastructure Services Providers in Europe), “No Such Thing as ‘75% Sovereign’: CISPE Responds to the European Commission’s Sovereign Cloud Framework,” October 24, 2025. Francisco Mingorance's quotation per interview with Incyber News, November 2025. CISPE subsequently issued a January 2026 position paper expanding the critique.

On April 15, Jensen Huang told Dwarkesh Patel that Trainium and TPU external growth was “one hundred percent Anthropic” — that Anthropic “is a unique instance, not a trend.”[1] The market read that as reassurance about Nvidia’s position. Yesterday’s piece argued it was the opposite: a concession, on the record, that the entire alt-silicon market is one customer, and that the customer exists because its equity-for-compute need lined up with a hyperscaler that had both the silicon and the checkbook.

Six days later, and nine days before earnings, Amazon priced that concession.

Today’s announcement pushes the investment structure to a potential cumulative position of $33 billion: Amazon invests $5 billion in Anthropic now and up to $20 billion more “tied to certain commercial milestones,” on top of the $8 billion already committed.[2] What the $25 billion of incremental equity buys, under the contract, is one word: primary.

Three rounds, three times the same word

September 2023: Amazon invests $4 billion. Anthropic names AWS “its primary cloud provider.”[3]

November 2024: Amazon invests another $4 billion. Anthropic names AWS “our primary cloud and training partner.”[4]

April 2026: Amazon invests $5 billion now, with up to $20 billion more contingent on milestones. Anthropic’s language: “We continue to choose AWS as our primary training and cloud provider for mission-critical workloads.”[5]

Three rounds. Three times the same word. At $4 billion cumulative, “primary.” At $8 billion cumulative, “primary.” At up to $33 billion cumulative, still “primary” — now narrowed by a qualifier that did not exist in either previous agreement. “For mission-critical workloads” is not a deepening of exclusivity. It is a ring-fence around which AWS retains claim to workloads, and, by extension, which it does not.

The reason the ring-fence appears in this round and not the previous two is disclosed in the same document: Claude is now “the only frontier AI model available to customers on all three of the world’s largest cloud platforms: AWS (Bedrock), Google Cloud (Vertex AI), and Microsoft Azure (Foundry).”[5] “Primary” in 2026 refers to one of three formally first-class hyperscaler relationships; in 2023, it referred to the only such relationship.

The triangulation mechanics

The $25 billion reads as defensive spending when compared with the two deals that preceded it.

On November 18, 2025, Microsoft invested up to $5 billion in Anthropic, and Nvidia committed up to $10 billion, against a $30 billion Anthropic commitment to Azure compute and up to 1 GW of Grace Blackwell and Vera Rubin capacity.[6] On April 6, 2026, Broadcom disclosed in an 8-K that Anthropic had committed to approximately 3.5 gigawatts (GW) of Google TPU capacity starting in 2027, on top of the 1 GW already coming online in 2026 through the October 2025 Google Cloud agreement.[7] Mizuho estimates Broadcom’s Anthropic-attributed revenue at $21 billion in 2026 and $42 billion in 2027.[8]

Amazon’s response, three weeks later, commits up to $33 billion in cumulative equity against $100 billion in Anthropic AWS spend over 10 years and 5 GW of Trainium capacity, with roughly 1 GW expected by the end of 2026.[2] Across the three hyperscalers, Anthropic now holds up to $40 billion in potential equity commitments against compute spend exceeding $130 billion flowing back to them.

AWS remains primary by the measure that matters operationally — 5 GW is five times the initial Azure commitment and one-and-a-half times the 2027 Google ramp. That is what Jassy’s quote points to, and it is the real commercial substance: capacity, Claude Platform native integration inside AWS accounts, and the Annapurna engineering loop on Trainium chip design.[2] None of that is nothing. It is also not what Amazon has historically paid for. The equity-to-capacity ratio has moved from $4 billion per “primary cloud provider” to $4 billion per “primary cloud and training partner,” and now up to $25 billion per “primary training and cloud provider for mission-critical workloads.” Capacity scaled. The word narrowed.

The round-trip is affordable for each hyperscaler because of the other side of Anthropic’s balance sheet. Anthropic disclosed today that run-rate revenue has “surpassed $30 billion, up from approximately $9 billion at the end of 2025” — a 3.3x expansion in four months.[5] At that growth rate, losing primary status to Azure or Google Cloud is not a loss of a billion-dollar customer. It is a tens-of-billions-per-year revenue stream compounding on the capex already committed.[9]

What the $20 billion actually is

The $20 billion tranche is not an investment commitment. It is a commercial-milestone-gated option on further equity issuance, with the milestones undisclosed in today’s filing. Broadcom’s April 8-K used parallel language from the other direction: “The consumption of such expanded AI compute capacity by Anthropic is dependent on Anthropic’s continued commercial success.”[7]

Both sides of every deal in the triangle are now demand-contingent. The equity flows if Anthropic keeps compounding. The compute flows if Anthropic keeps compounding. The hyperscaler revenue flows if Anthropic keeps compounding. None of it flows if the $9 billion to $30 billion trajectory from end-2025 to April-2026 is a pull-forward rather than a durable curve.

That is the unstated reason “for mission-critical workloads” appeared in the 2026 language. If growth continues, the qualifier is decorative — everything becomes mission-critical. If growth pauses, the qualifier is that Anthropic retains operational flexibility to shift non-critical workloads across the three clouds based on price and capacity, which is exactly what a compute buyer with three first-class supplier relationships should do.

The qualifier hovers over a second distribution boundary that took shape two weeks earlier. Amazon Bedrock launched Claude Mythos Preview on April 7 as a “gated research preview” — available only in the US East (N. Virginia) region and only to allow-listed organizations.[10] Anthropic declined to make Mythos generally available, citing its autonomous hacking capabilities. Internal testing surfaced a 27-year-old OpenBSD vulnerability and chained Linux kernel privilege-escalation exploits, among other findings across major operating systems and browsers.[11]

Eight days after the Bedrock launch, the European Commission opened a formal inquiry into the model, invoking the EU general-purpose AI Code of Practice that Anthropic has signed: assessment obligations apply to services “that may or may not be offered in Europe.”[12] The “meaningful expansion of international inference in Asia and Europe” that today’s Amazon press release cites applies to the standard Claude product line. Mythos — the most mission-critical workload Anthropic ships — sits inside Bedrock but outside that expansion. “Primary” is now narrowing on three axes: the linguistic qualifier in the contract, the product-geography tiering that restricts the frontier cybersecurity model to a single US region within Bedrock, and the regulatory boundary that keeps that tier out of the EU.

Jensen’s concession, priced

Yesterday’s piece argued that custom AI silicon is additive to Nvidia rather than substitutive because the only external customer who matters is Anthropic — and Anthropic exists because of a difficult-to-replicate capital-structure arrangement. Today’s announcement confirms the diagnosis from both sides. Trainium’s external pull-through is so concentrated in Anthropic that Amazon paid up to $25 billion in incremental equity to hold contract language already in place at $8 billion cumulative, plus a narrowing qualifier. The lab, which was a structural anomaly in November 2024, has extracted up to $40 billion in potential hyperscaler equity in six months, even as compute commitments exceed $130 billion. The capital-structure arrangement that built the one customer is now the default funding model for the labs behind the leaders.

Yesterday’s piece closed on who the next Anthropic would be. Today prices the first one: three rounds of “primary,” a narrowing to “mission-critical,” a second tier carved out at the product-geography boundary, and $33 billion of potential equity held by a single hyperscaler that cannot afford to let the relationship downgrade.

The market had all day Monday to read the Amazon press release as a capital raise. The number it should read instead is $25 billion — the price of a word, in a document that simultaneously narrows the word’s scope.

Notes

[1] “Jensen Huang – TPU competition, why we should sell chips to China, & Nvidia’s supply chain moat,” Dwarkesh Podcast, April 15, 2026. Huang stated that Anthropic “is a unique instance, not a trend” and that Trainium and TPU external growth is “one hundred percent Anthropic.” See “Anthropic Is Not a Trend,” The AI Realist, April 20, 2026, for the Additive-vs-Substitutive Test framework and the capital-structure argument referenced throughout this piece.

[2] “Amazon and Anthropic expand strategic collaboration,” Amazon, April 21, 2026. Structure: $5 billion disbursed now, up to $20 billion more “tied to certain commercial milestones,” on top of the previously committed $8 billion. Commercial commitment: Anthropic to spend more than $100 billion on AWS technologies over ten years, including Trainium2, Trainium3, Trainium4, and future generations; up to 5 GW capacity. Claude Platform on AWS provides native Anthropic console access through AWS accounts without additional credentials or billing relationships. The Annapurna engineering collaboration is described in the same document as daily communication between the Anthropic and AWS engineering teams regarding the Trainium chip design.

[3] “Expanding access to safer AI with Amazon,” Anthropic, September 25, 2023. Original announcement of $4 billion with AWS as “primary cloud provider.” Language is precise and worth preserving in quotation: “primary cloud provider,” not “exclusive” and not “sole.” Google was already an Anthropic investor at this time; the “primary cloud provider” designation was formally applied to AWS alone.

[4] “Powering the next generation of AI development with AWS,” Anthropic, November 22, 2024. An additional $4 billion, bringing the cumulative total to $8 billion. AWS designation upgraded to “primary cloud and training partner.” The Trainium training commitment appears here for the first time.

[5] “Anthropic and Amazon expand collaboration for up to 5 gigawatts of new compute,” Anthropic, April 20, 2026 (dated one day prior to the Amazon press release). Full quote: “We continue to choose AWS as our primary training and cloud provider for mission-critical workloads.” The “mission-critical workloads” qualifier is new in the 2026 language and does not appear in the 2023 or 2024 announcements. The triple-hyperscaler framing (”Claude remains the only frontier AI model available to customers on all three of the world’s largest cloud platforms”) is also new. Revenue disclosure: “Our run-rate revenue has now surpassed $30 billion, up from approximately $9 billion at the end of 2025.” Consumer strain disclosure: Our unprecedented consumer growth, in particular, has impacted reliability and performance for free, Pro, Max, and Team users, especially during peak hours.” — Tthe operational case for capacity expansion sits alongside the capital-structure analysis and does not displace it.

[6] “Microsoft, NVIDIA and Anthropic announce strategic partnerships,” Microsoft Official Blog, November 18, 2025. Anthropic commits to $30 billion of Azure compute capacity and up to 1 GW of capacity on Nvidia Grace Blackwell and Vera Rubin systems. Microsoft invests up to $5 billion; Nvidia invests up to $10 billion. Anthropic valuation at the time of this deal: approximately $350 billion, up from $183 billion in September 2025. See also CNBC coverage of the valuation trajectory.

[7] Broadcom Form 8-K, filed April 6, 2026. Direct quote: “Anthropic, beginning in 2027, will access through Broadcom approximately 3.5 gigawatts as part of the multiple gigawatts of nex- generation TPU-based AI compute capacity committed by Anthropic. The consumption of such expanded AI compute capacity by Anthropic is dependent on Anthropic’s continued commercial success.” This is the disclosure that formalizes demand-contingency on the compute side, mirroring the milestone-gating on Amazon’s $20 billion tranche.

[8] “Broadcom agrees to expanded chip deals with Google, Anthropic,” CNBC, April 6, 2026. Mizuho analyst Vijay Rakesh estimates: $21 billion in Broadcom AI revenue from Anthropic in 2026, $42 billion in 2027. Broadcom’s role isa TPU manufacturing partner to Google; the Anthropic relationship routes through Google Cloud with Broadcom as the silicon supplier.

[9] Amazon’s 2026 capital expenditure guidance of approximately $200 billion was disclosed on the Q4 2025 earnings call in February 2026, as referenced by CNBC in “Amazon to invest up to another $25 billion in Anthropic,” April 20, 2026. The $5 billion disbursed today is roughly 2.5 percent of guided 2026 capex; the $25 billion incremental equity ceiling, spread over the unknown milestone period, would represent a materially smaller annualized percentage. The comparison is given to scale the current-year cash impact, not to conflate multi-year equity ceilings with annualized capex.

[10] “Amazon Bedrock now offers Claude Mythos Preview (Gated Research Preview),” AWS What’s New, April 7, 2026. AWS description: Mythos Preview is available only in the US East (N. Virginia) region through Amazon Bedrock, with access “limited to an initial allow-list of organizations.” AWS frames the release posture as a “deliberately cautious approach to release, prioritizing internet-critical companies and open-source maintainers.”

[11] “Claude Mythos Preview and Project Glasswing,” Anthropic, April 7, 2026. Anthropic announced Mythos on the same day as the Bedrock launch, citing a material capability jump over Claude Opus 4.6 and declining to make the model generally available. The core Project Glasswing partners are eleven organizations (Amazon Web Services, Apple, Broadcom, Cisco, CrowdStrike, Google, JPMorgan Chase, the Linux Foundation, Microsoft, Nvidia, and Palo Alto Networks), with approximately forty organizations total in the broader testing cohort. Anthropic is providing up to $100 million in usage credits to Glasswing partners and $4 million to open-source security organizations. Technical details of the autonomous vulnerability discovery — including the twenty-seven-year-old OpenBSD bug, chained Linux kernel privilege-escalation exploits, and a browser sandbox escape — are documented in the “Mythos Preview Technical Report,” Anthropic Frontier Red Team, April 2026.

[12] “Anthropic talks to EU, including on its cyber security models, Commission says,” Reuters, April 17, 2026. European Commission spokesman Thomas Regnier confirmed the April 15 briefing and invoked the EU general-purpose AI Code of Practice, to which Anthropic is a signatory: “In this framework, there is an obligation to assess and mitigate risks that could come from a service that may or may not be offered in Europe.” See also “Anthropic Briefs EU Regulators on Mythos Cybersecurity Concerns,” PYMNTS, April 17, 2026, citing Agence France-Presse coverage of the same briefing.

On April 15, 2026, Jensen Huang sat down with Dwarkesh Patel for what was meant to be a measured defense of Nvidia’s competitive position [1]. Nvidia had just closed fiscal 2026 with $215.9 billion in revenue, $193.7 billion in data center, and a full-year GAAP gross margin of 71.1% [2]. The brief was clear: acknowledge the alternatives, reassert the moat, reassure the analysts. Asked why Anthropic had committed to multi-gigawatt deployments on Google TPU and Broadcom-designed silicon in October 2025 [3] — when Nvidia’s own benchmarks claim the best price-performance in the market — Jensen reached for the simplest possible denial.

“Anthropic is a unique instance, not a trend,” he said [1]. Then, warming to the argument, he went further. Without Anthropic, he asked, why would there be any TPU growth at all? Why would there be any Trainium growth at all? One hundred percent Anthropic, in both cases. One customer.

Jensen was speaking in the context of external, third-party commercial demand — the only demand that tells you whether hyperscaler custom silicon has broken out of single-company use. Google’s internal TPU footprint (Search, Ads, YouTube, Gemini serving) dwarfs any outside customer and was never in question. The concession that matters is that outside Google’s and AWS’s own walls, TPU and Trainium growth as training platforms is one lab.

The quote was meant to shrink the alt-silicon story. It succeeded in shrinking it so completely that it confirmed the single-customer concentration the “everyone’s a chip company” narrative was designed to obscure. Two of the most-hyped custom silicon programs in the industry are, by the CEO of the market leader’s own admission, dependent on a single AI lab. If that lab changes its capital structure, slows down, or rebalances its next generation toward Nvidia, external TPU, and external Trainium revenue go with it. The CEO of the market leader said this out loud, on the record, twice across two segments of the same interview. A careful communicator could argue this was deliberate narrative-setting rather than Streisand — Jensen is meticulous, and the framing locks in a clean “second trend starting” storyline if a second lab emerges. Either read sharpens the point. Deliberate or accidental, the concession is that alt-silicon growth is a capital-structure phenomenon concentrated in one customer, not a technology wave.

The piece that follows takes Jensen seriously on the concentration, and then asks the question he did not want to be asked. If alt-silicon growth is one customer, what produced that customer? And what conditions would produce the next one?

The engineering is real. The question is what it replaces.

The press cycle around custom AI silicon has been continuous since late 2025. Meta is shipping multiple MTIA generations at scale for ranking and is now deploying them for some generative-AI inference [4]. Microsoft rolled Maia 200 into production Azure clusters through the winter [5]. Anthropic’s engineers are writing low-level kernels that interface directly with AWS Trainium and contributing to the Neuron stack [6]. OpenAI’s Broadcom-designed accelerator has been taped out and is scheduled for deployment at 10 gigawatts starting in 2026 [7]. Tesla taped out its AI5 chip on April 15 and announced AI6 and Dojo 3 are in development [8]. Broadcom closed Q1 FY2026 with $8.4 billion in AI revenue, up 106% YoY, and disclosed a $73 billion AI backlog [9]. Google’s Gemini 3, launched November 18, 2025, was trained on Google’s TPUs per Google’s public framing and Jeff Dean’s November 22 Stanford presentation; Google has not published a granular silicon-mix disclosure [10].

These are not press releases. They are real engineering, at real silicon teams, shipping on real timelines. Dismissing them is a mistake. So is assuming they substitute for what came before.

The market has been pricing the second possibility. Nvidia stock fell roughly 12% across November 2025, with a single-day drawdown of as much as 7% intraday on November 25 that wiped out roughly $250 billion in market cap, triggered by The Information’s report that Meta was evaluating TPU deployment from 2027, compounding the Gemini 3 launch a week earlier [11]. The sell-side was not unified: Bernstein’s Stacy Rasgon, Melius’s Ben Reitzes, and Evercore’s Mark Lipacis each published notes acknowledging additivity at the megawatt layer while flagging concentration and pull-forward risk. The bearish version the drawdown priced in more aggressively than any published note: Broadcom’s $73 billion AI backlog — disclosed December 11, 2025 as spanning “over the next six quarters” and flagged by Hock Tan as “a minimum” [9] — as the counterweight to Nvidia’s $95.2 billion in purchase and capacity commitments in the FY2026 10-K [12]. The implicit trade is that custom silicon is substituting for Nvidia at the hyperscaler level, and Nvidia’s growth has to slow.

The deployment data says otherwise. On February 24, 2026, Meta announced a multi-year, multi-generation Instinct agreement with AMD for 6 gigawatts of GPUs, with the first 1-gigawatt tranche on MI450 and subsequent tranches spanning future Instinct generations — at a press-estimated $60 billion or so over five years (AMD has not disclosed a dollar value; CFO Jean Hu described it as “double-digit billions per gigawatt”) and a performance-based warrant granting Meta up to 160 million AMD shares, gated on three concurrent conditions (GPU shipment milestones, AMD share-price thresholds with the final tranche at $600, and Meta technical and commercial milestones), worth roughly 10% AMD equity at full vesting [13].

One week earlier, Meta signed a separate multi-year commitment with Nvidia for millions of GPUs [14]. Meta’s forward 2026 capex guidance is $115 to $135 billion, up from $72 billion in actuals in 2025 [15]. Both bets grow simultaneously.

Microsoft’s Q2 FY2026 capex came in at $37.5 billion — a quarterly record. Two-thirds went to GPUs and CPUs, according to Amy Hood [16]. Microsoft is deploying Maia 200 in production while buying Nvidia at a pace that would have been unthinkable eighteen months ago.

Nvidia itself grew fiscal 2026 data center revenue 68% year over year to $193.7 billion [2]. Its forward supply commitments grew faster: from $16.1 billion at the prior year-end to $95.2 billion at the close of FY2026 — roughly 5.9x, or nearly nine times the revenue growth rate [12]. That gap is itself interpretable. Read charitably, it reflects Nvidia pre-booking TSMC CoWoS-L capacity for H2 2026 Vera Rubin deliveries and HBM4 supply through 2027. Read skeptically, it is pull-forward that has to be digested if AI capex growth decelerates before commitments convert to shipments. Either read is compatible with the additive thesis; neither vindicates it automatically.

This is the core fact the market is misreading, and the argument this piece is built around. Custom silicon is real. It is not displacing Nvidia. It is being added on top of Nvidia purchases, at every hyperscaler except one. That distinction — between substitution and addition — determines whether Nvidia’s concentration risk is easing or about to break. Additive custom silicon leaves Nvidia growth intact as the AI workload itself grows faster than custom silicon can absorb. Substitutive custom silicon caps Nvidia growth even as the workload grows. Right now, the data is almost entirely additive. Call this the Additive-vs-Substitutive Test — the first filter every hyperscaler silicon announcement should pass through, answered every ninety days by the quarterly capex breakouts. So far, with one exception, the answer is addition. And Jensen’s Dwarkesh admission, read carefully, explains why.

Two refinements sharpen the picture. First, additive deployment depends on workload growth outrunning custom silicon’s absorption rate — a bet on the AI capex supercycle continuing. If frontier training hits a scaling plateau in 2027 and AI capex growth drops from roughly 50% to 15% year over year, the same custom silicon plans that are additive today become substitutive tomorrow — same MTIA, same Maia, same Trainium2, cutting into an Nvidia share that can no longer grow its way around them. The additive story is growth-rate-dependent, not baked into the architecture.

Second, additive in megawatts is not additive in Nvidia’s revenue pool. Much of what hyperscalers spend on Broadcom XPU alongside Blackwell is spending Nvidia would otherwise have captured, though a portion of custom silicon demand — Meta’s ad-ranking workloads in particular — was never competitive for Nvidia anyway. Broadcom’s consolidated gross margin ran at 77% in Q1 FY2026, but full AI rack systems — where Broadcom resells the expensive HBM memory, substrates, and advanced packaging it buys from third-party suppliers rather than earning its usual margin on chip design alone — carry materially lower margins. CFO Kirsten Spears guided on the December 11, 2025, Q4 FY2025 call to roughly 100 basis points of sequential gross-margin compression entering Q1 FY2026 as rack-scale mix grew; on the March 4 Q1 call, she softened it, telling analysts the impact “is actually not going to be substantial at all.” UBS’s Timothy Arcuri pressed Hock Tan on that same Q1 call, framing rack-scale margins at “maybe 45%, 50%”; Tan rejected the framing, telling Arcuri he “must be a bit hallucinating” [9].

Nvidia’s data center segment carries a materially higher gross-margin structure than a pass-through-heavy XPU system [2]. Compute deployment can grow at every hyperscaler while Nvidia’s share of the capex dollar compresses, which is the scenario the market is actually pricing when it sells Nvidia on a Google announcement. Additivity in megawatts does not mean additivity in margin.

Google is the exception that proves the rule.

Google is that exception. Gemini 3 was trained entirely on TPUs, and this is load-bearing not because the chips are better — Nvidia still insists it wins on price-performance, and the alt-silicon camp has not yet accepted Jensen’s public invitation to publish comparative results on MLPerf or InferenceMAX [1]. It is load-bearing because Google has had a decade to do so. The first TPU was deployed internally in 2015. Ten years of hardware generations, the XLA compiler, and JAX. Gemini 3 was not the moment Google pivoted away from Nvidia. It was the moment the public caught up to a migration that had already been completed within the company, long before the model launched.

No other hyperscaler has a decade. AWS announced Trainium in 2020 and shipped its first Trn1 instances in October 2022. Microsoft began talking about Athena, the project that became Maia, in 2022. Meta’s MTIA program began serious deployment in 2023, and its first use of generative AI training is only now starting [4]. All of these programs are four years old or less. Google’s is ten. The gap is not technical genius; it is that Google built the software stack before anyone else thought they needed to, and had the internal workload volume to justify hardware iteration when no one else would have seen the return.

The Google exception matters because it sets the bar for what “full-stack silicon exit” actually requires: a decade of compounding software investment, a vertically integrated model organization that designs training code against the hardware rather than PyTorch-on-CUDA defaults, and the balance sheet to absorb the opportunity cost of running below Nvidia performance during the transition. That is a short list. It contains exactly one company. Everyone else operates inside a different constraint. Why a partial exit happened at all is a different question, and the answer flips from engineering to finance.

Why there is only one Anthropic.

Which brings us back to Jensen’s concession. If TPU and Trainium external growth is one customer, why that customer? The answer is not that Anthropic found Trainium and TPU to be objectively better chips than Blackwell. The answer, as Jensen himself explained in the next breath on the Dwarkesh podcast, is capital structure.

Jensen’s account is worth reconstructing because it is the most candid public explanation by a Nvidia executive of how the alt-silicon market was created. By his telling, Anthropic in its early growth phase needed five to ten billion dollars of equity investment to fund its compute consumption — a scale no venture capital firm would commit to an unprofitable AI lab. Google could write that check. Amazon could write that check. Nvidia, at the time, could not. Nvidia had never done large equity investments and had not internalized that the labs’ capital structure was inseparable from their silicon choice. By the time Nvidia understood this, Anthropic had already signed the equity-for-compute deals that locked its training on TPU and, later, on Trainium. Jensen described this as his miss [1].

The implication is the thesis of the piece. Anthropic’s silicon path was not decided by chip quality. It was decided by who could write the equity-for-compute check at the moment the check was needed. The alt-silicon market was not a technology event. It was a capital-structure event — the Capital-Structure-Not-Chip-Quality Mechanism, the second framework the reader can take away. Large labs needing billions in equity against compute consumption do not evaluate silicon options on FLOPs per dollar. They evaluate which counterparty can fund them for the next 18 months, and they accept whatever silicon comes with it.

Read through this lens, Jensen’s “unique instance” line flips meaning. Anthropic is not unique because its leadership preferred exotic silicon. Anthropic is unique because its capital needs and timing lined up with a hyperscaler that had both the chips and the checkbook. OpenAI went the other way — taking Microsoft’s capital, contingent on Azure compute, which at the time was overwhelmingly Nvidia. Azure’s own alt-silicon program (Athena, later Maia) had been in development since 2022 but was not production-ready for frontier training at the decisive capital moments. Compounding the capital path, OpenAI’s training stack had co-evolved with Nvidia from GPT-2 onward: CUDA kernels, Nvidia-native distributed training, and inference tuned to Nvidia's topology. Anthropic, founded in 2021 with a clean start, had no comparable stack to port. The result: OpenAI trained on Nvidia, and its aggregate compute posture, as Jensen conceded, remains vastly Nvidia-weighted even with the AMD MI450 deal of October 2025 and Broadcom-designed custom silicon now in production [7][14].

The forward-looking question is: who is the next Anthropic? Not in the sense of capability, but in the sense of the capital-structure setup — a lab needing five to ten billion in equity for compute, arriving at a moment when a non-Nvidia hyperscaler can write the check and Nvidia cannot. The answer, increasingly, is: nobody, because the arbitrage is closing on both sides.

It is closing from Nvidia’s side because Nvidia is now writing those checks itself. The $30 billion equity stake Nvidia finalized in OpenAI as part of that company’s $110 billion round earlier in 2026 — a scaled-back structure that succeeded the “up to $100 billion” infrastructure letter of intent Nvidia signaled in September 2025 — and the up-to-$10 billion Anthropic stake announced November 18, 2025 alongside Microsoft’s own up-to-$5 billion commitment and a $30 billion Anthropic-Azure compute deal [17] are the mechanism’s correction. Jensen told the Morgan Stanley Technology, Media & Telecom Conference on March 4, 2026, that both investments are likely Nvidia’s last before those companies go public, and returned to the theme on Dwarkesh a month later [17].

The arbitrage is also closing from the other side — not because Google and Amazon stopped writing compute-linked equity checks, but because the number of counterparties willing to write them proliferated. Microsoft’s commercial RPO backlog reached $625 billion by year-end 2025, with approximately 45% tied to OpenAI per analyst estimates (Microsoft has not broken this out) [16]. Oracle took its slice through Stargate. Google continues writing checks to Anthropic, linked to the TPU [3]. The arbitrage is no longer a narrow window between Nvidia’s old reluctance and its new willingness. It is a multi-counterparty equity-for-compute market that any sufficiently capital-hungry frontier lab can draw against, with silicon attached to whichever counterparty wins the allocation. The next Anthropic does not need to exist as a single, uniquely situated actor, because the arrangement that created the first one has become the default funding model. And labs that draw against this market are multi-sourced from day one — training on TPU, inferring on Trainium, committing to Nvidia for next-generation capacity. That spreads silicon share across vendors; it does not concentrate it on any single alt-silicon platform.

This is why “Anthropic is not a trend” may well be right, but not for the reason Jensen intended. The concentration is not concentrating further because labs with Anthropic’s capital profile are now routinely multi-sourced — a training cluster on TPU, an inference posture on Trainium, a compute commitment on Nvidia, every vendor paid. Whether Anthropic itself rebalances back toward Nvidia in its next generation — the company has simultaneously committed to multi-gigawatt Grace Blackwell and Vera Rubin deployments alongside its Trainium and TPU expansions [17] — will determine whether the “one customer” even stays at one in the way Jensen meant.

What is actually being deployed.

With that frame in place, the deployment picture becomes legible. Each hyperscaler silicon program deserves a clean, honest reading, because press coverage has systematically blurred the distinction between inference and training, between announced and shipped products, and between generative-AI workloads and older recommendation workloads that happen to use the same silicon family.

Meta’s MTIA program is the most mature of the non-Google efforts, with four generations shipped and hundreds of thousands of units deployed for ads ranking and feed personalization. MTIA is not yet the primary training platform for Meta’s frontier generative models — that remains Nvidia and increasingly AMD MI450-class silicon under the 6-gigawatt February agreement [13]. Meta’s own engineers describe MTIA as a ranking workhorse progressing toward generative-AI inference. Meta formalized this trajectory on April 14, 2026 — one day before Jensen recorded with Dwarkesh — announcing an expanded Broadcom partnership through 2029 covering multiple MTIA generations, with a 1-gigawatt commitment Meta described as the opening installment of a multi-gigawatt buildout, and with MTIA — per Broadcom’s announcement — becoming the first AI silicon on a 2nm process [4]. All of that capacity sits inside Meta’s 2026 capex envelope alongside, not in place of, the continued Nvidia commitments and the 6-gigawatt AMD Instinct deployment. Calling Meta a chip company is accurate. Calling Meta’s chip program a substitute for its Nvidia and AMD commitments misreads the capex guide: $115 to $135 billion in 2026, with growth across both custom and merchant silicon [15].

Microsoft’s Maia 200 entered production Azure clusters through the winter, in the US Central region, supplying only a fraction of Azure’s AI capacity. The deployment-level truth of the Microsoft bet is the $37.5 billion quarterly capex figure, two-thirds of which is allocated to GPU and CPU, disclosed on the Q2 FY2026 earnings call [16]. Satya Nadella disclosed on that same call that Microsoft added nearly one gigawatt of AI capacity in the quarter. Almost all of that gigawatt is not Maia.

AWS Trainium is the alt-silicon platform with the deepest model-level co-design story. Anthropic’s engineers are explicitly contributing to the Neuron software stack and writing kernels that interface directly with Trainium silicon [6]. Project Rainier — the 500,000-chip Trainium2 cluster in New Carlisle, Indiana — was activated in October 2025 and, per AWS CEO Matt Garman at launch, is running and training Anthropic’s models today. AWS is committed to doubling it to one million Trainium2 chips by the end of 2025 [18]. This is the strongest non-Google case for model-platform convergence on non-Nvidia silicon. It is also, per Jensen’s admission, the entire external Trainium adoption story.

OpenAI’s custom silicon program with Broadcom, announced October 2025 as a term sheet for 10 gigawatts starting in 2026, is the largest single non-Nvidia commitment by any AI lab — though Hock Tan on the Q1 FY2026 call specified OpenAI contributions of only “over 1 gigawatt” in 2027, back-weighting the remaining nine gigawatts into 2028 and 2029 [7]. OpenAI is also the anchor customer for a 6-gigawatt multi-generation AMD Instinct deployment announced on October 6, 2025 (the first gigawatt on MI450, with future generations to follow) [19], and the counterparty to Nvidia’s $30 billion equity investment, accompanied by a Grace Blackwell/Vera Rubin compute commitment [17]. Aggregating publicly announced OpenAI compute commitments across counterparties — Microsoft Azure, Oracle’s Stargate arrangement, AMD, Broadcom, and Nvidia — produces a disclosed sum somewhere in the $800 billion to $1.2 trillion range over 2025–2035, depending on how much weight the reader gives Stargate’s $500 billion headline (aspirational: Musk has publicly disputed its funding and SoftBank’s underwriting remains uncertain) [20]. Even discounting Stargate entirely, the aggregate is well north of half a trillion dollars. Every major vendor is represented. Nvidia remains the largest line item. This is additivity on an Olympian scale.

Tesla’s AI5 tape-out on April 15, 2026 is a dual-purpose chip Musk has positioned for both Optimus inference and data-center training — in his own words, “AI5, AI6 and subsequent chips will be excellent for inference and at least pretty good for training,” with Dojo’s training mission persisting “in the form of a large number of AI6 SoCs on a single board” [8]. It is not a pure FSD accelerator, but it is also not yet shipping at scale or training any xAI frontier model. xAI’s actual frontier training cluster, Colossus 2, is Nvidia-based: approximately 555,000 Nvidia GPUs across H100, H200, and Blackwell generations at the Memphis complex, with Musk targeting 1.5 gigawatts by April 2026 (independent satellite-based observers have flagged delivered capacity as materially below the stated target) [21]. The company most stylistically associated with the “build our own chips” narrative is, at the frontier training layer today, entirely Nvidia.

Pulling these five programs together, the pattern is consistent. Real engineering. Real silicon. Narrow deployments relative to the overall AI capacity being stood up. Additive to Nvidia, not substitutive. The Google exception is not evidence the pattern is changing; it is evidence of what it takes to be the exception, and no other hyperscaler has the ingredients.

The deployment picture explains where we are. The real question is: where are we going?

The lock-in is migrating up the stack.

The silicon story does not end here. The deeper argument — the one Jensen made on the same Dwarkesh podcast, in a completely different context, without noticing what he was conceding — is that the competitive battleground is moving from the kernel layer to the model architecture layer.

For most of 2023 and 2024, the dominant framing of Nvidia’s moat was CUDA. The argument ran: even if competitors build comparable silicon, the CUDA ecosystem, with its libraries, kernels, compiler toolchain, and fifteen years of accumulated developer familiarity, is what keeps frontier labs on Nvidia hardware. Switching costs were described at the level of writing new attention kernels, porting custom CUDA extensions, and rewriting inference serving infrastructure.

This argument has become progressively less true. OpenAI wrote Triton to abstract kernel generation across backends; Triton’s backend, per Jensen’s own description, contains substantial Nvidia-contributed technology, and it is also the path through which OpenAI compiles for non-Nvidia targets [1]. Anthropic writes kernels directly to Trainium with AWS's help and feeds architectural input into Trainium3 [6]. Google’s JAX and XLA stack is co-designed primarily against TPU. The hyperscaler labs have staff who can write low-level kernel code for multiple silicon targets, and the institutional capacity to do it. Jensen acknowledged this on Dwarkesh: Nvidia’s kernel engineers are deeply embedded inside their AI lab partners’ stacks, and “It’s not unusual that by the time we’re done optimizing their stack or optimizing a particular kernel, their model sped up by 3x, 2x, 50%” [1]. That is a description of a joint engineering relationship, not a lock-in through opacity. An Nvidia reading would note that the embedding itself is the moat — the density of engineering relationships does not require CUDA exclusivity to function. Both readings are defensible. What is not defensible is the 2023-era claim that CUDA kernels themselves are the primary barrier. The CUDA kernel moat is real but smaller than it was.

The real moat is now forming at the model architecture layer, and the evidence comes from the places the industry pretends not to see. In August 2025, DeepSeek released V3.1 with a numerical format alignment called UE8M0 FP8, co-designed with forthcoming Chinese domestic silicon. In a top-pinned comment on its official WeChat account, DeepSeek clarified that UE8M0 FP8 is, in the company’s own words, “designed for the next generation of domestically produced chips to be released soon” [22]. A frontier Chinese lab is designing its model’s numerical representation around a specific upcoming domestic silicon architecture. The model is being co-designed with the hardware. The portability story — train on Nvidia, serve on anything — does not hold at this level of precision co-design.

The DeepSeek case is not isolated. Gemini 3 is co-designed with TPU’s interchip interconnect topology. Anthropic is not just writing kernels for Trainium; it is feeding architectural requirements into Trainium3 [6]. Each case is a model whose training path is tuned to the primitives of a specific hardware family.

The industry tried to standardize low-precision formats in 2023 under the Open Compute Project’s Microscaling (MX) specification, published September 2023, with scale-factor formats including UE8M0 — the unsigned 8-bit power-of-2 scale DeepSeek referenced. That effort partially worked and partially fragmented. Both Nvidia’s Blackwell and forthcoming Chinese domestic accelerators implement MX-compatible FP8. But the model-layer decision of which MX variant to tune to, and which hardware’s tensor-core quirks to target, still produces silicon-specific optimization paths that do not port cleanly. Nvidia’s NVFP4 on Blackwell, the MX-standard MXFP4 across AMD and Intel, and DeepSeek’s explicit alignment of UE8M0 scale factors to upcoming Chinese domestic silicon are three model-layer decisions that each lock trained weights to a specific silicon family [22].

This is the Model-Layer Lock-In Migration, the third framework the reader can take away. The moat is moving from the kernel up. A model trained with UE8M0 quantization on Ascend-class silicon does not run day one at equivalent quality on Blackwell. A model trained with sparse MoE routing optimized for TPU’s 3D torus does not run day one on an Nvidia NVL72 optimized for NVLink Switch. Silicon-specific optimizations creep up the stack, out of the kernel, into the model itself. Switching cost is no longer kernel rewrite time. It is a training run costing hundreds of millions of dollars and months at the frontier scale.

This has a consequence that CUDA lock-in never had. CUDA had a switching-cost moat at the ecosystem and habit levels. Painful to switch away from, but in principle reproducible — build enough libraries, fund enough kernel ports, give it a decade, and a competitor could assemble a comparable stack. That is roughly what Triton, XLA, and the Neuron SDK are doing. The CUDA moat is not disappearing, but it is being incrementally eroded by compiler-layer investment, and Jensen knows it. It is why he spent a third of the Dwarkesh interview repositioning Nvidia’s advantage as the density of engineering relationships inside the AI lab partners’ stacks rather than the kernel ecosystem itself [1].

Model-layer co-design is a different kind of moat. It does not sit in a rebuildable library. It sits inside trained weights that cost nine-figure sums to reproduce. A lab that trains its next-generation model natively against TPU topology, or against Trainium’s interconnect, or against a Chinese domestic chip’s UE8M0 scale format, has embedded the silicon dependency into the model artifact itself. The switching cost is not “rewrite your kernels”; it is “rerun your training”—a cost that cannot be amortized by compiler work, only paid by running the training again on different silicon for another hundred-million-plus and three-to-six months. Compiler abstraction — the Triton and MLIR lineage — can bridge kernel-level differences. It cannot undo the numerical format in which a model was trained, or the routing topology against which its experts were tuned. The moat is moving to the layer where abstraction cannot reach.

The most striking evidence is not from Anthropic or DeepSeek. It is from Jensen. On the same podcast, arguing for why Nvidia should be allowed to keep selling compute to Chinese customers despite U.S. export controls, he made an almost startling case: if Chinese open-weight models end up optimized for Huawei’s silicon architecture rather than Nvidia’s, that would be a real strategic loss, because those models would then diffuse to markets outside China and establish Huawei as the reference platform [1]. This is the model-silicon co-design argument, as this piece frames it, stated exactly by the CEO who stands to lose the most from it. Jensen sees it happening. He is warning about it, out loud, against himself, because he sees it happening to him too.

What would have to break.

Every thesis has to be falsifiable to be useful. This one has four specific tests to watch through 2026 and 2027.

The first test is the additive vs. substitutive test applied to quarterly capex breakouts. As long as Meta, Microsoft, AWS, and Google all continue to grow both their custom silicon deployments and their Nvidia purchases in parallel, the additive story holds. If any single hyperscaler reports a quarterly capex breakout showing custom silicon growth and a simultaneous absolute reduction in Nvidia purchases — not slower growth, but a cut — the picture changes. Nothing in the data through Q1 2026 suggests this is imminent.

The second test is whether any frontier lab outside Google publishes a training run conducted entirely on non-Nvidia silicon, at a scale and benchmark level comparable to Gemini 3 or the current Claude generation. Anthropic is the candidate most likely to clear this bar, given the kernel-level Trainium work now in production at Project Rainier [18]. Reuters reported April 9, 2026, that Anthropic is exploring the design of its own silicon alongside its Trainium, TPU, and Nvidia commitments — active but early, with no specific design or dedicated chip team publicly committed [18]. Pre-committed threshold: if Anthropic’s next flagship Claude model, shipping in 2026 or 2027, is disclosed as trained majority or entirely on Trainium, on TPU, or on a hybrid Trainium-TPU configuration with no Nvidia in the loop, the “one customer is all there is” thesis weakens. If that model also runs day one with equivalent quality on Nvidia inference fleets, the model-layer lock-in thesis weakens with it.

The third test is whether NVLink Fusion — Nvidia’s initiative to allow its interconnect to integrate with non-Nvidia accelerators, including AWS’s forthcoming Trainium4 [23] — actually ships on schedule. If it does, the re-coupling of AWS to Nvidia at the networking layer is explicit, and the partial alt-silicon exit becomes narrower than the commitments suggest. If it fails to ship or ships with technical constraints, AWS’s alt-silicon story becomes more independent than it currently appears.

The fourth test is the portability bar at the model layer. If an open-source frontier model ships with documented day-one parity across five or more silicon backends — Nvidia, Google TPU, AWS Trainium, AMD Instinct, and a Chinese domestic target — the model-layer lock-in migration is arrested. This has not yet happened at frontier quality. The trajectory, per the DeepSeek UE8M0 example, is in the opposite direction.

If all four tests resolve the way they have so far, the picture is stable. Nvidia remains the dominant silicon vendor in a market growing faster than any custom silicon program can absorb. Broadcom captures the non-Nvidia design-house layer, with a $73 billion AI backlog — disclosed on the December 11, 2025 Q4 FY2025 call as spanning “over the next six quarters” and flagged by Hock Tan as “a minimum” — concentrated across six XPU customer relationships, four publicly named (Google, Meta, Anthropic, OpenAI) and two unnamed, with one widely reported by analysts to be ByteDance [9]. Tan’s stated line of sight to chip revenue “significantly in excess of $100 billion” in 2027 frames the forward opportunity, though Tan was explicit that the figure is chips-only and excludes rack and system revenue [9]. TSMC’s CoWoS-L packaging capacity for leading-edge AI silicon, alongside HBM4 supply from Micron, SK hynix, and Samsung, together form the binding constraint at the manufacturing layer — and the primary reason every player’s announced timelines slip six to twelve months relative to their press releases. Google remains the one full-stack exception. Anthropic remains the one candidate to cross over. Everyone else runs Nvidia as the first-class platform and accumulates custom silicon as an additive hedge.

The two-layer story is this. Near term, over the next three to five years: deployment is Nvidia-plus-custom, with “plus” being the operative word. Longer term, five to ten years: the model-layer lock-in migration is the real battleground. Models are being co-designed with specific silicon in ways that make training runs non-portable, and the vendor that captures the largest installed base of frontier models co-designed for its silicon inherits the switching costs of the CUDA used to carry them. Today, that is still Nvidia, by a wide margin. Tomorrow, it is a contest between Nvidia’s NVFP4, Google’s TPU-native training paths, AWS’s Trainium-Anthropic co-design, and China’s UE8M0-plus-Huawei combination — the model layer fragmenting along silicon-specific lines faster than the silicon itself diversifies at the chip layer.

The concentration Jensen described on April 15 was real. The reassurance he tried to offer was not. And the part of the moat he spent a decade building at the CUDA kernel layer is not the part that will decide the next cycle, because the lock-in is moving to where the trained weights are.

Notes

[1] Dwarkesh Patel, “Jensen Huang – TPU competition, why we should sell chips to China, & Nvidia’s supply chain moat,” Dwarkesh Podcast, April 15, 2026. All Jensen Huang statements cited in this piece are drawn from this transcript and the associated video/audio.

[2] NVIDIA Corporation, Form 10-K for fiscal year ended January 25, 2026, SEC filing; see also Q4 FY2026 CFO commentary, February 2026. Revenue of $215.9B, data center revenue $193.7B, Q4 GAAP gross margin 75.0%, full-year 71.1%, operating cash flow $102.7B, free cash flow $96.6B, $4.5B charge in Q1 FY26 for H20 excess inventory following April 2025 U.S. export license requirements.

[3] Anthropic, “Expanding our use of Google Cloud TPUs and Services,” corporate blog post, October 23, 2025; Anthropic, “Expanding our partnership with Google and Broadcom,” corporate blog post, April 7, 2026; Broadcom Q4 FY2025 earnings disclosure of $11 billion additional Anthropic custom silicon order following $10 billion earlier in FY2025. The October 2025 commitment spans up to one million TPUs, bringing over a gigawatt of compute capacity online in 2026; the April 2026 expansion adds 3.5 gigawatts of next-generation TPU capacity routed via Broadcom, coming online from 2027.

[4] Meta Platforms corporate engineering blog, MTIA deployment updates through 2025; Meta, “Meta Partners With Broadcom to Co-Develop Custom AI Silicon,” April 14, 2026. MTIA v1 was announced in 2023; v2 entered broad ranking deployment in 2024; v3 and v4 extended capabilities through 2025. MTIA 300, announced March 2026, is already running Meta’s ranking and recommendation workloads, with the remaining chips in the new four-chip family slated through 2027. Training for Llama frontier models remains primarily on Nvidia and, under the February 24, 2026 agreement, on AMD Instinct (MI450 first gigawatt, future generations following). The April 14 expansion commits to more than 1 gigawatt of MTIA compute as the opening installment of a multi-gigawatt buildout through 2029, with Hock Tan stepping off Meta’s board into an advisory role focused on the custom silicon roadmap. Broadcom’s accompanying press release characterized MTIA as the “industry’s first 2nm AI compute accelerator” — an attribution to Broadcom’s own marketing, not independent verification.

[5] Microsoft Azure blog and press releases on Maia 200 deployment, January 2026. Initial production clusters in US Central Azure region.

[6] Anthropic, “Powering the next generation of AI development with AWS,” corporate blog post, November 22, 2024; AWS re:Invent 2024 keynote by Matt Garman; Project Rainier activation coverage, October 29, 2025. Anthropic’s own published description: “we’re writing low-level kernels that allow us to directly interface with the Trainium silicon, and contributing to the AWS Neuron software stack to strengthen Trainium. Our engineers work closely with Annapurna’s chip design team to extract maximum computational efficiency from the hardware.”

[7] OpenAI and Broadcom, “OpenAI and Broadcom announce strategic collaboration to deploy 10 gigawatts of OpenAI-designed AI accelerators,” co-announcement, October 13, 2025; Broadcom Q1 FY2026 earnings call, March 4, 2026, confirming OpenAI as sixth XPU customer with deployment beginning H2 2026 and targeted completion by end of 2029. Only a term sheet was signed at announcement, not a binding purchase order. On the Q1 FY26 call, Hock Tan specified OpenAI’s 2027 contribution at “>1 gigawatt,” effectively back-weighting the bulk of the 10-gigawatt commitment into 2028 and 2029.

[8] Electrek, “Tesla taped out AI5 chip, Musk says — nearly 2 years behind schedule,” April 15, 2026; Tom’s Hardware, “Elon Musk demonstrates first sample of Tesla AI5 processor,” April 15, 2026; Musk public statements on X, August 8 and August 10, 2025, including “AI5, AI6 and subsequent chips will be excellent for inference and at least pretty good for training” and “Dojo 3 arguably lives on in the form of a large number of AI6 SoCs on a single board.” AI5 is positioned for Optimus inference and for Tesla data-center clusters as Dojo’s training-mission successor, manufactured split between TSMC Arizona and Samsung Taylor, Texas, with mass production expected late 2026 to 2027. AI5 is not currently training any xAI frontier model; xAI’s Colossus 2 remains Nvidia-based.

[9] Broadcom Q4 FY2025 earnings call, December 11, 2025 (source for $73 billion AI backlog figure, which Hock Tan characterized as spanning “over the next six quarters” and flagged as “a minimum”); Broadcom Q1 FY2026 earnings release and conference call, March 4, 2026; Futurum Group, “Broadcom Q1 FY 2026 Earnings Driven by XPU Momentum,” March 5, 2026. Q1 FY26 AI revenue $8.4B (+106% YoY); Q2 guidance $10.7B (+140% YoY). Hock Tan on Q1 FY26 call stated line of sight to chip revenue “significantly in excess of $100 billion” in 2027, and was explicit that the figure is chips-only (XPUs, switch chips, DSPs) and excludes rack and system revenue. Six XPU customer relationships disclosed, four publicly named by Broadcom (Google TPU, Meta, Anthropic, OpenAI) and two unnamed; one of the unnamed customers is widely reported by sell-side analysts (Cantor Fitzgerald, CNBC-cited analysts, The Information) to be ByteDance — an analyst attribution, not a Broadcom confirmation. On gross margin: Q1 FY26 consolidated non-GAAP gross margin was 77%; CFO Kirsten Spears on the December 11, 2025 Q4 FY25 call guided to approximately 100 basis points of sequential compression entering Q1 FY26, tied to the higher mix of AI system-level sales that include third-party pass-through costs. On the March 4, 2026 Q1 FY26 call, Spears softened the framing, telling analysts “the impact relative to our overall mix is actually not going to be substantial at all.” UBS analyst Timothy Arcuri pressed Hock Tan on that same Q1 FY26 call, framing rack-scale gross margins at “maybe 45%, 50%” and asking whether blended margin could drop 500 basis points as racks scale. Tan rejected the framing, telling Arcuri he “must be a bit hallucinating.”

[10] Gemini 3 launched November 18, 2025, announced by Jeff Dean, chief scientist at Google DeepMind and Google Research, on X and in Google’s official product blog. Dean’s subsequent Stanford University presentation on November 22, 2025 framed Gemini 3 as the culmination of Google’s decade-long TPU program, with training path disclosed publicly as TPU-based. Google has not published a granular silicon-mix model card disclosure, so “trained on TPUs” is based on Google’s public framing and Dean’s presentation rather than on a formal quantitative disclosure. On-premises Gemini 2.5 deployments via Google Distributed Cloud do run on Nvidia Blackwell; the TPU training claim applies to the primary cloud training and serving path, not to all Gemini deployments.

[11] Coverage of Nvidia’s November 2025 drawdown: Fortune, “Markets wipe $250 billion off Nvidia as they digest Google’s revenge,” November 25, 2025; CNBC, “Nvidia stock falls 4% on report Meta will use Google AI chips,” November 25, 2025. Nvidia stock fell approximately 12% across November 2025, with a single-day decline on November 25 that ranged from 4% (close) to 7% (intraday low), wiping out approximately $250 billion in market capitalization. The primary catalyst for the November 25 move was The Information’s report that Meta was evaluating TPU deployment from 2027, compounding Gemini 3’s launch on November 18. Nvidia publicly defended its position, asserting “greater performance, versatility, and fungibility than ASICs.”

[12] NVIDIA Corporation Form 10-K, fiscal year 2026, SEC filing. Direct language from the filing: “the Company’s consolidated outstanding inventory purchase and long-term supply and capacity obligations balance was $95.2 billion.” Prior-year balance was $16.1 billion, implying approximately 5.9x year-over-year increase. The 10-K notes a significant portion of this balance relates to inventory purchase obligations.

[13] AMD, “AMD and Meta Announce Expanded Strategic Partnership to Deploy 6 Gigawatts of AMD GPUs,” February 24, 2026 press release; AMD Q4 2025 earnings call with CEO Lisa Su and CFO Jean Hu; Markets Daily coverage of the warrant and GPU plan, February 27, 2026. Five-year agreement for up to 6 gigawatts of AMD Instinct GPUs across multiple generations: first 1-gigawatt tranche built on MI450 architecture, subsequent tranches spanning future Instinct generations. AMD did not disclose a dollar value; CFO Jean Hu described economics as “double-digit billions per gigawatt.” The $60 billion over five years figure is a press and analyst estimate (AP, Deseret News) rather than an AMD-disclosed number. Performance-based warrant grants Meta up to 160 million AMD shares, vesting gated on three concurrent conditions: GPU shipment milestones, AMD share-price thresholds (with the final tranche at $600), and Meta technical and commercial milestones. Full vesting corresponds to roughly 10% AMD equity.

[14] Reporting on Meta’s February 2026 multi-year agreement with Nvidia preceding the AMD announcement; see synthesis in humai.blog, “Meta Is Buying Millions of Nvidia Chips,” March 9, 2026. Meta described the two deals as a supplier diversification strategy rather than substitution.

[15] Meta Platforms Q4 2025 earnings call, late January 2026; DataCenterDynamics, “Meta estimates 2026 capex to be between $115-135bn,” March 11, 2026. 2025 capex $72.2 billion; 2026 guidance $115-135 billion. Meta also established a new Meta Compute division in early 2026 to consolidate AI data center operations.

[16] Microsoft, FY26 Second Quarter Earnings Conference Call transcript, Microsoft Investor Relations; CNBC, “Microsoft (MSFT) Q2 earnings report 2026,” January 28, 2026. Amy Hood on the call: capital expenditures $37.5 billion, roughly two-thirds on short-lived assets primarily GPUs and CPUs. Satya Nadella confirmed nearly one gigawatt of total capacity added in the quarter. RPO of $625 billion, up 110% YoY. The ~45% tied to OpenAI is a sell-side analyst attribution rather than a Microsoft disclosure; Microsoft has not broken out OpenAI’s share of its commercial RPO.

[17] CNBC, “Nvidia CEO Huang says $30 billion OpenAI investment ‘might be the last,’” March 4, 2026 (Morgan Stanley Technology, Media & Telecom Conference). The “might be the last” characterization of the OpenAI and Anthropic investments was made at Morgan Stanley TMT on March 4, 2026; Jensen returned to the same theme on the Dwarkesh podcast on April 15, 2026. The $30 billion Nvidia equity stake in OpenAI is part of OpenAI’s $110 billion round, finalized in early 2026 — a restructuring of the earlier September 2025 “up to $100 billion” Nvidia-OpenAI infrastructure letter of intent. On the November 2025 Anthropic transaction: per Microsoft’s official announcement and Anthropic’s corresponding blog post, “Microsoft, NVIDIA and Anthropic announce strategic partnerships,” November 18, 2025, Nvidia committed to invest up to $10 billion in Anthropic, while Microsoft committed to invest up to $5 billion. Anthropic simultaneously committed to $30 billion in Azure compute over time and a multi-gigawatt Nvidia Grace Blackwell / Vera Rubin commitment.

[18] AWS press and Matt Garman, Project Rainier launch coverage, October 29, 2025; AWS Indiana data center in New Carlisle, running approximately 500,000 Trainium2 chips at launch, with AWS’s stated target of doubling to one million Trainium2 chips by end of 2025 (independent confirmation of the end-of-2025 target achievement is not publicly available). Garman at launch described the cluster as running and training Anthropic’s models. Total Amazon stake in Anthropic reached $8 billion prior to the November 2025 Azure transaction. On the Anthropic-own-silicon exploration: Reuters exclusive by Cherney & Seetharaman published April 9, 2026 and widely republished through April 10; see Silicon Republic summary, “Anthropic reportedly mulls designing own chips amid shortage,”. The reporting cites three sources and frames the effort as early-stage, with no publicly committed design or dedicated chip team, occurring alongside Anthropic’s existing multibillion-dollar compute commitments with Nvidia, AWS, Google, and Microsoft.

[19] AMD and OpenAI, “AMD and OpenAI Announce Strategic Partnership to Deploy 6 Gigawatts of AMD GPUs,” corporate press release, October 6, 2025. First 1-gigawatt deployment on MI450 architecture; subsequent tranches span future AMD Instinct generations. Equity warrant structure parallel to the Meta deal (up to 160 million shares, milestone-gated on shipment, AMD share-price thresholds, and OpenAI technical milestones).

[20] Author aggregation of publicly announced OpenAI compute commitments across counterparties, per company disclosures and financial press coverage, late 2025 through early 2026. Components include: Microsoft ($250 billion multi-year Azure compute commitment, confirmed via Microsoft’s October 28, 2025 OpenAI recapitalization disclosure); Oracle OCI via the SoftBank-led Stargate infrastructure initiative (announced aspirational scale of $500 billion — Musk has publicly disputed the funding, SoftBank’s underwriting remains uncertain, and Oracle’s contract scope has been reported at closer to $300 billion over five years); AMD (press-estimated $60 billion over 6 gigawatts of multi-generation Instinct GPUs per the October 6, 2025 strategic partnership [19]); Broadcom (custom silicon over 10 gigawatts, commitment value not separately disclosed); and Nvidia (Grace Blackwell / Vera Rubin compute commitment accompanying the $30 billion equity investment [17], successor to the September 2025 “up to $100 billion” infrastructure LOI); AWS ($38 billion over seven years, announced November 3, 2025). Figures reflect announced commitments at varying degrees of bindingness, not disbursed spending. The defensible aggregate range is $800 billion to $1.2 trillion across 2025-2035, depending on how much weight the reader assigns to Stargate’s aspirational $500 billion headline. The “over a trillion dollars” figure is an author calculation from these components, not a single officially reported number, and includes the full Stargate headline value.

[21] xAI Memphis complex reporting, Q1 2026; Musk public statements on X, January 17, 2026 and April 15, 2026; Tom’s Hardware and Epoch AI satellite-imagery analysis of delivered capacity, January–February 2026. The Memphis complex (Colossus 1 + Colossus 2 + the MACROHARDRR building purchased December 30, 2025) collectively houses approximately 555,000 Nvidia GPUs spanning H100, H200, and Blackwell generations — not a single homogeneous Blackwell cluster. Musk’s stated target for 1.5-gigawatt capacity by April 2026 (per January 17 X post) is a target, not independently verified; satellite-based analyses through early 2026 estimated delivered cooling capacity materially below 1 gigawatt. Dojo (custom D-series training chip) was wound down August 2025 (Bloomberg, August 7; Musk confirmation, August 10, 2025); the training mission persists via AI5/AI6-based board clusters per Musk’s own framing.

[22] DeepSeek official WeChat account, top-pinned comment accompanying V3.1 release, August 21, 2025; CNBC, “DeepSeek hints latest model will be compatible with China’s ‘next generation’ homegrown AI chips,” August 22, 2025; South China Morning Post, “DeepSeek hints China close to unveiling home-grown next-generation AI chips,” August 21, 2025. DeepSeek’s own statement, in translated form: “UE8M0 FP8 is designed for the next generation of domestically produced chips to be released soon.” DeepSeek did not name the chip vendor. Technical precision: UE8M0 is the unsigned 8-bit power-of-2 scale-factor format defined within the Open Compute Project’s Microscaling (MX) specification v1.0, published September 2023 — not a Chinese-invented format. Element types in MXFP8 are E4M3 or E5M2; UE8M0 is the shared per-block scale. Nvidia Blackwell also natively supports MXFP8 with E8M0 scales. DeepSeek’s alignment is therefore of its model’s scale-factor behavior to the forthcoming Chinese domestic silicon (reportedly Moore Threads MUSA 3.1 and VeriSilicon VIP9000 in some variants) that implements MXFP8 — a model-layer co-design decision, not the invention of a new numerical format. The V3.1 technical paper states the model was trained “using the UE8M0 FP8 scale data format to ensure compatibility with microscaling data formats.” Separately, FT and Reuters reported (August 13–14, 2025) that DeepSeek attempted to train its R2 model on Huawei Ascend accelerators in mid-2025 but reverted to Nvidia H20 after encountering training-stability issues.

[23] NVIDIA developer communications and industry coverage of NVLink Fusion integration with AWS Trainium4, disclosed in late 2025 around AWS re:Invent. Architectural integration is described at the fabric layer, allowing NVLink-compatible interconnect to integrate with non-Nvidia accelerators. Specific keynote venue and shipping date subject to verification against primary AWS and Nvidia disclosures.