Cogeneration Server Rooms: No More Wasted Server Heat in Industry and in Our Homes

Large data centres have their place: banking, healthcare, public administration and the training of the largest AI models need physically protected, centralised facilities. The problem lies elsewhere. Most of them burn megawatt-hours of electricity on computing, then spend tens of percent more on cooling just to dump the heat into the air. Many large facilities also use evaporative cooling and evaporate huge amounts of water in the process. Meanwhile homes, apartment blocks, greenhouses, breweries, dairies or other industrial plants and municipal swimming pools pay for gas, electricity or district heat to warm water to exactly the temperatures that servers treat as waste.

The answer is modular, distributed server rooms: instead of one huge hall, thousands of small modules in homes, apartment blocks, plants and pools. Understood this way, a cogeneration server room turns one kilowatt-hour of electricity into two products: computing and heat. Distribution makes it possible to use waste heat widely, right where it is produced, to use the idle connection capacity of existing buildings instead of waiting for new grid connections, and to save the water that large data centres evaporate in cooling towers.

The point is not to replace big data centres but to complement them where it makes sense: bulk, less sensitive computing can run inside buildings that need heat anyway.

The idea is simple: liquid-cooled compute modules are placed where heat is needed and connected to a heat buffer, a heat pump, energy storage and the building management system (BMS). The cost of cooling IT becomes a source of heating. Below is the concept through the lens of physics, hydraulics and automation, without the marketing gloss.

🛠️ 1. IT reality: what such a server computes and why it can last 7–10 years

• 🔒 What the module does not do. Critical systems (banks, healthcare, government), latency-sensitive transactions and training of giant language models, which requires thousands of GPUs linked by NVLink or InfiniBand, stay in large data centres.
• ⚙️ What it does. Most cloud traffic is bulk, asynchronous “grunt work”: inference for everyday AI agents, image and video generation, 3D rendering, media transcoding, batch processing. These jobs do not need ultra-low latency between nodes, just cheap power and effective heat removal.
• ⏳ Lifetime. Three to four years is mostly corporate depreciation logic: working hardware is replaced to pack more power into the rack. With 100% liquid cooling there are no thermal shocks, and power can be capped. Under such conditions a lifetime of seven to ten years is a reasonable design assumption, and older generations handle smaller models and batch jobs well.
• 🔌 Operator model (plug & play). The building owner provides the connection, internet and takes the heat. A remote operator manages the rack, service and replacement of compute cartridges.

🌡️ 2. Physics and hydraulics: heating the building is cooling the processor

Liquid cooling (direct-to-chip or immersion) removes the fans, so the module runs about as quietly as a heat pump. Almost all electricity drawn by the processors turns into heat. In typical liquid-cooled modules the recovery buffer runs at 25–40°C, and in specialised high-temperature modules up to 50°C. This wide range lets most of the heat be used directly, with a heat pump only where a warmer medium is needed. At every scale the core is a heat buffer and a water-to-water heat pump:

1. 💧 Buffer and direct use. Server coolant releases heat into a 25–40°C buffer (up to 50°C with high-temperature modules). Without any compressor it can preheat mains water from 10°C to 30–35°C (up to about 45°C with high-temperature modules) or feed low-temperature loads: greenhouse soil heating, a pool basin, underfloor heating or low-temperature panel radiators (these usually need to be oversized because they run at a low temperature). A backup boiler or electric heater tops up the buffer, not the IT module itself.
2. 🔥 Raising the temperature. Where a warmer medium is needed (domestic hot water at 55–60°C, older radiators, some process heat) a water-to-water heat pump uses the 25–40°C buffer as a stable, warm source (instead of −10°C winter air), so in favourable conditions COP reaches 5.5–7.0, and more with a warmer buffer.
3. ♻️ Symbiosis. By drawing heat from the buffer, the heat pump also cools the liquid returning to the processors. Heating the building and cooling the server are one thermodynamic process.

🏠 3. Micro scale: a single-family home, 3–5 kW module

• ❄️ Winter: a 3–5 kW module (72–120 kWh of heat per day in continuous operation) can cover the base load of a modern home’s underfloor heating and hot water.
• ☀️ Summer: hot water for a family of four takes about 5–6 kWh a day. Surplus heat goes to a garden pool or greenhouse.
• 🌬️ Emergency dump: when nothing else can take heat, a simple dry cooler or AC unit rejects it outdoors.

🏭 4. Macro scale: agriculture and food industry, heat 365 days a year

• 🍅 Greenhouses: 25–40°C heat goes straight into root-zone heating, with no heat pump.
• 🥛 Dairies, breweries, food processing and other industry: process water (pasteurisation, brewing, CIP cleaning) is heated all year. Modules provide free preheating from 10°C to 30–35°C (higher with high-temperature modules); heat pumps top up to process temperatures.
• 🛡️ Hygiene: heat passes through certified plate exchangers in the plant room, so servers are fully separated from food production zones.

🏢 Multi-family buildings: heat for the whole community

An apartment block or housing estate needs heat all year round, because domestic hot water (DHW) and its circulation run in summer too. The modules connect to the substation or the estate boiler room in two ways, often combined:

• 💧 Directly: the 25–40°C buffer preheats mains water for DHW (from 10°C to 30–35°C). This is the cheapest part of the energy and needs no compressor. The same buffer can feed low-temperature systems such as underfloor heating in newer buildings.
• 🔥 Boosted by a heat pump: a water-to-water heat pump with the buffer as its source lifts water to 55–60°C for DHW and to the parameters of the heating system (usually after lowering the supply temperature or a thermal upgrade). A cascade of several micro heat pumps adds redundancy.

The existing substation or boiler stays as peak top-up and backup, so residents never notice an outage. Modules placed next to the substation also use the building’s existing electrical connection, and their BMS-controlled power yields to induction hobs and EV chargers in the evening peak.

🏊 5. Swimming pools and water parks: the thermodynamic “holy grail”

Processor coolant (25–40°C) is as warm as pool water (27–32°C) or warmer, and pools need heat all year. Heat from the plant room flows in three streams:

1. 🌊 Pool basin: the IT buffer heats 28°C pool water through a titanium exchanger. No compressor, just a small circulation pump.
2. 🚰 Make-up water: regulations require roughly 30 l of fresh water per visitor per day. 10°C mains water is preheated to 25–30°C for free.
3. 🚿 Showers (55°C) and hall ventilation (around 32°C): handled by a water-to-water heat pump using the buffer as its source.

Liquid-cooled racks are sealed, so they do not draw in humid, chlorine-laden air, and titanium exchangers protect the system from pool chemistry.

🔄 6. Deployment: return-pipe integration, swarm architecture, backup

• 📉 Return-pipe integration: the module heats water returning from the building before it reaches the boiler or substation. Most of the year the old source stays off; in frost it only tops up.
• ⚠️ Condensing boilers: too high a return (above roughly 30–35°C) stops condensation. Controls either let the modules take the whole load or divert heat to hot-water preheating.
• 🐝 Swarm architecture: instead of one big server with one heat pump, a cascade of small modules (e.g. 20 × 5 kW), each with its own micro heat pump. Servicing two of twenty means 10% less output and no single point of failure.
• 🔥 Backup: if compute jobs stop, BMS-controlled valves route water through the existing boiler, substation or an LPG peak boiler.

🔋 7. Protecting the grid connection: PV, BESS, Modbus and BACnet

A building’s power profile is uneven: induction hobs and EV chargers at home, machine start-ups in a workshop, pumps and attractions at a pool. A constant server load could trip main fuses or trigger contracted-capacity penalties. So the module works with PV, battery storage (BESS) and HEMS/BMS/EMS over Modbus TCP or BACnet IP:

• PV powers servers during the day and charges storage with surplus.
• BESS performs peak shaving: it detects a spike in building demand and discharges, shaving that peak so grid draw stays below the contracted capacity.
• The BMS sees the module as a controllable load (power throttling), a heat source and a thermal buffer.

⚡ An answer to the shortage of grid connection capacity

Grid operators increasingly refuse new connections or make investors wait for years. Meanwhile, in existing buildings the contracted capacity sits idle for most of the day: homes, schools, plants and pools use their full capacity only in short peaks. Distributed cogeneration server rooms use and optimise this existing capacity instead of requiring new connections and new halls.

• ☀️ Local PV surplus: solar energy that at sunny noon would be exported for next to nothing or curtailed by the inverter powers computing on site and charges the heat buffer.
• 📈 Better use of the connection: a BMS-controlled module fills consumption valleys, and during building peaks it throttles down or the battery takes over.

📊 8. Summary: comparison of building types

Power and heat-use figures are conceptual assumptions for analysing a specific site, not guaranteed results.

✅ Conclusions

Distributed, modular data centres do not replace large, secure facilities; they take over the bulk work that does not need them. Placing that compute where a grid connection already exists and sits underused, absorbing local PV surplus, and year-round heat demand, with liquid cooling, swarm architecture, return-pipe integration and open protocols, turns the cost of cooling processors into savings on heating, and saves the water that large data centres would otherwise evaporate in cooling towers.

🔮 Next topic: working with dynamic tariffs and virtual power plants (VPP): ramping up compute and charging the heat buffer when energy prices are zero or negative.