Anthropic commits $11.6B to Akamai's distributed cloud for CPU workloads
A seven-year contract for dedicated capacity on Akamai Cloud, expandable to about $20 billion. The 8-K adds outage exits, a $1.7 billion memory buy, and a warrant that vests with each new $3 billion of spend.
The press release names CPU workloads, not GPUs. The 8-K lets Anthropic exit any work order after a major outage.
Akamai filed an 8-K on September 24, 2026 saying Anthropic has committed to pay it about $11.6 billion for dedicated cloud computing capacity over seven years. Akamai's press release says the capacity will support Anthropic's "accelerating CPU workload demands" on Akamai Cloud's distributed infrastructure. The contracts were signed on September 18.
The deal can grow by up to $9 billion more, which Akamai rounds to a potential total of about $20 billion. The filing places the new commitments under a master services agreement dated May 5, 2026, as two work orders it calls Project Plan 2 and Project Plan 3. Each has its own seven-year term. SiliconANGLE, citing Bloomberg, says Anthropic was the unnamed frontier model company behind a $1.8 billion Akamai commitment disclosed in May.
Core to edge, on CPUs
The press release describes Akamai Cloud as "a continuum of compute from core to edge" on a network spanning thousands of points of presence, built with diversified hardware. The workload it names is CPU work. Neither "GPU" nor "inference" appears anywhere in the release or the 8-K.
Neither document says which Anthropic workloads will run there, which regions or sites get the capacity, or how many machines are involved. TechNode Global notes that no Asia-Pacific allocation was announced, and that the companies did not say whether Akamai replaces other suppliers or runs alongside them. None of the coverage we read quotes Anthropic.
Exits for outages and takeovers
Two terms in the 8-K cover outages and a change of control. Anthropic may terminate each project plan "upon notice of a material outage, subject to certain conditions." It may end the whole agreement if control of Akamai passes to a direct competitor. And if the master agreement ends over a breach, any project plan not involved in that breach keeps running as a separate contract.
Akamai also has to build this. It estimates about $5.5 billion of capital spending for the initial commitment, plus about $1.7 billion more in 2026 to pre-purchase parts, including memory. The same filing shows it authorizing Jabil, which manufactures its custom servers, to buy about $1.7 billion of memory components and hold them on consignment. Akamai says its 2026 revenue guidance does not change.
Warrants that grow with committed capacity
Akamai also issued Anthropic non-voting warrants worth up to about 5% of its stock, with the exercise price payable in cash. About 2% vests on Anthropic's first payment under Project Plan 3, and the rest vests in three steps as Anthropic commits each further $3.0 billion, according to the 8-K.
Akamai shares rose 22% in extended trading on September 24, Reuters reported. This follows Anthropic's $10 billion Volta deal and Broadcom's chip debt talks, which we covered in August.
Why a build studio cares
Our read, not anything either company has said: the model runs on GPUs, but much of what an AI product does around each inference call is ordinary CPU work. Tool calls, code sandboxes, page fetches and agent loops all run there, and they slow down the further they sit from the user or the service they touch. A GPU contract does not cover any of it. The part we would copy is in the contract, not the capacity. Anthropic wrote an outage exit into every work order and a takeover exit into the master agreement, and kept the work orders independent of each other. When we run a Surface Audit, domain and hosting control are already on the checklist, and a written exit from the hosting vendor belongs right next to them. We build with Claude and have no financial stake in Anthropic or Akamai.
Next step: read Item 1.01 of Akamai's 8-K for the termination and warrant terms in full. If your product depends on one hosting vendor with no written exit, write to us at hello@gattyworks.com.