← ALL INSIGHTS
INSIGHT · 4 MIN READ

The Invisible Hero of the AI Boom: How Closed-Loop Liquid Cooling is Saving the Data Center.

data center

Once upon a time, in the vast, quiet landscapes of the American Midwest, the digital world lived a relatively peaceful existence. Inside massive, warehouse-like structures, rows upon rows of servers hummed harmoniously, working around the clock to serve up your favorite creator’s latest Instagram reel or that heartwarming post on Facebook. Every day, these traditional data centers relied on a simple, trusty friend to keep them comfortable: air. Large, industrial fans would breathe cool air over the server racks, maintaining a perfect equilibrium. It was an era of predictable temperatures and steady, reliable compute power.

But one day, the artificial intelligence revolution arrived.

The demands of the digital world shifted overnight. Suddenly, we weren’t just asking our computers to retrieve photos; we were asking them to think, generate, reason, and create. To achieve this, the hardware—specifically the GPUs—became astonishingly powerful. But with this incredible new power came a fiery byproduct: immense, relentless heat. The harder these AI models worked, the more the hardware sweat. And at a certain point, the trusty old method of simply blowing more air through a server rack stopped being an efficient—or even possible—method of cooling.

Because of that, the brightest engineering minds had to completely rethink the anatomy of the data center. Because of that, they realized that to support the future of artificial intelligence, they had to reinvent the plumbing. Until finally, a harmonious, sustainable ecosystem was born—one where closed-loop liquid cooling and artificial intelligence itself joined forces to keep the internet running without melting down.

This is the story of how the physical infrastructure behind the AI boom is quietly saving the day.

The Heat is On: The Limitations of Air Cooling Data Centers

To understand the magnitude of this engineering challenge, we have to look at where we started. Not too long ago, using traditional air cooling methods to keep AI hardware from overheating was an achievable, everyday solution.

When I visited a data center in Altoona, Iowa, I witnessed this legacy firsthand. There, racks of powerful Nvidia H100s were kept perfectly chilled entirely through air cooling, with incredibly minimal water usage. In this specific facility, small amounts of water were only used at the very beginning of the data center cooling process. During the warmer Midwestern months, water was used to pre-cool the incoming air, but a drop of water was never sent directly to the computing hardware itself.

It was an elegant solution for its time. But as we transition deeper into the AI era, newer, denser, and exponentially more powerful AI hardware designs have created an unavoidable thermal bottleneck. The physics of air simply cannot carry away the heat fast enough. If you try to cool today’s most advanced servers with air, you reach diminishing returns rapidly. You would need nearly double the size of the server tray just to fit the required air cooling fans and heat sinks. You’d be building bigger and bigger trays, taking up massive amounts of real estate, just to house the exact same compute capacity.

The industry needed a hero. And when I visited Meta’s AI Infrastructure facility in Texas, I found out that the most fascinating technology inside the building wasn’t actually the multi-million dollar AI chips. It was the intricate, highly engineered plumbing.

Enter the Hero: Closed-Loop Liquid Cooling for AI Servers

When we talk about the environmental impact of artificial intelligence, there is a very common, very pervasive misconception: that AI data centers are automatically massive, wasteful water hogs. The image that comes to mind is millions of gallons of fresh water being poured over servers and flushed down the drain.

The reality of sustainable AI infrastructure solutions depends entirely on the cooling design. And the hero of our story is a marvel of modern engineering called closed-loop liquid cooling.

The basic idea behind closed-loop liquid cooling is surprisingly simple, yet profoundly effective. Instead of blowing air, a specialized liquid coolant—a meticulously balanced mixture of water and glycol—is piped directly to the server hardware. This liquid passes over the chips, absorbing and moving the heat away from the server racks with incredible thermal efficiency. (Water, as it turns out, is vastly superior to air at absorbing

THE CONVICTION BRIEF

One brief like this, monthly.

Subscribe
FAQ

On modernizing CPG data

What does "data as a product, not a byproduct" actually mean?

It means each critical data domain gets a named owner accountable for its quality, availability, and adoption. A byproduct has no owner, no roadmap, and no service level; a product is measured by whether people use it. The shift is organizational before it is architectural.

Why start with the organization instead of the technology?

The three shifts in this piece are ownership, consumption, and governance — and none is primarily a technology decision. Companies that dominate with data made the decision before they drew the diagram. New tooling on top of unowned data just moves the same problem to a faster stack.

What's wrong with a 2015-era data stack?

Those stacks were optimized for storage and ingestion — getting data in and keeping it. Modern stacks optimize for the person pulling data out: the demand planner, the trade manager, the pricing agent. The stack that wins is the one the business actually pulls from, not the one that stores the most.

How is governance-as-enabler different from governance theater?

Governance that lives in review boards slows everything and protects little. Governance that lives in the platform — contracts, permissions, and quality gates enforced at the pipeline — speeds teams up and holds under audit. One is a meeting; the other is enforced by default.

Do we need to rebuild everything at once?

No. Start by assigning an owner to one critical domain and designing that domain for consumption, then move governance into the platform for it. The pattern is deliberate and incremental, which is why the leaders treat it as a series of shifts rather than a single migration.