A plain account of how a data center's rejected heat becomes food, water, and lasting community assets — the mechanism, the proof already running on four continents, and the honest limits. In the open. No NDA.
A data center turns electricity into heat and throws nearly all of it away. Reuse has lagged in the U.S. not because the heat is absent, but because air-cooled systems made it uneconomical to catch — air is a poor heat carrier. Water isn't: by volume it carries thousands of times more. As the industry shifts to liquid cooling, that heat finally becomes catchable — and that single transition is what makes a neighboring greenhouse feasible. We're not asking the industry to change course; we're building on the course it's already on.
The standard objection is that this heat is "low-grade" — warm, but cooler than many uses need. That's exactly why district heating struggles: building networks want 60–70°C. A greenhouse is the rare customer that wants precisely what a data center most easily gives — comfortable growing air around 28°C. The mismatch that defeats other reuse is the match that makes this one work.
The cheapest megawatt-hour of heat is the one already being produced.
A trillion-dollar build-out is colliding with communities that have stopped saying yes. Public reporting now ties more than $286 billion in U.S. data-center projects to local opposition — roughly $130 billion of it in the first quarter of 2026 alone.1 A town weighing one is caught between a tax base it can't afford to lose and residents who are out of patience — increasingly about their power bill. These facilities get built with or without a given town’s blessing — the question is whether the community ends up with something real beside it, or just the noise, the lines, and the bill.
What residents want back isn't a tax-revenue slide. It's a benefit that is local (it stays with the people bearing the cost), visible (a resident perceives it without taking anyone's word), and durable (it lasts the life of the facility). This brief is about one question: whether reclaimed heat can be that benefit — and how it's held to account.
A data center's power bill, water draw, and land footprint are exactly what a town fears. Reclaimed on site, the same three become resources the community gets back — each metered, each with honest limits.
Rejected heat at roughly 35–50°C, carried next door through a sealed loop that never touches the servers, holds a greenhouse at growing temperature year-round. The thermodynamics are standard; the full math lives on the engineering page.
The limit: less heat is needed in summer than a campus rejects — we use a sliver, the rest is unchanged.Closed-loop irrigation recaptures most of what the plants don't drink: one water system, four climate configurations, a single published net-withdrawal number. Net-zero town-water draw in temperate Virginia; on the coast, the job inverts — the greenhouse absorbs stormwater instead.
The limit: it doesn't change the data center's own water use — that's the operator's footprint, already falling 31–52% as liquid cooling replaces air.2On-site composting turns greenhouse waste back into living soil — enough to keep the beds self-sustaining, with the surplus going back to the town's gardens, parks, and schools. The full plan and figures live in the build hub.
The limit: surplus compost volume is an engineering design target† until the first season is measured.Food is the flagship because a town can taste it. But the heat is a platform: where a greenhouse isn't the first move, the same loop can warm a rec center, a municipal pool, or nearby buildings — heat in, food out, and more besides.
The fastest way to lose a careful reader is to blur these together. So we don't. Here is the honest division — where each claim sits, and how you can check it.
A claim you can audit is not greenwashing. A claim you cannot is. We would rather under-promise and show our work.
The sharpest objection to a project like this isn't technical. It's that a greenhouse becomes a green fig leaf — a photogenic distraction that buys approval while a facility's real impacts continue. That critique is correct about the danger. Which is exactly why the project is built to be measured, not believed — so the benefit can't quietly turn into theater.
The safeguard is metering. We tie the benefit to third-party-metered, publicly reported delivered heat and crop output — the same logic the best policy proposals use, binding any incentive to verified energy actually delivered rather than promised. If the heat doesn't flow and the food doesn't grow, the condition isn't met, and the record shows it. The meter is what keeps it honest.
It doesn't have to be "build freely" or "stop building." The data center can be approved on the term that it co-locates a community greenhouse — written into the Conditional Use Permit as an enforceable condition. That's what turns a one-time promise into a durable asset: on the record, metered, and lasting the life of the facility.
Co-location of the greenhouse is a term of the CUP, not a side promise.
Delivered heat and crop output are third-party-metered and reported on the record.
The condition carries teeth if the benefit isn't delivered — the consequence is defined up front.
It lasts the life of the facility, so the benefit stays with the people bearing the cost.
Between 2022 and 2026, controlled-environment farms with enormous capital behind them went bankrupt. We're not blind to it; we built the model to do the opposite of what killed them. We took the survivors' discipline — one anchor crop, secured offtake, a right-sized build — and paired it with the one advantage none of them had: heat that costs nothing. The farms that died were paying for the single input a data center throws away for free.
And there's a deeper difference. This greenhouse doesn't have to turn a profit to succeed — it's insurance on the project beside it, which is exactly what lets it absorb a bad harvest and still cost a rounding error against the facility it protects.† The thing that has to succeed isn't the produce. It's the proof.
A greenhouse built for roughly $5.4 to $16 million†, sized to be trivial against the billions it sits beside, changes the answer a community gives. The mechanism is proven. The benefit is metered. The limits are stated plainly. It's a farm next door — and a town can verify it from the road.
1 Data Center Watch / 10a Labs, incl. Q1 2026 report; reported by NBC News & Fortune, 2026. 2 Microsoft-led life-cycle assessment (Nature, 2025): liquid cooling cuts the cooling footprint ~31–52% vs. air. † Internal Intelligent Harvest design target, not a measured result; figures reflect 2025–26 estimates and are confirmed by third-party metering once built. Additional figures drawn from public reporting (Moody's; NREL; Ohio River Valley Institute).
The full research brief, the deal structure, and the build documents live behind the Build Hub — for the partners and officials we’re already in conversation with. It isn’t for everyone’s eyes. Meet with us, and we’ll lay all of it out.
Request accessWhether a data center is coming to your community or already there, we’ll think it through with you — what the heat could grow, and what it would and wouldn’t do for your town. No obligation, no sales pitch.