When a data center comes to your community, it brings a tax base — and it brings strain. There’s a way for the town to come out ahead: co-locate a community greenhouse on the facility’s waste heat, and the warmth it was throwing away grows food the whole town can see, taste, and verify.
Your residents’ anger is real and, in 2026, increasingly about their power bill — more than half of Americans now blame new data centers for rising electricity costs, the top concern on the list.1 We won’t pretend a greenhouse fixes a rate (the causation is genuinely complicated, and honest analysts say so2). But the deeper grievance — the town absorbs the costs while the benefits go elsewhere — is real, and it’s what you’re being asked to answer.
Block it, and the project and its tax base move to the county that says yes; the town fought hard for an empty table. Wave it through, and the community is left with the noise, the lines, and the bill — with little to show for it. The deciding factor, again and again, is genuine local support: in Maine in 2026, even after a contested statewide fight, the one project the governor moved to protect was the one a community actually wanted.3 The postscript is the part written for you, though: that operator later walked away, and the town could enforce none of what it had been promised.4 Local support decides the politics. Permit conditions decide what your town actually keeps.
We’re pro-community. These facilities get built with or without us; our only job is making sure your town ends up with something real beside it instead of just the power lines, the traffic, and the bill. So here’s the honest scope, stated before you ask: a typical large facility draws ~100 MW and throws nearly all of it away as heat. One greenhouse uses a thin sliver of that — well under 1%. We change nothing about how much power the servers draw or how much water they use. We will never pretend otherwise.
That honesty is the whole point. A project whose entire pitch is “a benefit you can verify” has to be the first to submit to verification — which is exactly what makes it something a community can trust.
It doesn’t have to be “build freely” or “stop building.” Co-locating a community greenhouse can be written into the Conditional Use Permit as an enforceable condition. That turns the heat the facility was wasting into a year-round asset the community can see, taste, and point to. In many of the rural counties these campuses target — the same places losing a grocery store to the next town over — a steady local source of fresh produce is a benefit residents feel at the dinner table, not just on a balance sheet, at a moment when the cost of food is on everyone’s mind.
It’s the rare 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). And in Virginia, it now comes with the Commonwealth’s explicit backing: HB 323 (2026) — the first law of its kind in the country — directs the Department of Energy to connect data centers with exactly this kind of nearby heat user, with a strategic plan due to the General Assembly September 1, 2026. Writing heat reuse into a permit is no longer a novel ask; it’s the direction the state is already moving. For the residents who’ll ask you hard questions, we wrote a page that meets them honestly.
A data center is one of the few buildings in your jurisdiction built to survive a blackout — it carries backup power most of the community doesn’t. Designed for it, the greenhouse beside it can share that backup: a heated, lit site still growing food when an ice storm or heat wave takes the grid down. For an emergency-management plan, that’s a powered, sheltered, food-producing asset sitting on the fence line. We’d set the particulars with the engineer of record — we name it because it’s real, and because no sponsorship banner can match it.
The sharpest objection to a project like this is that the greenhouse becomes a green fig leaf that buys approval while the real impacts continue. The project is built to be measured, not believed — the benefit is tied to metering, so it can’t quietly become theater.
A ban leaves the table empty. This gives you something to say yes to — and a paper trail that protects you for having said it. Pressure-test every line before you sign — as a careful official will — and the condition language you write becomes the template the next county copies. The thorough jurisdictions are the ones that end up setting the standard; we’d like you to be one, and we want you to hold the language to the fire to get there.
Design target Figures are internal design targets for a ~2.5-acre flagship, not measured results.
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.
The third-party-metered benefit, the avoided-cost case, and the honest limits — the accessible version of the full brief.
Read the research →How the benefit gets written into a permit as a condition of approval, plus the full deal structure and schematics — behind the gate.
Request access →Bring your town, the project, the questions. We’ll think it through with you — what the heat could grow, and what it would and wouldn’t do for your community. No obligation, no sales pitch.
Start the conversation ↓1 Heatmap poll, May 2026. 2 E3 analysis, 2026; rate drivers are multiple. 3 Maine LD 307 vetoed Apr. 2026; override failed — no statewide ban exists; governor cited strong local support for the protected project. 4 Sentinel Data Centers withdrew from the Jay, Maine project, June 2026; the project is on hold. † Greenhouse figures are engineering design targets for a ~2.5-acre, four-zone flagship.
Net-zero town-water draw in temperate Virginia (committed), water-neutral aiming net-positive in the desert (under validation), a stormwater sink on the coast (committed) — and metered everywhere. And where the operator signs the campus roof tie-in, the optional Campus Catchment supplies the data center's own first fill and hottest-day cooling from rain the campus caught, on a second published meter. If your town prefers the greenhouse simply sustain itself — that is the whole deal, and the gauge still gets published.
See the water architecture →