Akamai’s Anthropic Deal Turns on Annual Revenue, Not Hype

Akamai’s new Anthropic contract is large enough to change the company’s revenue mix, but the useful number is not the headline commitment. It is $1.66 billion a year, calculated as $11.6 billion of contracted value / 7 years = $1.66 billion per year. That annual run rate compares with Akamai’s latest annual revenue of $4.208 billion, which the annual filing breaks into $2.243 billion of security revenue + $1.257 billion of delivery revenue + $0.708 billion of cloud computing revenue = $4.208 billion. On that base, the Anthropic contract equals $1.66 billion / $4.208 billion = 39.4% of one recent year’s companywide revenue. That is why the story matters for stocks: it is not a routine AI press release; it is a contract big enough to test whether Akamai can turn infrastructure demand into durable cash flow.

Context

Akamai disclosed that Anthropic committed approximately $11.6 billion under project plans tied to dedicated cloud computing capacity and managed support services. The company also said the arrangement runs for 7 years, so the simple annualized commitment is $11.6 billion / 7 years = $1.66 billion. Reuters reported that Akamai shares rallied after the deal and noted the embedded warrant that could give Anthropic up to 5% of Akamai, calculated by the company as 7.7 million common-equivalent shares / roughly 154 million implied shares outstanding = 5.0%.

The market reaction is understandable, but it should be separated from the economics. Akamai is trying to move from its older delivery-network identity toward a mix led by security and cloud infrastructure. The June-quarter filing showed cloud infrastructure services revenue of $99.319 million for the quarter. Annualizing that quarter gives $99.319 million * 4 = $397.276 million. The Anthropic annualized commitment of $1.66 billion is therefore $1.66 billion / $397.276 million = 4.2 times that annualized quarterly cloud infrastructure services base. Against the full-year cloud infrastructure services figure in the annual report, the contrast is larger: $1.66 billion / $313.9 million = 5.3 times.

The analysis

The first layer of the math is scale. A $1.66 billion annualized contract, calculated as $11.6 billion / 7 years = $1.66 billion, would be material even for a much larger software infrastructure company. For Akamai, the denominator is modest: latest annual revenue was $4.208 billion, calculated in the filing as $2.243 billion security + $1.257 billion delivery + $0.708 billion cloud computing = $4.208 billion. The contract’s annualized value is therefore $1.66 billion / $4.208 billion = 39.4% of that revenue base.

The second layer is capital intensity. Akamai estimated total capital expenditures related to the $11.6 billion commitment at about $5.5 billion. The implied capex load is $5.5 billion / $11.6 billion = 47.4% of contracted value. The pre-operating-cost gap is $11.6 billion - $5.5 billion = $6.1 billion, or $6.1 billion / $11.6 billion = 52.6% of contracted value. That remaining 52.6% is not profit. It still has to absorb power, co-location, depreciation timing, support costs, financing costs, and any service-level penalties or inefficiencies. The deal can be economically attractive, but the arithmetic says it is an infrastructure build, not asset-light software.

The timing also matters. Akamai said the 2026 capital expenditure increase tied to the commitment is about $1.7 billion. That is $1.7 billion / $5.5 billion = 30.9% of the expected project capex front-loaded into 2026. The company reported cash, cash equivalents, and marketable securities of $4.616 billion at the end of the June quarter; the near-term project capex equals $1.7 billion / $4.616 billion = 36.8% of that liquidity figure. Akamai also reported $7.640 billion of convertible senior notes outstanding, so notes to cash and securities were $7.640 billion / $4.616 billion = 1.65 times. That does not make the balance sheet fragile by itself, but it makes execution discipline more important.

The warrant is the third layer. Akamai said Anthropic received a warrant for up to 7.7 million common-equivalent shares, or about 5% of shares outstanding. That implies a share base of 7.7 million / 5.0% = 154 million shares. The portion expected to vest with the current commitment is 3.1 million shares, which equals 3.1 million / 154 million = 2.0% of that implied share base. The exercise price is $111.33 per common-equivalent share, so full exercise proceeds would be $111.33 * 7.7 million shares = $857.2 million. Initial expected vesting would represent $111.33 * 3.1 million shares = $345.1 million of exercise value. This structure gives the customer upside if the relationship expands, while shareholders absorb potential dilution if the commercial milestones are met.

The optional expansion is meaningful but should be treated as optional. Akamai said the relationship could expand by up to an additional $9 billion. Adding the pieces gives $11.6 billion + $9.0 billion = $20.6 billion of potential commitment, which the company described as approximately $20 billion. Annualized over the same 7-year framework, that would be $20.6 billion / 7 years = $2.94 billion per year. But the difference between committed and potential is the whole point: $9.0 billion / $20.6 billion = 43.7% of the maximum package is not yet the same as the disclosed contractual commitment.

Risks and counterpoints

The risk is that the contract proves less profitable, less timely, or less durable than the headline suggests. The assumption that carries the thesis is that Akamai can convert $11.6 billion / 7 years = $1.66 billion per year into attractive cash flow after spending $5.5 billion / $11.6 billion = 47.4% of the commitment on capex. If that assumption breaks, the conclusion breaks with it.

The main operating risk is delivery. The SEC filing says the commitments are subject to delivery and service availability requirements, so revenue visibility is tied to performance, not just signing. The second risk is customer concentration. One contract annualized at $1.66 billion equals $1.66 billion / $4.208 billion = 39.4% of recent annual revenue, so a delay, renegotiation, outage, or strategic shift by Anthropic would matter. The third risk is cost inflation. If memory, servers, power, or co-location costs rise above the planned $5.5 billion capex envelope, the capex ratio moves above $5.5 billion / $11.6 billion = 47.4%, and the cash-flow case weakens.

The counterpoint is that Akamai is not starting from zero. It already reported $99.319 million of cloud infrastructure services revenue in the June quarter, equal to $99.319 million * 4 = $397.276 million annualized, and it had already disclosed more than $2.8 billion of multi-year cloud infrastructure services commitments. Adding Anthropic gives $2.8 billion + $11.6 billion = $14.4 billion of disclosed cloud infrastructure commitments across customers. That reduces, but does not remove, the risk that this is one customer driving the story.

What to do with it

The useful approach is to track conversion, not chase the announcement. The watch items are straightforward: recognized revenue versus the $1.66 billion annualized commitment, capex versus the $5.5 billion estimate, liquidity versus the $1.7 billion near-term capex increase, and dilution versus the 3.1 million initially vesting shares. Each update can be checked against the same arithmetic.

This is not a buy-or-sell signal. It is a change in the analytical frame. Akamai now has a contract whose annualized value equals $1.66 billion / $4.208 billion = 39.4% of recent annual revenue, but it also has a buildout whose capex equals $5.5 billion / $11.6 billion = 47.4% of the contract. The equity thesis turns on whether the company can make that spread real in cash, on time, without letting one AI customer become the entire story.

Sources

• Akamai Form 8-K on Anthropic agreement
• Akamai press release on $11.6 billion Anthropic agreement
• Akamai Q2 2026 Form 10-Q
• Akamai 2025 Form 10-K
• Reuters via Schwab: Wall Street ends higher as investors buy AI stocks