Google Open-Sources a Liquid-to-Air Cooling Sidecar for Air-Cooled Data Centers

Deepak Jain — Wed, 17 Jun 2026 16:00:00 +0000

Google has unveiled an open-source liquid-to-air cooling sidecar designed for air-cooled data center environments, as reported by Data Center Dynamics on June 17, 2026. The design targets one of the most pressing constraints in the industry: modern AI accelerators increasingly require direct liquid cooling, while the vast majority of existing data center floor space was built to move heat with air alone.

A sidecar of this type is a heat-exchanger cabinet that sits beside a rack of liquid-cooled servers, circulating coolant through the chips in a closed loop and then rejecting that heat into the room’s existing airflow — no facility water piping required. By publishing the design openly, Google is inviting vendors and operators to build and adapt it rather than keeping it proprietary.

Executive Summary

The announcement matters less for what the hardware is than for where it lets liquid cooling go. Direct-to-chip liquid cooling has become effectively mandatory for the densest AI training hardware, but deploying it normally requires facility-level infrastructure — coolant distribution units, piping loops, and water connections that most operating data centers simply do not have. A liquid-to-air sidecar sidesteps that requirement: the liquid loop stays local to the rack, and the building’s existing air-handling systems carry the heat away as they always have.

That makes this a retrofit play. Enterprises, colocation tenants, and smaller operators sitting on air-cooled capacity gain a path to host at least some liquid-cooled equipment without construction projects. It is also a continuation of Google’s recent posture of contributing cooling designs to the open hardware ecosystem rather than treating them as competitive secrets — a bet that standardizing the plumbing layer accelerates the whole market Google’s cloud and AI businesses depend on.

The report available at the time of writing is brief, and the announcement as covered leaves key engineering and availability details unstated — including the design’s cooling capacity, its publication venue and license, and whether it reflects hardware Google runs in production. Those specifics will determine whether this is a broadly useful reference design or a niche one.

The Retrofit Gap Is the Industry’s Quiet Bottleneck

Headlines about AI data centers focus on new gigawatt-scale campuses, but most of the world’s installed data center capacity is older, air-cooled space designed for racks drawing 5 to 15 kilowatts. Current AI server racks can draw many times that, and the chips inside them ship with cold plates that expect liquid, not airflow. Operators of existing facilities face an unattractive menu: leave AI workloads to someone else, undertake disruptive plumbing retrofits in live buildings, or find a bridge technology.

Liquid-to-air sidecars are that bridge. Because the liquid never leaves the immediate vicinity of the rack, the facility itself does not need water loops, external coolant distribution plants, or new mechanical rooms. The trade-off is physics: the room’s air systems still have to absorb every watt the sidecar rejects, so total rack density remains bounded by the building’s air-handling and power envelope. A sidecar extends the life of air-cooled space; it does not turn a legacy building into a frontier AI facility.

Why Give the Design Away?

Google has form here. The company has run liquid-cooled custom TPU accelerators internally since roughly 2018, and in 2025 it announced it would contribute a production coolant distribution unit design to the Open Compute Project, the industry body through which hyperscalers share hardware specifications. Open-sourcing a sidecar fits the same logic: cooling hardware is not where Google differentiates, but an immature, fragmented cooling supply chain slows everyone — including Google and the customers of its cloud business.

Open designs give equipment manufacturers a common reference to build against, which tends to lower prices, improve interoperability, and widen the vendor pool. For Google there is also a soft-power dividend: hyperscaler-authored designs shape industry standards, and the ecosystem that grows up around them tends to stay compatible with the author’s infrastructure choices. None of that makes the contribution less useful — but it is worth understanding open-source hardware as strategy, not charity.

Winners, Losers, and the Honest Limits

The clearest beneficiaries are operators of existing air-cooled facilities — enterprise server rooms, regional colocation providers, and edge sites — who gain an on-ramp to liquid-cooled hardware without capital construction. Cooling-equipment manufacturers get a design they can productize; some may welcome the demand signal, while vendors selling proprietary sidecar and rear-door heat exchanger products now face an open alternative that could compress margins.

The honest caveat is that the announcement, as reported, is a design release, not a product with published performance data. Until the specification’s capacity, tested configurations, and licensing terms are public and third parties have built against it, the practical impact is prospective. Open hardware contributions have a mixed track record: some become de facto standards, others languish without a manufacturing ecosystem. Which path this design takes depends on details the initial coverage does not yet supply.

Background

Google is one of the world’s largest data center operators and has cooled its custom TPU AI accelerators with liquid since roughly 2018 — years before liquid cooling became an industry-wide necessity. In 2025 it began contributing pieces of that cooling stack to the open hardware ecosystem, announcing a production coolant distribution unit design for the Open Compute Project, the body through which hyperscalers share server and infrastructure specifications.

The backdrop is a market-wide squeeze: AI hardware demand is rising far faster than new liquid-ready facilities can be built, leaving a large installed base of air-cooled data centers unable to host the densest equipment. Bridge technologies that bring liquid cooling into air-cooled buildings — sidecars and rear-door heat exchangers among them — have become one of the fastest-moving segments of data center engineering.

Source: Google unveils new open-source liquid-to-air cooling sidecar for air-cooled environments — Data Center Dynamics report, June 17, 2026, on Google’s open-source cooling hardware release.

⚠ What They Aren’t Saying

What the Release Doesn’t Say

Specifications: The report does not state the sidecar’s heat-rejection capacity in kilowatts, its dimensions, supported rack configurations, or coolant type — the numbers that determine which facilities can actually use it.
Publication and licensing: Where the design files live, under what license, and whether the contribution flows through the Open Compute Project or another venue is not specified.
Production pedigree: It is unclear whether this design is deployed in Google’s own fleet, and at what scale, or whether it is a reference design without an operational track record.
Ecosystem commitments: No manufacturing partners, availability timelines, or cost comparisons against proprietary sidecar and rear-door heat exchanger products are named in the coverage available at publication.

Frequently Asked Questions

What did Google announce?

According to a June 17, 2026 Data Center Dynamics report, Google unveiled an open-source liquid-to-air cooling sidecar — a heat-exchanger design that lets liquid-cooled server racks operate inside data centers built only for air cooling.

What is a liquid-to-air cooling sidecar?

It is a cabinet installed beside a server rack that pumps coolant through cold plates on the chips, then transfers the collected heat into the room’s air through a radiator-like heat exchanger. The liquid loop stays local, so the building needs no water piping.

Why do modern AI servers need liquid cooling?

Current AI accelerators concentrate so much power in so little space that moving enough air across them is impractical. Liquid carries heat far more efficiently than air, so dense AI racks increasingly ship with cold plates that require a liquid loop.

Why can't existing data centers simply add liquid cooling?

Full liquid cooling normally requires facility water loops, coolant distribution units, and mechanical plant that older buildings lack. Retrofitting live facilities is disruptive and expensive, which is the gap a self-contained sidecar is designed to bridge.

What does open-sourcing a hardware design mean?

It means publishing the engineering specification so any manufacturer or operator can build, modify, or productize it without paying licensing fees. It standardizes the design rather than keeping it as one company’s proprietary product.

Who benefits most from this design?

Operators of existing air-cooled space — enterprises, regional colocation providers, and edge sites — that want to host liquid-cooled hardware without construction. Equipment makers also gain a common reference design to build against.

How does a sidecar differ from a rear-door heat exchanger?

A rear-door heat exchanger mounts on the back of a rack and typically cools exhaust air, often using facility water. A liquid-to-air sidecar runs a closed liquid loop directly to the chips and rejects the heat into room air, needing no facility water at all.

Has Google contributed cooling designs before?

Yes. Google has run liquid-cooled TPU accelerators internally since around 2018, and in 2025 it announced it would contribute a production coolant distribution unit design to the Open Compute Project, the hyperscaler-led open hardware body.

What are the limits of liquid-to-air cooling?

The room’s air systems still absorb every watt the sidecar rejects, so total density stays bounded by the building’s air-handling and power capacity. It extends air-cooled facilities meaningfully but cannot match purpose-built liquid-to-liquid plants.

Does this eliminate the need for new AI data centers?

No. Frontier-scale training clusters still demand purpose-built facilities with facility-level liquid cooling and enormous power. The sidecar addresses the much larger population of existing buildings that need moderate liquid-cooled capacity.

What key details does the announcement leave open?

As reported, the cooling capacity in kilowatts, the design’s publication venue and license, whether Google runs it in production, manufacturing partners, and cost comparisons against proprietary alternatives were all unspecified.

What is the Open Compute Project?

The Open Compute Project is an industry organization through which hyperscalers and vendors publish open hardware specifications for servers, racks, power, and cooling, aiming to standardize designs and broaden the supplier ecosystem.

Why would Google give away cooling technology?

Cooling is not where Google competes; an immature cooling supply chain slows the whole AI buildout it depends on. Open designs grow the vendor pool, lower costs, and tend to steer industry standards toward the contributor’s architecture choices.

What should operators do with this news today?

Treat it as a signal to watch rather than a product to buy. Until the specification, performance data, and licensing are published and vendors build against them, operators should track the design’s ecosystem while evaluating existing sidecar products.