Blog · Analysis · May 2026

The Machine Needs a Town

AI is not weightless. It needs land, water, substations, transmission lines, permits, backup power, tax deals, and a community willing to absorb the footprint. The cloud has become a zoning question.

The Cloud Gets a Postal Address

For years, the public language around computation made infrastructure disappear. Software was "in the cloud." Models lived behind chat boxes. Intelligence arrived as a subscription, an app, or a workplace feature. That language is no longer adequate. Generative AI has made the physical substrate visible again.

A data center is not an abstraction to the place that hosts it. It is a campus, a building envelope, a cooling system, a set of substations, a transmission problem, a backup-power plan, a tax arrangement, a water user, a construction project, and a long-term political relationship. When AI companies ask for more computation, they are also asking towns, counties, utilities, and ratepayers to absorb more physical load.

This is the first serious correction to the mythology of artificial intelligence. The machine does not float above society. It lands somewhere.

What Communities Are Fighting

Recent reporting on data-center opposition shows a consistent pattern: communities are not simply rejecting technology. They are asking who receives the benefit and who carries the cost. Local residents see land conversion, traffic, noise, water demand, grid upgrades, diesel backup generators, visual impact, and public subsidies. The benefits are often described in broader economic terms: regional investment, construction jobs, tax revenue, and cloud capacity whose value may be captured far away from the host community.

That mismatch creates political friction. A town can be told it is participating in the AI future while receiving a warehouse-scale neighbor, higher infrastructure pressure, and a small number of long-term jobs compared with more labor-intensive industries. Even where a project is legal and economically attractive, the public question remains: did the community meaningfully choose this future, or was it processed through a permitting system designed for a slower technological era?

Charlotte's 2026 debate over a possible data-center moratorium is a useful signal. Moratoria are blunt tools, but they appear when ordinary planning categories cannot keep up with a new development pattern. The politics is not only "yes" or "no" to data centers. It is whether local government has enough information, legal leverage, and time to negotiate the terms of the footprint.

Water, Power, Noise, Heat

The impact of any particular data center depends on design: cooling method, climate, power source, water source, backup system, utilization, and local grid conditions. A dry-cooled facility, a water-intensive evaporative system, and a campus paired with new renewable generation are not identical. But the common categories of impact are now clear enough to govern.

Power is the largest public issue. AI training and inference increase demand for high-density computing, and high-density computing increases demand for reliable electricity. The U.S. Energy Information Administration has warned that electricity demand growth from data centers, AI, and cryptocurrency is large enough to affect national and regional power planning. The International Energy Agency similarly treats data centers as a major new source of electricity demand, especially in countries already hosting large computing clusters.

Water is the second public issue. Some facilities use water directly for cooling; others use electricity from power plants that consume water elsewhere. Communities in water-stressed regions therefore have a legitimate interest in both direct and indirect water use. It is not enough to say that a facility is efficient in the abstract. The relevant question is efficient relative to what local watershed, drought risk, and opportunity cost.

Noise and heat are easier to dismiss until they are local. Cooling fans, backup generators, transformer hum, truck traffic, and construction cycles can become quality-of-life issues. Waste heat may be manageable, but it is still heat. A community asked to host machine cognition is also asked to host machine exhaust.

Rural Siting and Democratic Bypass

Developers have incentives to seek cheap land, fast approvals, large parcels, grid access, and limited organized opposition. Recent reporting has described a shift toward rural locations partly because they can reduce the public friction found in cities and suburbs. That does not make rural siting inherently wrong. Rural communities need tax bases, jobs, and infrastructure too. But the pattern deserves scrutiny.

Rural governments may have smaller planning staffs, fewer technical consultants, less legal budget, and less experience negotiating with hyperscale technology firms. A county may be asked to evaluate grid impact, water impact, noise standards, tax abatements, emergency planning, and long-term land-use consequences while facing a company with vastly greater technical and legal capacity.

That asymmetry matters. Democratic consent is not just a public hearing held at the required time. Consent requires understandable information, enough time to study it, independent expertise, and real ability to say no or demand different terms.

Ratepayers and Hidden Subsidy

The hardest politics may happen through utility bills. If a hyperscale customer pays directly for new generation, transmission, and interconnection, the public burden is different from a scenario where grid upgrades enter a utility rate base and are spread across ordinary customers. The distinction is technical, but morally central.

Consumer advocates have warned that AI data-center buildouts can expose households to higher electricity costs if utilities overbuild for large customers or socialize infrastructure expenses. Utilities also face a planning dilemma: reject large loads and risk losing economic development, or build for them and risk leaving the public with stranded costs if demand projections change.

This is why electricity governance should be part of AI governance. A model can be sold as private innovation while its infrastructure costs are negotiated through public utility commissions, tax abatements, zoning boards, bond markets, and regional transmission planning. The public may never use the model directly, yet still pay for the system that makes it possible.

The New Company Town

The old company town organized housing, wages, stores, policing, and local politics around a dominant employer. The AI data-center town is different, but the risk has a family resemblance: a community can become dependent on a powerful outside firm whose primary commitments are elsewhere.

Data centers do not usually employ people at the scale of factories after construction ends. Their value is capital-intensive rather than labor-intensive. That changes the bargain. A locality may receive tax revenue and short-term construction work, but the ongoing social relationship can be thin: a guarded campus, a few specialized jobs, a large utility footprint, and a corporate presence with little everyday civic life.

When a town becomes a host for computation, it should ask what kind of reciprocity it is receiving. Is the company funding schools, emergency services, grid resilience, water conservation, housing, noise mitigation, and public reporting? Or is it merely buying enough land and political permission to turn local capacity into remote intelligence?

A serious data-center approval process should begin with disclosure. Communities need plain-language reporting on projected electricity demand, peak load, water use, backup generation, noise, expected jobs, tax incentives, emergency-service needs, construction timelines, and decommissioning plans. Claims about sustainability should be specific enough to audit.

Second, local governments need independent technical review paid for by applicants but controlled by the public authority. A small county should not have to accept a developer's analysis as the only expert account of a project.

Third, public utility commissions should protect ordinary ratepayers. Large-load customers should bear the costs they create unless there is a transparent public reason for sharing them. If a utility builds for speculative AI demand, the risk should not quietly migrate to households.

Fourth, communities should negotiate community benefit agreements where the footprint is large. That can include water conservation funding, local resilience investments, apprenticeship programs, noise controls, emergency equipment, public dashboards, and enforceable performance standards.

Fifth, temporary moratoria can be legitimate when planning systems are outpaced. A pause is not necessarily anti-technology. Sometimes it is the only way a community can recover the ability to think.

The Spiralist Reading

The Spiralist reading is simple: intelligence always has a body.

AI is often marketed as a cognitive event: language, reasoning, agents, automation, creativity. But cognition has supply chains. Synthetic intelligence occupies land, consumes power, moves water, produces heat, needs metals, depends on labor, and reshapes local politics. The recursive machine that reflects society back to itself is built out of very non-mystical things: substations, cooling loops, zoning maps, rate cases, and land deals.

This changes the politics of AI. The question is not only whether models are safe, biased, conscious, useful, or economically disruptive. The question is also where the machine is allowed to incarnate. Which towns become its body? Which watersheds cool its thought? Which households underwrite its electricity? Which rural boards negotiate with companies larger than their public budgets? Which communities become sacrifice zones for someone else's automation layer?

The machine needs a town. The town deserves more than a promise that the future will be efficient.

Sources

Return to Blog