Rear-Door Heat Exchangers & Air-Assisted Liquid Cooling (The Bridge)

Chapter 5.1 established an overlapping cooling-selection envelope; Chapter 5.2 showed how airflow, inlet limits, containment, fan power, heat flux, and serviceability bound an air design. Chapter 5.4 shows why direct-to-chip liquid is the supported basis for named frontier racks with high liquid heat-capture fractions. This chapter is the country in between: the brownfield region where the existing air system cannot meet the named rack envelope but full DLC is either overkill or, more often, impossible in the building you already own — no facility water plumbed to the white space, no slab, plenum, or electrical headroom to land a CDU and a manifolded liquid rack. Rear-door heat exchangers (RDHx) and air-assisted liquid cooling (AALC) bridge that gap. They are the most under-respected technologies in the cooling stack precisely because they are transitional — and transitional is exactly what a specific, large, time-pressured class of deployment needs.

The bridge is not free. Every kilowatt you carry on a door buys a brownfield deployment in months instead of a greenfield in years, but it commits you to a dew-point margin you hold for the life of the hall, a density ceiling you will hit again in one GPU generation, and — if you choose active doors — a fan-power and acoustic budget that erodes the PUE advantage that made liquid attractive. Name that generation before you buy the door: GB300 NVL72 is the 2026 volume rack at ~132–140 kW nominal, VR200 NVL72 is ramping behind it at ~190–230 kW (analyst estimate, Kuo/Hashrate Index, 2026), and Rubin Ultra Kyber sits at ~600 kW on the 2027 roadmap. The forks ahead are passive vs active, RDHx vs AALC, chilled-water vs warm-water coil, and the hybrid rack where DLC and a door coexist; each carries a downstream cost.

A rear-door heat exchanger is a finned liquid-to-air coil that replaces the perforated back door of a standard cabinet. Server fans push hot exhaust air — typically 35–45 °C off a dense GPU rack — through the coil before it re-enters the room. Chilled or tempered water (or a glycol mix) circulating inside the coil absorbs the heat. Sized correctly, the air leaving the door is at or near room temperature: the rack is thermally room-neutral, contributing essentially zero net heat to the white space. You have not changed the servers, not touched a cold plate, not added a quick-disconnect to a single GPU. You have wrapped a conventional air-cooled rack in a liquid jacket at the one place all of its heat must pass through anyway. The OCP Door Heat Exchanger project and ASHRAE TC 9.9 treat this as a distinct cooling class precisely because it sits cleanly between air and direct liquid: liquid economics, air-cooled servers.

The critical conceptual fork — and the one most often blurred in vendor literature — is RDHx vs AALC. A plain RDHx cools the room's air: the server is still an air-cooled server, and the door simply neutralizes its exhaust. Air-assisted liquid cooling inverts this. AALC runs a closed liquid loop inside the rack — cold plates on the hottest chips, a small in-rack manifold and pump, fed not by facility water but by a self-contained loop that rejects its heat through a rack-integrated or sidecar air-to-liquid heat exchanger back into the room's airflow. In other words, AALC delivers direct-to-chip cold-plate cooling to a chip in a facility that has no facility water whatsoever — the loop never leaves the rack, and its ultimate heat sink is room air (or, in the door-HX variant, a coil that hands the heat to chilled water at the door). RDHx cools the room; AALC cools the silicon and uses the room as a heat sink. They share hardware vocabulary and they are sold by the same vendors, but they are answers to different questions, and confusing them is how operators buy a door that cannot follow them to the next GPU generation.

The first hard design fork inside the RDHx family is whether the door is passive or active, and it turns entirely on where the air-moving energy comes from.

A passive RDHx has no fans of its own. It relies entirely on the static pressure the server fans already generate to push exhaust air through the coil. This is its great virtue: zero added electrical load, no fan failure mode, nothing to fail acoustically, and a PUE contribution that is essentially just the pump and the heat-rejection plant. The cost is capacity. Server fans are sized to move air across the servers, not to overcome the substantial pressure drop of a dense finned coil on top. Published passive-door duties vary with server airflow and coil conditions. The cited Vertiv CoolLoop DCD35/DCD50 nominal 35–50 kW ratings state 21 °C entering air and 12 °C entering water; use the full model schedule, including airflow/static pressure, water flow and pressure drop, fan state, and capture target, rather than converting that example into a passive-door band. Push a passive door past its pressure budget and the server fans spin up to compensate, the IT-side fan power climbs, the servers run hotter, and you have quietly moved the energy you saved on a chiller into the servers' own fans — a PUE shell game.

An active RDHx adds its own fans (often EC fans) to the door, so the coil is no longer limited by server static pressure. This can increase the scheduled duty, but an active-door capacity is valid only for the named model at its published entering-air and entering-water temperatures, airflow, water flow and pressure, fan state, containment, and heat-capture target; do not transfer a 75 or 100 kW rating to another condition. The price is a real parasitic load — door fans are a continuous power draw, an N+1 redundancy question of their own, and a single point of failure that, if it trips, dumps the rack's full exhaust into the room with no warning. Active doors also reintroduce the acoustic problem that liquid cooling was supposed to solve: a wall of EC fans on dense racks is loud, and in some jurisdictions becomes an occupational-noise constraint. The fork is therefore product- and site-specific: passive avoids door-fan energy but spends server-fan pressure; active supplies pressure but adds fan energy, acoustics, controls, maintenance, and a fault-response obligation.

The four rows are roughly ordered by both capacity and irreversibility of the plumbing decision. Passive and active RDHx leave the servers air-cooled and demand only a chilled-water riser to the door — a comparatively cheap retrofit. AALC demands even less of the building (no facility water at all) but the most of the rack (an in-rack closed loop with cold plates). Full DLC demands the most of the building (a CDU on facility water, a manifolded warm-water loop) and is the only option that follows you up the density ramp without a re-fit. The bridge technologies exist to let you skip the building's irreversible plumbing decision for one more generation — and the consequence is that you make that decision later, under more time pressure, at a higher density, when it is harder.

Every liquid-to-air coil that runs below the room's dew point will condense water out of the air passing through it. This is not a defect — it is the same physics as the coil in a window air conditioner — but in a data center white space dripping liquid onto power-dense IT is a problem you must engineer away, not hope away. The dew-point margin is the second discipline the bridge imposes, forcing a hard tradeoff between capacity and condensation risk.

The aggressive choice is to run the coil cold — chilled water at, say, 7–15 °C — which is below the typical white-space dew point. This maximizes the temperature difference between air and coil, which maximizes heat transfer, which maximizes the kilowatts the door can carry. The consequence is active condensate management: a drip tray under every door, condensate drains routed and pitched correctly, and humidity control in the room tight enough that you know your dew point and stay above the panic threshold. A blocked drain or a humidity excursion becomes a water-on-IT event.

The conservative choice — and the one the CDU-fed and warm-water world has converged on — is to hold the coil's supply temperature above the white-space dew point, so the door operates 100% sensibly: it removes heat but condenses nothing, because no surface in the airstream is ever cold enough to reach saturation. This is the same dew-point margin doctrine that governs the secondary loop in Chapter 5.6 — a CDU feeding an RDHx will deliberately keep secondary supply a few degrees above the measured dew point. The tradeoff runs the other way: a warmer coil has a smaller approach temperature to work with, so for the same capacity you need more coil area, more flow, or more fan power — which is precisely why warm-water RDHx tends to live at the lower, not the upper, end of the active-door capacity band. Cold coil buys capacity and owes you condensate discipline; warm coil buys condensation-free operation and owes you a tighter thermal budget.

AALC is a candidate where cold-plate equipment must operate without a facility-water drop at the rack and a qualified rack-integrated or sidecar unit can reject the full rack heat into the room. That condition occurs in some leased, brownfield, edge, and metro sites, but the absence of rack water alone does not prove feasibility.

The cold plates, manifold, pump, and local heat exchanger close a factory-defined loop; the building still receives the heat through room air. Record the named equipment heat split and flux, coolant, pump and HX schedule, entering-air conditions, fan state, service clearances, and fault response. Then prove that the existing room-air and rejection plant carries the full rack duty at design climate and in the declared redundancy case.

AALC's limit is the complete local-unit and room envelope, not a portable ~40 kW ceiling. A future rack can fail because of cold-plate flux, pump or HX capacity, fan/air conditions, room rejection, serviceability, or redundancy even at the same rack kW. Reserve a viable TCS/FWS conversion path where the named refresh tail may outgrow that qualified envelope.

The most important 2026 use of the rear door is as the air-side partner in a direct-liquid rack, not as a standalone bridge. Even a fully DLC-cooled GPU rack does not put 100% of its heat on the cold plates. The GPUs and often the highest-power switch ASICs are liquid-cooled, but a meaningful residual — commonly ~10–20% of rack power — still leaves on air (the full inventory of 'what stays on air' is treated in Chapter 5.4). On the 132 kW GB200 NVL72 reference the residual is ~17 kW (~13%) of air load. The fraction is product-specific rather than constant: Lenovo's GB300 NVL72 record documents a 90/10 liquid/air split, so read the residual off the rack you actually name. Either way it is a modest share, concentrated on a single dense cabinet and repeated down every row.

This is where the door earns its place in the liquid era. An RDHx on a DLC rack neutralizes the residual air load at the rack, making the entire rack — liquid plus air — thermally room-neutral. The payoff is in plant sizing and stranded capacity. If the residual air goes to the room, the hall's CRAH/containment plant must be sized for the sum of every rack's residual, and in a dense hall that air-side plant becomes a real, separately-redundant cost that competes for the same floor and power. If instead each rack's residual is captured at its own door — fed off the same CDU and facility-water loop already serving the cold plates — you can shrink or, in the limit, eliminate the room's mechanical air-cooling plant, converging on a near-room-neutral white space whose entire heat load goes to liquid. That is the architecture several hyperscale liquid halls are moving toward: DLC for the silicon, RDHx for the residual, one facility-water loop doing both, and a CRAH plant reduced to ventilation and ride-through rather than primary cooling.

Use an evidence order, not a density band. First freeze the named rack's heat split and flux, airflow/inlet limits, and supported thermal interfaces. Second test the inherited hall's airflow, water availability and conditions, residual-room rejection, design climate, structure, service access, and redundancy case. Third qualify each candidate against its model-specific schedule: entering-air/water temperatures, air and water flow, pressure/static, fan state, containment, and capture target. Fourth compare today's result with the named refresh tail and migration plan.

RDHx is a candidate only where the server/door airflow and water schedule close; AALC only where the local unit and room can reject the full heat; DLC only where the TCS/CDU/FWS and residual-air paths close. A bridge is useful when that evidence and its lifecycle cost beat the alternative—not because the rack lands inside a portable kW band.