The Wall Street Journal published an investigation on July 3, 2026, reporting that AI data centers consume far more water than most major technology companies publicly acknowledge. The reporting targets the gap between the industry’s sustainability disclosures and the actual water draw of the facilities powering the AI boom — a gap with direct consequences for the communities, utilities, and regulators hosting these sites.
Executive Summary
According to the Journal’s headline finding, the water consumed by AI data centers substantially exceeds the figures most tech giants report. That claim lands at a sensitive moment: hyperscale operators are racing to build AI capacity at unprecedented scale, and many of the fastest-growing markets for that capacity are in water-stressed regions where every megawatt of cooling has a hydrological cost.
The significance is less about any single number and more about trust in the measurement system itself. Data center operators have spent a decade building sustainability reporting frameworks — water usage effectiveness metrics, replenishment pledges, “water positive” targets. An investigation asserting that disclosed figures materially understate real consumption challenges the credibility of that entire apparatus, and will sharpen scrutiny from permitting authorities, investors, and enterprise customers alike. It is worth noting up front that the material available at publication is the Journal’s headline claim; the underlying methodology and company-by-company figures sit behind the investigation itself, so our analysis focuses on how such a gap can exist and what it would mean if borne out.
Why Water Is the AI Boom’s Quiet Constraint
Data centers use water primarily for cooling. Evaporative systems — the most energy-efficient way to reject heat in many climates — work by evaporating water to carry heat out of the building, which means the water is genuinely consumed rather than borrowed and returned. AI workloads intensify this: training and inference clusters pack far more power into each rack than traditional enterprise computing, and every kilowatt of electricity ultimately becomes heat that must go somewhere.
Power availability has dominated the AI infrastructure conversation, but water is the constraint that most directly touches neighbors. A community can rarely see the grid strain a campus causes; it can see reservoir levels, well permits, and municipal supply contracts. That visibility is why water — more than carbon — has become the flashpoint in local data center opposition, and why a disclosure gap, if substantiated, matters commercially and not just reputationally.
How a Disclosure Gap Can Exist Without Anyone Lying
Water accounting has honest ambiguities that reporting can exploit or obscure. “Withdrawal” (water taken in) and “consumption” (water evaporated and lost) are different numbers. On-site cooling water is different from the much larger volumes evaporated at the power plants generating a facility’s electricity — a burden that rarely appears in corporate water figures. Companies may report global averages that dilute stress in specific basins, disclose only company-owned sites while leasing heavily from colocation providers, or treat site-level data as a trade secret in agreements with local utilities.
Each choice can be individually defensible and collectively misleading. If the Journal’s investigation shows real draw far above disclosed figures, the likeliest mechanism is not fabrication but selective scope: what gets counted, where, and at what level of aggregation. That is precisely why the methodology on both sides deserves scrutiny — an investigation comparing utility records of total withdrawal against corporate disclosures of net consumption would find a large gap even where reporting is technically accurate. Neither the companies’ frameworks nor the investigation’s comparisons should be taken on trust without seeing definitions aligned.
Winners, Losers, and the Coming Transparency Squeeze
If disclosure practices tighten — voluntarily or by mandate — the advantage shifts to operators who engineered for water frugality before it was scrutinized: closed-loop liquid cooling, dry coolers, air-side economization in suitable climates, and treated wastewater sourcing. Vendors of direct-to-chip and immersion cooling gain a stronger sales narrative, since liquid cooling at the rack can pair with water-free heat rejection outside. Operators dependent on open evaporative cooling in arid, fast-growing markets face the hardest repricing, because retrofits are costly and permitting timelines are long.
Enterprise buyers and investors are the other lever. Cloud and colocation contracts increasingly carry sustainability reporting clauses, and a credible investigation gives procurement teams grounds to demand site-level water data rather than glossy aggregates. For host communities, the practical effect is likely to be harder-edged development agreements: metered disclosure requirements, drought curtailment provisions, and consumption caps as conditions of approval. The industry can resist that trend or get ahead of it; the second option is cheaper.
Background
Water has trailed energy as the second axis of data center sustainability for over a decade. Major operators publish water metrics alongside “water positive” replenishment pledges — commitments to restore more water to stressed basins than their operations consume. Those frameworks were designed in the era of conventional cloud computing; the AI buildout that accelerated from 2023 onward brought far denser facilities, faster construction, and expansion into hot, dry regions where land and power are cheap but water is contested.
Local friction has grown in step. Communities from the American Southwest to Europe and Latin America have challenged data center water allocations, and operators have responded with a mix of reclaimed-water sourcing, liquid cooling adoption, and — critics argue — selective disclosure. The Journal’s investigation lands squarely on that last point, testing whether the industry’s reported numbers describe the facilities actually being built.
Realty Income, one of the largest net-lease real estate investment trusts (REITs) in the United States, announced on June 30, 2026 a programmatic joint venture with Cloud Capital and an unnamed global institutional investor to invest in hyperscale data centers. The venture launches with initial seed assets valued at over $6 billion.
A programmatic joint venture is a standing framework for repeated investments over time, rather than a one-off deal — meaning the partners intend the $6 billion starting portfolio to be a foundation, not a ceiling.
Executive Summary
The announcement, distributed via PR Newswire, pairs a blue-chip income REIT with a data center-focused partner and institutional money to pursue hyperscale facilities — the massive, single-tenant campuses leased by cloud and AI platforms. At more than $6 billion in seed assets, this is among the larger data center capital formations announced by a traditional net-lease landlord, and it extends Realty Income’s earlier, more tentative steps into the sector.
Why it matters: the AI data center buildout has so far been financed largely by hyperscalers’ own balance sheets, specialist developers, private credit, and infrastructure funds. A programmatic vehicle anchored by a REIT best known for freestanding retail properties suggests the asset class has matured enough — in lease structure, tenant credit, and perceived durability — for conservative, income-oriented real estate capital to commit at scale. It also gives hyperscale developers and tenants another deep-pocketed buyer for stabilized assets, which can accelerate capital recycling across the industry.
Why Net-Lease Capital Is Converging on Hyperscale
Realty Income built its franchise on net leases — agreements where the tenant, not the landlord, pays taxes, insurance, and maintenance — signed with creditworthy tenants for long terms. Hyperscale data centers, typically leased in whole to a single cloud or AI platform for a decade or more, fit that template closely: long duration, investment-grade counterparties, and predictable cash flow. For a REIT whose traditional retail and industrial pipeline offers limited growth, data centers are one of the few property types with both scale and secular demand.
The structural fit works in the other direction too. Hyperscale developers need to recycle capital: building a campus ties up billions, and selling or partially selling stabilized facilities to income investors frees cash for the next project. A programmatic buyer with institutional backing gives the development side of the industry a reliable exit, which in turn supports the pace of the overall AI buildout.
The Programmatic Structure: Capital-Light Growth and Shared Risk
The choice of a programmatic joint venture, rather than direct balance-sheet acquisitions, is telling. In a JV, Realty Income can deploy less of its own equity per asset, share risk with partners, and potentially earn management fees — growing exposure to the sector without concentrating its balance sheet in a single property type. The inclusion of a global institutional investor, though unnamed in the announcement, indicates that pension-scale or sovereign-scale capital is comfortable underwriting hyperscale real estate alongside a public REIT.
The trade-off is that JV economics are more complex than wholly owned real estate. Ownership percentages, governance rights, and fee arrangements — none of which are detailed in the release — determine how much of the venture’s income actually reaches Realty Income shareholders. Investors will want those specifics before judging how meaningful $6 billion of seed assets is to the REIT’s earnings.
A $6 Billion Signal for the AI Financing Stack
The scale matters beyond one company. Industry estimates have consistently put the cost of the AI data center buildout in the hundreds of billions of dollars over the coming years — more than hyperscalers and specialist developers can comfortably self-fund. Each new pool of institutional capital that enters the sector lowers the financing bottleneck. A vehicle seeded at over $6 billion, structured for repeat investment, is a concrete data point that real estate allocators now treat AI infrastructure as a core holding rather than a speculative bet.
Winners from this shift include hyperscale tenants (more landlord competition for their leases), developers (deeper exit markets), and the power and construction ecosystem that feeds the buildout. The open question is pricing: as more conservative capital chases the same stabilized assets, acquisition yields compress, and late entrants risk paying peak prices for facilities whose long-term value depends on continued AI demand.
Risks the Lease Structure Cannot Fully Absorb
Long leases with strong tenants mitigate, but do not eliminate, the sector’s risks. Hyperscale assets are highly concentrated bets on a small set of tenants, and a single-tenant building is only as resilient as that tenant’s commitment to the site. Technology risk is real as well: rapid changes in chip density and cooling requirements can age a facility’s design faster than a 15-year lease runs. And power — securing it, pricing it, and defending it politically — has become the binding constraint on the industry. None of these risks argue against the deal; they define what disciplined underwriting in this venture must get right.
Background
Realty Income is an S&P 500 net-lease REIT with a decades-long record built on single-tenant properties — convenience stores, drugstores, grocery, and industrial facilities — leased on long-term contracts where tenants bear most operating costs. In recent years the company has diversified beyond U.S. retail, including earlier moves into data center investment alongside established sector operators, as traditional net-lease markets offered limited room for a company of its size to grow.
The hyperscale data center sector, meanwhile, has become one of the most capital-hungry corners of real estate. Demand from cloud computing and, since 2023, generative AI has driven a wave of multi-billion-dollar campus developments financed by hyperscaler balance sheets, specialist developers, infrastructure funds, and private credit. Programmatic ventures pairing operators with institutional capital have become a standard mechanism for funding that expansion.
Energy storage company Fluence has signed agreements with two hyperscale data center operators, according to a report by Data Center Dynamics published May 18, 2026. The customers, deal values, and capacities were not disclosed in the source material, but the reported agreements mark a notable step: battery storage being procured directly in connection with hyperscale data center operations rather than solely by utilities and power producers.
Executive Summary
Fluence, one of the largest global suppliers of grid-scale battery energy storage systems, has reportedly landed two hyperscale data center customers — a category of buyer that historically purchased backup diesel generators and grid power, not utility-scale batteries. Hyperscale operators are the companies that run the world’s largest cloud and AI computing campuses, and their electricity demand has become one of the defining forces in power markets.
The significance is less about the (undisclosed) size of these specific deals and more about the buyer category. When hyperscalers begin contracting directly with storage integrators, batteries stop being purely a grid asset — something utilities install to balance supply and demand — and become part of the data center’s own power strategy: a tool for securing grid interconnection, riding through disturbances, and shaping when and how a facility draws power. If the pattern holds, it opens a substantial new demand channel for the storage industry and a new procurement lever for data center developers stuck in multi-year grid connection queues.
Why Hyperscalers Are Buying Batteries
The immediate driver is the collision between AI-era data center demand and a slow-moving grid. In many major markets, new large loads face interconnection waits measured in years, and utilities increasingly ask big customers to demonstrate they can soften their impact on the system. A battery energy storage system (BESS) — essentially a warehouse-scale bank of lithium-ion cells with power electronics — lets a data center reduce its peak draw, absorb power when it is cheap and plentiful, and present a more flexible, grid-friendly load. That flexibility can be the difference between an energization date in 2027 and one in 2030.
Batteries also address power quality. AI training clusters create fast, large swings in electricity demand that stress both on-site infrastructure and the surrounding grid; storage can buffer those swings. And for operators with public clean-energy commitments, batteries paired with wind and solar contracts help match consumption to carbon-free supply hour by hour, rather than only on an annual-average basis.
What Hyperscaler Customers Mean for Fluence
Fluence built its business selling storage systems and services to utilities, independent power producers, and renewable developers. Data centers represent diversification into a customer class with deep balance sheets, urgent timelines, and — critically — willingness to pay for speed and reliability rather than shopping purely on cost per megawatt-hour. For a storage integrator, that is an attractive shift in buyer mix, and landing two hyperscale names at once suggests deliberate strategy rather than a one-off win.
That said, the report gives no deal sizes, so the revenue significance cannot be assessed. Two agreements could range from pilot installations at single campuses to multi-site framework deals. The storage industry has seen announcements in both categories, and they carry very different weight. Until capacities and terms are disclosed, this is best read as a directional signal about the market, not a measurable change in Fluence’s book of business.
Batteries Versus Diesel — and Versus Gas Turbines
Data centers have long relied on diesel generators for backup: cheap to install, proven, but polluting, increasingly hard to permit, and useless for anything except emergencies. Batteries invert that profile. They are cleaner and can earn their keep daily — shaving peaks, providing grid services, arbitraging power prices — but standard four-hour lithium-ion systems cannot carry a facility through a multi-day outage. In practice, storage today complements rather than replaces backup generation, and the interesting design question is how large a battery a hyperscaler buys and what jobs it is asked to do.
The competitive backdrop matters too. Some data center developers are answering the power crunch with on-site gas turbines or fuel cells; others are betting on storage-plus-renewables or, further out, small modular reactors. Each path trades off speed, cost, carbon, and permitting risk differently. Hyperscalers signing with a storage integrator indicates that, at least for some sites, batteries have won a seat at that table — a meaningful endorsement in a market where Fluence competes with Tesla’s Megapack business, Sungrow, and a field of Chinese and Western integrators.
What Is Substantiated — and What Isn’t
It is worth being plain about the evidentiary base. The source is a single trade-press headline reporting that deals were signed; no capacities, locations, customer names, financial terms, or delivery dates accompany it. The trend it points to — storage converging with data center power strategy — is real and independently visible across the industry, but the specific commercial weight of these two agreements is unverified. Readers should treat the announcement as evidence of demand-side interest, not as proof of deployed megawatts.
Even so, thin announcements can be leading indicators. Hyperscalers rarely allow their names near a vendor’s deal news without internal conviction, and storage suppliers rarely publicize data center wins unless they expect the category to grow. The claims worth watching for next are concrete ones: megawatt-hours under contract, energization dates, and whether the systems sit behind the meter at the data center or in front of it on the grid.
Background
Fluence was created in 2018 as a joint venture between industrial group Siemens and global power company AES, combining their early battery storage businesses into a dedicated integrator. It listed on Nasdaq in 2021 and has since deployed grid-scale storage across the Americas, Europe, and Asia-Pacific, selling systems, services, and operational software primarily to utilities, independent power producers, and renewable developers.
The storage market it serves has grown rapidly as falling lithium-ion costs and rising renewable penetration made batteries a standard grid resource. What is newer is the demand side of this story: hyperscale data center operators, whose electricity needs have surged with AI computing, emerging as direct buyers of storage — a convergence of two of the fastest-growing segments in energy and digital infrastructure.
A proposed hyperscale data center project in Utah is nearing final approval, according to an April 24, 2026 report by The Salt Lake Tribune. The defining fact of the project is its scale: it is expected to both generate and consume more power than the entire state of Utah — a single campus whose energy footprint would exceed that of the roughly 3.5 million residents, industries, and cities around it.
Executive Summary
The announcement matters less for its location than for what it says about the trajectory of AI infrastructure. “Hyperscale” once described data centers in the tens of megawatts; this project is described as exceeding an entire state’s power production and consumption, which places it in a different category altogether — closer to a purpose-built energy district than a traditional data center.
Equally telling is the phrase “generate and consume.” The project is not simply a large load waiting for a utility hookup; it is expected to produce its own power at state-exceeding scale. That reflects a broader industry shift: when grid interconnection queues stretch for years, the largest AI developers increasingly bring their own generation rather than wait for the grid to catch up.
With final approval reportedly near, the project is a live test of how states weigh the economic development promise of AI campuses against questions about energy, water, land, and who ultimately bears the costs.
When One Campus Outweighs a State Grid
The comparison in the headline is the story. A state’s power system is the aggregate of every home, factory, farm, and city within its borders, built out over a century. A single campus expected to exceed that total implies a facility measured in gigawatts — thousands of megawatts — rather than the tens or low hundreds of megawatts that defined “hyperscale” even five years ago. For readers outside the industry: one gigawatt is roughly the output of a large nuclear reactor, and AI training clusters are now being planned in multiples of that unit.
This is the practical consequence of the AI compute race. Training and serving frontier AI models consumes electricity at industrial scale, and the constraint on building more capacity has shifted from chips and buildings to power. Projects are now sited where energy can be produced or delivered, and their announcements are increasingly described in energy terms first and computing terms second — exactly as this one is.
Generate and Consume: The Rise of Self-Powered Campuses
The report’s framing — that the project would generate as well as consume state-exceeding power — points to on-site or dedicated generation. This has become the defining pattern of the largest AI campuses. Utility interconnection queues in much of the U.S. run three to seven years, and no traditional utility planning cycle anticipated single customers requesting gigawatts. Developers who cannot wait are building “behind-the-meter” generation: power plants constructed alongside or within the campus, serving it directly.
Self-generation changes the risk calculus for everyone involved. For the developer, it trades grid dependence for fuel, permitting, and construction risk. For the incumbent utility and its ratepayers, it can be a relief — the load largely pays its own way — or a complication, depending on how the campus interacts with the shared grid for backup, water, and transmission. Which of these applies here is not specified in the source, and it is the single most important detail for assessing the project’s local impact.
Why Utah
Utah has quietly been a data center state for over a decade: it hosts major existing facilities including Meta’s Eagle Mountain campus and the federal government’s Bluffdale data center, and the Intermountain Power installation near Delta has long exported Utah-generated electricity at scale. The state offers comparatively inexpensive land, a dry climate favorable to certain cooling designs, and a regulatory environment that has historically courted large industrial projects.
But a project of this magnitude tests that hospitality in new ways. Water for cooling in an arid state, air-quality implications of any fossil-fueled generation, transmission siting, and the sheer land footprint all become state-level policy questions rather than county zoning matters. The fact that the project is “nearing final approval” indicates it has so far navigated that process — though the source does not detail what conditions, if any, approval carries.
The Economics Nobody Has Priced Yet
Multi-gigawatt campuses imply capital costs in the tens of billions of dollars when computing hardware is included, recovered only if demand for AI compute stays on its current trajectory for years. That is a genuine open question for the industry: these are among the largest private infrastructure bets in American history, and their payback depends on AI adoption curves that remain projections, not guarantees.
For host states, the bargain is also unsettled. Data centers bring construction jobs, property tax base, and prestige, but comparatively few permanent jobs per dollar invested, and their energy and water demands are permanent. States like Utah that approve state-scale campuses early will generate the case studies — favorable or cautionary — that the rest of the country uses to negotiate.
Background
Utah has been part of the U.S. data center map for over a decade, hosting Meta’s Eagle Mountain campus, the federal government’s Bluffdale facility, and the Intermountain Power installation near Delta, which has long generated Utah power at export scale. But the AI era has redefined what a large project looks like: campuses once measured in tens of megawatts are now proposed in gigawatts, with developers increasingly building dedicated generation rather than waiting years in utility interconnection queues. A project expected to exceed an entire state’s power production and consumption represents the outer edge of that trend as of early 2026.
Meta has confirmed that it will operate a hyperscale data center in east Tulsa, Oklahoma, according to the Tulsa World on 21 April 2026. The confirmation resolves the identity of the operator behind a large industrial computing project in the city’s eastern industrial corridor.
The report establishes the operator and the general location. It does not, in the material available to us, attach a published megawatt figure, capital investment number, employment commitment, construction schedule or incentive package to the project — all of which remain the substantive questions for Tulsa residents, ratepayers and suppliers.
Executive Summary
The news is the confirmation itself. Large data center projects are routinely assembled under placeholder corporate names and non-disclosure agreements while land is optioned, utility service is negotiated and incentives are cleared; the operator’s name is often the last thing to surface. Meta putting its name to an east Tulsa campus turns a speculative local story into a fixed point that utilities, contractors, county assessors and competing site selectors can now plan around.
It matters because “hyperscale” is not a small industrial category. A single modern hyperscale campus can become one of the largest electricity customers in its host utility’s territory, reshaping load forecasts, transmission planning and the economics of new generation for everyone else on the system. Whatever this specific site’s final size, its arrival changes the planning assumptions in northeastern Oklahoma.
It also matters for Oklahoma’s position in the national compute map. The state already hosts one of Google’s long-running campuses at Pryor, roughly an hour from Tulsa. A second major operator in the same region begins to look less like an isolated deal and more like a cluster — with the labor pool, contractor base and transmission attention that clusters attract, and the concentration risks that come with them.
What “Hyperscale” Confirms — and What It Doesn’t
“Hyperscale” describes an operating model, not a unit of measurement. It means a facility built and run at the scale of the largest cloud and platform companies: standardized building templates, tens of thousands of servers, custom networking, and power delivered at transmission voltage rather than the distribution voltage a typical factory takes. It says nothing precise about how many megawatts the site will draw or how many buildings will eventually stand on it.
That distinction matters here because the confirmation carries no published capacity figure. Industry framing around new campuses has drifted toward gigawatt-class language — a gigawatt being roughly the output of a large power plant, or the demand of a mid-sized city — and the largest recent US announcements have been in that range. But an unstated capacity is an unstated capacity. The honest reading on 21 April 2026 is that Meta has confirmed an operator and a location, and that anyone quoting a wattage for east Tulsa is extrapolating from the industry’s recent pattern rather than from the announcement.
The same caution applies in the other direction. Absence of a headline number is not evidence the project is modest; hyperscale campuses are typically phased, with each phase authorized against demand that does not yet exist when ground breaks. The realistic expectation is a site that grows in steps over years, with the final footprint set by demand and by how much power the local grid can actually deliver.
Tulsa’s Grid Math: PSO, SPP and the Wind Belt
Tulsa is served by Public Service Company of Oklahoma, an American Electric Power subsidiary, inside the Southwest Power Pool — the regional grid operator covering much of the central plains. That footprint has two relevant characteristics. It has abundant wind generation, which has historically made Oklahoma power cheap and carbon-light on an annual-average basis, and it has the classic wind-region problem that supply peaks when the wind blows rather than when a data center is drawing its steady, around-the-clock load.
Hyperscale load is close to flat: high utilization, day and night, largely indifferent to weather. Marrying that profile to a wind-heavy system means firm capacity, storage, transmission upgrades, or some combination — and the question of who pays for them is the central regulatory issue in nearly every large-load interconnection in the country right now. Utilities increasingly seek special large-load tariffs with minimum take obligations and exit fees, precisely so that if a campus is cancelled or shrinks, the infrastructure built for it does not land on residential bills.
Nothing in the confirmation tells us which structure applies here. That is the thing worth watching: the utility filings and any state regulatory dockets will disclose more about the real terms of this project than any ribbon-cutting will. If the arrangement is well designed, a very large customer paying full freight for its own upgrades can spread fixed system costs across more kilowatt-hours and mildly benefit other ratepayers. If it is poorly designed, the transfer runs the other way. Both outcomes are common enough that the question is not rhetorical.
Water, Land and the Terms of the Bargain
Water is the second recurring flashpoint, and it turns almost entirely on cooling design. Evaporative cooling is efficient with electricity but consumes water continuously; closed-loop and air-cooled designs consume far less water while drawing more power for the same heat rejection. Operators have moved toward lower-water designs in dry regions, and several publish water-use figures, but a design choice for east Tulsa has not been stated. Tulsa’s municipal supply comes from northeastern Oklahoma reservoirs and is not the constrained desert supply that has made this a crisis issue elsewhere — which lowers the temperature of the question without settling it.
On the fiscal side, Oklahoma has long used sales-tax exemptions on qualifying computing equipment and local property-tax abatements to compete for capital-intensive facilities. These tools work as intended: they lower the effective cost of the single most expensive input in a data center, the servers and electrical plant. They also produce the familiar asymmetry that makes such deals contentious. Construction employment is large and temporary — often well over a thousand trades workers at peak on a big campus — while permanent operations staffing at even very large sites is measured in the low hundreds. The durable local benefit is usually the property tax base after abatements expire, plus utility revenue and construction spending, not headcount.
That is an argument to be had on specifics, and the specifics have not been published. A fair assessment of this deal requires the abatement schedule, the assessed valuation assumptions, any clawback provisions, and the wage and hiring commitments. Until those are on the table, both boosterish jobs claims and blanket assertions that the community gets nothing are running ahead of the evidence.
A Second Oklahoma Cluster, and Who Gains From It
The clearest beneficiaries are regional and immediate: electrical and mechanical contractors, civil and earthworks firms, switchgear and transformer suppliers, fiber builders, and the trades unions and training pipelines that staff them. Data center construction is unusually equipment-heavy and schedule-driven, which tends to pull skilled labor from a wide radius and bid up local rates for the duration. Tulsa’s existing industrial and aerospace workforce is a reasonable base for that.
The second-order winner is Oklahoma’s site-selection story. Google’s long presence at Pryor gave the state a reference customer; a Meta campus near Tulsa gives it two independent validations, which is what site selectors for the next tenant actually look for. Clusters compound — transmission gets built, permitting staff get experienced, suppliers open local branches. The corresponding risk is concentration: a region that leans on a handful of very large loads inherits their capital cycles, and the AI build-out that is driving current demand is not guaranteed to hold its present pace.
The parties with the most at stake and the least information right now are residential and commercial ratepayers, and the neighborhoods nearest the site. Their exposure runs through utility tariffs, transmission cost allocation, construction traffic and noise, and the local tax base. Those are all decided in public proceedings — utility commission filings, county assessor records, municipal permits — and that is where scrutiny is best directed, by supporters and critics alike.
Background
Meta operates a global fleet of company-built data centers supporting its social platforms and, increasingly, large-scale AI training and inference. Like other hyperscalers, it typically develops campuses in phases on large rural or industrial parcels chosen for power availability, land, fiber routes and tax treatment, and it has expanded that program substantially through the current AI infrastructure cycle.
Oklahoma has competed for these projects on cheap land, a wind-heavy generation mix within the Southwest Power Pool, and long-standing tax exemptions for computing equipment. Google’s Pryor campus in the MidAmerica Industrial Park has been the state’s anchor example for over a decade. Tulsa itself brings an industrial and aerospace workforce and a metro-scale utility system, which is what distinguishes it from the small rural sites that have hosted most recent hyperscale announcements in the region.
