jain.com — data centers, connectivity and security, analyzed daily

Tag: Oklahoma

  • 55 Oklahoma Data Centers, Zero Water Permits: AI Cooling Runs on Utility Contracts

    55 Oklahoma Data Centers, Zero Water Permits: AI Cooling Runs on Utility Contracts

    TL;DR · 30-second read

    The Short Version

    Oklahoma has about 55 data centers, the giant warehouses of computers behind apps, websites and artificial intelligence. Not one has applied for a state permit to draw water.

    They buy water from local utilities like any other customer, so the state does not track how much they use. One Google site uses as much water each year as 10,000 homes, and most of it evaporates.

    With a $15 billion campus proposed near Yukon in a state hit by years of drought, neighbors are asking questions developers are not yet required to answer.

    None of the 55 data centers that advisory firm Baxtel lists in Oklahoma has applied for a state water permit, according to reporting by Investigate Midwest published in The Oklahoman. They buy water as customers of municipal utilities, rural water districts or industrial parks that already hold water rights, so their consumption sits largely outside state oversight. Senate Bill 259, signed by Gov. Kevin Stitt in May, allows groundwater permits for data centers only if they use water-conserving, recycling cooling systems, but it does not reach facilities that buy water instead of seeking permits.

    The gap is drawing attention as Atlanta-based Beltline Energy proposes a $15 billion, 1,000-megawatt campus of 15 buildings on 480 acres straddling Oklahoma City and Yukon. Yukon is considering selling the project up to 2.5 million gallons of wastewater per day, while Beltline has requested extensions on the water agreement and has not said which cooling system it would use.

    Executive Summary

    Oklahoma’s newest data center water rule targets the one route data centers do not use. State permits govern taking water directly from aquifers and rivers; data centers instead contract with local suppliers. “So far, we have not had any permits issued specifically to data centers,” said Julie Cunningham, director of the Oklahoma Water Resources Board.

    The practical consequence is that the decisions that determine how much water an AI campus consumes, including its volume, its source and whether it evaporates or recycles cooling water, are being made in municipal supply agreements rather than state permits. Yukon’s pending contract with Beltline is a live example.

    Closing the permitting gap would not by itself produce usage data. The state relies on self-reported figures, metering requirements have failed twice, and the water board reported fewer than 20 staff in 2025. Rep. Carl Newton, the author of SB 259, says a new bill next year will address data centers drawing groundwater through a secondary source.

    Why the Permit Rule Misses the Meter

    SB 259 attaches a sensible condition to groundwater permits: data centers can get one only if their cooling systems are designed to conserve and recycle water. But a permit is only required when a user withdraws water itself. A data center that buys from a city, a rural water district or an industrial park holding industrial water rights is treated as an ordinary customer of that system, and the state never sees an application. That is why a statewide count of zero permits sits alongside 55 listed facilities.

    The real regulatory instrument is therefore the supply contract. Google’s Pryor data center, the state’s largest, buys water from the state-owned MidAmerica Industrial Park, which draws and treats it from the Neosho River. Beltline’s Yukon purchase agreement hinges on a separate water agreement with the city. Whoever negotiates those contracts, usually a municipal utility or city council, effectively decides volume, source and whether the water is potable or treated wastewater. The state’s conservation standard never enters the room.

    This matters for everyone on the supply side. City water utilities are becoming the de facto gatekeepers for AI cooling, often with small staffs and without statewide guidance. Developers face a patchwork of local terms rather than one state rulebook. And residents who want answers, like Yukon-area neighbor Pencia Truhan, who said developers “don’t have to tell us what they’re going to do about water,” find no state filing to consult.

    The Cooling Choice Is Also a Power Choice

    Cooling design is where water and electricity trade off. Open-loop, or evaporative, systems like Pryor’s lose water to the atmosphere: Google reports the site consumes 1.1 billion gallons a year, about the annual use of 10,000 American households, and returns roughly 275 million gallons to the Neosho River. That leaves about 825 million gallons evaporating each year. Closed-loop systems recirculate water, and air-cooled systems use little water but significantly more electricity.

    For Beltline’s proposal, that trade-off lands on an unusually large base. A 1,000-megawatt campus would, at full capacity, draw roughly as much electricity as Oklahoma City’s average use and more than double the demand of Google’s Pryor facility. Choosing air cooling to spare local water would push that electricity figure higher; choosing evaporative cooling would do the reverse. Because the cooling system has not been disclosed, neither the water nor the full power burden can yet be estimated.

    Yukon’s Math: Wastewater, Wells and a 2035 Deadline

    Yukon’s planning memo describes selling Beltline up to 2.5 million gallons of wastewater a day, and officials have promised the project will not rely on drinking water. At full volume that is about 900 million gallons a year, comparable in scale to what Pryor evaporates annually. Using treated wastewater is a common way to spare potable supply, but the sale still commits a resource the city may want for other purposes.

    The city’s supply position is already tight. Yukon relies on 15 leased wells in the Garber-Wellington Aquifer plus purchases from Oklahoma City, and those leases expire in 2035. A city-commissioned study projects its 27,300 residents will grow by about 23% over 25 years, in Canadian County, the state’s fastest-growing county. Against that, Beltline-commissioned studies project 450 permanent jobs and $543.12 million in tax revenue over 25 years, figures that potential tax abatements would significantly reduce.

    Measurement Is the Harder Fix

    Even a closed loophole would leave a data gap. The Oklahoma Water Resources Board relies on self-reported water use. Newton’s original bill would have required commercial groundwater users to install meters; that provision was removed after opposition from Panhandle irrigation groups, and Stitt vetoed similar legislation in 2023 after the Oklahoma Farm Bureau and others argued it infringed on private property rights.

    Capacity is the other constraint. In 2025 the board reported fewer than 20 staff handling an average of 250 permit applications and amendments a year, plus investigations and fieldwork, and its 140-page Water Demand Forecast from last October does not mention data centers. Cunningham said the agency is working to build expertise. Until measured data exists, planners in a drought-stressed state are forecasting water demand without one of its fastest-growing users in the model.

    Background

    Data centers house the servers behind everyday online services, and the newest hyperscale facilities built for artificial intelligence concentrate enough computing to generate heat on an industrial scale. Removing that heat often uses large volumes of water, which is why cooling design has become a siting issue alongside land and power. Oklahoma already hosts one of Google’s largest facilities in Pryor, where the company outlined plans addressing power and water for new sites, and the state is drawing further proposals.

    Beltline Energy, based in Atlanta, began as a renewable energy developer that secured land and developed solar projects before selling them to investors, and it is applying a similar model to data centers. It has developed more than a dozen solar farms but lists no completed data center projects. Its Oklahoma proposals, in Yukon and Oklahoma City, Piedmont and Luther, arrive as the state’s water regulator, which relies on self-reported usage data, works to develop expertise in the sector.

    Sources

    Source: Loophole leaves data center water consumption in Oklahoma largely untracked (The Oklahoman), on how Oklahoma data centers buy water from utilities outside state permitting, and the proposed Beltline Energy campus near Yukon.

  • Meta Confirms Hyperscale Data Center in East Tulsa

    Meta Confirms Hyperscale Data Center in East Tulsa

    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.

    Source: It’s official: Meta will operate hyperscale data center in east Tulsa — Tulsa World, 21 April 2026, reporting Meta’s confirmation that it will operate a hyperscale data center in east Tulsa, Oklahoma.