Dow, one of the world’s largest materials science companies, has launched a liquid cooling support network for data centres, according to a report published by Data Centre Magazine on 18 May 2026. The reported launch positions Dow — a supplier of silicones, fluids, and specialty chemistries — as an organized participant in the fast-growing market for cooling the dense computing racks that power artificial intelligence.
Executive Summary
The announcement, as reported, is simple in outline: Dow is standing up a formal support network around liquid cooling for data centres. Support or partner networks in the materials world typically bundle products with validation, compatibility guidance, and access to a vetted ecosystem of collaborators — though the source report does not detail which of these Dow’s network includes.
Why it matters is larger than the announcement itself. Liquid cooling — circulating fluid to chips or immersing hardware in it, instead of relying on air — has moved from niche to necessity as AI servers pack more power into each rack than air can practically remove. When a company of Dow’s scale builds formal structure around that market, it signals that liquid cooling is graduating from a collection of point products into an industrial supply chain, with the materials layer — coolants, silicones, seals, thermal interfaces — treated as critical infrastructure rather than a commodity input.
Why a Chemicals Giant Is Organizing Around Server Cooling
Air cooling has a physics problem. Modern AI accelerators concentrate so much power in each rack that moving enough air through them becomes impractical, which is why the industry has shifted toward direct-to-chip liquid cooling (piping coolant across a cold plate mounted on the processor) and, in some deployments, immersion cooling (submerging entire servers in a non-conductive fluid). Every one of those approaches depends on chemistry: the coolant itself, plus the hoses, seals, gaskets, and thermal interface materials that keep fluid where it belongs for years at a time.
That is Dow’s home turf. Materials suppliers have historically sold into this market indirectly, through the vendors that build cooling hardware. A formal support network — if it follows the usual shape of such programs — moves the materials maker closer to the operators and equipment builders who actually deploy the technology, which matters because coolant compatibility failures (degraded tubing, fouled cold plates, additive breakdown) are among liquid cooling’s most feared operational risks.
Formalizing the Supply Chain Is the Real Story
The editorial significance here is less any single product and more the institutional signal. Liquid cooling’s early years were characterized by fragmented suppliers, proprietary fluids, and limited interoperability guidance. Buyers — hyperscale cloud providers, colocation operators, enterprises — have been pushing for validated, multi-vendor supply chains before committing facilities designed to run for decades. Ecosystem programs are how industrial suppliers answer that demand: they convert one-off product sales into standing relationships with documented compatibility.
Dow is not moving into an empty field. Fluid and chemistry players including Chemours, Shell, and Castrol have courted the data centre cooling market, while 3M’s announced exit from PFAS manufacturing by the end of 2025 removed a prominent supplier of certain engineered fluids and sharpened questions about fluid chemistry choices across the industry. Against that backdrop, a structured support offering from a major materials company is a bid for trust as much as for revenue: operators want assurance that the fluid in their loops will be supported, supplied, and compliant for the life of the facility.
What Buyers Should Watch For
For data centre operators and cooling equipment makers, the practical questions are concrete. Does the network provide compatibility validation across pumps, cold plates, and piping from multiple hardware vendors? Does it address regulatory exposure — notably the tightening scrutiny of per- and polyfluoroalkyl substances (PFAS) that affects some classes of engineered cooling fluids? And does it shorten the qualification cycle, which today can add months to a liquid cooling deployment?
The source report does not answer these questions, and it would be premature to credit the network with capabilities it has not publicly detailed. What can be said fairly is that the direction of travel — materials incumbents building formal, supported ecosystems around data centre liquid cooling — is exactly what a maturing market looks like, and buyers benefit when more credible suppliers compete to underwrite reliability.
Background
Dow traces its roots to 1897 and today ranks among the world’s largest materials science companies, supplying silicones, fluids, and specialty chemistries across dozens of industries. Its materials have long appeared inside electronics and thermal management applications, though typically sold through intermediaries rather than under a data centre-branded program.
The data centre cooling market has been reshaped by the AI build-out: rack power densities have climbed beyond what air cooling comfortably handles, pushing direct-to-chip and immersion cooling from experimental to mainstream. That shift has drawn fluid and chemistry suppliers — and their partner ecosystems — into a market once dominated by mechanical and HVAC vendors.
Iceotope, a UK-based data center cooling technology startup, has raised $26 million in new funding and says it intends to use the capital to scale, as reported by SiliconANGLE on May 14, 2026. The company specializes in liquid cooling — removing heat from servers with circulating fluid rather than fans and chilled air — a technology segment that has moved from niche to near-mandatory as AI computing hardware grows hotter and denser.
Executive Summary
The announcement itself is brief: a $26 million raise and a stated intent to scale. Investors, valuation, and use-of-proceeds details were not included in the source report. But the timing and the segment tell a larger story. Racks built for AI training and inference now routinely draw power densities that air cooling physically struggles to handle, and every serious data center operator is being forced to evaluate liquid cooling in some form.
For Iceotope, a longtime specialist in what it calls precision liquid cooling, fresh capital is a bet that the company can convert years of engineering work into deployments at the exact moment demand is inflecting. For the industry, it is one more data point that capital continues to flow toward the thermal side of the AI infrastructure buildout — not just chips and buildings, but the plumbing that keeps them running.
Why Investors Keep Funding the Thermal Layer
Cooling used to be a background line item in data center design. AI changed that. Modern accelerator-dense racks can draw many times the power of a traditional enterprise rack, and nearly all of that electricity becomes heat that must be removed. Air — the industry’s default coolant for decades — becomes impractical at these densities: you simply cannot move enough of it through a rack fast enough. Liquids carry heat far more efficiently, which is why liquid cooling has shifted from an exotic option to a planning assumption for new AI capacity.
A $26 million round is modest by AI-infrastructure standards, where individual data center campuses are financed in the billions. But it fits the pattern of the moment: investors funding the enabling-technology layer around the AI buildout, on the thesis that whoever wins the compute race, the cooling suppliers get paid. That thesis does not require picking a winning chipmaker or cloud — only believing that rack densities keep rising, which is currently one of the safer bets in the industry.
Where Iceotope Sits in a Crowded Field
Liquid cooling is not one technology but several. Direct-to-chip cooling pipes fluid through cold plates mounted on processors and has become the mainstream choice for hyperscale AI deployments. Immersion cooling submerges entire servers in dielectric (non-conductive) fluid. Iceotope’s approach — precision liquid cooling — delivers dielectric fluid to components inside a sealed chassis, aiming to capture most of immersion’s thermal benefits without the tanks and handling challenges of full immersion.
The competitive field is intense and getting more so. Large incumbents such as Vertiv and Schneider Electric have built out liquid cooling portfolios, cold-plate specialists serve the hyperscalers, and a cluster of venture-backed startups pursue immersion and chassis-level designs. Iceotope’s differentiation has historically rested on serviceability and suitability for edge and telecom environments as well as data halls — places where a sealed, self-contained cooling design matters. Whether that positioning wins share against the direct-to-chip mainstream is the central commercial question the company’s new capital must answer.
What $26 Million Buys — and What It Doesn’t
For a hardware company, scaling means manufacturing capacity, channel partnerships, and the field engineering to support deployments — all capital-intensive. A raise of this size can fund meaningful expansion for a focused firm, but it does not buy the balance-sheet heft of the industrial giants it competes with. That makes partnerships with server makers and infrastructure vendors, which Iceotope has cultivated in the past, strategically essential: the realistic path to volume for a cooling specialist runs through OEM channels rather than direct sales alone.
The flip side of a crowded, strategically important market is consolidation. Thermal management specialists have been steady acquisition targets for larger infrastructure players seeking credible AI-cooling stories. A funded, technology-differentiated company in this segment is both a competitor and, plausibly, a future acquisition — an outcome investors in this space have historically been comfortable underwriting. That is analysis of market structure, not a prediction about this company; the source report says nothing about Iceotope’s strategic intentions beyond scaling.
Background
Iceotope is a UK-based cooling technology company that has spent years developing chassis-level liquid cooling, branding its approach precision liquid cooling. It raised significant venture funding in 2021 and has pursued a partner-led route to market, working with server and infrastructure vendors to package its cooling into deployable systems for data centers, edge sites, and telecom environments.
The market context transformed around it. The generative AI boom that began in late 2022 drove data center rack power densities sharply upward, straining air cooling and turning liquid cooling into one of the fastest-growing categories in data center infrastructure. Incumbents, startups, and hyperscalers alike have poured investment into the segment, making thermal management a strategic battleground rather than a commodity afterthought.
An independent analysis published on Substack on 13 May 2026 argues that Nevada’s restrictions on evaporative cooling towers at data centers do not eliminate the industry’s water consumption so much as relocate it. The piece, headlined “The $3 Billion Blind Spot,” estimates that roughly 100 million gallons of annual water use moves from data center sites to the thermoelectric power plants that supply the extra electricity air-cooled equipment requires.
The item reached us as a syndicated Google News listing with the headline and a truncated summary; the full text and its underlying calculations were not available for review. The figures below are therefore reported as claims from a single, unverified source, and the analysis that follows tests the logic rather than endorsing the arithmetic.
Executive Summary
The claim is structural rather than scandalous, and that is what makes it worth taking seriously. Cooling a data center by evaporating water is thermodynamically cheap: the phase change from liquid to vapour carries away a great deal of heat for very little electricity. Remove that option, as a cooling tower ban does, and the heat still has to go somewhere. It goes into air-cooled chillers and dry coolers, which use no water on site but draw materially more power, particularly in desert summers when ambient air is hottest and the equipment is least efficient.
That extra power is generated somewhere. If it comes from gas, coal or nuclear plants using recirculating cooling, those plants evaporate water of their own. The water has not disappeared; it has crossed a jurisdictional and accounting boundary. On the site’s books, water use falls toward zero. On a whole-system basis, it may not.
Whether the net effect is good or bad for Nevada is a separate question from whether the accounting is complete, and the two are routinely conflated by both sides. Moving consumption out of a stressed groundwater basin into a different basin, or onto a grid increasingly served by solar and wind that consume almost no water, can be a genuine improvement even if the headline “zero water” figure overstates it. The problem is that current disclosure practice makes it nearly impossible to tell which is happening.
The Trade Is Water for Electricity, and It Is Real
Every cooling design is a choice about which resource to spend. An evaporative cooling tower sprays warm water over fill material and lets a fraction evaporate; the vapour leaves with the heat, and the site tops up the loss from the municipal supply or a well. A dry or air-cooled system rejects the same heat directly to the atmosphere using fans and refrigeration, consuming no water but more kilowatt-hours. In a hot, arid climate the penalty is largest exactly when demand peaks, because the temperature difference the equipment relies on is smallest on a 40°C afternoon.
Industry has a shorthand for the water side of this: Water Usage Effectiveness, or WUE, measured in litres of water per kilowatt-hour of IT load. It is a site metric. It counts what comes through the meter at the fence line. It does not count the water evaporated at a power station a hundred miles away to make the electricity that ran the fans, and it was never designed to. That is a reasonable engineering convention, not a conspiracy — but a metric built for one purpose becomes misleading the moment it is used as a sustainability claim in a public filing or a permit hearing.
The upstream figure is not fixed, and this is where the analysis’s headline number needs interrogation. Thermoelectric water intensity varies by an order of magnitude across generation types and cooling designs: once-through plants withdraw enormous volumes but return most of it, recirculating plants withdraw far less but evaporate most of what they take, and solar photovoltaic and wind consume essentially nothing beyond occasional panel washing. A 100 million gallon estimate is really a statement about an assumed grid mix, and reasonable analysts can differ on whether to use the average mix or the marginal generator that actually responds to new load.
Accounting Boundaries Decide the Answer Before the Arithmetic Starts
Carbon reporting solved a version of this problem years ago by splitting emissions into Scope 1 (direct), Scope 2 (purchased energy) and Scope 3 (everything else in the value chain). Water reporting has no equivalent convention in general use. There is no widely adopted “Scope 2 water” line item, so the electricity-embedded water footprint of a data center is, in most public disclosures, simply absent — not understated, absent.
Two further distinctions do a lot of quiet work in arguments like this one. The first is withdrawal versus consumption: water taken from a river and returned warmer is not the same as water evaporated and gone from the basin, and figures that mix the two can inflate or deflate a result dramatically. The second is location. A gallon evaporated from an over-allocated desert aquifer and a gallon evaporated beside a well-supplied river are equivalent on a spreadsheet and completely different in hydrological reality. Water-stress-weighted accounting exists to handle this, but it is not what most headline totals use.
Applied evenly, this cuts both ways. It undercuts an operator advertising an air-cooled campus as “water-free” when the phrase describes only the fence line. It equally undercuts a critic who books upstream gallons at full weight without asking whether that water leaves a stressed basin, whether the marginal generator is a gas plant or a solar farm, and whether the plant in question uses evaporative cooling at all.
Who Gains, Who Absorbs the Cost
The clearest winners are local water authorities and the residents they answer to. A ban on evaporative cooling gives a regulator a bright-line, enforceable rule that removes a visible, meterable draw from a constrained supply, and it does so without having to adjudicate every project’s efficiency claims. Whatever its system-wide merits, as local water policy it is administratively coherent.
Developers absorb a cost that is real but survivable. Air-cooled plant is typically more capital-intensive per megawatt of rejected heat, occupies more space, and raises Power Usage Effectiveness — the ratio of total facility power to IT power — which in turn raises operating cost and increases the megawatts a campus must contract for. For an operator negotiating an interconnection queue position in a constrained market, that last point may matter more than the electricity bill. Rising energy demand also strengthens the case for on-site or contracted generation, which is where the water question becomes the operator’s own again rather than an anonymous grid externality.
The party with the least voice is the community near the generating plant, which may sit in an entirely different county or state and has no standing in the data center’s permitting process. That asymmetry — decision made in one basin, consequence landed in another — is the substantive point the analysis raises, and it stands independently of whether the specific 100 million gallon estimate survives scrutiny.
Reading the Claim Fairly
A single Substack post working from public data is a legitimate contribution; independent analysis has repeatedly surfaced infrastructure issues before trade coverage did, and dismissing it on the basis of the venue would be lazy. But the same standard applied to a vendor sustainability report applies here: the estimate is only as good as its disclosed method, and we could not see the method.
The “$3 billion” in the headline is the weakest element on the available evidence. The figure is not defined in the material we can see — it could denote capital investment in affected facilities, the economic value at stake, an avoided-cost estimate, or something else entirely. Large round numbers in headlines travel further than the caveats attached to them, and a reader encountering this claim second-hand is likely to acquire a precise-sounding figure with no idea what it measures.
The responsible position, at this stage, is that the mechanism is sound and well understood, the direction of the effect is almost certainly correct, and the magnitudes are unverified. That is enough to justify better disclosure. It is not yet enough to justify a conclusion about whether Nevada’s policy makes the state’s water situation better or worse.
Background
Nevada sits at the sharp end of two trends at once. It depends heavily on Colorado River water through Lake Mead, where sustained drought and over-allocation have made every new consumptive use politically visible, and Southern Nevada has spent decades building one of the most aggressive urban water conservation programmes in the United States. At the same time, cheap land, favourable tax treatment and proximity to California demand have made the state a significant data center market, with large campuses clustered in Northern Nevada industrial parks and in the Las Vegas area.
The collision was predictable. As AI workloads pushed rack densities and total facility power upward through the mid-2020s, cooling water became a permitting flashpoint in arid states generally, not only Nevada. Restricting evaporative cooling is one of the more direct policy levers available to a water authority. Whether it reduces total water consumption or mainly relocates it is the question this analysis raises, and it is a question the industry’s current reporting conventions are not equipped to answer.
Data Center Knowledge published an analysis on May 11, 2026, titled “Redefining Hydronic Design for D2C Liquid Cooling,” addressing how the shift to direct-to-chip (D2C) liquid cooling is changing the way data center water systems — the hydronic plant — must be designed. The piece lands amid an industry-wide transition in which AI-driven rack power densities have climbed beyond what traditional air-cooled facility designs were built to handle.
Executive Summary
The core issue flagged by the headline is straightforward but consequential: direct-to-chip liquid cooling — where coolant is piped through cold plates mounted directly on processors, rather than cooling servers with chilled air — does not simply bolt onto the chilled-water infrastructure most data centers already have. Hydronic design, meaning the engineering of the pumps, piping, heat exchangers, and control systems that move liquid through a facility, was historically sized around air handlers serving racks of modest power draw. D2C changes the temperatures, flow rates, water quality requirements, and failure modes the plant must support.
Why it matters: liquid cooling has moved from niche to mainstream as AI accelerators push per-rack power well beyond what air can economically remove. Operators deciding between retrofitting existing plants and building new liquid-native facilities are making capital decisions that will constrain them for decades. A trade-press focus on hydronic fundamentals — rather than just on the servers or cold plates — signals that the industry’s bottleneck conversation is shifting upstream, from the rack to the plant room.
The Plant Room Becomes the Bottleneck
For two decades, data center cooling design treated the white space and the plant as loosely coupled: air handlers absorbed variation on the floor, and the chilled-water loop behind them changed slowly. Direct-to-chip cooling collapses that buffer. The coolant loop now terminates inches from the silicon, typically through a coolant distribution unit (CDU) — a device that isolates the clean, tightly controlled technology loop serving the servers from the facility water loop. That coupling means plant-side decisions about supply temperature, flow stability, and redundancy propagate directly to chip behavior, and legacy assumptions about acceptable temperature bands and transient response no longer hold automatically.
This is why hydronic design is having its moment in the trade press. The hard problems in liquid cooling are increasingly civil and mechanical engineering problems — pipe sizing, pump redundancy, water treatment, commissioning — not server-vendor problems. Operators who treat D2C as a rack-level product purchase, rather than a facility-level design change, risk discovering the mismatch after the equipment is on the dock.
Warm Water Changes the Economics
A frequently underappreciated aspect of D2C cooling is that cold plates can generally accept much warmer supply water than air-cooling systems require. Warmer facility water expands the hours in which outside air can reject heat without running chillers — so-called free cooling — which can reduce energy consumption and, in some designs, eliminate mechanical refrigeration for part or all of the year. But capturing that benefit requires designing the hydronic system around it: heat exchangers, dry coolers, and controls sized for warm-water operation, not a legacy chilled-water loop running at temperatures chosen for air handlers.
The economics cut both ways. A retrofit that simply taps an existing chilled-water plant may work, but it can leave the efficiency upside of liquid cooling unrealized and burden an aging plant with duty it was never sized for. A purpose-designed warm-water system costs more up front and demands different operational expertise. The Data Center Knowledge piece’s framing — redefining hydronic design rather than extending it — suggests the editorial judgment that incrementalism has limits here, a view worth testing against each facility’s actual constraints.
Winners, Losers, and the Skills Gap
If hydronic design is the new frontier, the beneficiaries are the firms that own that competence: mechanical engineering consultancies, CDU and heat-rejection equipment manufacturers, and colocation providers that invested early in liquid-ready plants. Operators of large fleets of air-era buildings face harder choices — retrofit selectively, densify only some halls, or cede the highest-density workloads to newer facilities. There is also a human dimension: hydronic systems at this criticality level need commissioning agents and operators fluent in water chemistry, two-phase transients, and leak response, and that talent pool is thin relative to the pace of AI buildout.
None of this makes air cooling obsolete. Most enterprise workloads remain comfortably air-coolable, and hybrid facilities — liquid for accelerator rows, air for everything else — are likely the dominant pattern for years. The design challenge the article’s title points to is precisely that hybridity: one plant serving two very different thermal customers.
Background
Data centers have been overwhelmingly air-cooled since the industry’s beginnings: chillers or outside air cool water, water cools air handlers, and air cools servers. That chain held while racks drew a few kilowatts each. The AI buildout of the mid-2020s broke the assumption, as accelerator-dense racks pushed power draw to levels where moving enough air became impractical, driving rapid adoption of direct-to-chip liquid cooling across hyperscale, colocation, and enterprise deployments.
The transition has unfolded in stages — first server-level cold plates, then rack-level manifolds and CDUs, and now, as this Data Center Knowledge piece reflects, a reckoning with the facility-level hydronic plant itself. Industry bodies and operators have been working toward common temperature classes and reference designs, but practice is still consolidating, which is why plant-level design questions remain live editorial territory in 2026.
Source: Redefining Hydronic Design for D2C Liquid Cooling — Data Center Knowledge analysis, published May 11, 2026, on how direct-to-chip liquid cooling is reshaping data center water-system design.
Ars Technica reported on May 10, 2026 that a data center drew roughly 30 million gallons of water — and that the consumption went undetected for months. The headline alone frames the story: the issue is not only the volume, which is significant but not unheard of for a large facility, but the fact that no one — apparently neither the operator’s oversight processes nor the local water authority — flagged it while it was happening.
Executive Summary
The report describes a data center that “guzzled” about 30 million gallons of water while the draw went unnoticed for months. For scale, 30 million gallons is roughly 45 Olympic-size swimming pools, or about a year’s supply for several hundred typical U.S. households. Data centers commonly use water for evaporative cooling — spraying or trickling water so that its evaporation carries away server heat — which is energy-efficient but consumptive: much of the water leaves as vapor rather than returning to the system.
Why it matters: the industry is under growing scrutiny over water in drought-prone regions, and the standard defense is that usage is metered, permitted, and disclosed to the relevant utility. An episode in which tens of millions of gallons flow without timely detection undercuts that assurance and strengthens the case — made by regulators and communities alike — for real-time submetering, faster reconciliation between withdrawals and billing, and public reporting of facility-level water use.
How Tens of Millions of Gallons Go Missing From View
Water is easy to lose track of in a way electricity is not. Power draw is metered continuously because it is billed continuously, and grid operators watch load in real time. Water billing, by contrast, often runs on monthly or quarterly meter reads, estimated bills, and manual reconciliation — and large industrial users sometimes draw from wells or dedicated lines that sit outside a municipality’s ordinary consumption dashboards. A facility running evaporative cooling around the clock can therefore accumulate an enormous draw between the moments anyone actually looks at the numbers.
The headline’s claim that “nobody noticed for months” is consistent with that structural lag rather than requiring any bad intent. But intent is not the point: a monitoring regime that only surfaces a 30-million-gallon draw after the fact is not a monitoring regime in any meaningful sense. The same volume flowing through a leak, a stuck valve, or an unauthorized connection would have gone equally unnoticed.
The Volume Is Ordinary; the Blindness Is the Story
Thirty million gallons over several months is within the range that large evaporatively cooled data centers can plausibly consume — big hyperscale campuses can use hundreds of thousands of gallons on a hot day. So the fair reading is not that this facility was uniquely thirsty, but that a routine level of industrial water use ran without effective oversight. That distinction matters for how the industry should respond: the fix is measurement and disclosure, not necessarily a smaller pipe.
It also matters for the public debate. Data center water use is frequently discussed in aggregate estimates precisely because facility-level figures are scarce — operators often treat water contracts as confidential, and utilities have historically honored that. Every incident like this one shifts the burden of proof: if the numbers are unremarkable, operators strengthen their own position by publishing them; if the numbers only emerge when something goes wrong, skepticism is the rational default.
What Good Looks Like: Metering, WUE, and Utility Practice
The remedies are unglamorous and well understood. Continuous submetering at the facility intake, with telemetry to both the operator and the water utility, turns months of invisibility into hours. Publishing water usage effectiveness (WUE — liters of water consumed per kilowatt-hour of IT load, the water analogue of the PUE efficiency metric) lets outsiders compare facilities on a common basis. Utilities, for their part, can set anomaly thresholds on large industrial accounts the way credit-card issuers flag unusual spending — an established technique that simply has not been standard practice for water.
There are trade-offs worth being honest about. Cutting water use usually means air-cooled or closed-loop systems, which consume more electricity — shifting the environmental burden from watershed to grid. Communities and operators may reasonably choose evaporative cooling in water-rich regions. But that choice is only defensible when the water is measured, permitted, and disclosed. Transparency is the precondition for the trade-off being legitimate, and this episode is a case study in what happens when it is absent.
Background
Data center water use has become one of the industry’s most contested environmental questions, alongside electricity demand. As AI and cloud growth drive construction of ever-larger campuses, communities from the American Southwest to Europe have pushed back on facilities sited in water-stressed regions, and operators have responded with a mix of efficiency pledges, “water positive” commitments, and — less often — actual facility-level disclosure. Unlike power, which is continuously metered and increasingly reported, water has historically been governed by opaque utility contracts and infrequent meter reads, leaving both regulators and the public reliant on aggregate estimates rather than measured data. Incidents in which large draws surface only after the fact have repeatedly reset that debate.
Johnson Controls, one of the world’s largest building-technology and HVAC companies, reported an 8% year-over-year increase in sales for its fiscal second quarter, with data center cooling demand cited as a principal driver, according to a May 7, 2026 report by Facilities Dive. Because Johnson Controls’ fiscal year ends in September, its second quarter covers roughly January through March 2026.
Executive Summary
The headline number — 8% sales growth at a company of Johnson Controls’ scale — is notable less for its size than for its attribution. When a diversified industrial that sells everything from fire-suppression systems to building controls credits data center cooling as the engine of a quarter, it quantifies something the industry has sensed for two years: AI-driven data center construction has become a primary demand source for the industrial HVAC sector, not a niche vertical.
Cooling is the second-largest consumer of power and capital in a data center after the IT equipment itself, because nearly every watt a server draws becomes heat that must be removed. As hyperscale operators — the companies running the largest cloud and AI facilities — race to add capacity, the vendors who make chillers, air handlers, and thermal-management systems are seeing that race show up directly in their revenue lines. Johnson Controls’ quarter is one of the cleaner public data points yet on how large that effect has become.
From Building Controls to AI Infrastructure Supplier
Johnson Controls has spent recent years narrowing its portfolio toward commercial buildings and applied HVAC — the large, engineered cooling systems used in campuses, hospitals, and data centers — including divesting its residential and light-commercial HVAC business to Bosch and acquiring Silent-Aire, a maker of modular cooling and hyperscale data center equipment, in 2021. A quarter in which data center cooling is called out as the growth driver suggests that repositioning is doing what it was designed to do: concentrate the company’s exposure where capital spending is heaviest.
That matters for how investors and customers should read the company. Johnson Controls is increasingly priced and evaluated not as a building-products conglomerate but as a supplier to AI infrastructure buildouts — a category that commands different growth expectations, and different scrutiny, than traditional construction-linked HVAC.
The Economics of the Cooling Boom
Data center cooling is attractive business for industrial vendors for structural reasons. The equipment is large, engineered-to-order, and often sold with long-term service contracts — chillers (machines that produce chilled water to absorb heat from server halls) run continuously for decades and require ongoing maintenance. Hyperscale projects are also ordered in fleets rather than units, which fills factory backlogs years ahead and gives manufacturers unusual visibility and pricing power compared with the one-building-at-a-time commercial construction cycle.
The industry is simultaneously navigating a technology transition. As AI chips grow denser, air cooling reaches physical limits, and liquid cooling — circulating coolant directly to the chips or their racks — is taking a growing share of new deployments. That transition is an opportunity for incumbents with liquid-capable portfolios and a risk for anyone whose installed strength is concentrated in legacy air-based systems. The source report does not break down how much of Johnson Controls’ growth came from which technology, a distinction that matters for judging how durable the growth is.
A Rising Tide Across the Vendor Field
Johnson Controls is not alone in reporting data-center-driven strength; the same demand wave has lifted results across thermal-management and power-equipment vendors, and competitors such as Vertiv, Carrier, Trane Technologies, Schneider Electric, Munters, and Daikin all compete for slices of the same buildouts. The significance of this quarter is corroborative: each vendor that attributes measurable growth to data centers adds evidence that hyperscale capital spending is flowing through to the industrial supply chain broadly, rather than pooling with one or two specialists.
For data center operators and enterprises planning capacity, the flip side of vendor prosperity is procurement reality: strong vendor demand typically means longer lead times and firmer pricing for large cooling equipment. Buyers who plan orders early, standardize designs, and lock delivery slots hold the advantage in a seller’s market.
The Concentration Question
The risk embedded in an 8% quarter driven by one end market is the same as its appeal: concentration. Data center demand is ultimately a derivative of a handful of hyperscalers’ AI capital-expenditure decisions. If AI infrastructure spending decelerates — because of monetization pressure, power-availability constraints, or efficiency gains that reduce cooling intensity per unit of compute — the vendors that re-oriented toward this vertical would feel it quickly. Nothing in the source report suggests that is imminent, but a growth story built on one customer class deserves to be monitored as one.
The even-handed reading: this quarter substantiates real, current demand flowing to a major HVAC vendor. It does not, by itself, establish how long the cycle runs, and the headline-level detail available leaves the durability question open.
Background
Johnson Controls traces its roots to 1885, when Warren S. Johnson commercialized the electric room thermostat, and grew over the following century into one of the world’s largest building-technology companies, spanning HVAC equipment (including the York chiller brand), building automation, and fire and security systems after its 2016 merger with Tyco. In recent years the company has deliberately narrowed toward commercial and engineered building systems, selling its residential and light-commercial HVAC business to Bosch and investing in data center capabilities, most visibly through the 2021 acquisition of hyperscale cooling specialist Silent-Aire.
That repositioning coincided with the AI infrastructure boom, in which data center construction — and the power and cooling systems it requires — became one of the fastest-growing capital-spending categories in the global economy, reshaping demand for the entire industrial HVAC sector.
Johnson Controls announced on May 5, 2026 the release of its second data center reference design guide, aimed at advancing cooling for industrial-scale AI factories — the very large, GPU-dense data centers built to train and run artificial intelligence models. The guide follows the company’s earlier reference design publication and continues its effort to give data center developers pre-engineered, repeatable cooling blueprints rather than one-off custom designs.
Executive Summary
The announcement itself is straightforward: a major cooling and building-technology vendor has published a second installment in a series of reference design guides for AI data center thermal management. A reference design, in this context, is a validated engineering template — equipment selections, piping and airflow topologies, controls logic — that a developer can adopt largely as-is instead of engineering a cooling plant from scratch for every project.
Why it matters is the industry moment. AI computing has pushed rack power densities far beyond what traditional air cooling handles economically, forcing a rapid shift to liquid cooling. That shift has collided with a shortage of engineers who have actually designed liquid-cooled facilities at scale. Vendors who can package proven designs stand to compress project timelines and, not incidentally, lock their own equipment into the template. Johnson Controls publishing a second guide signals both that the first found an audience and that the company sees standardized, productized cooling design as a durable competitive front — not a one-off marketing exercise.
Reference Designs Are the Industry’s Answer to a Speed Problem
The binding constraints on AI data center construction are power, equipment lead times, and engineering hours — in roughly that order. Every hyperscaler and colocation developer is trying to shorten the time from land acquisition to energized racks, and bespoke mechanical design is one of the slowest, most error-prone stages. A reference design guide attacks that stage directly: if the cooling plant is pre-engineered and pre-validated, developers can order long-lead equipment earlier, permit faster, and reuse the same design across multiple sites.
This mirrors what happened in earlier infrastructure waves. Hyperscale data centers of the 2010s converged on repeatable electrical and mechanical templates, which is a large part of how build times fell even as facilities grew. AI factories reset that progress because liquid cooling — circulating fluid directly to chips or to rear-door heat exchangers instead of relying on chilled air — changed the entire mechanical architecture. Reference designs are how the industry rebuilds its muscle memory for the new architecture.
Standardization Is Also a Land Grab
A vendor-published reference design is not a neutral standard. It is a template built around the publisher’s own chillers, coolant distribution units, controls, and services. If a developer adopts the guide, Johnson Controls equipment becomes the default bill of materials, and switching components later means re-validating the design. That is the same playbook chip vendors use with their own data center reference architectures: publish the blueprint, become the default.
Seen that way, a second guide is a competitive statement aimed at the other large thermal players — the established chiller and precision-cooling manufacturers all racing to publish AI-ready architectures — and at engineering firms whose custom-design business a good-enough template partially displaces. For buyers, the trade-off is real but usually favorable: some vendor lock-in in exchange for schedule certainty and a design someone else has already de-risked. The buyers with the least to gain are those with strong in-house engineering; the biggest beneficiaries are the second wave of AI data center developers — enterprises, sovereign projects, smaller colocation firms — who lack liquid-cooling experience entirely.
What a Guide Can and Cannot Prove
It is worth being clear-eyed about what a design document demonstrates. Publishing a guide shows engineering investment and market intent; it does not by itself prove field performance, energy efficiency, or delivery capacity at the scale AI factories demand. The metrics that ultimately matter — cooling capacity per megawatt, water and energy consumption, equipment lead times, uptime in operation — are established by built projects, not publications. The announcement, as reported, is a step in productizing AI cooling; the evidence of success will be reference customers and operating facilities that used the designs. That is not a criticism of the release so much as the correct lens for reading any vendor reference architecture.
Background
Johnson Controls traces its history to the 19th-century invention of the room thermostat and has grown into one of the world’s largest building-technology companies, spanning HVAC equipment, industrial chillers, controls, and services. Over the past several years it has leaned hard into data centers as a growth market, positioning its chiller lines, coolant distribution equipment, and controls for the AI buildout.
The market context is a structural shift: the AI boom has driven rack power densities beyond air cooling’s practical limits, making liquid cooling a requirement rather than a niche option and setting off a race among thermal-management vendors to publish standardized, repeatable designs. Reference architectures — long a fixture in chip and server ecosystems — have become the mechanism through which cooling vendors compete to define how AI factories get built.
CoreWeave, the AI-focused cloud provider, published a piece titled “Liquid Cooling for AI Data Centers: Run Cold, Act Bold,” making the argument that liquid cooling — circulating fluid directly to or near the chips rather than relying on chilled air — should be treated as the default engineering choice for dense AI training and inference clusters, not a specialty option.
The post, surfaced in early May 2026, is a vendor thought-leadership piece rather than a product or facility announcement: no new sites, capacity figures, or customer commitments accompany it. Its significance lies in who is saying it — one of the largest dedicated AI cloud operators publicly framing liquid cooling as table stakes.
Executive Summary
The core claim is architectural: modern AI accelerators are being packed into racks at power densities that air cooling struggles to serve economically, so operators who standardize on liquid cooling now will deploy the newest hardware faster and run it more efficiently than those who retrofit later. That position aligns with the direction of the hardware itself — flagship AI rack systems from the leading accelerator vendors are increasingly designed around liquid cooling from the outset.
Why it matters: cooling has quietly become one of the binding constraints on AI buildout, alongside power availability and chip supply. A data center designed for traditional air-cooled racks often cannot accept the densest AI systems without significant rework of its mechanical plant, piping, and floor layout. When a major AI cloud provider says liquid cooling is the default, it is effectively telling the colocation and construction ecosystem what the demand side now expects.
For buyers and investors, the practical takeaway is less about CoreWeave specifically and more about the signal: the market for AI capacity is bifurcating between facilities that can support liquid-cooled density and those that cannot, and the gap affects deployment speed, efficiency, and ultimately the cost of delivered compute.
Why Cooling Became the Bottleneck
For most of the data center industry’s history, air cooling was sufficient: racks drew a few kilowatts, and moving enough cold air through the room was a solved problem. AI changed the arithmetic. Training clusters concentrate power-hungry accelerators as tightly as possible to shorten the distances data travels between chips, because interconnect latency and bandwidth directly affect training performance. That pushes rack densities far beyond what conventional air handling was designed for, and at some point the physics favors liquid — water and engineered fluids carry heat far more effectively than air.
CoreWeave’s framing of liquid cooling as a default rather than an exception reflects where the hardware roadmap already points. The densest current-generation AI rack systems are engineered for direct liquid cooling, meaning operators who want the newest silicon at full density have limited choice. In that sense the post is less a prediction than a description of a constraint the industry is already living with — but stating it as doctrine matters, because much of the world’s existing data center stock was not built for it.
The Economics: Efficiency Versus Retrofit Cost
The business case for liquid cooling rests on two ledgers. On the operating side, liquid systems can reduce the energy spent on cooling itself — a meaningful lever, since cooling is typically one of the largest non-IT loads in a facility, and every watt saved on cooling is a watt available for revenue-generating compute in power-constrained markets. On the capital side, however, liquid cooling requires piping, coolant distribution units, leak management, and often structural changes, which is straightforward in a new build and expensive in a retrofit.
That asymmetry is the strategic subtext of a piece like this. Operators that standardized early on liquid-ready designs can absorb each new accelerator generation with incremental changes; operators with large air-cooled footprints face a harder choice between costly conversion and ceding the densest workloads. CoreWeave, which built its business specifically around GPU infrastructure for AI, has an obvious interest in emphasizing a criterion where purpose-built AI clouds hold an advantage over general-purpose incumbents — which does not make the underlying engineering argument wrong, but readers should recognize the alignment between the message and the messenger.
Winners, Losers, and the Supply Chain Ripple
If liquid cooling is the default, the beneficiaries extend well beyond AI clouds. Suppliers of coolant distribution units, cold plates, piping, and heat-rejection equipment see their addressable market expand from a niche to a standard line item in every AI facility. Colocation providers with liquid-ready halls gain pricing power for AI tenants; those without face pressure to invest. Engineering and construction firms with liquid-cooling experience become scarcer resources in an already stretched buildout.
The risk side deserves equal attention. Liquid cooling adds mechanical complexity — leaks, coolant chemistry, maintenance procedures — into environments that prize uptime above almost everything. Standardization across vendors is still maturing, which raises the possibility of stranded investment if designs shift between hardware generations. And efficiency gains at the rack level do not eliminate the larger constraint: many AI projects today are gated by grid power availability, a problem no cooling technology solves on its own.
Background
CoreWeave began as a cryptocurrency mining operation before pivoting to GPU cloud computing, and rode the generative AI boom to become one of the largest providers of dedicated AI infrastructure, going public in 2025. Its business model — building or leasing data centers purpose-designed for dense GPU clusters and renting that capacity to AI developers — makes facility engineering choices like cooling central to its competitive position.
The broader industry context: for decades, air cooling dominated data centers because rack power draws were modest. The AI era reversed that, with accelerator racks reaching power densities that favor liquid-based heat removal, and the latest flagship AI rack systems are designed for liquid cooling from the factory. That has turned cooling from a back-of-house mechanical detail into a strategic differentiator in the race to deploy AI capacity.
Trade publication Data Center Knowledge reported on May 1, 2026 that cooling capability is failing to keep pace with the power density of AI computing hardware in data centers. The report frames a problem now visible across the industry: racks packed with AI accelerators draw far more power — and therefore shed far more heat — than the air-cooled infrastructure most facilities were built around, turning thermal management into a gating factor for AI capacity.
Executive Summary
The core claim is simple but consequential: the heat produced by AI hardware is rising faster than the industry’s ability to remove it. Every watt a server consumes becomes heat that must be carried away, and conventional data centers were engineered for racks drawing modest single-digit to low-double-digit kilowatts. Dense AI training clusters concentrate an order of magnitude more power in the same floor space, pushing air-based cooling — fans, raised floors, and computer-room air handlers — toward its physical limits.
Why it matters: if cooling cannot keep up, it does not matter how many GPUs a company can buy or how much grid power a site can secure. Thermal capacity becomes the binding constraint on AI deployment schedules. That reality is forcing a generational transition toward liquid cooling — circulating coolant directly to chips or immersing hardware in fluid — and it is reshaping how facilities are designed, financed, and leased.
Heat Is the Hard Ceiling, Not Power or Chips
The AI buildout has been narrated mostly as a race for GPUs and grid connections, but this report points at the quieter bottleneck between them: getting heat out of the building. Air cooling works by moving enormous volumes of chilled air past hot components, and its effectiveness falls off sharply as power concentrates. Past a certain rack density, no arrangement of fans and airflow containment can remove heat as fast as modern accelerators generate it. Liquid, which carries heat far more efficiently than air, becomes a physical necessity rather than an optimization.
That distinction matters for planning. Power shortages can sometimes be solved with money and patience — new substations, on-site generation. Thermal limits are baked into a building’s design: pipe runs, floor loading, chilled-water plant capacity, and the space between racks. A facility designed for air cooling cannot simply be told to run hotter.
The Retrofit Problem: Old Buildings, New Physics
The industry’s installed base is the crux of the struggle the report describes. Most operating data centers were designed years before dense AI clusters existed. Retrofitting them for direct-to-chip liquid cooling means adding coolant distribution units, leak detection, new piping, and often structural work — all while existing tenants keep running. That is slow, expensive, and disruptive, which is why much of the highest-density AI capacity is going into purpose-built greenfield facilities instead.
The economic consequence is a widening split in the market. Modern, liquid-ready capacity commands premium pricing and pre-leases quickly, while older air-cooled facilities risk sliding toward commodity workloads. For operators, the question is no longer whether to invest in liquid cooling but how much of the existing portfolio is worth converting versus running out its useful life on conventional enterprise and cloud workloads.
Winners, Losers, and the Supply Chain in Between
A constraint this fundamental redistributes value. Suppliers of liquid-cooling hardware — cold plates, coolant distribution units, immersion systems, heat exchangers — and the engineering firms that integrate them stand to benefit from a multi-year upgrade cycle. Chipmakers are increasingly designing accelerators that assume liquid cooling, which pulls the whole ecosystem along. Operators with liquid-ready designs and available power gain leverage in lease negotiations with AI tenants who have few alternatives.
The losers are less obvious but real: enterprises and smaller cloud providers holding long leases in facilities that cannot economically support high-density deployments, and AI projects whose timelines quietly slip because the cooling plant — not the chips — is the long-lead item. For buyers of AI capacity, thermal specifications are becoming as important a diligence item as price per kilowatt.
Background
For most of the industry’s history, data centers were cooled by air: chilled air pushed through raised floors and aisles past servers drawing a few kilowatts per rack. That model scaled comfortably through the enterprise and cloud eras. The AI boom broke the pattern — training clusters built on power-hungry accelerators concentrate an order of magnitude more power per rack, and the industry has responded with a generational shift toward liquid cooling, a technique long used in supercomputing but new at commercial scale.
By early 2026, the constraint conversation around AI infrastructure had expanded from chip supply to grid power and, increasingly, to thermal capacity — the subject of this report. Cooling now sits alongside power procurement as a first-order determinant of where and how fast AI capacity gets built.
Carrier Ventures, the venture arm of HVAC and building-systems giant Carrier Global, announced on April 28, 2026 that it is expanding its investment in ZutaCore, a maker of two-phase, direct-to-chip liquid cooling technology. The stated purpose is to scale liquid cooling for AI data centers, where rapidly rising chip power densities are outrunning traditional air cooling. The announcement, distributed via PR Newswire, did not disclose the size or terms of the expanded investment.
Executive Summary
Carrier first backed ZutaCore with a strategic investment and partnership announced in late 2024. This follow-on commitment signals that Carrier sees direct-to-chip cooling — hardware that removes heat at the processor itself rather than from the room around it — as central to its data center strategy, not a side experiment. For a company whose traditional data center business is facility-level equipment such as chillers and air handlers, that is a meaningful shift in where it believes thermal value will be captured.
The ‘why now’ is straightforward: AI accelerators have pushed rack power draws from the tens of kilowatts into the hundreds, a range where moving heat with air alone becomes physically and economically impractical. Liquid cooling has moved from niche to necessity for AI deployments, and every major thermal-management vendor is racing to own a piece of the resulting stack. The open question is whether the announcement represents scaled commercial traction or primarily a strategic option on a still-contested technology — the release headline promises scale, but the syndicated text offers no deployment figures, customer names, or dollar amounts to measure it by.
Why an HVAC Giant Wants Inside the Rack
Carrier’s historical position in data centers is at the facility level: chillers, cooling towers, and air-handling systems that condition entire halls. Direct-to-chip cooling changes where the critical engineering happens. When heat is captured at the silicon by cold plates and carried away in fluid loops, the highest-value thermal decisions move from the building to the rack — territory contested by specialists like ZutaCore, CoolIT, and Motivair, and by IT-side players such as Vertiv and the server manufacturers themselves. An expanded investment in ZutaCore is a hedge against disintermediation: if Carrier does not have a credible chip-level offering, it risks being relegated to supplying the commodity heat-rejection equipment at the end of someone else’s thermal chain.
There is also a plausible offensive logic. A vendor that can pair chip-level heat capture with its own facility-scale heat rejection can sell an integrated thermal chain — from cold plate to cooling tower — which is attractive to operators who currently stitch that chain together from multiple vendors. Whether Carrier and ZutaCore intend to productize such an integrated offering is not stated in the announcement, but it is the strategic prize this kind of pairing points toward.
Two-Phase Cooling, Explained — and Why It Is Contested Ground
Most liquid cooling deployed for AI today is single-phase: water or a water-glycol mix flows through a cold plate on the chip, warms up, and carries the heat away. ZutaCore’s approach is two-phase — a dielectric (non-electrically-conductive) fluid boils directly on the cold plate, absorbing large amounts of heat as it vaporizes, then condenses elsewhere in the loop. The physics advantage is real: boiling absorbs far more heat per unit of fluid than simple warming, which matters as individual accelerator packages climb toward and beyond kilowatt-class heat output. Because the fluid is non-conductive, a leak is also less catastrophic than a water leak inside a server.
The counterweight is ecosystem maturity. Single-phase water cooling is the volume standard for current AI reference designs, with an established supply chain, well-understood operating practices, and trained technicians. Two-phase systems introduce different fluids, pressures, and service procedures, and specialty dielectric fluids carry their own cost and, depending on chemistry, environmental scrutiny. The bet embedded in Carrier’s investment is that next-generation chip heat densities will strain single-phase designs enough to open a mainstream window for two-phase — a defensible thesis, but one the market has not yet settled.
What the Announcement Does and Does Not Substantiate
Read carefully, this is a statement of investor conviction, not a disclosed commercial milestone. A follow-on investment from a strategic corporate backer is a genuine positive signal: corporate venture arms rarely double down on portfolio companies whose technology their own engineers have found wanting. It suggests the 2024 partnership produced enough validation to justify more capital.
What the syndicated release does not provide is the evidence a buyer or investor would need to gauge momentum: the investment amount, ZutaCore’s resulting valuation or Carrier’s stake, named customers, deployed megawatts, or manufacturing capacity commitments. ‘Scale liquid cooling for AI data centers’ is a direction, not a metric. That does not make the announcement empty — strategic capital and an incumbent’s distribution reach are real assets for a smaller technology vendor — but the gap between the headline’s ambition and the disclosed specifics is worth keeping in view. The same skepticism should be applied evenly: competing single-phase vendors’ claims of inevitability are also assertions, not settled fact, in a market where chip roadmaps can shift the thermal calculus every generation.
Background
Carrier Global, spun off from United Technologies in 2020, is one of the world’s largest providers of heating, ventilation, air conditioning, and refrigeration systems, with a long-standing data center business centered on facility-level cooling equipment. ZutaCore, founded in the mid-2010s with roots in Israel, developed a waterless two-phase direct-to-chip cooling platform aimed at high-density computing. The two companies first linked up in late 2024, when Carrier announced a strategic investment and partnership with ZutaCore as part of a broader industry pivot toward liquid cooling.
That pivot has been driven by the AI buildout: accelerator-dense racks have pushed power and heat densities beyond what air cooling can economically handle, turning liquid cooling from a specialty into a core requirement of new AI data center designs and drawing HVAC incumbents, power-infrastructure vendors, and startups into direct competition for the rack thermal stack.
