The same hot water cools the servers and warms a working farm next door — and the town that was handed a power bill and a fight gets food, jobs, and something it can walk into instead. The cloud keeps every watt of its capacity. The community finally gets its half of the bargain. Not the data center or the town. Both.
Capture a thin sliver of the waste heat a data center already throws away, and it becomes a year-round greenhouse beside the campus. The servers draw the same power either way — the town just gets the upside.
Greenhouse figures are engineering design targets for a ~2.5-acre, four-zone flagship · CO₂ avoided vs. natural-gas heat at ~0.18 kg/kWh · illustrative




The waste heat, the crops, even the cooling change with the climate. What never changes is the thing we solve: a community that won't say yes. Here's exactly what that looks like across the four climates defining the fight right now — starting on the coast, where the water question is loudest.
Here the water problem inverts — not drought but flooding, sinking ground, and a stressed aquifer. Hampton Roads is sinking about twice as fast as the sea is rising, and the region is spending $1B+ to refill the Potomac Aquifer it can't keep over-drawing.
A campus that becomes a stormwater sink instead of a flooding liability — capturing intense rainfall, running on rain and condensate, never pumping the aquifer. Aquifer-neutral we can stand behind today; aquifer-positive the aim. Our committed lead market.
The largest data-center market on Earth — and the one turning fastest. Voter comfort with a data center nearby fell from 69% in 2023 to 35% in 2026. The objection isn't power. It's "what do we get?"
A greenhouse the town can walk into — strawberries, oranges, fresh ginger and gourmet mushrooms — feeding Data Center Alley itself, same-day, with zero food-miles. The most relatable possible answer to the benefit gap.
A statewide drought emergency, the Great Salt Lake collapsing, and a hyperscale campus whose heat critics liken to "23 atomic bombs a day." Now every new data center is being forced to answer for its water and its heat.
A closed-loop greenhouse that recycles most of its own water, cools without evaporating, and — where brackish groundwater allows — uses the waste heat to make supply. The heat island turns into food, and the water answer is one you can put on a meter.
Long, hard winters where a data center vents its waste heat straight to the sky — while the same campus still faces the same neighbors saying no.
Free heat becomes a year-round harvest — strawberries in February, oranges fruiting in the dark. Proof a windowless box can give a town something it could never grow on its own.
The crops and the cooling flex by site. The permission doesn't.
You're not wrong to ask what a windowless box and a heat plume give back. Lower electricity bills? Rarely. Lasting jobs? A handful. You deserve a real answer — not a tax-revenue slide and a logo on a little-league jersey.
You're not the villain. The AI we all use runs on this infrastructure — and you've been handed a permitting fight you can't message your way out of. You need goodwill that's genuine and visible, not another press release nobody believes.
You're right to want a real answer. You're also right to be skeptical of one. So we built ours to be audited, not believed — metered food and jobs your community can walk into, and a way to hold us to it.
See the deal — and how to hold us to itYou're not the villain — you've been handed a permitting fight you can't message your way out of. You need goodwill that's genuine and visible, not another press release nobody believes. A greenhouse beside the campus is the one that's real.
See the operator caseAttach a benefit to the permit you can actually point to — third-party-metered food and jobs the community can walk into — and the next data center becomes an easier yes instead of the next fight.
See the case for cities & officialsEvery data center is already a heat plant — it just throws that heat away into the sky. We capture it, and grow something with it.
A sealed loop draws the low-grade waste heat off the cooling system. It never touches the servers, and it never changes how the data center runs.
That heat warms an adjacent community greenhouse, growing fresh food year-round — on land that was only ever going to host a fence.
The town gets food, real jobs, and a place to bring its kids. The data center finally has a story worth telling — and the permit fight becomes a ribbon-cutting.
What the harvest actually feeds
~900 people’s fruit and vegetables. Every. Single. Day.
4,660
servings of fresh fruit & vegetables a day
365 days a year · never a season
The math, in full
The World Health Organization counts a serving of fruit or veg as 80 grams — about a handful, or one medium orange. Five of them (400 g) is a full day. So:
That’s not a truckload passing through on the interstate. It’s ~4,660 servings of real produce a day — the berries in a kid’s lunch, the greens on a dinner plate — grown a few miles away instead of three states over, every single day of the year.
Illustrative design targets for a ~2.5-acre, four-zone flagship greenhouse. Serving size and daily intake per the WHO (80 g per serving; 400 g / five servings recommended daily). 300,000 lb ≈ 136,078 kg ≈ 372,816 g per day across 365 days. Figures vary by site.
A data center is coming, or already here. Move the slider to its size, and see what the heat it currently throws away could grow instead — in food, jobs, cleaner air, and warmth put to use. Every number here is a published engineering estimate, scaled honestly. Nothing inflated. You can check all of it.
About the size of a typical hyperscale campus — the electricity of roughly 100,000 homes.
Tell us your town and what worries you. We’ll explain — honestly, in plain words, using the numbers above — what a co-located greenhouse would and wouldn’t do for your community.
Generated to be plain and honest, grounded in the estimates above. It won’t promise lower bills — the honest answer is that’s complicated — and it will say where the limits are.
Estimates scale from a ~2.5-acre, four-zone flagship greenhouse (~300,000 lbs, ~20 year-round jobs, ~700 tons CO², ~3,000 MWh heat reused per year) co-located on the host campus, scaled with the practical greenhouse capacity a site of this size can support and capped at three flagship modules. Reusable-heat basis ~0.75 MWh per MWh of IT load. CO² vs. natural-gas heat at ~0.18 kg/kWh. People-fed equivalent at the WHO-recommended 400 g of fruit & vegetables per day (~322 lbs per person-year); car-equivalent at the EPA average of ~4.6 t CO² per vehicle-year. All figures are engineering design targets, not guarantees — the full basis is in the engineering page and the research brief.
A drop of water and a unit of heat walk you through everything on this page — the loop, the wall, the tank, the strawberry in January — in plain language a fourth-grader can follow. Built for kids and classrooms; quietly useful at council meetings too.
Follow the leftover heat from a humming server all the way to a winter strawberry.
Take the trip →The other half of the loop — how giving warmth away is exactly how the servers stay cool.
Find out →Same physics as the engineering page. Considerably more high-fives.
A flagship is roughly two and a half acres of greenhouse beside the campus — four climate zones growing food all year, warmed almost entirely by the data center next door. Not a science project. A real farm, open to the people it feeds.
Year-round berries the whole town knows by name — the front door of the farm.
Warm-climate roots that thrive on exactly the gentle, steady heat a data center throws off.
Prized varieties that need no sunlight at all — just warmth, and plenty of it.
Lemons and oranges through the dead of winter — the kind of thing people drive to see.
Data-center heat already warms greenhouses, homes, and farms across four continents — and a wave of U.S. projects is now converging, independently, on exactly this model. The open question was never whether it works. It's who does it cleanly, at community scale.
Hive Digital's 32 MW campus heats a ~90,000 sq ft greenhouse, growing vegetables near the Arctic Circle.
Meta channels recovered server heat into the municipal district-heating network for thousands of homes.
SAIHEAT already runs liquid-cooled compute heating a local greenhouse — the U.S. pattern, live today.
Fidelis's Monarch campus would pair up to 1,000 MW with greenhouses and captured CO₂ — the model at scale.
Sources: Uptime Institute; Visual Capitalist / Hive Digital; ReImagine Appalachia · 2023–26
The loop, the heat grades, the buffer, the deliberately small heat pump — and the open items most decks skip. We're recruiting an engineer of record, and if the physics doesn't hold, we'd rather you tell us now.
Read the researchPermission, not power, is what's stalling the build-out — communities are organizing against projects that hand them nothing but power lines and a bill, and they're winning. The farm next door changes that math: the town gets something real, and the operator gets the yes it couldn't otherwise buy.
Sources: Data Center Watch / 10a Labs; McKinsey · 2025–26
"I believe AI is one of the most genuinely useful advances of our era — and I love this planet. For a long time those two things felt at war. Intelligent Harvest is the peace I went looking for, couldn't find, and decided to build."
Contractor interested in getting involved? Operator looking to build? City official looking for a greener option? Reach out — we read every note personally.
The full document library — the research, the proof, the model, and the paperwork — lives behind the Build Hub. Access is granted to partners with an NDA on file.
Request Build Hub access →