CalMatters published a report on May 4, 2026, headlined “The data center backlash is here — and Big Tech is spending big to shape it.” The story frames a growing wave of community opposition to hyperscale data center projects alongside what the outlet characterizes as significant expenditures by large technology companies to influence public perception, local politics, and permitting outcomes.
Because only the headline and outlet are available in the source feed reviewed here, the specific dollar figures, named companies, jurisdictions, and campaign tactics referenced by CalMatters are not reproduced in this article.
Executive Summary
The CalMatters headline crystallizes a trend that has been building for at least two years: as artificial intelligence workloads push hyperscalers to site ever-larger campuses, the communities being asked to host them are pushing back on power draw, water consumption, tax abatements, noise, and land conversion. The report’s framing — that Big Tech is “spending big to shape” the response — asserts a coordinated influence effort rather than a series of isolated PR moves.
Why it matters: data center siting has moved from a technical procurement exercise into contested civic politics. If the pattern CalMatters describes holds, project timelines, community-benefit agreements, and utility-rate designs will increasingly be decided in front of city councils and public-utility commissions rather than in back-of-house negotiations. That reshapes cost of capital, land option strategies, and the reputational exposure of every operator in the sector — not only the hyperscalers named in any given story.
What is not yet substantiated from the source reviewed: the scale of spending, its recipients, which companies are most active, and whether the activity meets the legal threshold of lobbying, political advertising, or grassroots organizing under applicable state law.
Why the Backlash Arrived Now
Two forces converged. First, AI training and inference clusters draw hundreds of megawatts per campus — an order of magnitude above the 20 to 50 megawatt facilities that dominated the last cycle — which has pulled data centers onto grids and into rate cases that previously ignored them. Second, the queue of new interconnection requests in regions like Northern Virginia, Central Ohio, Georgia, and parts of California has spilled into residential-adjacent parcels, which surfaces zoning, noise, and traffic issues that colocation providers historically avoided by clustering in industrial zones. When a project competes with households for the same substation capacity, the fight becomes visible on the household’s electric bill.
The CalMatters framing suggests operators have recognized this shift and are resourcing it accordingly. That is consistent with public lobbying disclosures across several states in prior reporting cycles, though the specific 2026 figures referenced by CalMatters are not in the material reviewed here.
What ‘Spending to Shape’ Can Mean — And What It Cannot
Influence spending is a broad category. It ranges from clearly disclosed activity — registered lobbyists, campaign contributions filed with state ethics agencies, membership dues to trade associations — to less transparent forms such as sponsored community events, funded economic-impact studies, and paid grassroots organizing. Each carries different legal, ethical, and reputational weight. A community-benefits fund is not the same instrument as an astroturf letter-writing campaign, and conflating them weakens both critique and defense.
Fair questions cut both ways. Of industry: which expenditures are disclosed, which studies are independently peer-reviewed, and are the jobs and tax figures cited in siting hearings audited after the fact? Of critics: are the coalitions organic residents’ groups, or do they receive funding from competing land uses, ratepayer advocates, or ideological funders — and is that funding disclosed? Neither question should be used to dismiss the other side; both should be answered on the record.
The Economics Underneath the Politics
A single gigawatt-scale AI campus can represent 5 to 10 billion dollars of capital, decades of property-tax revenue, and a few hundred permanent jobs — a lopsided ratio that has always made data centers a peculiar economic-development target. Local officials get large capex announcements and modest payroll; residents get transmission upgrades that may or may not be socialized across the rate base. The math is defensible when the load is firm, the tax abatements are time-limited, and the utility recovers infrastructure costs from the specific customer causing them. It becomes politically fragile when any of those conditions slip.
Operators who invest early in transparent cost-allocation frameworks, independently verified water and power reporting, and enforceable community-benefit agreements tend to face lower opposition later. Those who rely primarily on influence spending to smooth approvals may win individual projects but raise the ambient political risk premium for the whole sector.
Implications for the Broader Infrastructure Stack
The backlash is not confined to hyperscalers. Colocation providers, connectivity carriers building fiber to new campuses, and power developers proposing behind-the-meter gas or nuclear all inherit the reputational climate the largest builders create. If permitting friction rises, the winners are likely to be operators with existing entitled land, brownfield reuse expertise, and demonstrated ability to close power-purchase agreements without triggering rate-case fights. The losers are speculative greenfield developers dependent on speed-to-permit assumptions that no longer hold.
For enterprise buyers and investors, the practical read is that siting risk deserves the same diligence weight as latency, power price, and fiber diversity. Contracts should account for the possibility that a project announced today may face a very different approval environment when it enters construction two years from now.
Background
Data centers evolved from single-tenant enterprise rooms in the 1990s to multi-tenant colocation campuses in the 2000s and hyperscale cloud regions in the 2010s. The current AI cycle, beginning roughly in 2023, has pushed unit sizes an order of magnitude higher and concentrated demand in a handful of metro areas already facing grid constraints. Communities that welcomed earlier generations of facilities as quiet, tax-generating neighbors have found the new class harder to absorb.
CalMatters is a nonprofit newsroom covering California policy and politics; its coverage of data center siting has focused on the intersection of AI infrastructure demand, state climate goals, and local land-use authority. The May 4, 2026 article extends that beat into the influence-spending dimension of the debate.
The Tennessee Valley Authority (TVA) will charge data centers more for power under a separate rate, according to an April 28, 2026 report by the Chattanooga Times Free Press. The federally owned utility, which supplies electricity across Tennessee and parts of six neighboring states, is effectively carving hyperscale computing load out of its general commercial and industrial rate structure and pricing it as its own customer class.
Executive Summary
According to the report, TVA — the largest public power provider in the United States — is establishing a distinct rate under which data centers will pay more for electricity than they would under existing industrial tariffs. A “rate class” is the category a utility assigns to groups of customers with similar usage patterns; creating a new one for data centers means the utility believes this load is different enough in size, growth, and risk to deserve its own pricing.
Why it matters: this is one of the clearest signals yet that utilities are no longer treating gigawatt-scale computing demand as ordinary industrial load. When a system as large as TVA’s formalizes a premium rate for data centers, it sets a reference point that other utilities, regulators, and public power boards across the country can cite. For operators planning campuses in the Tennessee Valley — a region that has actively courted data center investment — the cost of power, typically the largest ongoing operating expense of a data center, just became a moving target.
Pricing Hyperscale Load as Its Own Risk Category
Utilities have historically loved large industrial customers: steady, predictable consumption spreads fixed grid costs over more kilowatt-hours, which can lower rates for everyone. Data centers complicate that logic. They arrive in enormous increments, request interconnection faster than generation and transmission can be built, and — critically — a project can be cancelled or relocated after a utility has committed capital to serve it. A separate rate class is the standard regulatory tool for isolating that risk: it lets the utility recover the cost of serving data centers from data centers, rather than socializing it across households and smaller businesses.
The reported move fits a broader pattern. Utilities and regulators in several U.S. markets have been developing large-load tariffs with features like minimum-demand charges, longer contract terms, and collateral requirements. TVA formalizing a higher rate suggests the debate has shifted from whether hyperscale load should be treated differently to how much more it should pay.
What a Premium Rate Means for Data Center Economics
Electricity is usually the single largest recurring cost of operating a data center, and for AI-oriented facilities running dense, power-hungry hardware, the sensitivity is even greater. A structurally higher rate changes site-selection math: the Tennessee Valley’s traditional pitch — abundant, relatively inexpensive, largely carbon-light power from a mix that includes nuclear and hydro — becomes less differentiated if data centers pay a premium over the headline industrial rate. The report does not disclose the size of the premium, so the practical impact could range from a rounding error to a genuine deterrent.
Operators have levers in response: negotiating long-term supply agreements, bringing their own generation or storage to the table, or shifting flexible workloads to hours when the grid has spare capacity. But each of those adds complexity and capital cost, and none fully escapes a tariff that applies by customer class. The likely near-term effect is that hyperscalers press for contract structures — rather than published rates — where their scale gives them negotiating room.
A Public Power Precedent With National Reach
TVA occupies an unusual position: it is a federally owned corporation that sets its own rates through its board rather than through a state public utility commission. That autonomy means it can move faster than investor-owned utilities, whose large-load tariffs must survive contested rate cases. If TVA’s data center rate takes effect as reported, it becomes an operating precedent other utilities can point to when they argue that hyperscale customers should carry a larger share of grid-expansion costs.
There is a fairness argument on both sides worth stating plainly. Ratepayer advocates contend that residential customers should not fund transmission and generation built for a handful of technology companies. Data center operators counter that they are long-tenured, high-load-factor customers whose demand justifies infrastructure the whole region eventually benefits from, and that punitive pricing simply pushes investment — and its tax base and jobs — to neighboring territories. The reported story does not resolve which framing TVA’s rate design reflects, and the details of the tariff will determine whether it reads as prudent risk allocation or as a growth deterrent.
Background
The Tennessee Valley Authority was created by Congress in 1933 and grew into the largest public power system in the country, serving roughly ten million people through a network of local power companies. Its generation mix — including nuclear, hydroelectric, gas, and coal — and its historically competitive industrial rates helped make the Tennessee Valley a magnet for energy-intensive industry, and more recently for data center development tied to cloud and AI growth.
That growth collided with a nationwide reality: electricity demand, flat for two decades, began rising sharply as hyperscale computing facilities requested interconnections measured in hundreds of megawatts. Utilities across the U.S. responded by rethinking how such load is priced and contracted, seeking to protect other ratepayers from stranded-cost risk. TVA’s reported creation of a separate, higher data center rate places it among the most prominent utilities to formalize that shift.
Veolia, one of the world’s largest water and environmental services companies, announced on April 27, 2026 that it is working with Amazon to develop a reclaimed-water cooling system for data centers. The collaboration targets Amazon Web Services (AWS) facilities, aiming to substitute treated, recycled water for the potable water that many data centers currently draw for cooling.
Executive Summary
The announcement pairs the operator of some of the world’s largest water-treatment networks with the world’s largest cloud provider on one of the industry’s most scrutinized problems: how much drinking-quality water data centers consume to stay cool. Reclaimed water — wastewater that has been treated to a standard fit for industrial reuse, though not for drinking — can displace that potable draw, easing pressure on municipal supplies in the communities where hyperscale campuses cluster.
For Amazon, the partnership supports its publicly stated goal of becoming “water positive” by 2030 — returning more water to communities than its operations consume — and, just as practically, it addresses a growing source of friction in siting and permitting new capacity. For Veolia, it signals a move to position water expertise as core infrastructure for the AI-era data center buildout. The release, however, is light on specifics: no named sites, volumes, timelines, or financial terms were disclosed.
Why Water Is the Data Center Industry’s Quiet Constraint
Power gets most of the headlines, but water is increasingly the constraint that shapes where data centers can be built. Many large facilities use evaporative cooling, which chills servers efficiently by evaporating water — often millions of gallons per year per site, much of it drawn from the same municipal systems that supply homes. In drought-prone regions, that draw has become a genuine permitting and community-relations issue, with local opposition to new campuses increasingly citing water alongside electricity and land.
The industry measures this through water usage effectiveness (WUE) — water consumed per unit of computing energy delivered — and operators face growing pressure from regulators, investors, and neighbors to disclose and reduce it. A credible, scalable alternative to potable water is therefore worth real money: it can be the difference between a project that clears local approval and one that stalls.
What Reclaimed Water Solves — and What It Doesn’t
Reclaimed water is municipal or industrial wastewater treated to a quality suitable for non-potable uses such as irrigation and industrial cooling. Using it for data center cooling substitutes a resource that would otherwise be discharged for one that communities drink. That is a genuine improvement, and it is proven ground: power plants and heavy industry have run on recycled water for decades. The engineering challenge is real but tractable — reclaimed water’s chemistry can promote scaling, corrosion, and biological growth in cooling loops, which is precisely the treatment problem a company like Veolia exists to solve, along with the pipeline infrastructure needed to move recycled water from treatment plants to campuses.
What reclaimed water does not do is reduce total water consumption. Evaporative cooling still evaporates the water, whatever its source. It changes which water is used, not how much — a meaningful distinction in water-stressed basins, where hydrologists note that treated wastewater returned to rivers also supports downstream flows. The release, as summarized, does not address consumption volumes or how the system compares with closed-loop and other low-water designs.
The Strategic Logic for Both Sides
For Veolia, hyperscale data centers represent a growth market adjacent to its core business: the company already operates treatment plants and industrial-water services worldwide, and packaging that capability for cloud providers moves it up the value chain from utility contractor to strategic infrastructure partner in the AI buildout. A named relationship with Amazon is also a powerful reference for selling similar systems to other operators.
For Amazon, the calculus spans sustainability accounting and siting pragmatism. Progress toward its water-positive pledge requires exactly this kind of substitution at scale, and demonstrating a reclaimed-water pathway gives AWS a stronger story in front of the councils and water authorities that approve new capacity. If the partnership produces a repeatable template rather than a single showcase, it could modestly widen the map of viable data center locations — and put competitive pressure on other hyperscalers, some of which have taken the different route of designs that eliminate evaporative water use entirely.
Background
Data center water use moved from an engineering footnote to a public issue over the past several years, as hyperscale construction accelerated to serve cloud and AI demand and communities in water-stressed regions began scrutinizing how much potable water evaporative cooling consumes. The major cloud providers have responded with public commitments — Amazon’s is a pledge to be water positive by 2030 — and with a mix of recycled-water sourcing, more efficient cooling designs, and replenishment projects.
Veolia, formed from more than a century of French municipal water operations and now one of the world’s largest environmental-services groups, has built its industrial business on exactly this kind of problem: treating and delivering non-potable water for cooling and process use. The April 2026 announcement extends that franchise into hyperscale computing, an infrastructure market whose growth currently outpaces most of the industrial sectors Veolia has traditionally served.
An entity calling itself the Transatlantic Investment Group announced on April 27, 2026 a €50 billion AI data center and innovation campus in Croatia. The announcement describes the project as the largest investment in Croatian history and among the largest private U.S. investments in Europe. Beyond that headline framing, the release provides few operational details — no named site, power figure, timeline, or anchor tenant.
Executive Summary
The announcement positions Croatia — an EU, eurozone, and Schengen member on the Adriatic — as the destination for one of the largest AI infrastructure commitments ever declared in Europe. A €50 billion figure, if realized, would place the project in the same conversation as the multi-hundred-billion-euro wave of AI campus announcements that has swept the U.S. and, increasingly, Europe and the Gulf since 2024.
Why it matters: hyperscale AI buildout is going global. Power, land, and permitting constraints in Europe’s established data center markets — Frankfurt, London, Amsterdam, Paris, Dublin — have pushed developers toward secondary markets, and a commitment of this size in Croatia would be the strongest signal yet that the frontier has moved to Southeast Europe. But the announcement, as published, is a statement of intent. The distance between a declared figure and energized capacity is measured in grid connections, financing closes, and construction phases — none of which are detailed here. Readers should treat this as a significant claim awaiting substantiation, not a shovel-ready project.
Why Croatia? The Logic of AI’s Geographic Spillover
Europe’s traditional data center hubs are effectively full. Utilities in Dublin and Amsterdam have restricted new grid connections for large facilities, and Frankfurt and London face similar power and land pressure. That has redirected capital toward markets that can offer three things at once: available power, developable land, and EU regulatory standing. Croatia checks the third box cleanly — it is inside the EU single market, the eurozone, and Schengen — which matters for data sovereignty rules that push European enterprises and governments to keep AI workloads on EU soil.
The strategic framing as a “private U.S. investment in Europe” also fits a broader pattern: American capital funding AI capacity abroad, both to serve regional demand and to diversify away from congested U.S. power markets. For Croatia, a country whose economy leans heavily on tourism, an anchor investment in digital infrastructure would be transformative — which is precisely why the announcement’s superlatives deserve careful measurement against what has actually been committed.
What €50 Billion Buys — and What an Announcement Doesn’t
At current costs, hyperscale AI capacity runs very roughly in the tens of millions of euros per megawatt once you include the chips inside. A €50 billion program therefore implies gigawatt-class ambitions — a campus that would rank among the largest in Europe and consume electricity on the scale of a sizable city. Nothing in the announcement explains where that power comes from, and in AI infrastructure, power is the project. Grid interconnection queues, not capital, are the binding constraint almost everywhere.
Industry observers have also learned to discount announcement figures. Across the sector, headline commitments are typically phased over a decade, contingent on demand, and structured so that early phases are a small fraction of the total. That is not a criticism of this project specifically — it is how large campuses are legitimately built — but it means the meaningful milestones to watch are land acquisition, a signed grid agreement, a financing close, and a named hyperscale or AI-lab tenant. None appear in the source material.
Winners, Losers, and the Regional Ripple
If even a first phase proceeds, the beneficiaries are identifiable: Croatia’s grid operator and power producers (who would need to expand generation and transmission), regional construction and electrical trades, European chip-adjacent suppliers of cooling and power equipment, and connectivity providers building fiber routes to link the Adriatic to Frankfurt, Milan, and Vienna. An “innovation campus” component, if real, could seed a local AI workforce — though such components are also the easiest part of an announcement to promise and the last to be funded.
The competitive question is who this capacity would serve. Europe’s AI compute demand is growing, and the EU has actively courted large-scale AI infrastructure through initiatives like its AI gigafactory push. But Croatia would be competing with Spain, the Nordics, and Southern European markets that offer abundant renewables and established subsea connectivity. A project of this scale succeeds or fails on tenant demand, and the announcement names none.
Background
Croatia joined the European Union in 2013 and adopted both the euro and Schengen membership in 2023, completing its integration into the EU single market. Its economy has historically leaned on tourism and shipping, with a small but growing technology sector; it has not previously hosted hyperscale data center capacity, which in Europe has concentrated in the so-called FLAP-D markets — Frankfurt, London, Amsterdam, Paris, and Dublin.
That concentration is now breaking up. Power and land constraints in the established hubs, EU data sovereignty rules encouraging in-region AI capacity, and Brussels-backed initiatives to attract large-scale AI computing have pushed developers toward Southern and Eastern Europe. The Croatian announcement, if substantiated, would be the largest expression of that shift to date.
Google has begun construction on a data center in Kronstorf, a municipality in the Linz-Land district of Upper Austria, according to a groundbreaking announcement posted to the Google Cloud Press Corner and distributed on 23 April 2026. The item marks the start of physical work on the site.
The release as circulated is a headline announcement. It does not, in the version distributed through news syndication, state the campus size, planned power capacity, capital commitment, construction timeline, staffing, or whether the facility will underpin a new Google Cloud region for Austria.
Executive Summary
Groundbreaking is the point at which a data center stops being a land holding and becomes a construction project. For a hyperscaler — an operator running compute at global scale, such as Google, Amazon Web Services, Microsoft or Meta — it normally implies that land control, planning permission and, critically, a grid connection agreement are already settled. Those are the hard parts. Steel and concrete are comparatively easy.
The significance of Kronstorf is geographic more than technical. Europe’s data center industry has historically concentrated in five markets known as FLAP-D: Frankfurt, London, Amsterdam, Paris and Dublin. Those markets are now constrained less by demand than by electricity — grid connection queues, local moratoria and planning resistance have pushed new capacity outward into secondary markets with available power. Upper Austria, sitting on a hydro-heavy generation mix and on fiber routes between Munich, Vienna and northern Italy, fits that pattern.
What the announcement does not do is tell buyers anything actionable. Google has not, as far as the distributed release states, committed to a launch date or to an Austrian cloud region. Enterprises with Austrian data residency requirements should treat this as an encouraging signal about Google’s intentions, not as a procurement input.
Why Austria, and Why Now
The proximate driver of hyperscale expansion into new European markets is power availability, not proximity to customers. Latency between Kronstorf and Frankfurt is a rounding error for most workloads; the difference that matters is whether a transmission operator can deliver tens of megawatts on a schedule the builder can plan around. In several established hubs it cannot. Dublin’s grid operator has restricted new data center connections in the Greater Dublin area for years, and Amsterdam imposed a construction pause that reshaped Dutch development. Frankfurt and London face their own queue and land pressures.
Austria offers a different profile. Its electricity generation is unusually hydro-weighted by European standards, which is attractive both for carbon accounting and for price stability relative to gas-linked markets. Upper Austria is an industrial region with existing heavy-load infrastructure — the kind of grid that was built for manufacturing and can, in principle, be repurposed for compute. Kronstorf sits between Linz and Steyr, close to that industrial corridor.
None of this is stated in the release. It is the standard site-selection logic of the sector, and it is the most plausible reading of the decision. Readers should hold it as inference, not as a company claim.
What a Groundbreaking Actually Signals
Announcements of this kind are frequently over-read in both directions. A groundbreaking is a stronger signal than a land purchase or a memorandum of understanding: capital has been committed, contractors are mobilised, and the permitting and interconnection work that typically consumes years has largely concluded. Hyperscalers do not break ground on sites they intend to abandon, and the sunk cost from this point forward rises steeply.
It is a weaker signal than a service commitment. Large data center builds commonly run two to four years from groundbreaking to first customer traffic, and campuses are usually delivered in phases, with later buildings contingent on demand and on the operator’s capital plan at the time. A groundbreaking therefore says a facility is being built; it does not say when it will serve traffic, at what capacity, or which Google products will run on it.
The distinction matters most for the question of a Google Cloud region in Austria. A physical data center and a published cloud region are related but separate things — regions require multiple availability zones, a defined service catalogue and a launch commitment. The release, as distributed, does not make that commitment, and the absence should not be filled in by assumption.
Winners, Losers, and the Local Ledger
The clearest beneficiaries are Austrian enterprises and public-sector bodies with data residency obligations, who gain a credible prospect of in-country hyperscale capacity, and the regional construction and electrical trades, who capture the build phase — the largest and shortest-lived share of employment any data center generates. Local landowners and the municipal tax base typically benefit as well.
The competitive read is that Google is buying optionality in the DACH region rather than responding to a single anchor customer. Microsoft and AWS both hold established positions in German-language markets, and Vienna already hosts commercial colocation from international operators. Entering Austria with owned capacity changes Google’s cost structure and its sovereignty story simultaneously — owned facilities are cheaper at scale than leased ones and easier to make claims about.
The costs land locally and are worth stating plainly rather than defensively. Large sites consume grid capacity, land and, depending on the cooling design, water; operational employment is modest relative to capital deployed. Communities that raise these points are asking legitimate questions, and the honest answer is that this release provides no basis to evaluate them in either direction. When Google publishes capacity, cooling method and water sourcing, those figures should be tested — and so should any counter-claims made about them.
Reading a Thin Announcement Fairly
It would be unfair to characterise this release as evasive. Groundbreaking announcements are ceremonial by convention across the industry, and operators routinely withhold capacity figures for competitive and security reasons. Google’s more detailed European disclosures have historically followed at launch rather than at first excavation.
It would be equally unfair to present the announcement as more than it is. What is substantiated: construction has started at Kronstorf, and Google is the party announcing it. What is not substantiated by the release text: megawatts, euros, jobs, dates, cooling design, power procurement, and any regional service commitment. Coverage that supplies those numbers should be checked against a primary source.
For infrastructure buyers, the practical posture is patience. Treat Kronstorf as evidence of Google’s medium-term intent in Central Europe, factor it into three-to-five-year architecture planning, and revisit when the operator publishes a launch date or a region announcement.
Background
Google operates a global network of owned data centers supporting Search, YouTube, Workspace and Google Cloud, with a substantial European footprint including sites in Ireland, the Netherlands, Belgium, Finland and Denmark. Its cloud business competes with Amazon Web Services and Microsoft Azure, where physical proximity and in-country capacity increasingly matter for regulated customers subject to data residency rules.
Austria has hosted commercial colocation and enterprise data centers for years, largely concentrated around Vienna, but has not been a primary hyperscale construction market. The wider shift of European capacity toward secondary markets has been driven principally by electricity: as grid connections in Dublin, Amsterdam and Frankfurt became constrained, operators moved toward regions with spare transmission capacity and favourable generation mixes. Upper Austria, with its hydro-heavy power supply and existing industrial grid, sits squarely in that category.
