Liquid Cooling
Definition
Liquid cooling uses liquid-based systems, such as direct-to-chip cooling or immersion cooling, to remove heat from servers, GPUs, and accelerators. It is increasingly important for AI infrastructure because dense GPU clusters can exceed the practical limits of traditional air cooling.
Why it matters
Cooling capability can determine whether a data center is AI-ready. Liquid cooling can support higher rack density and better efficiency, but it introduces capex, maintenance complexity, retrofit risk, water or fluid management, and operational skill requirements. Investors should treat cooling design as a core underwriting variable, not a technical footnote.
Common misconceptions
- •Liquid cooling is not one technology; direct-to-chip and immersion systems have different economics and risks.
- •Liquid cooling does not eliminate power constraints.
- •A facility advertised as AI-ready may still require major cooling retrofits for next-generation GPUs.
- •A facility described as liquid-cooling ready may still lack sufficient piping, heat rejection, controls, maintenance procedures, or tenant-compatible hardware for production use.
Technical details
Common approaches
Direct-to-chip cooling moves liquid through cold plates attached to processors or accelerators. Immersion cooling submerges hardware in dielectric fluid.
Hybrid designs may combine air cooling for some components with liquid cooling for high-heat chips.
Economic impact
Liquid cooling can improve PUE and support higher density, potentially increasing revenue per square foot or per megawatt.
Offsetting costs include cooling distribution units, plumbing, facility retrofits, leak management, maintenance, and potential hardware compatibility limitations.
Diligence questions
Which cooling system is installed or planned, and what densities does it support?
Is the facility retrofitted or purpose-built for liquid cooling?
Who bears retrofit cost, downtime risk, and maintenance responsibility under tenant contracts?
Reliability and operations
Review redundancy, leak detection, water quality, pumps, coolant compatibility, service access, spare parts, and procedures for isolating failures without taking an entire cluster offline.
Allocate responsibility for loops, warranties, monitoring, maintenance, and damage among facility, operator, hardware vendor, and tenant.
Retrofit and capacity risk
Existing buildings may need structural, electrical, plumbing, controls, and heat-rejection upgrades before supporting dense liquid-cooled racks. Construction can displace revenue-producing capacity.
Underwrite commissioned density and include retrofit capex, downtime, and phased customer migration.
Capacity-to-revenue bridge
For Liquid Cooling, bridge physical capacity to billable revenue. Start with contracted or announced units, then deduct capacity not yet delivered, powered, cooled, networked, commissioned, accepted by customers, or available after redundancy and maintenance requirements.
Build a monthly schedule for installed capacity, usable capacity, committed capacity, billed capacity, and collected revenue. This prevents double-counting the same GPU, rack, or megawatt across marketing pipeline, financing collateral, and customer backlog.
Separate high-margin infrastructure revenue from pass-through power, setup fees, burst usage, credits, taxes, and reimbursed costs. Revenue quality depends on margin, duration, collectability, and renewal probability, not only gross contract value.
Contract and counterparty diligence
Review the exact contracting party, guarantor, minimum commitment, ramp schedule, delivery conditions, service levels, termination rights, cure periods, force majeure, assignment rights, deposits, and lender step-in rights.
Customer quality matters because AI demand can be volatile. Underwrite concentration, funding runway, payment history, use case, workload portability, and whether the customer can switch to hyperscalers or newer hardware.
Supplier diligence should cover title transfer, liens, serial-number evidence, warranty, replacement rights, export controls, delivery delay remedies, and whether a reseller actually controls the inventory it promises.
Operating constraints and cost stack
AI compute economics are constrained by power price, power availability, cooling design, rack density, network fabric, facility uptime, maintenance, software orchestration, spare parts, and labor. A GPU fleet can be technically installed but commercially weak if one of these constraints binds.
Stress power-price increases, curtailment, delayed interconnection, transformer lead times, cooling retrofits, customer credits, lower utilization, and hardware failures. Compare gross utilization with contribution margin after power and operating costs.
For financing, match customer contract tenor and hardware useful life to debt amortization. A long loan against short-lived or rapidly repricing hardware can leave residual-value risk with the lender or vehicle.
Refresh, residual value, and monitoring
Track hardware by cohort: model, purchase date, installed cost, memory profile, networking, warranty, utilization, average realized rate, power draw, and expected resale or redeployment value.
Monitor competitive GPU pricing, new chip launches, customer workload shifts, inference versus training mix, cloud spot pricing, and resale market depth. A unit that still functions can become economically stale before physical failure.
Warning signs include revenue booked before acceptance, unclear ownership of hardware, repeated delivery delays, rising service credits, power constraints, low realized utilization, customer nonpayment, and capex needs that are not reflected in the financing model.