A closed loop is not a water claim

In a technical drawing, closed-loop cooling looks like a complete answer.

A blue line carries cool liquid toward the computing equipment. It returns red after absorbing heat, passes through a heat exchanger, and begins the journey again. The fluid moves in a circle. Nothing appears to enter or leave.

That image is why “closed loop” has become shorthand for low-water or even waterless cooling.

But the drawing often stops before the water question does.

A closed loop describes what happens to the working fluid inside a defined circuit. It does not tell us how heat eventually leaves the data center, whether another part of the cooling system uses evaporation, or what happens outside the chosen boundary.

ASHRAE defines a closed system as one in which circulating water or brine is enclosed and shut off from the atmosphere, apart from a possible connection through an expansion or compression tank. The definition is about containment and circulation. It makes no claim about the environmental performance of everything connected to the circuit.

The fluid is enclosed. The heat is not.

Heat enters the loop at the servers and has to cross its boundary somewhere else. What happens at that point determines far more about water use than the shape of the pipework. Following the complete heat path makes that boundary visible.

One loop can sit inside another

Modern data-center cooling rarely consists of one circuit performing the entire job.

Consider a server cooled directly at the processor. A metal cold plate sits on a CPU or GPU. Coolant flows through channels inside the plate, absorbs heat, and carries it away. ASHRAE’s explanation of liquid-cooling cold plates shows why flow, temperature, pressure, material compatibility, and cleanliness all have to be managed carefully.

That first circuit may run between the servers and a coolant distribution unit. At the unit, heat passes through another exchanger into a facility-side loop. The two liquids may never mix. One serves the computing equipment; the other transports heat through the building or toward outdoor equipment.

The facility loop still has to do something with the energy it received. It may carry heat to a dry cooler, pass it into a refrigeration system, connect to an evaporative cooling tower, or transfer it into another building or industrial process.

Several of those systems can contain closed loops at rack or facility level. Their demands on local water resources can still be radically different.

The phrase therefore needs a second question attached: which loop is closed?

The same loop can have three different endings

The heat can end in outdoor air

In one design, a closed liquid loop carries heat from the data center to a dry cooler.

Fans move outside air across coils containing the warm liquid. Heat crosses the coil wall and enters the air, while the liquid remains inside the pipes and returns to the facility. The process resembles a car radiator on a much larger scale.

Because final heat rejection does not depend on evaporation, the system does not require continual replacement of water lost to the atmosphere. The loop still has to be filled, monitored, protected against corrosion and freezing where necessary, and maintained. Fans and pumps still use electricity, and compressors may be needed if outdoor conditions cannot maintain the required temperature.

ASHRAE’s AI cooling guidance notes that warmer liquid loops can support dry heat rejection in many climates. Extreme heat can change what the system requires.

The heat can end in evaporation

Now take the same closed server loop and connect it, through heat exchangers, to a cooling-tower system.

The liquid still returns to the processors. The rack-level loop remains closed. Farther along the chain, another circuit carries heat to a cooling tower. Some of its water evaporates. More leaves as blowdown to prevent minerals from becoming too concentrated. Fresh makeup water replaces those losses.

The U.S. Department of Energy traces this full path from IT equipment through water circuits to a tower where evaporation releases heat to the atmosphere.

The tower itself recirculates water, but recirculation does not prevent consumption. The word “closed” applied to one circuit. The water consumption occurred beyond it.

The heat can end with another user

A third system transfers heat out of the data center and into something that needs it.

Warm liquid may supply an exchanger connected to a district-heating network, greenhouse, building, hot-water system, or industrial process. Instead of rejecting all the heat outdoors, the data center makes some of it available to another load.

But heat recovery is not a permanent exit unless demand is permanent too. A greenhouse may need less heat in summer. A district network has seasonal demand. An industrial process may stop for maintenance. The data center still produces heat whenever its equipment runs.

A complete design therefore needs another route for the hours when the heat user cannot accept the full output. Cooling reliability must remain intact during failures, maintenance, and changes in demand.

These three endings can use similar language at the beginning. Each may contain a closed circuit carrying heat away from computing equipment. The final heat sink changes the water, energy, equipment, and operating story.

Closed does not mean untouched

A closed loop is not normally emptied and refilled as part of every cooling cycle. That does not mean the fluid remains untouched for the life of the data center.

The circuit must be charged during installation. Water or another coolant may need treatment to control corrosion, biological growth, scaling, material degradation, or freezing. Pressure, flow, temperature, chemistry, and leak detection have to be monitored.

A loop may be drained during repair or component replacement. Small losses may have to be replaced. A leak can turn an expectedly minor makeup requirement into a significant one until it is found.

This does not make a closed system equivalent to an evaporative tower. The scale and purpose of the water input are different. But “the water circulates” should not be translated into “the facility will never require water.”

There is another boundary outside the cooling plant. Electricity generation can carry its own water footprint. Manufacturing servers, pumps, heat exchangers, and pipes also requires resources. A facility may have low direct freshwater consumption and still have water-related effects elsewhere.

The main water article examines those direct and indirect boundaries, while the lifecycle article extends the frame to construction, hardware production, replacement, and end of life.

The meter should count what crosses the boundary

Imagine 10,000 liters circulating through a cooling loop.

The pump may move that inventory around the system many times in one day. The water has been used repeatedly as a heat-transfer medium, but the facility has not necessarily consumed another 10,000 liters each time it completes the circuit.

Gross circulation is therefore a poor measure of water demand. What matters for the site is what crosses the boundary: how much freshwater enters, how much returns, how much is discharged, how much evaporates, and how much new water normal operation requires.

Water Usage Effectiveness tries to make one part of this relationship comparable by dividing annual site water use by the energy consumed by IT equipment. The WUE article examines the formula and its limits.

Even then, withdrawal and consumption cannot be treated as synonyms. Water taken from a supply and returned to the same local system creates a different condition from water evaporated into the atmosphere. Initial fill and routine makeup are also different operating events.

In its proposed 2026 data-center rating methodology, the European Commission distinguishes freshwater input from return flows in closed and semi-closed cooling-water systems. The accounting rule reflects a physical truth: water inside a pipe is not necessarily water being consumed.

The efficiency trade-off remains

Avoiding evaporation can reduce direct freshwater consumption. It can also change energy use.

Evaporative cooling works well because the phase change from liquid to vapor carries away a large amount of heat. Under suitable conditions, it can reject heat using less electricity than a fully dry system.

Dry heat rejection avoids that continual evaporative loss, but high outdoor temperatures can reduce its effectiveness. Larger exchangers, faster fans, higher coolant temperatures, mechanical refrigeration, or a hybrid mode may be needed.

A facility may achieve a lower PUE partly through a system that consumes more water. Another may accept higher cooling-energy demand to reduce direct water use. PUE does not settle that trade-off.

Closed-loop cooling does not remove the exchange. It can create more options for managing it. A well-designed liquid loop can move heat efficiently at higher temperatures, making dry cooling or heat recovery practical for more hours of the year. The right arrangement depends on climate, workload density, power, water, space, and reliability.

Ask where the heat leaves the loop

For a buyer, operator, or local authority, “Is the cooling closed loop?” is not enough.

Ask which circuit is being described, where it transfers heat, whether any downstream system uses evaporation, how much freshwater enters during normal and hot-weather operation, what water is needed for filling and maintenance, and where heat goes when no other user can accept it.

Those questions reveal the pumps, fans, heat exchangers, cooling towers, dry coolers, water connections, and customer-side systems a deployment may need. They expose dependencies that otherwise appear after the site has already been chosen. Cooling therefore belongs inside site selection, not in a specification exercise completed afterward.

Policloud develops physical, modular data-center infrastructure for defined sites. Cooling and water claims have to remain attached to the relevant configuration and complete thermal path.

A modular unit may arrive with much of its cooling infrastructure integrated. Thermodynamically, it remains connected to everything around it.

The loop can be contained. Its consequences cannot.

Closed-loop cooling tells us that a fluid comes back. To understand the water impact, we still need to ask where the heat went.