Kentucky’s two biggest cities are drawing lines around the giant computer warehouses being built to run artificial intelligence.
Louisville proposed a size limit of 500,000 square feet, roughly nine football fields. Only three months earlier, the city approved one about 28 football fields big. Lexington stopped accepting new applications until October 31 after neighbors objected to plans to expand one.
Why it matters: city halls, not just tech companies, are now deciding how big these buildings can get and where they can go.
Kentucky’s two largest cities moved on June 9 to rein in hyperscale data centers, the Kentucky Lantern reported. Lexington’s Urban County Council suspended its legislative rules to impose a moratorium on data center applications through Oct. 31 while it writes zoning amendments. The same day, the Louisville Metro Planning Commission released a draft ordinance that would ban any data center larger than 500,000 square feet and restrict facilities over 250,000 square feet to industrial areas.
Louisville residents have 30 days to comment on the draft before it goes to Louisville Metro Council. In March, the same planning commission approved a 1.6 million-square-foot data center in West Louisville despite local opposition.
Executive Summary
Lexington and Louisville took different routes to the same goal on the same afternoon. Lexington hit pause: no new data center applications until Oct. 31, prompted by a developer’s purchase of a local data center property that it intends to expand. Louisville went straight to rules: a draft siting ordinance with a hard size ceiling of 500,000 square feet and industrial-only zoning for anything over 250,000 square feet.
The significance lies in the numbers. Louisville’s proposed ceiling is less than a third of the size of the facility the city approved three months earlier. For developers planning large AI campuses, that means the maximum scale of a project in Kentucky’s biggest city may be fixed by a planning document, regardless of what the grid or the supply chain could support.
Both cities cited resident concern. Lexington Mayor Linda Gorton said she supports “very tight controls” and that the city does not support public incentives for the developer seeking to expand.
A Ceiling Set Below a Third of March’s Approval
The number that carries this story is the gap between two Louisville decisions made three months apart. In March, the Louisville Metro Planning Commission approved a 1.6 million-square-foot data center in West Louisville over local objections. On June 9, the same commission released a draft ordinance that would ban any data center larger than 500,000 square feet, less than a third of that approved facility, and confine anything over 250,000 square feet to industrial zones.
This is how local zoning becomes a constraint on the scale of AI buildout. Hyperscale campuses, the very large facilities built for cloud and AI operators, draw much of their economic advantage from concentration: one site, one large electrical connection, one security perimeter, shared cooling infrastructure. A hard floor-area ceiling means a developer who wants that scale in Louisville would have to split it across buildings or sites, if the final ordinance allows that at all, or build somewhere else. In either case, the largest permissible project is being set by the planning code, independent of what power and equipment supply could support.
The effects fall on specific groups: developers and landowners holding Louisville sites, the local utility planning for large new electrical loads, and residents who opposed the March approval. Brian Davis, director of Louisville’s office of planning, described the goal as “clear, achievable standards that provide transparency and clarity for both residents and potential developers.” Clarity does have value for investors, since a known ceiling is easier to finance around than a case-by-case fight. But the ceiling sits well below the size of the projects that prompted it.
Two Cities, Two Tools: Pause Versus Rulebook
Lexington and Louisville used different instruments on the same day. Lexington’s council suspended its legislative rules to impose a moratorium through Oct. 31 while it drafts zoning amendments: pause first, rules later. Louisville, where a separate committee tabled a data center moratorium earlier in June, went straight to draft regulations and opened a 30-day public comment period before the ordinance reaches Metro Council.
For developers, the difference matters. A moratorium stops the clock entirely and leaves the eventual rules unknown. Lexington’s amendments could end in controls or, potentially, an outright ban. A draft ordinance keeps applications possible and tells the market roughly what it will face. Neither city has final rules today, and Lexington’s pause alone runs for nearly five months.
Lexington’s action was triggered by a single transaction, a developer buying an existing local data center property with plans to expand it. Council member Emma Curtis called it “a case of an issue being expedited because of constituent concern and advocacy.” That is a direct statement that resident objections, not a staff study, set the timetable. That is a legitimate part of local democracy. It also means the rules will be written with one specific project in view.
Square Feet Are a Blunt Proxy for the Grid
Mayor Gorton stated the concern most clearly: data centers “do not produce many jobs, and have the potential to increase utility costs on local residents.” Both points are common in these debates, and both deserve the same scrutiny applied to developers’ promises of economic benefit. Gorton did not attach figures to either claim. Whether a large facility actually raises household bills depends heavily on how the utility and state regulators assign the cost of new generation and transmission, and neither city’s action settles that question.
That exposes a limit in Louisville’s approach. Floor area is easy to measure and enforce, but it is only an indirect measure of what worries residents most: electricity demand. Servers built for AI draw far more power per rack than conventional cloud equipment, so two buildings of the same size can place very different loads on the grid. A 500,000-square-foot cap controls land use, traffic and physical footprint. It controls power draw only loosely.
For industry readers, the practical point is that Kentucky’s largest cities are regulating the most visible dimension of data centers first. Site selection now depends on local square-footage thresholds as well as power availability and land cost, and Louisville’s shift between March and June shows those thresholds can move within a single planning cycle.
Background
Kentucky has long hosted smaller data centers supporting services such as cloud storage. The wave of investment in artificial intelligence has brought a different class of facility nationwide: hyperscale data centers that can consume as much electricity as an entire power plant and can span millions of square feet.
Louisville has already experienced that shift. In March its Planning Commission approved a 1.6 million-square-foot data center in West Louisville despite local pushback, and earlier in June a separate city committee tabled a proposed data center moratorium. Lexington’s action followed a developer’s purchase of an existing local data center property with plans to expand it.
Birmingham, Alabama, has passed strict new rules for giant data centers, the warehouse-sized buildings full of computers that run cloud services and artificial intelligence.
They must sit at least 500 feet from homes, more than a football field and a half.
They cannot run their own gas-fired power plants on site.
Their cooling must use no more water than an ordinary office building.
Nearby neighbors must be told by certified letter before one is built.
The city, not the state, now decides these terms.
The City of Birmingham announced on June 9, 2026, that its City Council had approved a zoning ordinance setting 20 protective conditions for hyperscale data centers, the very large facilities built by cloud and AI operators. The city describes it as the toughest such ordinance in Alabama.
The rules include a 500-foot setback from residential districts, a 1,000-foot separation from high-capacity transit facilities, a 5-acre minimum lot size, mandatory closed-loop cooling, a ban on onsite gas turbines and round-the-clock diesel generation, noise studies before and after construction, disclosure of projected peak electricity demand, and certified-mail notice to property owners within 500 feet.
Executive Summary
Birmingham has written the most contested parts of AI data center development, power, water and noise, directly into its zoning code. A developer seeking a site in the city now has to show where its water comes from, how much electricity it expects to draw at peak and in what phases, which utility will supply it, and how it will keep noise at the property line in check, all before the project can proceed.
The most consequential provision is the prohibition on onsite gas turbines and diesel generators running 24/7. Onsite gas generation has become one of the ways large AI campuses bring capacity online faster than a utility connection allows. Birmingham has closed that route within city limits while leaving room for solar, fuel cells and battery storage under review.
The city pairs these limits with a pitch: it cites its strong electrical grid, industrial infrastructure and affordable land as reasons developers want to build there. The ordinance is an attempt to keep that demand while setting the conditions locally.
Power Moves From the Utility Contract to the Zoning File
Traditionally, how a data center gets its electricity is negotiated between the developer and the utility, and the city’s role is limited to land use. Birmingham’s ordinance changes that in two ways. First, it restricts the generation a site may build for itself: gas turbines and diesel generators running around the clock are prohibited, solar and fuel cells are allowed, and battery storage is permitted subject to emergency-response review. Second, it requires developers to disclose projected peak demand, planned development phases and the identity of the utility provider as part of the application.
For AI-focused developers, that matters because speed to power is often the binding constraint. When a utility cannot deliver a large new connection quickly, one workaround has been to install gas turbines on site and run them as primary or bridging power. Within Birmingham, that option is off the table. A hyperscale project there will depend on grid supply, supplemented only by solar, fuel cells or batteries, which puts the utility’s delivery timeline back at the center of the project schedule.
The disclosure requirement has a quieter effect. Peak demand projections and phasing plans give the city a public record of how much load each project intends to add and when. That turns electricity from a private commercial term into something neighbors and officials can see and question during permitting.
The Water Rule Is a Performance Standard With an Energy Cost
The ordinance does not just require closed-loop cooling; it sets a benchmark that water use be no greater than that of a similarly sized office building. That is a performance test, not simply a technology checkbox. Closed-loop systems recirculate the same coolant rather than evaporating water to shed heat, which sharply reduces consumption.
The trade-off is well understood in the industry: cooling without evaporation generally takes more electricity, particularly in hot, humid summers like Alabama’s. Birmingham has therefore chosen to protect local water supplies at the price of somewhat higher power draw per facility, which loops back to the peak demand figures developers must now disclose. Dense AI hardware, which runs hotter than conventional servers, makes that trade-off more pronounced.
Setbacks, Not Lot Size, Will Decide Where Campuses Fit
A 5-acre minimum lot is modest by hyperscale standards, so it is unlikely to be the constraint that matters. The 500-foot setback from residential and urban neighborhood districts is more demanding: a 5-acre parcel is only about 470 feet on a side if square, so a small site bordering a neighborhood could struggle to fit a building at all. In practice, the rules steer large projects toward bigger industrial tracts, which Birmingham, with its long manufacturing history, has in supply.
The 1,000-foot separation from high-capacity transit facilities is less common. It keeps land near major transit, which cities typically reserve for housing and employment-dense development, from being absorbed by facilities that employ relatively few people once built. Combined with pre- and post-construction noise studies, acoustical walls and certified-mail notice within 500 feet, the ordinance front-loads community disclosure rather than leaving disputes to surface after construction.
Weighing the City’s ‘Toughest’ Claim
The city’s description of the ordinance as Alabama’s toughest and as a mark of national leadership is its own characterization, and it has not published a side-by-side comparison with other jurisdictions to support it. What can be said is that combining an onsite gas ban, a water-use benchmark, noise studies and power disclosure in a single zoning instrument is more comprehensive than codes that address only setbacks or noise.
For developers, stricter rules are not purely a cost. Clear conditions published in advance reduce the risk of a project being stalled by opposition late in the process, and a site that meets them arrives with a documented answer to the questions neighbors most often raise. The larger point is structural: state-level tax incentives can make Alabama attractive, but in Birmingham it is the city code that now determines whether and how a specific site gets built.
Background
Birmingham grew as an iron and steel center, leaving it with industrial land, heavy electrical infrastructure and rail and utility corridors that suit large facilities. Alabama has courted data centers with state tax incentives and has already drawn large projects from companies such as Google and Meta elsewhere in the state.
Nationally, the surge in AI computing has driven demand for ever-larger data centers that consume significant electricity and, depending on cooling design, water. Many local zoning codes were written before facilities of this scale existed, and cities have begun adding specific rules on siting, noise, water and power as proposals arrive.
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.
