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

Tag: AI infrastructure

  • Louisville’s 500,000 Sq Ft Cap Shows Local Zoning Now Gates AI Data Center Scale

    Louisville’s 500,000 Sq Ft Cap Shows Local Zoning Now Gates AI Data Center Scale

    TL;DR · 30-second read

    The Short Version

    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.

    Sources

    Source: Kentucky’s two largest cities take action to address concerns over hyperscale data centers (Kentucky Lantern), on Lexington’s data center moratorium and Louisville’s draft data center siting ordinance.

  • Amazon’s 7x Water Claim Rests on Hotter Servers, a Test for AI-Era Cooling

    Amazon’s 7x Water Claim Rests on Hotter Servers, a Test for AI-Era Cooling

    TL;DR · 30-second read

    The Short Version

    Amazon says the buildings that run its websites, apps and artificial intelligence services use about one-seventh the water of a typical facility of their kind.

    The main trick is letting the computers run warmer. Outside air cools the buildings about 90% of the time. Water is used only when it is hotter than about 85 degrees Fahrenheit outside.

    This matters because these buildings are multiplying, and their neighbors want to know how much local water they take. The open question is whether the newest artificial intelligence chips, which Amazon says needed a new kind of liquid cooling, will let that approach last.

    Amazon said in a June 11, 2026 post on its About Amazon site that its global data center operations used 0.12 liters of water per kilowatt-hour (L/kWh) in 2025. The company puts that at more than seven times better than an industry average of 0.84 L/kWh and says it is a 52% improvement since 2021. It withdrew about 2.5 billion gallons of water across its global data center footprint in 2025.

    Amazon credits two things for the result. The first is free-air cooling, which it uses about 90% of the time. The second is higher server temperature limits, so that evaporative cooling runs only when outside air is above roughly 85°F. The company also said it is 75% of the way to its 2030 water-positive goal and that it runs 26 facilities on 100% reclaimed water, with 130 more contracted.

    Executive Summary

    Amazon has published a headline water-efficiency figure for its data centers: 0.12 liters of water for every kilowatt-hour of energy in 2025. It set that against an industry average of 0.84. The company explains how it got there. It relies on outside air for most cooling, uses evaporative cooling only in the hottest hours, and has spent several years raising the temperatures its servers are allowed to run at. It says this cut water use without raising hardware failure rates.

    The figure matters because water has become one of the main local questions asked of new data center campuses. Amazon’s explanation also shows that water efficiency is a set of engineering trade-offs, not a fixed property of a building. The company chose to use some water on hot days rather than run chillers, which it says need 25% to 35% more electricity at the moments the grid is most stressed.

    Two things are harder to assess. One is the comparison itself: Amazon did not publish how the 0.84 average was built or on what basis each peer’s figure is measured. The other is the future. Amazon says denser AI chips already required a custom liquid cooling system, so the air-first approach behind the 7x figure now has to hold up as AI capacity grows.

    The Water Number Is Really a Temperature Number

    Amazon’s 0.12 liters per kilowatt-hour did not come from a new water technology. It came from deciding how rarely to use water at all. About 90% of the time, Amazon says, its data centers use free-air cooling. Outside air is drawn past the servers and pushed back out, with no water involved. Water comes into play only through evaporative cooling. In that process, hot air passes through a water-soaked medium and cools by five to 10 degrees as the water evaporates. Amazon now switches that on only when outside air exceeds roughly 85°F.

    That threshold is the lever. Every degree of heat the servers can tolerate removes hours from the evaporative season, so raising operating temperatures cuts water use directly. Amazon’s own evidence is specific:

    • Two identical data centers on the same campus, one running hotter, differed by about 50% in water use.
    • Northern Virginia, its largest region by IT load (the power drawn by the computing equipment itself), cut water use 42% year over year while demand grew.
    • Thousands of hours of campus data showed no increase in failure rates at the higher temperatures.

    Those results fit the 52% efficiency improvement Amazon reports since 2021.

    The same logic is why this is a test for AI-era cooling. The approach depends on air being able to carry heat away from the servers. Amazon itself says denser, more powerful AI chips required a completely custom liquid cooling system. It has not said how much of its fleet now runs that way, whether those systems rely on evaporative water on hot days, or how a growing share of AI capacity will move the 0.12 figure. The air-first playbook behind the 7x gap was proven on the fleet Amazon has run since 2021. Whether it carries over to high-density AI halls is the next data point to watch.

    Water or Watts: The Trade Behind the Ratio

    Amazon is explicit that a low water number is partly a choice about electricity. The alternative it names is chillers, which work like giant air conditioners and, by Amazon’s figures, typically need 25% to 35% more electricity. The timing of that extra load is the problem. It arrives in the hottest hours, when household air conditioning is already straining the grid. Amazon concluded it is better to spend some water on those days than to add power demand at the peak.

    That is a defensible engineering position, and it cuts against a simple reading of water metrics. An operator could report a lower water ratio by running chillers, which shifts the burden onto the grid and, depending on how that electricity is generated, onto water used off site. Conversely, a site that uses more water may be sparing a stressed grid. For utilities and local planners, the useful question is how much water and how much power a campus uses together at the peak hour, not either one in isolation.

    Amazon did not quantify the grid side of its trade. It has not said how much peak demand evaporative cooling avoids across its fleet, or how many hours a year its sites in hot regions exceed 85°F. Without those figures, the argument rests on the chiller penalty range alone.

    Why 0.12 and 0.84 Are Hard to Line Up

    Liters per kilowatt-hour is the industry’s standard water-efficiency ratio, often called water usage effectiveness. It divides the water used for cooling by the energy consumed by the IT equipment. Amazon describes it as water per unit of compute, but the denominator is energy, not work done. A fleet running more efficient chips gets more computing out of each kilowatt-hour, and the metric does not capture that in either direction.

    The 7x claim depends entirely on the 0.84 industry average. Amazon’s chart cites sustainability reports and blogs from Microsoft, Google and Meta alongside its own report. The company did not publish how 0.84 was derived: which operators it covers, how they were weighted, or whether each figure measures water withdrawn (taken from a source) or water consumed (evaporated and not returned). Large operators do not all report water the same way, so a like-for-like reading requires knowing which basis each number uses.

    Scope matters too. Amazon’s absolute figure, about 2.5 billion gallons in 2025, is a withdrawal number for its global data center footprint. The 2% year-over-year decline it cites applies only to sites it owns and operates directly. The company did not say whether the 0.12 ratio is based on withdrawal or consumption, or whether leased facilities are included. None of that makes the claim wrong. It does mean the 7x multiple is Amazon’s own calculation rather than a figure a reader can reproduce from peers’ reports.

    Replenishment and Reclaimed Water Carry the Local Story

    Efficiency is only half of Amazon’s water case. The company has committed to being water positive by 2030, meaning it returns more water to communities than its data center operations use. It says it is 75% of the way there, returning 3 gallons for every 4 used in 2025. It has announced more than 50 projects that are expected to return over 5.8 billion gallons a year once fully implemented, which is more than twice its 2025 withdrawals. Examples include:

    • storing Columbia River winter flows in an aquifer in Hermiston, Oregon;
    • a runoff pipeline in Pina del Ebro, Spain;
    • watershed restoration near Guadalajara, Mexico.

    Replenishment is an accounting balance. Its value to a given town depends on whether the returned water lands in the same basin the data center draws from. Reclaimed water addresses the local question more directly, because it replaces drinking water with treated wastewater at the site itself. Amazon says 26 facilities already run on 100% reclaimed water, more than any other cloud provider, and 130 more are contracted. It has also funded infrastructure and helped with permitting for programs in Mississippi, Hong Kong and Indonesia. If those 130 facilities come online, reclaimed supply may matter as much to neighbors as the headline efficiency ratio.

    Background

    Amazon operates one of the world’s largest data center fleets, mostly to run Amazon Web Services (AWS), its cloud computing business. Data centers convert nearly all the electricity they use into heat, and removing that heat is where most of their water goes. The industry commonly measures water efficiency as liters of water per kilowatt-hour of IT energy, a ratio known as water usage effectiveness, or WUE.

    Amazon has committed to being water positive by 2030 and has expanded its use of reclaimed water from wastewater treatment plants. Amazon says data centers account for less than 0.5% of global industrial water use. Still, where a campus draws its water matters to the surrounding community, and Amazon says its water team is particularly focused on water-scarce areas.

    Sources

    Source: Amazon’s data centers are 7x more water-efficient than the industry average. Here’s how we do it. (About Amazon): Amazon’s account of its 2025 data center water efficiency, cooling methods, and progress toward its water-positive goal.

  • Dell’Oro: AI Buildouts and Memory Inflation Push 1Q 2026 Data Center Capex Higher

    Dell’Oro: AI Buildouts and Memory Inflation Push 1Q 2026 Data Center Capex Higher

    Market research firm Dell’Oro Group reported that worldwide data center capital expenditure moved higher in the first quarter of 2026, attributing the increase to two forces working in tandem: continued buildouts of AI infrastructure and inflation in memory costs. The finding, published June 10, 2026, comes from the firm’s ongoing tracking of data center IT and infrastructure spending.

    The headline pairing matters. It signals that the capex surge is being driven not only by more servers, accelerators, and facilities being deployed, but also by each unit of that equipment costing more — a distinction with real consequences for how the numbers should be read.

    Executive Summary

    Dell’Oro Group’s first-quarter 2026 reading extends a multi-year run of elevated data center spending tied to artificial intelligence. Capex — capital expenditure, the money operators sink into servers, networking gear, storage, and the facilities that house them — climbed again in the quarter, with AI infrastructure named as the primary engine and memory cost inflation as a significant amplifier.

    The memory angle is the notable wrinkle. High-bandwidth memory (HBM) and conventional DRAM are essential inputs to AI servers, and when their prices rise, total spending rises even if unit volumes were flat. Dell’Oro’s framing suggests both effects are in play: operators are buying more, and paying more per unit of what they buy.

    For the infrastructure industry, the read-through is that the AI spend cycle is broadening rather than cresting. Spending strength that persists into 2026 — after two years in which skeptics repeatedly called a peak — keeps demand signals strong for chipmakers, memory suppliers, server OEMs, colocation providers, and the power and cooling ecosystem behind them.

    Broadening, Not Peaking

    Every quarter of continued capex growth is a data point against the “AI bubble about to deflate” thesis — and a data point that must itself be scrutinized. A first-quarter increase in 2026 means the hyperscalers and large AI builders entered the year still accelerating, not digesting. Historically, capex cycles in IT infrastructure end with a visible plateau in quarterly spending before the decline; Dell’Oro’s reading indicates that plateau has not yet arrived.

    The word “broadening” is doing real work here. Early AI capex was concentrated in a handful of hyperscale cloud providers. As the cycle matures, spending typically spreads to second-tier cloud operators, GPU-cloud specialists, enterprises building private AI capacity, and sovereign or national AI initiatives. A quarter in which growth continues at scale is consistent with that widening base of buyers, though the release headline alone does not break out who spent what.

    Memory Inflation: Growth With an Asterisk

    The second driver Dell’Oro names — memory cost inflation — deserves careful reading. Memory (DRAM for general computing, and especially high-bandwidth memory stacked directly alongside AI accelerators) has been in tight supply as AI demand outstripped what the small number of memory manufacturers could produce. When memory prices rise, every AI server costs more, and aggregate capex inflates mechanically.

    That means dollar-denominated capex growth overstates the growth in deployed computing capacity. An analyst comparing 1Q 2026 spending to a year earlier is partly measuring more infrastructure and partly measuring more expensive infrastructure. For memory suppliers this is a windfall; for buyers it is margin pressure; for anyone using capex as a proxy for AI capacity coming online, it is a reason to discount the headline number somewhat. Dell’Oro’s decision to name inflation explicitly as a driver is a useful piece of intellectual honesty in a market prone to reading every big number as pure demand.

    Winners Along the Supply Chain

    The beneficiaries of this spending pattern are ordered by scarcity. Memory manufacturers sit at the top: rising prices on constrained supply flow almost directly to their revenue. Accelerator vendors and the server OEMs that integrate them continue to ride volume growth. Behind the IT equipment, the physical layer — data center developers, colocation operators, power equipment makers, and cooling specialists — benefits from every incremental megawatt the AI buildout requires, and their revenue tends to lag IT capex, meaning a strong 1Q 2026 for equipment implies continued facility demand into 2027.

    The squeezed parties are buyers without pricing power. Smaller cloud providers and enterprises paying inflated memory prices face a worse cost position than hyperscalers, who negotiate supply agreements at scale. If memory inflation persists, it acts as a regressive tax on the smaller end of the AI market — one more force concentrating AI capacity among the largest players.

    The Risk Ledger

    None of this eliminates cycle risk. Capex is a leading indicator of expected demand, not proven demand: the spending only pays off if AI services generate revenue commensurate with the infrastructure behind them. Input-cost inflation adds a second risk — cycles fed partly by price increases can unwind sharply when supply catches up and prices normalize, as memory markets have done repeatedly across their history. And the physical constraints on the buildout, chiefly electric power availability, remain unresolved in many markets.

    The balanced read: 1Q 2026 confirms the AI infrastructure cycle remains in its expansion phase, while the memory-inflation component is a reminder to separate dollars spent from capacity gained before drawing conclusions about either demand or durability.

    Background

    Data center capex has been the defining economic story of the AI era. Since large language models triggered an infrastructure race in 2023, the biggest cloud and AI companies have committed historically unprecedented sums to accelerated computing — spending that flows through chipmakers and server vendors into land, buildings, power, and cooling. Independent trackers like Dell’Oro Group, which has analyzed telecom and data center equipment markets since 1995, provide the industry’s scorecard for whether that race is accelerating or cooling.

    Memory has emerged as the cycle’s chokepoint. Production of high-bandwidth memory is concentrated among a handful of manufacturers, and AI demand has kept supply tight, pushing prices upward across memory categories. That inflation now shows up directly in aggregate capex figures — making 2026 the year analysts must ask not just how much the industry is spending, but how much of that spending buys new capacity versus simply covering higher input costs.

    Source: AI Infrastructure Buildouts and Memory Cost Inflation Drove Data Center Capex Higher in 1Q 2026, According to Dell’Oro Group — Dell’Oro Group’s first-quarter 2026 data center capex report announcement, published June 10, 2026.

  • Ohio Would Halve a $1.6B Data Center Break. The Harder AI Fight Is Who Pays for the Grid

    Ohio Would Halve a $1.6B Data Center Break. The Harder AI Fight Is Who Pays for the Grid

    TL;DR · 30-second read

    The Short Version

    Ohio lawmakers want to shrink a tax break for data centers, the giant warehouses of computers that run artificial intelligence and online services. The break cost the state roughly $1.6 billion last year. The bill would cut it in half.

    The bigger fight is over electricity bills. These buildings use so much power that new power lines and power plants have to be built. Manufacturers and environmental groups warn that ordinary households could end up paying part of that cost.

    Senators aimed to pass the bill within a day.

    Ohio state Sen. Brian Chavez unveiled a sweeping data center bill on Tuesday, June 9, attaching a long list of policy changes to a measure originally written only to study the issue, the Ohio Capital Journal reported. The proposal would cut the state’s discretionary sales and use tax exemption for data centers from 100% to 50%, or 75% for projects that build on brownfields and bring their own power. The exemption has grown to roughly $1.6 billion in the last year. The bill would also cap local property tax abatements at 50%, end data center access to Ohio’s 30-year mega project job creation grant, require data centers to track and report water use, and direct the Public Utilities Commission of Ohio (PUCO) to create a separate electricity rate class for data centers.

    The Senate Energy Committee was scheduled to advance the bill Wednesday morning, June 10, with a full Senate vote planned for later the same day.

    Executive Summary

    Ohio’s bill is one of the broadest state-level rewrites of data center policy so far. It covers tax incentives, nondisclosure agreements, water monitoring, utility billing, and a new surety bond meant to protect local governments. The tax provisions are the most concrete part. A roughly $1.6 billion incentive would be cut in half, with a larger 75% break reserved for projects on brownfields (previously developed, often contaminated land) that supply their own electricity.

    The provision that drew the sharpest testimony was the proposed data center rate class. It is modeled on the tariff PUCO approved for AEP Ohio last year, which the Ohio Manufacturers’ Association is now challenging in the Ohio Supreme Court. The underlying question is the one now running through every state served by PJM Interconnection, the regional grid operator: when AI-era data centers drive new transmission, distribution and generation spending, who ends up paying for it? PJM plans a backstop auction in September to secure 15 gigawatts of new generation. It has warned that without state rules, those costs could fall on other consumers, including residential customers.

    With a committee vote and a floor vote planned within about a day of introduction, the chance to refine the rate-class language before the Senate acts was limited.

    Tax Policy That Doubles as Power Policy

    The headline change is a 50% cut to the sales and use tax exemption. The more revealing detail is the exception. Projects keep a 75% break only if they build on brownfields and bring their own power. That condition ties Ohio’s largest data center incentive to a developer’s grid footprint as well as its capital spending. In practice, the state would be paying a premium for sites that reuse industrial land and lean less on utility-supplied electricity.

    Other provisions point the same way. Capping local property tax abatements at 50% and removing access to the 30-year mega project job creation grant both reduce the long-term public subsidy a single campus can collect. Together, these changes suggest Ohio is trying to stay open to data center investment while no longer competing mainly on how much tax it will forgo. Developers already planning Ohio sites will need to revisit their project economics. Those able to secure their own generation gain a relative advantage. The bill does not define what counts as bringing their own power, and that definition will matter.

    The Harder Fight Is the Rate Class

    The tax changes drew relatively little objection in testimony. The utility billing provision did not. The bill directs PUCO to create a data center rate class that assigns generation, distribution and transmission costs to data centers, similar to AEP Ohio’s existing data center tariff. The Ohio Manufacturers’ Association, already challenging that tariff in court, opposed extending the model statewide. Its energy consultant, John Seryak, described one project in AES Ohio’s territory that would need roughly $230 million in supplemental grid equipment. He said that once the cost is financed over 40 years with return on equity and interest, it comes to about $850 million, and the tariff would recover only $300 million of it. These are the association’s estimates, not audited figures. But the mechanism is plain. If a rate class spreads a project’s costs over years and collects less than the full lifetime cost, the gap has to be paid by someone else on the system.

    Seryak raised a second concern about the minimum monthly demand payments these tariffs impose. Minimum payments are generally meant to ensure a large customer covers the capacity built for it. He argued they could also inflate utilities’ load forecasts, pushing them to plan for more capacity whose cost is then spread across all ratepayers. They could also weaken a data center’s incentive to use power efficiently. The Ohio Environmental Council Action Fund raised a related gap. Nolan Rutschilling asked lawmakers to add explicit language telling PUCO how to handle PJM’s September backstop auction for 15 gigawatts of new generation. He said the large-load tariff might cover it, but the bill should make sure it does. The affected parties are clear. Manufacturers and households pay if costs leak out of the rate class. Developers pay more if it is written tightly. Utilities have to forecast and build against whatever the final design encourages.

    Water, NDAs and Local Leverage

    On water, the bill directs the Ohio EPA to develop a water quality testing plan and report any anomalies. Data centers would have to track and report their water use and adopt conservation practices, including closed-loop cooling, which recirculates coolant rather than continually drawing fresh water. This gives regulators data they currently lack. It does not set usage caps.

    The nondisclosure agreement provision drew criticism from both parties. The bill states that an NDA cannot prohibit or limit the release of a public record. Sen. Bill DeMora, D-Columbus, said this “does nothing to stop NDAs,” because it does not ban them. Sen. Jerry Cirino, R-Kirtland, worried from the other direction that the bill could hurt data centers’ ability to negotiate with local governments. The proposed surety bond is the most unusual local protection. It would equal the average salary of all of a data center’s workers over ten years, which Chavez described as “financial insurance” for affected communities. Save Ohio Parks asked for some carbon-free energy requirements and pointed to diesel backup generators as a pollution concern. The bill as introduced does not include such a requirement.

    Speed Leaves the Details Unsettled

    Chavez’s timeline, with a floor vote potentially one day after introduction, means the most contested language faced little revision in the Senate. DeMora warned that “anything the legislature does in a swift amount of time ends up being bad for everybody.” The risk is concentrated in the rate-class provision. The tax percentages are simple numbers. The cost-allocation rules are not, and they would be left largely to PUCO to design while the AEP tariff remains in litigation.

    For the wider PJM region, Ohio’s bill is a sign of where state policy is heading. Incentives are being trimmed and made conditional, while the real policy work moves to utility commissions and tariff design. That is where the costs of AI-driven load growth will actually be divided.

    Background

    Ohio, particularly central Ohio, has become a major destination for large data center campuses. Its utilities, including AEP Ohio and AES Ohio, are part of the PJM Interconnection grid, which covers all or parts of 13 states and Washington, D.C. As AI-driven demand for computing power has grown, PJM and its member states have struggled with how to pay for the transmission lines, substations and power plants needed to serve that load without shifting costs onto existing customers.

    PUCO approved a data center tariff for AEP Ohio last year to assign more of those costs to data centers. The tariff is now under challenge by the Ohio Manufacturers’ Association in the Ohio Supreme Court. Chavez’s bill draws on testimony from the Ohio Senate’s Select Committee on Data Centers and would extend a similar rate-class approach across the state’s utilities.

    Sources

    Source: Ohio lawmakers introduce sweeping new data center legislation (Ohio Capital Journal), covering Sen. Brian Chavez’s bill on data center tax breaks, water use, NDAs and utility rate classes.

  • MIT Spinout Applies Nuclear Passive Cooling to Data Centers

    MIT Spinout Applies Nuclear Passive Cooling to Data Centers

    MIT News reported on June 9, 2026, that a startup spun out of the university is commercializing a data-center cooling system inspired by the passive heat-removal designs used in nuclear reactors, with the stated goal of making data centers more sustainable by reducing the energy — and, per the editorial framing, the water — that cooling consumes.

    The syndicated release available to us carried the headline and framing but few technical or commercial specifics; we analyze the concept on its merits and flag what remains unsubstantiated below.

    Executive Summary

    The announcement matters because cooling is one of the largest costs — in electricity, in water, and increasingly in permitting friction — of operating a data center. A system that borrows from nuclear engineering’s passive-safety playbook, where heat is removed by natural physical forces rather than powered machinery, is aimed squarely at that cost. In a reactor, passive cooling means hot fluid rises and cooler fluid sinks, circulating heat away without pumps; the appeal for data centers is the same: fewer energy-hungry moving parts between the hot chip and the outside air.

    The timing is not accidental. AI training and inference hardware has pushed per-rack power to levels that conventional air cooling struggles to handle, and communities hosting data centers are scrutinizing water withdrawals from evaporative cooling systems. Any credible technology that reduces both the electric and water bills of heat rejection will get a hearing from operators.

    What the source material does not yet establish is whether this particular system works at commercial scale: no performance figures, customer deployments, funding details, or timelines were available in the release we reviewed. The physics pedigree is real; the commercial case is, for now, a thesis.

    From Reactor Safety to Server Racks

    Nuclear plants pioneered passive cooling for a stark reason: a reactor must shed heat even when the power fails. Designs built on natural circulation exploit the fact that heated fluid becomes less dense and rises while cooled fluid sinks, creating a self-sustaining loop that moves heat with no pumps, no fans, and no operator action. Decades of licensing scrutiny have made these principles among the most carefully validated in thermal engineering.

    A data center’s problem is gentler — servers fail safely when they overheat, reactors do not — but structurally similar: concentrated heat that must move continuously to the outdoors. Today that journey is powered at nearly every step, by server fans, chilled-water pumps, compressors, and cooling towers. A passive or semi-passive loop that lets buoyancy or phase change do part of that work attacks the electricity bill directly, and if it rejects heat without evaporating water, it attacks the water bill too. The startup’s bet, as framed by MIT News, is that reactor-grade thermal design can be repackaged at data-center price points.

    Why Cooling Is the Data Center’s Second Power Bill

    For a typical facility, the electricity that does computing is only part of the meter; a meaningful share of total load goes to moving heat, which is why the industry obsesses over power usage effectiveness (PUE) — the ratio of total facility power to IT power. Every point of cooling overhead removed either cuts operating cost or frees grid capacity for more servers, and grid capacity is currently the scarcest input in the AI buildout.

    Water is becoming the second constraint. Many large facilities cool cheaply by evaporating water, and withdrawals have become a flashpoint in drought-prone regions, slowing permits and souring community relations. A technology that credibly reduces both energy and water use would not just trim costs — it would widen the map of places a data center can be built. That is the strategic prize behind this announcement, and it explains why a cooling story from a university lab merits industry attention.

    A Crowded Race, and a Conservative Customer

    The spinout is not entering an empty field. Direct-to-chip liquid cooling is already shipping at scale from established vendors, immersion cooling has committed adopters, and rear-door heat exchangers are a common retrofit. Most of these still depend on pumped loops and mechanical chillers, so a passive approach is differentiated in principle — but it must prove it can handle the extreme heat density of modern AI racks, where natural circulation alone has historically been hardest to apply.

    The harder obstacle may be cultural. Data-center operators are deeply conservative buyers: uptime is the product, and unproven thermal systems are among the last things they will gamble on. The path for a startup here almost always runs through small pilot deployments, published performance data, and partnerships with equipment incumbents or colocation providers willing to host a proving ground. None of those milestones is evidenced in the material released so far, which is normal for a lab-to-market story at this stage — but it defines exactly what to watch for next.

    Background

    Data-center cooling has been through several generations: raised-floor air cooling, hot/cold aisle containment, evaporative economization, and most recently liquid cooling driven by AI accelerators whose heat output overwhelms air. Each generation traded capital cost against energy and water consumption, and the AI era has sharpened that trade-off — power and water availability now routinely determine where facilities can be built at all.

    Nuclear engineering, meanwhile, spent decades perfecting passive heat removal for safety reasons, producing some of the most rigorously validated thermal designs in existence. The MIT spinout profiled here sits at the intersection of those two histories, part of a broader wave of university-born startups applying energy-sector engineering to computing infrastructure.

    Source: Startup’s nuclear-inspired cooling system could make data centers more sustainable — MIT News report of June 9, 2026, on an MIT spinout adapting reactor-style passive cooling for data centers.

  • Birmingham’s 20-Point Code Turns AI Data Center Power Plans Into Zoning Terms

    Birmingham’s 20-Point Code Turns AI Data Center Power Plans Into Zoning Terms

    TL;DR · 30-second read

    The Short Version

    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.

    Sources

    Source: The City of Birmingham approves Alabama’s toughest zoning ordinance, establishing 20-point community protections for data center development, the City of Birmingham’s June 9, 2026 announcement of its hyperscale data center zoning rules.

  • Crusoe’s Contracted AI Infrastructure Pipeline Nears 5 GW

    Crusoe’s Contracted AI Infrastructure Pipeline Nears 5 GW

    Crusoe, the energy-focused AI infrastructure company, announced on June 8, 2026 that its contracted pipeline of AI data center capacity is approaching 5 gigawatts (GW). For scale, 5 GW is roughly the output of five large nuclear reactors — a volume of power commitments that until recently was associated only with the largest cloud providers, not venture-backed startups.

    Executive Summary

    The announcement is a milestone marker rather than a single project reveal: Crusoe is telling the market that the sum of its contracted AI infrastructure — data center capacity it has agreements to build and power, though not necessarily capacity that is built and running today — now approaches 5 GW. The company rose to prominence as the developer of the massive Abilene, Texas campus associated with the Stargate initiative and OpenAI workloads, and has positioned itself as an ‘energy-first’ builder that secures power before it builds compute.

    Why it matters: power, not chips or land, has become the binding constraint on AI buildout. A 5 GW contracted pipeline would place Crusoe among a very small group of companies — hyperscalers like Microsoft, Google, and Amazon, plus a handful of neoclouds and developers — able to credibly promise gigawatt-scale capacity to AI customers. It is also a signal to capital markets that Crusoe’s backlog, and therefore its future revenue base, is growing faster than its operational footprint. The distinction between contracted and energized capacity is the key to reading this announcement critically, and the release (as distributed) offers little detail to close that gap.

    Five Gigawatts Puts a Startup in Hyperscaler Company

    A gigawatt is a billion watts — enough electricity to supply hundreds of thousands of homes. Traditional enterprise data centers were measured in single-digit megawatts; a 5 GW pipeline is three orders of magnitude larger, and it puts Crusoe’s commitments in the same conversation as the multi-gigawatt expansion programs of the hyperscale cloud providers. That a company founded in 2018 can plausibly claim this scale says as much about the AI market as about Crusoe: frontier-model training and large-scale inference have created demand for campuses of a size that the industry simply did not build five years ago.

    The strategic logic of announcing the number is straightforward. In today’s market, customers signing multi-year AI capacity deals care less about a provider’s current server count than about its ability to deliver power-secured capacity on a schedule. A large contracted pipeline is the sales asset. It is also the financing asset: infrastructure lenders and joint-venture partners underwrite backlog, and Crusoe has previously worked with institutional capital partners to fund construction at its flagship sites. A bigger contracted number supports bigger project-finance facilities.

    The Energy-First Playbook

    Crusoe’s differentiation has always been that it approaches computing from the energy side. The company began by capturing natural gas that oil producers would otherwise flare (burn off as waste) and using it to power computing on site — first cryptocurrency mining, a business it later divested to focus entirely on AI. That origin shaped a playbook the company now applies at campus scale: go where energy is available or can be generated, secure it under contract, and build compute there, rather than queuing for grid connections in saturated data center markets like Northern Virginia.

    Nearing 5 GW of contracted capacity suggests the playbook is compounding. Grid interconnection queues in the United States can run five years or longer, so developers who can bring their own generation, or who locked in positions early, hold a genuine scarcity asset. The open question — one the announcement does not answer — is what the 5 GW’s energy mix looks like: how much is grid-connected utility power, how much is behind-the-meter gas generation, and how much depends on transmission or generation that still needs permits. Each of those paths carries very different timelines, costs, and emissions profiles.

    Contracted Is Not Energized: Reading the Number Critically

    The headline verb matters. ‘Contracted’ capacity is a pipeline metric: it typically bundles signed customer commitments and power agreements across facilities in various states of completion, from operational halls to sites that are years from first power. It is a legitimate and widely used industry measure — hyperscalers and developers alike tout pipeline gigawatts — but it is not the same as capacity serving customers today, and the announcement as distributed does not break down how much of the 5 GW is energized versus under construction versus signed-but-unbuilt.

    The gap between contracted and delivered is where AI infrastructure risk lives. Turbines, transformers, and switchgear have multi-year lead times; skilled construction labor is scarce; and a pipeline concentrated in a small number of anchor customers is only as strong as those customers’ own capital plans. None of this is a criticism specific to Crusoe — every gigawatt-scale developer faces the same execution stack — but it is the correct lens for a pipeline announcement: the 5 GW figure describes obligations and opportunity, and the value is realized only as sites reach commercial operation.

    What It Means for the Neocloud Race

    Crusoe sits in the cohort commonly called neoclouds — specialized providers such as CoreWeave, Nebius, and others that build GPU-centric infrastructure outside the traditional hyperscale clouds. The cohort is stratifying fast: a handful of players are reaching multi-gigawatt scale with deep capital partnerships, while smaller GPU renters compete on price for commodity workloads. A near-5 GW pipeline would place Crusoe firmly in the first group, and its energy-development capability distinguishes it even within that group, since most rivals lease capacity from third-party data center developers rather than originating power themselves.

    For the broader market, the announcement is another data point that AI power demand continues to translate into signed commitments, not just projections — relevant to utilities planning generation, to equipment suppliers sizing order books, and to competitors deciding whether to build or buy capacity. For customers, more credible gigawatt-scale suppliers means more negotiating options beyond the big three clouds. The caveat for all parties is the same: announced pipelines across the industry now sum to far more capacity than supply chains and grids can deliver on advertised schedules, so delivery track record — not pipeline size — will decide the winners.

    Background

    Crusoe was founded in 2018 around an unusual thesis: capture natural gas that oil producers flare off as waste and use it to power computing at the wellhead. That ‘digital flare mitigation’ business initially ran cryptocurrency mining, which Crusoe divested in 2025 to concentrate entirely on AI infrastructure. The pivot proved well timed — the company became the developer of the multi-gigawatt Abilene, Texas campus tied to the Stargate AI initiative and OpenAI workloads, raised successive large venture rounds that reportedly valued it around $10 billion by late 2025, and built out an AI cloud offering alongside its data center development arm.

    The market context is a historic collision between AI demand and electric-power supply. Data center development, long measured in tens of megawatts, is now planned in gigawatts, and US grid interconnection backlogs have made secured power the industry’s binding constraint. That environment created the ‘neocloud’ category of specialized AI providers and made contracted-gigawatt milestones — like the one Crusoe announced here — the yardstick by which the buildout race is measured.

    Source: Crusoe’s contracted AI infrastructure nears 5 GW — company announcement, published June 8, 2026, stating that Crusoe’s contracted AI infrastructure pipeline is approaching 5 gigawatts.

  • Data Center Power Costs Draw Lawmakers Toward Rate-Design Fixes

    Data Center Power Costs Draw Lawmakers Toward Rate-Design Fixes

    Bloomberg Government reported on June 8, 2026 that lawmakers are floating solutions to the rising power costs associated with data centers — a signal that the electricity-bill impact of the computing buildout has moved from utility commission dockets into the legislative arena. The report’s headline frames the issue squarely as a cost problem in search of a policy fix.

    The report arrives amid an unprecedented wave of data center construction driven by artificial intelligence workloads, which has made large computing facilities one of the fastest-growing sources of new electricity demand in the United States.

    Executive Summary

    The core news, per Bloomberg Government’s June 8 report, is that the cost side of the data center boom — specifically, who pays for the power infrastructure these facilities require — is now attracting active legislative attention, with lawmakers proposing potential solutions rather than merely holding hearings. The report itself is headline-level; the specific proposals, sponsors, and legislative vehicles are not detailed in the material available to us, and we flag that below.

    Why it matters: for the past two years, the fight over data center power costs has largely played out state by state, before public utility commissions — the regulators who approve electricity rates. When lawmakers start floating statutory fixes, the rules of the game can change faster and more broadly. Rate design — the technical framework that decides how a utility’s costs are divided among households, businesses, and large industrial customers — is the lever most often discussed, because it determines whether a new transmission line or power plant built substantially to serve a data center is paid for by that data center or spread across everyone’s bills.

    For data center developers, utilities, and the customers signing multi-hundred-megawatt capacity deals, this is policy risk in its early, formative stage — the moment when engagement matters most and outcomes are least predictable.

    Why Electricity Bills Became a Data Center Story

    Data centers concentrate enormous electrical demand in single locations: a large AI campus can draw as much power as a mid-sized city. Serving that demand often requires new generation, new transmission lines, and substation upgrades. Under traditional utility rate-making, much of that infrastructure cost goes into the utility’s general ‘rate base’ — the pool of investment recovered from all customers over decades. When the new demand comes overwhelmingly from one class of customer, other ratepayers can end up subsidizing infrastructure they did not ask for and do not use.

    That cost-shifting question is what turns an infrastructure story into a kitchen-table story. Household electricity bills are politically salient in a way that interconnection queues are not, and the Bloomberg Government headline — lawmakers floating solutions to data center power costs — suggests elected officials now see both a genuine allocation problem and a constituency that cares about it. It is worth being even-handed here: data centers also bring tax revenue, jobs during construction, and in some regions have funded grid upgrades that benefit all users. The policy question is not whether data centers are good or bad, but whether the current rules assign their costs accurately.

    The Rate-Design Toolkit Lawmakers Are Reaching For

    Although the report does not specify which solutions are on the table, the toolkit in active discussion across the industry is well established. It includes creating dedicated tariff classes for very large loads, so data centers pay rates reflecting their actual cost to serve; minimum-take or long-term contract requirements, which protect other customers if a data center closes or scales back before its infrastructure is paid off; and ‘bring your own power’ frameworks that push hyperscale customers toward self-supplied or co-located generation. Each approach shifts risk between the data center customer, the utility’s shareholders, and the general ratepayer base — and each has trade-offs in speed, cost, and legal durability.

    The federal-versus-state dimension matters too. Retail rate design is traditionally state territory, while interstate transmission costs and wholesale market rules sit with federal regulators. Legislative proposals could target either layer, and the editorial significance of lawmakers entering the fray is that statutes can override or standardize what has so far been a patchwork of case-by-case commission rulings.

    Policy Risk Meets the AI Buildout

    For the data center industry, the emergence of legislative interest is a double-edged development. On one hand, clear statutory rules could reduce uncertainty: developers currently face a different rate fight in every state, and a predictable large-load tariff framework can actually accelerate siting decisions. On the other hand, rules written in a politically charged environment — where rising bills are the headline — could impose costs, contract terms, or delays that change project economics, particularly for speculative capacity built ahead of signed tenants.

    Utilities sit in the middle. Load growth is the best news the regulated utility sector has had in decades, but only if regulators and legislators let them recover the associated investment without triggering a ratepayer backlash. Expect utilities to support frameworks that lock in long-term commitments from data center customers, and expect hyperscale buyers with strong credit to accept them in exchange for speed. The parties most exposed are smaller developers and enterprises without the balance sheet to sign decade-long minimum-payment contracts. For everyone in the buildout, the practical takeaway is that power procurement is no longer just an engineering and price question — it is now a regulatory and legislative one.

    Background

    Electricity demand from data centers has grown rapidly since the generative-AI boom began in late 2022, ending roughly two decades of flat U.S. power demand and making computing facilities one of the largest sources of new load on the grid. Individual AI campuses now request capacity measured in the hundreds of megawatts — comparable to small cities — concentrated in hubs such as Northern Virginia, Texas, and the Midwest.

    The cost question has followed the demand. Since 2024, state utility commissions have fielded a growing number of cases over how to charge very large loads, and several utilities have proposed dedicated data center tariffs. Bloomberg Government, the source of this report, is a policy-focused news service covering Congress and federal agencies, which itself suggests the issue has reached the national legislative agenda rather than remaining purely a state regulatory matter.

    Source: Data Center Power Costs Push Lawmakers to Float Solutions — Bloomberg Government News report, June 8, 2026, on emerging legislative proposals addressing data-center-driven electricity costs.

  • Apple Expands Private Cloud Compute: Securing AI Inference at Scale

    Apple Expands Private Cloud Compute: Securing AI Inference at Scale

    Apple’s Security Research team published a post titled “Expanding Private Cloud Compute” on June 7, 2026, signaling growth of the company’s purpose-built cloud platform for AI inference. Private Cloud Compute (PCC) is the system that handles Apple Intelligence requests too demanding for on-device processing, running them on Apple-designed servers engineered so user data is never stored and never accessible to Apple itself.

    The post comes from Apple’s own security engineers rather than its marketing organization — a channel Apple has used since 2024 to document PCC’s architecture in unusual technical depth.

    Executive Summary

    Apple announced an expansion of Private Cloud Compute, the custom infrastructure it launched in June 2024 to extend its device security model into the data center. PCC’s core promise is that cloud AI requests are processed statelessly on Apple silicon servers, with no persistent storage, no privileged operator access, and cryptographic attestation that lets a user’s device verify the exact software a server is running before sending it anything.

    An expansion matters beyond Apple’s ecosystem because PCC is one of the few production systems that treats AI inference privacy as a hardware-enforced property rather than a contractual promise. As enterprises weigh where to run sensitive AI workloads, Apple’s approach has become a reference point that pressures cloud providers, chipmakers, and data center operators to raise the bar on verifiable, confidential inference.

    The syndicated item we reviewed carries the headline and publication date only, so the scope of the expansion — capacity, regions, hardware, or new capabilities — is analyzed here in the context of what Apple has previously disclosed, with open specifics noted below.

    Why Verifiable AI Inference Is Hard

    Conventional cloud privacy rests on policy: contracts, audits, and access controls that customers must ultimately take on trust. PCC was designed to replace that trust with verification. Servers run a hardened operating system with no remote shell or administrative access, computation is stateless — meaning a request is processed in memory and discarded, never written to disk — and every production software image is published to a public transparency log. An iPhone or Mac will refuse to send a request to any server whose cryptographic measurements do not match a logged, inspectable build.

    That last mechanism is the genuinely novel part. It means Apple cannot quietly deploy a modified server build to a subset of machines without either publishing it for researcher scrutiny or cutting those machines off from all client traffic. For an industry accustomed to “we don’t look at your data” assurances, an architecture where the client enforces the promise is a meaningful shift.

    Custom Silicon as a Security Strategy

    PCC runs on Apple-designed silicon in Apple-operated data centers, carrying over device-grade protections such as Secure Boot and the Secure Enclave, a dedicated coprocessor that guards encryption keys. Vertical integration is what makes the attestation story coherent: when one company controls the chip, the boot chain, the operating system, and the model runtime, there are far fewer seams where a component from another vendor must simply be trusted.

    The trade-off is cost and scale. Hyperscalers pursue related goals with confidential-computing technologies — trusted execution environments from Intel, AMD, and Nvidia that encrypt data even during processing — which work across heterogeneous fleets but involve more parties in the trust chain. Apple’s approach is cleaner but only Apple can run it, which is precisely why its expansion is watched as a benchmark rather than adopted as a template.

    What Expansion Signals for the Infrastructure Market

    Growing PCC means growing a fleet of custom inference servers, and that carries familiar data center consequences: more capacity, more power, and continued momentum behind purpose-built AI silicon as an alternative to general-purpose GPU clusters. It also confirms that private, server-side inference — not just on-device AI — is central to Apple’s long-term Apple Intelligence roadmap.

    For enterprises and infrastructure buyers, the competitive effect may matter most. Every vendor now selling “private AI” will increasingly be asked the questions PCC was built to answer: Can I verify what software processed my data? Who holds the keys? What happens to the request after the response is returned? Providers that can answer with attestation rather than assurances stand to win the most sensitive workloads.

    Background

    Apple introduced Private Cloud Compute in June 2024 alongside Apple Intelligence, positioning it as an extension of the iPhone’s security model into the data center: custom Apple silicon servers, a hardened operating system, stateless processing, and a public transparency log that lets devices verify server software before use. In October 2024 Apple opened the system to outside scrutiny, publishing a detailed security guide, releasing a Virtual Research Environment for researchers, open-sourcing portions of the code, and offering bounties up to $1 million for critical PCC exploits.

    The Security Research blog has since served as Apple’s channel for documenting PCC’s evolution — an unusually technical window into production AI infrastructure from a company historically known for secrecy, and one of the few public accounts of securing large-scale AI inference end to end.

    Source: Expanding Private Cloud Compute – Apple Security Research, Apple’s security engineering blog post announcing growth of its Private Cloud Compute AI inference platform, published June 7, 2026.

  • Behind-the-Meter Gas Plants for Data Centers May Raise US Energy Bills

    Behind-the-Meter Gas Plants for Data Centers May Raise US Energy Bills

    Utility Dive reported on June 7, 2026 that behind-the-meter gas plants — power generation built on a data center’s own site, outside the utility’s meter — will raise US energy bills. The finding lands as AI data center developers increasingly turn to on-site gas turbines to sidestep multi-year grid interconnection queues, raising the question of who ultimately pays for the workaround.

    Executive Summary

    The report’s headline claim is direct: the wave of behind-the-meter (BTM) gas generation being planned for US data centers will not insulate ordinary consumers from AI’s power demand — it will add to their bills. “Behind the meter” means the plant serves the facility directly, bypassing the utility grid for most or all of its supply, and often bypassing the retail rates, transmission charges, and regulatory review that grid-served customers face.

    Why it matters: BTM gas has been marketed as the pressure-release valve for the AI boom — a way for hyperscalers to get hundreds of megawatts energized in two or three years instead of waiting five or more for grid interconnection, without burdening other customers. If independent analysis concludes the opposite — that these plants raise systemwide costs anyway — it undercuts a central argument utilities, developers, and some policymakers have used to wave the projects through, and it strengthens the hand of regulators pushing for special large-load tariffs and cost-allocation rules.

    Why Data Centers Are Building Their Own Power Plants

    The context for this report is the collision between AI-driven load growth and a grid that cannot connect large customers quickly. Interconnection queues in major US markets stretch years, and transmission upgrades longer still. For a hyperscaler racing to deploy GPUs, a gas turbine on-site — behind the meter — converts an electricity problem into a procurement problem: buy the turbine, permit the plant, burn the fuel, skip the queue. That speed premium is why BTM gas has moved from a niche arrangement to a defining feature of the current data center buildout.

    The pitch to regulators has been that this is self-contained: the data center pays for its own generation, so other ratepayers are held harmless. The Utility Dive report’s conclusion — that these plants will raise US energy bills — challenges that framing at its core.

    How a Private Power Plant Can Raise Everyone Else’s Bill

    With only the headline finding available, the report’s specific modeling cannot be evaluated here, but the mechanisms by which BTM generation can raise systemwide costs are well understood in utility economics. First, natural gas markets are shared: a fleet of new gas plants competing for fuel, pipeline capacity, and turbines can push up gas prices, and because gas units set the marginal price of electricity in much of the country, higher gas costs flow into wholesale power prices for everyone. Second, BTM facilities typically still rely on the grid for backup and startup power while contributing little to the fixed costs of the wires — costs that get spread across remaining customers. Third, if BTM load later converts to grid service, the system must absorb a large customer it never planned for.

    Each of these is a cost-shifting channel, not a conspiracy: individually rational decisions by data center developers can still produce a collectively expensive outcome. That is precisely the kind of externality utility regulation exists to police.

    Winners, Losers, and the Regulatory Stakes

    The near-term winners of the BTM boom are clear regardless of the report’s conclusion: gas turbine manufacturers with multi-year order books, gas producers and pipeline owners, and developers who can monetize speed-to-power. The contested question is who bears the residual cost. If the report’s finding holds, the losers include residential and small-business ratepayers — and, notably, utilities’ own political capital, since public backlash over rising bills tends to land on the regulated utility whether or not it caused the increase.

    For the data center industry, the strategic risk is regulatory: findings like this one give state commissions ammunition to impose standby charges, minimum-take tariffs, exit fees, or cost-allocation rules on large loads. Several states were already moving in that direction before this report. Operators that get ahead of the issue — structuring deals that demonstrably cover their grid costs — will face less friction than those that treat BTM as a permanent regulatory bypass.

    Background

    The US data center industry entered a period of unprecedented power demand growth in the mid-2020s, driven by AI training and inference workloads. After two decades of roughly flat US electricity consumption, utilities began forecasting sustained load growth, with data centers the largest single driver. Grid interconnection processes designed for a slower era became the bottleneck, and “speed to power” replaced land and fiber as the industry’s scarcest resource.

    Behind-the-meter generation — long a niche arrangement for industrial plants with steam needs or reliability concerns — was repurposed as the fast lane: developers began pairing data center campuses with dedicated on-site gas turbines, sometimes at gigawatt scale. Utility Dive, a trade publication covering the US electric power sector, has tracked the resulting policy fight over who pays for AI’s power appetite; this report is part of that running debate.

    Source: Behind-the-meter data center gas plants will raise US energy bills — Utility Dive, a June 7, 2026 report on the ratepayer costs of on-site gas generation built for US data centers.