A data center doesn't have to drain the town if you harvest the heat. harvest the water. harvest the soil.

A data center takes a town's power, its water, and its land. Intelligent Harvest hands all three back — as harvest. We co-locate a community farm — a working greenhouse — on the data center's fence line and put its rejected heat to work growing food the town can see, taste, and verify.

Powers the cloud. Feeds the town.

Scroll
What's at stake

Too often, a town gets the strain — and a banner.

A data center brings a tax base, and it brings the noise, the truck traffic, and worry about the power bill. Today most towns are left holding the strain with little to show for it beyond a logo on a scoreboard. It doesn't have to go that way. The land along the fence line can hold something a community actually keeps: a working greenhouse the neighbors can walk into.

How it works

We lead with the greenhouse.

A year-round community greenhouse sits on the data center's fence line. The heat a server hall would vent to the sky — warm, not scorching — is carried next door through a sealed loop and used to grow food all winter long. Real strawberries in January. Steady greenhouse jobs. A benefit a resident can verify from the road, without taking anyone's word for it.

The greenhouse isn't the business — it's the proof. It's the part of the project a town can taste.

Walk the heat's journey
Sunlit rows inside a community greenhouse
Staple · The pound engine

Snacking Tomatoes

The crop that carries the harvest — the one greenhouse tomato that pays, grown on heat the servers threw away.

Staple · The fresh crew

Greens & Herbs

Lettuce, leafy greens, and cut herbs — picked in the morning, on a plate across town by dinner.

Community crop · The pound engine

Cucumbers

Heavy, fast, and cheap to grow — the crop that fills the community’s share by the crate.

Story crops · The delight

Strawberries & Gourmet Mushrooms

Real berries in January and a cool, dark mushroom room — small rooms with a big story, never the whole farm.

What the harvest actually feeds

How much produce is 695,000 lbs† a year?

~2,700 people’s fruit and vegetables. Every. Single. Day.

10,800

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. A person eats roughly 260 lb of fresh fruit and vegetables a year (USDA). So:

695,000 lb produce / year†
÷  365 days≈ 1,904 lb / day ≈ 863,700 g
÷  80 g one WHO serving≈ 10,800 servings / day

695,000 lb / year
÷  ~260 lb one person’s year (USDA)≈ 2,700 people, every day

of which  ≥ 15% the community covenant · donated≈ 104,000 lb† ≈ 400 people

That’s not a truckload passing through on the interstate. It’s ~10,800 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. And at least 15% of it is the town’s by covenant: about 400 people’s produce, donated before a pound is sold.

Modeled design targets (†) for a ~2.5-acre flagship greenhouse at maturity, Richmond-class climate — central estimate 695,000 lb/yr, honest range 561,000–809,000 lb by crop-mix and season. Serving size per the WHO (80 g). People-fed at USDA per-capita fresh fruit-and-vegetable availability, ~250–270 lb per person-year (~260 used): 695,000 ÷ 260 ≈ 2,700; the community covenant of at least 15% ≈ 104,000 lb ≈ 400 people. 695,000 lb ≈ 315,250 kg ≈ 863,700 g per day across 365 days. December delivers ≈44% of a mean month — winter output is real but leaner. Figures vary by site; every modeled figure holds its dagger until a meter verifies it.

The three harvests

Three things a data center wastes. Three we put to work.

A facility's power bill, water draw, and land footprint are exactly what a town fears. The same three resources, reclaimed on site, are what it gets back.

Harvest the heat

Reuses rejected heat.

Low-grade heat — roughly 35–50°C — that would otherwise blow straight up into the sky becomes a year-round growing climate next door. We don't make energy. We catch what's already being thrown away.

Standard heat-exchanger + buffer tank. Two loops, one wall, never mixed. Read more
Harvest the water

One system, four climates.

Closed-loop irrigation recaptures what the plants don't drink. Net-zero town-water draw in temperate Virginia, net-positive in the desert, a stormwater sink on the coast — committed where the gear is proven, metered everywhere.

Net-positive and stormwater modes are under validation by region.† Read more
Harvest the soil

A loop that closes.

On-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 own gardens, parks, and schools.

Surplus compost volume is an engineering design target.† Read more
See it for your town

Real numbers in your hometown.

A data center is coming, or already here — and here is the number that matters: one flagship greenhouse runs on the rejected heat of less than 1.5 MW of IT†. Not the campus — a sliver of it. Choose how many greenhouses, and see what that sliver grows — 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.

Flagship greenhouses 1greenhouse

One flagship runs on the rejected heat of ~1.42 MW† of IT — about 1.4% of a typical 100 MW campus, which throws away enough heat for ~70† of these.

1,390,000lbs of food / year
Snacking tomatoes, greens and herbs, cucumbers, strawberries, gourmet mushrooms — grown across town, not trucked across the country. Enough fresh produce for about 2,700 people’s fruit & vegetables every day of the year — at least 15% of it the town’s by covenant, about 400 people’s worth, donated before a pound is sold.
~16local jobs
Year-round and rooted in place — the kind of work a server hall can’t provide.
1,400tons CO₂ avoided / year
Heat reused instead of burned — about 304 cars taken off the road.
5,260MWh of heat put to use
Warmth that was venting straight into the sky — a sliver of what the campus rejects, the rest unchanged.
Ask in plain language

What would this mean for your town?

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 flagship greenhouse at maturity (695,000 lb† of produce — honest range 561,000–809,000 lb — about 16 people† employed year-round (band 15–30, checked against nine working greenhouse operations at the same footprint); ~700 tons CO₂ avoided, held at the conservative end while its re-derivation stays open; and ~2,630 MWh† of heat reused, from an annual band of 2,540–2,720 MWh) 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. December delivers ≈44% of a mean month. Heat basis: ~0.75 MWh captured per MWh of IT load, ≈747 kW† delivered per MW at the greenhouse manifold. CO₂ vs. natural-gas heat at ~0.18 kg/kWh. People-fed at USDA per-capita fresh fruit-and-vegetable availability (~260 lb per person-year): 695,000 ÷ 260 ≈ 2,700 per flagship; the community covenant of at least 15% ≈ 104,000 lb ≈ 400 people, donated; each flagship runs on the rejected heat of ~1.42 MW† of IT (1,058 kW design-night demand ÷ 747 kW delivered per MW), so a typical 100 MW campus could feed ~70† of them and three draw under 5% of it; 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.

Beyond the greenhouse

One river of heat. Used in order, down to the last degree.

We lead with the greenhouse. We don’t stop there.

The water leaves the greenhouse still warm — so we don’t send it home. It runs down a cascade: each use takes what the last one left, and the plant gets its water back cooler than it gave it. No heat pump anywhere, nothing lifted or boosted. A data center rejects enough heat to run a whole park; the park takes what the town needs and leaves the rest.

A person resting in a warm outdoor pool
01 The hottest water · a leased module

The springs

The warmest water off the exchanger is exactly what a thermal spa wants — the Nordic-bath model, outdoor pools steaming in January on heat that was going into the sky. Run by an operator, on a lease that pays the park.

A glass greenhouse in a field
02 The first duty · the covenant

The community farm

The greenhouse is the flagship because a town can taste it. It takes its warmth through under-bench and floor loops, grows all winter, and puts at least 15% of the harvest in the town’s hands before a pound is sold. A propagation house alongside starts the seedlings the region’s farms and forests need.

Fish in clear, moving water
03 The flat leg · a leased module

The fish house

Water comes out of the greenhouse at about 80 °F — the temperature warm-water fish grow in. A fish house holds it there and turns it into protein; in Norway, data-center heat already runs trout and lobster farms. An operator raises the fish; the park keeps them warm.

Beer being poured at a barCherry tomatoes on a wooden board
04 Where the harvest goes · the channel

The table and the store

A restaurant and a farm store on the same ground the food was grown — picked in the morning, on the plate that night. The shortest supply chain there is, and the place a town meets its data center in person.

An older couple laughing together at home
05 The return leg · the land

The neighborhood

The last, gentlest warmth runs under the floors of homes built on the return leg — radiant heat, fresh food across the street, warm pools down the lane — before the water goes home to the plant. Then it starts again.

We lead with food because you can taste it. The rest of the park is what the heat does on its way home.

Why you can trust it

Charm on top, evidence underneath.

A project whose entire pitch is "a benefit you can verify" has to be the first to submit to verification. So we hold ourselves to it: delivered heat and crop output are third-party-metered and publicly reported — on the record, not advertised by us. Every internal projection on this site is marked plainly as a design target (†) until built performance confirms it. A claim you can audit is not greenwashing. A claim you cannot is.

Virginia agrees. HB 323 (2026) — the first state law in the country directing action on data-center waste-heat reuse — passed the Senate 39–0. The most resented building in America is also the one both parties want to fix, and this is the fix.

The full account

What reclaimed heat can do for a town.

We wrote the whole account in the open: the mechanism, the proof already running on four continents, the honest limits, and how a greenhouse — or a heated pool, or a warm public building — becomes a lasting community asset. No NDA, no spin.

Who it's for

Three rooms. Three honest pitches.

The same project answers to three audiences — and we say something different, and true, to each.

The team

Different companies. One build.

An HDD and energy operator. The Mid-Atlantic’s tank leader. A founder who tells the story. Three companies meeting at one fence line — with the crews, rigs, and tanks to put a town’s heat to work.

Meet the team
Get in touch

Bring your town, the project, the questions.

Whether 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.

Built in Lynchburg, Virginia — close to the communities and the build-out this model is built to serve.