If a data center wants to build in your community, you’re caught between a tax base you can’t afford to lose and constituents who are out of patience. A moratorium sends the project — and its revenue — to the next county. Rubber-stamping it costs you at the next election. There’s a third option, and it’s one you control: approve the facility only on the condition that it feeds the town.
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; you fought hard for an empty table. Approve it as-is, and you own the noise, the lines, and the bill at the next election, with only a sponsorship banner to show for it. Maine just lived this: the legislature passed the nation’s first statewide moratorium, the governor vetoed it, the override failed — and the one project she protected was the one with genuine local support.3 Consent is the deciding variable, not the gavel.
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 you can defend at a podium.
You don’t have to choose between “build freely” and “stop building.” You can approve the data center on the term that it co-locates a community greenhouse — written into the Conditional Use Permit as an enforceable condition. That converts the heat the facility was wasting into a year-round asset your district 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). 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. You should assume that risk and legislate against it. We built the project so you can.
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 you’re weighing a moratorium or a rezoning, we can walk you through the condition language and what it would mean for your specific district. No obligation, no sales pitch — you have no budget for us to chase.
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 the project, the parcel, the politics. We’ll think it through with you before you’re at the podium — 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. † Greenhouse figures are engineering design targets for a ~2.5-acre, four-zone flagship.
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, honest about what's still under validation, and metered everywhere.
See the water architecture →