LiquidStack 300 MW U.S. multi-site order

Project brief

What is publicly known

Status: deploying, based on a supplier-reported contract rather than observed installation. LiquidStack announced in January 2025 that an unnamed United States data center operator had ordered 300 megawatts of cooling capacity for several sites. The order uses repeated CDU-1MW units, each rated at one megawatt under set conditions.

A coolant distribution unit, or CDU, controls the clean server loop and moves its heat to facility water. LiquidStack calls the buyer a long-established operator that is adding sites for artificial intelligence. It also says it can make and ship the units on a fast schedule.

The claim is large, but the public proof is thin. The buyer has not named a site or confirmed the deal. There is no permit, ship date, delivery record, or public price that can be used to check it.

The cooling relevance lies in the scale and repeatable format. One-megawatt blocks point to standard direct-to-chip or hybrid pods rather than one custom plant. Yet 300 megawatts of unit nameplate is not always 300 megawatts of live computing load.

Spare units, backup design, water temperatures, and phased delivery can all reduce the load served at one time. Unknowns include the buyer, sites, unit count, price, dates, loop temperatures, backup plan, server type, and installed status. The label would be stronger if the buyer confirmed the order or if shipping and site work became public.

Named sites and unit records would let capacity be assigned to real projects. We would move a commissioned share to operating only after site evidence showed units carrying load. A cancelled order, a large cut in scope, or no sign of delivery would move the record back to planned.

The headline must not be treated as 300 operating megawatts.

Status is labeled from public evidence. Supplier orders, MoUs, pilots, projects under delivery, and operating sites are not counted as equivalent.