Every build in the line does the same friendly thing: computing happens, warmth gets caught instead of thrown away, and plants grow on heat that was already paid for. The only question is how many people you’re feeding.
For the homesteader who wants fresh herbs at arm’s reach — and a warm, green room to read in while the snow falls.
A backyard greenhouse kept warm through a Virginia winter by a single quiet compute node — the whole big idea, at a scale one family can own, prove, and eat from.
The node heats the growing space directly; the roof catches rain for the beds. And it earns while it warms — though we’ll say it plainly: a heat pump delivers cheaper BTUs. The Pod’s case is that its warmth comes with a small paycheck attached, not that it’s the cheapest heater at the store.
Built for homesteaders, food ministries, schools, and restaurants that want winter greens with their name on them.
| Greenhouse | Palram Canopia Glory 8×12 (~$2,845 list) |
| Heat source | Heatbit Maxi Pro compute node, 1,500 W ($1,499 list) |
| Water | roof catchment → rain barrel → beds |
| Power | standard residential circuit |
| Season | winter greens & herbs, 12 months † |
| Time to grow | a weekend or two of assembly |
For the neighborhood feeder — a food bank, church, or campus putting fresh produce on a few hundred plates, every single day, even in February.
| Compute | 18 hydro-cooled ASICs, 40-ft high-cube |
| IT load | 102 kW |
| Recovered heat | ~97 kW at 45–55°C |
| Greenhouse | ~6,500 sq ft, double-poly gutter-connect |
| Electrical | 480 V, 3-phase, 200 A service |
| All-in capital | $550–700k † |
| Deployment | 4–6 months † |
A 40-foot container of hydro-cooled computing beside roughly 6,500 square feet of greenhouse. Big enough to feed programs and paychecks; small enough to arrive on a flatbed.
Hydro-cooled machines hand their warmth over as hot water, naturally and nearly silently — no fan roar next to your nonprofit. At full hum the container delivers about 97 kW of warmth at 45–55°C, which happens to be exactly what a greenhouse’s hydronic heating wants. That carries the glass through a central-Virginia design night, with margin.
This is the build for the food bank that outgrew a Pod and the town that isn’t ready for a Campus — churches, school districts, community colleges, co-ops.
For the visionary who wants their town to taste its own data center — a market stand, school cafeterias, and 900 neighbors eating from the fence line.
Production greenhouses at an operating data center’s fence line, warmed by the heat it already rejects. Campuses are numbered by greenhouse — Campus 1, 2, 3 — because the honest measure of scale is how much glass the warmth can carry.
The flagship greenhouse is a four-zone house of roughly 2.5 acres: winter strawberries, turmeric and ginger, gourmet mushrooms, and a citrus grove the public walks through. One greenhouse of this design reuses on the order of 3,000 MWh of rejected heat a year† — and we change nothing about the servers. One greenhouse draws well under 1% of a large facility’s power, and we’ll never pretend otherwise.
This is the build for towns where a data center is coming — the option you control, negotiated into the deal, so the benefit is real, metered, and permanent.
| Siting | fence-line co-location, sealed thermal main |
| Flagship house | ~2.5 acres, four growing zones |
| Heat reused | ~3,000 MWh / greenhouse / yr † |
| Produce | ~300,000 lb / yr † |
| Jobs | 14–20 year-round † |
| Verification | BTU meter at the transfer station |
| Scale-up | Campus 2, Campus 3 — add glass, not promises |
Two loops trade warmth through a wall of steel and never share a drop. Server water stays server water; greenhouse water stays greenhouse water.
A tank holds warmth until the plants ask for it, and a small conventional heater covers the coldest nights — so a quiet hour for the servers is never a cold hour for the crop.
A BTU meter at the handoff turns the promise into a number anyone can read. Verified benefit, not vibes.
