Why is cooling an architecture choice?
Cooling is not the equipment you add after compute. It sets rack density, site design, maintenance model, and the kinds of chips the building can host.
Cooling becomes binding when the site can buy chips and power but cannot remove heat at the density the roadmap requires.
Every watt becomes heat
Almost all electricity consumed by a data center eventually becomes heat. The compute layer turns power into answers, then the facility has to move the heat somewhere else.
That makes thermal design a first-order constraint. If heat removal fails, utilization fails.
Air gives way to liquid at high density
Air cooling is simple and serviceable, but it struggles as rack density rises. Direct-to-chip liquid cooling moves heat through cold plates and coolant loops before it spreads through the room.
Immersion and other liquid approaches can support still higher densities, but they change service workflows, vendor choices, and building design.
Water, climate, and permitting enter the stack
Cooling ties AI infrastructure to local climate, water availability, environmental permits, and public tolerance. A site that works thermally in one region may be politically or physically hard in another.
This is why data-center geography is not only about cheap power. It is also about where heat can be rejected reliably.
Thermals shape chip choice
A hotter accelerator may be worth it if the rack and facility are built for it. The same chip can be a bad fit in a legacy building with lower density assumptions.
The buyer is not choosing a chip in isolation. The buyer is choosing a chip plus a cooling architecture plus an operating model.
The durable edge is thermal headroom
Sites with liquid-ready distribution, serviceable rack layouts, and room for denser future systems can absorb new chip generations faster.
That headroom is a strategic asset because the hardware clock is faster than the building clock.