What agreement did Anthropic and Akamai confirm?
Akamai announced a multiyear cloud infrastructure services agreement with Anthropic, with a contract value of $11.6 billion and a term of seven years. The company framed the commitment as a response to Anthropic’s growing demand. The figure and duration, therefore, are no longer based only on a leak or a report attributed to sources: they are part of Akamai’s announcement.
The headline figure needs an important qualification. The $11.6 billion describes the value of the commitment over the life of the contract; it is not a one-time payment, and it does not prove that all the capacity covered by the agreement is installed and available from the outset. The announcement also does not make clear, without further detail, how the amount is allocated across services, locations, or deployment phases.
Akamai said the infrastructure will support Anthropic workloads that use CPUs. That identifies a class of computing resources, but does not specify the systems’ configuration, how capacity will be allocated, or which particular tasks will run on it. It would therefore be premature to describe the contract as a precise quantity of accelerators or as capacity that is already operational, unless further information is published.
How does the earlier $1.8 billion figure fit in?
An earlier report attributed to Bloomberg and carried by MarketScreener described a cloud computing contract worth $1.8 billion. Akamai later announced a $11.6 billion commitment over seven years. These two figures should not be presented as contemporaneous estimates of the same scope: the available reports place them at different points in time, with the first appearing as a precursor to the expanded agreement.
Even so, the sources provided do not explain in enough detail whether the $1.8 billion contract was replaced, rolled into the newer commitment, formally expanded, or negotiated as a separate stage. The most defensible wording is that Bloomberg reported an earlier $1.8 billion agreement and Akamai subsequently announced a $11.6 billion commitment. There is no basis here for adding the two amounts together or claiming they are separate commitments.
There is also a difference in how headlines present the amount: Bloomberg Law headlined its report at $12 billion, while its text and other coverage refer to $11.6 billion. The $12 billion figure can be read as a rounded version of the reported value, but the precise amount supported by Akamai’s announcement is $11.6 billion.
What the published figures mean
| Published figure | What it supports | What it does not establish |
|---|---|---|
| $1.8 billion | Bloomberg reported an earlier cloud computing agreement. | That it is an additional amount on top of the later commitment. |
| $11.6 billion | Akamai announced this value for a seven-year multiyear agreement. | That all the spending has already occurred or all capacity is in service. |
| $12 billion | A rounded figure used in the Bloomberg Law headline. | That the precise contract value differs from the $11.6 billion announced by Akamai. |
Why does cloud capacity matter to Anthropic?
Artificial intelligence systems need infrastructure to be developed and run. As demand for a company’s products grows, it may need to expand its computing resources, contract for external services, or combine capacity from multiple sources. Akamai’s announcement confirms that Anthropic has committed to buying cloud services over the long term; it does not, on its own, reveal how that capacity fits into Anthropic’s overall mix of providers and facilities.
The explicit reference to CPU workloads matters because it avoids reducing all AI infrastructure to a single type of processor. However, the announcement does not specify which particular services will run on those resources. For example, it does not establish that the capacity will be used exclusively for inference, training, storage, or any specific application.
From a business perspective, a multiyear commitment can give the provider contractual visibility and reserve resources for the customer. That is a general interpretation of this kind of agreement, not a guarantee that capacity will be delivered by a particular date or a measure of its effect on model performance. To follow what happens next, it is important to distinguish between signing a contract, installing infrastructure, and bringing it into operation.
How to assess future updates
- 01Check whether the information comes from an official announcement or from a source attributing details to people familiar with the negotiations.
- 02Separate the total contract value from spending already made and from capacity currently available.
- 03Look for details about resources, services, locations, and deployment phases before attributing a specific workload to the infrastructure.
- 04Treat operating dates as unconfirmed unless the companies publish a verifiable schedule.
What is known about deployment, capacity, and timing?
The available information confirms the contract term and announced value, as well as the reference to CPU workloads. It does not provide a detailed schedule for bringing the capacity online, a technical measure of its scale, or a list of data centers that would show where the service will be provided. Nor does it say what share of the resources will be delivered in each year of the contract.
For that reason, the agreement should be understood as a commercial commitment for infrastructure, not as proof that all the capacity has already been built or connected. Long-term contracts can involve phased deployment, but there is not enough information here to describe the phases or to say that this is definitely how this particular agreement is structured.
The supplied sources also do not specify how operational responsibilities will be divided, what availability metrics will apply, or which conditions could change the contracted volume. These details may matter to customers and investors, but they should not be filled in with assumptions.
A possible equity stake is not the same as an automatic investment
Reuters reports republished by Investing.com and TradingView mention that Anthropic obtained an option related to a stake of up to 5% in Akamai. Akamai’s official announcement also includes a warrant. The existence of this instrument can be reported as part of the described terms, but it should not be interpreted as an acquisition that has already taken place.
An option or warrant confers a right subject to conditions; by itself, it does not mean that shares have been issued, that Anthropic has exercised the right, or that it currently owns the stake. The supplied sources do not provide the exercise conditions, price, timing, or other terms needed to assess the possible corporate impact. Without that information, any estimate of the stake’s value or the likelihood that it will be acquired would be speculative.
The relationship between the services contract and the equity instrument should also be described carefully. The available information presents them as elements of the agreement, but does not provide enough detail to conclude what the warrant would mean in specific scenarios or whether it is tied to particular milestones.
What can be concluded—and what remains open?
The firm conclusion is that Akamai announced a $11.6 billion, seven-year cloud services agreement with Anthropic, with CPU workloads among the stated uses. The earlier $1.8 billion figure was attributed to Bloomberg and should be retained as background reporting, not added to the later amount without evidence that the two are separate commitments.
The announcement represents a significant commitment to buy infrastructure, but it does not by itself show how much new capacity will be operational, when it will be available, or how it will be divided among Anthropic’s workloads. Nor does it establish that the agreement reduces reliance on any particular other provider, because the sources do not describe Anthropic’s infrastructure mix as a whole.
The deployment schedule, technical capacity and its distribution, the specific tasks that will use CPUs, and the precise contractual relationship between the initial figure and the expanded commitment remain unclear. As for the equity component, the existence of a warrant or option is not enough to say that an investment has been completed. Those are the distinctions between what is confirmed, what is attributed to media reports, and what is still unknown.
Open questions
- The schedule for installing the capacity or bringing it into operation is not specified.
- The sources do not quantify CPU resources or detail their distribution across data centers or deployment phases.
- It is not established whether the $1.8 billion agreement was replaced, expanded, incorporated into the $11.6 billion commitment, or is separate.
- The supplied material does not include all terms of the warrant or option, including the price, timing, and exercise conditions.
- The specific Anthropic workloads that will use the contracted infrastructure are not identified.
Keep exploring
Sources consulted
Corrections and transparency
If you spot incorrect or outdated information, send us a correction with the page and source we should review.
Submit a correction