The lease gets signed in a conference room several states away from the county. The hearing happens in a middle school gym on folding chairs. Both rooms belong to the same logo, and only one of them is the room the town will remember.
If you run a cloud region, train models, or buy megawatts in a colocation hall, you are the data center user. You did not assemble the land. You did not file the conditional use permit. You may never have sat in the gym. But when the campus goes live, the name on the region map is yours, and so is everything the community learned on the way to the vote.
what a hyperscale data center is
A hyperscale data center is a facility built around a single very large tenant's workload — a public cloud region, an AI training cluster, a platform's core — at a scale where the campus, not the building, is the unit. Individual halls run tens of megawatts; campuses now plan in the hundreds of megawatts and increasingly above a gigawatt, on parcels of hundreds to thousands of acres. Colocation (colo) is the neighboring model: an operator builds and runs the hall and leases space and power, by the rack, the cage, or the megawatt, to many customers at once.
The distinction matters for this post because the town does not make it. To the neighbor, a 300-acre campus is a data center. To the county, it is a CUP with a name on it. To the person typing "hyperscale data center" into a search bar, it is usually a job, an investment, or a permit problem. This post is about the permit problem, and about who inherits it.
who actually owns the campus
Four roles, often four different companies, sometimes one. The gap between them is where accountability leaks.
| role | who it is | what they hold | what they risk at the hearing |
|---|---|---|---|
| owner (PropCo) | REIT, infrastructure fund, or developer-turned-landlord that holds the land and the shell | Ground rent, lease income, exit value | Carrying cost and interconnection deposits burning through a delay; a denial strands the basis |
| developer / powered-land assembler | The group that options farmland, secures the interconnection queue position, and files the entitlements | Speed-to-power; the sale or lease at shovel-ready | The vote itself; a moratorium erases the timeline they sold |
| tenant (hyperscale lessee) | The cloud, AI, or platform company signing a long build-to-suit lease, or self-developing the campus | The workload, the region, the logo | Brand, license to operate in the next county, sustainability claims tested against a real basin |
| user (enterprise colo customer) | A bank, insurer, retailer, or software firm renting racks or megawatts inside someone else's hall | Uptime and compliance | Invisible to the town; still the demand that draws the water and the power |
Colo operators sit between the first and third rows: they own or lease the hall and sell it by the megawatt. The landlord's risk is a clock. The tenant's risk is a name. Both are real, and this post does not pick a villain, because the hearing does not either. A county commissioner voting no on a Tuesday night is voting against a project, and the project has all four of you in it.
the logo is what the town remembers
Land assembly for a hyperscale campus usually runs through a special-purpose entity. That is ordinary practice, not concealment; it is how any large, multi-year land program is done. In Licking County, Ohio, a Meta affiliate called Sidecat LLC paid more than $1.1 million per acre for parcels in 2025, in a county where farmland trades at $10,000 to $15,000 an acre. The sellers took the bid with open eyes. CNBC's September 2026 reporting on rural land markets quotes Texas Agriculture Commissioner Sid Miller, speaking at a July protest in Lubbock, saying developers "give sometimes 10 times the value, so it's hard for farmers to turn that down."
Notice what survived the transaction, though. The LLC name did not. The brand did. The same thing happens to project code names: a code name gets the CUP, and the town learns whose region it is at the ribbon cutting, or earlier, from a utility filing. That Licking County assembly is ordinary practice, not a deception claim. The "they called it a business park" objection is a different pattern — Lee County, North Carolina, and other places where the filing name hid the use. Do not fuse the two. Either way, the frustration still lands on the tenant, because the tenant is the only party with a name the neighbor already knows.
This is the identity problem for data center users. Your sustainability report was written for investors and customers. The county is reading it too, and comparing it to a well that dropped and a church that can hear the chillers. A water target booked in another basin does not help you in this one; corporate water stewardship is not a restored basin explains why the program's volumes and the physical place are two different ledgers.
A landlord can sell the campus. A tenant cannot sell the memory of how it was approved.
rotation does not retire the story
The industry's answer to fatigue in Northern Virginia and Michigan has been geographic rotation: put the next campus in Florida, Texas, or another jurisdiction with a faster clock. As a land strategy, it works. As a brand strategy, it does not, because the community you left keeps the story and the community you arrive at reads it.
Berkshire Hathaway's Greg Abel told CNBC in September 2026 that there is "a lot more pushback in the communities across the U.S." — from a company whose interest is mostly in selling the power. Analysts at Mizuho wrote the same week that investors think data centers could be a significant issue in the midterm elections. When power investors and sell-side desks say it out loud, the tenant should assume the next county's planning staff has already read the last county's minutes.
Rotation carries a second cost the lease does not show. The new corridor's farmland and water are about to be priced the way the last one's were. CNBC notes that powered sites in Northern Virginia and the Northeast passed $8 million per acre last year, according to CBRE. A tenant arriving in a new county arrives as the reason the next farm sale happens, whether or not the tenant signs the deed. That is the fight you inherit — not because you are the developer, but because you are the demand.
tenant specs, not charity
Here is the shift that makes the rest of this useful. Hyperscale leases already carry specifications the landlord has to meet: power density, redundancy tier, fiber diversity, delivery dates, uptime credits. The same instrument can carry the living-system terms the hearing is actually about. Written this way they are not corporate giving. They are siting and lease requirements, priced and enforced like the rest of the spec.
| tenant spec | what it says in the lease or RFP | the objection it speaks to | what it does not do |
|---|---|---|---|
| same-basin water | Cooling and makeup water sourced and offset in the basin the campus draws from; funded recharge, wetland, or riparian work in that basin, not a credit elsewhere | "It will drop the well." Roughly 43% of data centers globally sit in high water-stress areas, and water is the concern raised most often in contested projects (the water spoke) | Replace closed-loop or air-cooled engineering. Both are needed. Funded recharge does not guarantee any individual well |
| living buffer | A funded, maintained vegetated buffer of stated depth and species on the campus edge facing homes, schools, and churches | "The bedroom hums at 3 a.m." Dense belts attenuate, and they carry stormwater and habitat while they do it (the noise spoke) | Delete the setback, the generator rules, or the acoustic design. A buffer attenuates; it does not erase a 24/7 hum. It is not a scrubber |
| farmland ratio | For every acre padded, a stated number of working acres in the same county placed under permanent protection and recorded (the farm spoke) | "This changes who we are." | Stop the million-dollar-an-acre bid. It decides what the acres you did not pad become |
| no-abatement option | The tenant will accept — or require — a package without a property tax abatement, paired with a recorded community benefits agreement | "A trillion-dollar company wants a break." St. Louis approved a campus in April 2026 with no abatement and a recorded, binding agreement | Fix a county's tax math. It removes one resentment row from the hearing |
| public reporting | Water, buffer condition, protected acreage, and fund flows reported on a stated cadence to a public page, with recourse if missed | "They called it a business park." Trust dies on secrecy and recovers on records | Substitute for the CUP, the hydraulic study, or the tariff filing |
Read the third column again. Every entry is a sentence a neighbor has said into a microphone. The second column is the version a procurement team can put in an RFP and a general counsel can enforce.
For the enterprise colo customer, the same table becomes a supplier questionnaire. You already ask your provider about PUE, renewable matching, and SOC 2. Ask which basin the water comes from and what is funded there. If the answer is a stewardship PDF about a different watershed, you have found the gap.
what the tenant cannot buy
Honesty about the limits is what keeps this from being a lobbying script.
A tenant spec does not lower anyone's electric bill. Grid upgrades and who pays for them are a tariff and cost-causation question; the honest answer there is developer-funded upgrades and ratepayer-protection language, not a planting plan (data centers and your electric bill). A living buffer attenuates a hum; it does not erase diesel generators in a cold snap. Public reporting builds trust; it does not replace the hydraulic study a city engineer wants before the CUP. A protected-acres ratio changes what the county keeps; it does not undo the price a neighbor was paid or refused.
Say all of this at the hearing. The commissioner does not need poetry, and the neighbor can tell when the hard rows are being skipped.
where ensurance sits in the lease
Ordinary insurance protects the owner and the tenant after a loss: property, business interruption, sometimes political risk. A denied permit is mostly uninsured time. Ensurance funds the living systems the hearing is about — the watershed, the working land, the buffer — before the vote, in the same place, as a present-tense commitment the county can verify. It is not the watershed. The watershed exists whether or not anyone funds it. Ensurance is how a campus pays into it, on a record the public can read.
In practice the tenant specs above map to funded place accounts: a basin account for the same-basin water row, an open-space account for the farmland ratio and the buffer. A certificate is the instrument that ties a dollar to a named place and reports back — that is the one-line gloss, and it belongs here in the body, not in the first screen of a permit conversation. Live examples include inland-wetlands.ensurance and rural-open-space.ensurance. Volumes are small today. A live solutions page and three May 2026 posts on water, noise, and farmland are the current stage; this series is the next one.
The point for a tenant is placement. Put the funded place in the lease, the RFP, and the recorded agreement, where it binds the landlord and the developer as much as it binds you. Do not put it in a later ESG PDF, where it binds no one and answers nothing at the microphone.
what to do before the next site
If you are a hyperscale lessee, add the five specs above to the site-selection scorecard and the lease term sheet before the developer files. It costs you a negotiation. It saves you the hearing you would otherwise lose.
If you are a colo buyer, send the table to your provider as a questionnaire. The basin question alone will tell you what you need to know.
If you are the owner or the assembler, the tenant is about to ask for this. Arriving with it is faster than being asked.
Talk to someone who can structure the living-system terms for a specific campus →
See how ensurance applies to data centers → · and to corporations with nature dependencies →
Next in the series: the cheapest insurance against a denied permit — what ordinary coverage pays after the no, and why funding the place first is cheaper.
the series
Six posts on why communities oppose data centers, and how owners, tenants, and developers fund the answer before the vote.
- why communities oppose data centers — the full opposition inventory
- data centers and your electric bill — the ratepayer row, stated honestly
- a community benefits agreement is not a press release — recorded terms vs. a sustainability page
- how to get a data center approved faster — the hearing package
- if you lease the hall, you inherit the fight — tenants, users, and the memory of the campus (this post)
- the cheapest insurance against a denied permit — pay-after vs. fund-now
Sibling posts from May 2026: data centers drink water. ensurance refills the glass, the cheapest noise wall is a forest, and data centers don't have to eat the farm.