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

Tag: AI infrastructure

  • Virginia Approves First Data Center Power Tax: A Precedent for AI-Era Grid Costs

    Virginia Approves First Data Center Power Tax: A Precedent for AI-Era Grid Costs

    Virginia has approved what is being described as the first-ever data center power tax, according to a June 23, 2026 report from Data Center Knowledge. The measure makes Virginia — home to the largest concentration of data centers in the world — the first U.S. state to attach a dedicated levy to data center power consumption.

    Details of the tax’s rate, structure, and effective date were not included in the initial report, but the “first-ever” framing marks a significant policy departure: rather than courting data centers exclusively with incentives, the state that hosts more of them than any other is now taxing the electricity they use.

    Executive Summary

    The significance of this measure lies less in its mechanics — which the initial reporting does not detail — than in its symbolism and its likely ripple effects. Virginia built its data center dominance in part on a generous sales-and-use tax exemption for data center equipment, a policy other states copied for two decades. A power tax moving in the opposite direction signals that the political economy of hosting data centers has shifted: the question in Richmond is no longer only how to attract capacity, but how to make that capacity pay for the grid strain it creates.

    For operators, hyperscalers, and their customers, the precedent matters more than the immediate cost. Utilities and regulators across the country have been wrestling with how to allocate the enormous transmission and generation investments driven by AI-era load growth — and whether ordinary ratepayers are subsidizing them. A dedicated tax on data center power is one answer to that question, and now the largest data center market on earth has adopted a version of it. Other states weighing similar debates will be watching closely.

    Because the available source is a headline-level report, the analysis below focuses on the policy context and the questions the measure raises, rather than on provisions that have not yet been publicly detailed.

    Why Virginia Was Always Going to Move First

    Northern Virginia — particularly Loudoun County’s “Data Center Alley” — hosts the densest cluster of data centers anywhere in the world, a position built on early internet-exchange infrastructure, proximity to federal customers, and a long-standing tax exemption on data center equipment. That concentration has made Virginia the place where the costs of the AI buildout show up first and loudest: transmission congestion, multi-year interconnection queues, land-use fights, and public concern that residential electricity bills are absorbing grid investments made largely to serve large industrial loads.

    Virginia’s own legislative auditors flagged these tensions in a December 2024 study of the industry’s fiscal and energy impacts, and the General Assembly has debated data center energy policy in every session since. Seen against that backdrop, a power tax is not a bolt from the blue — it is the next step in a multi-year negotiation between a state and an industry that has become its signature economic engine and its biggest new source of electricity demand.

    The Real Question: Who Pays for AI-Era Grid Growth?

    Electric grids recover their costs from customers through rates, and when one customer class grows explosively — as data centers have — regulators must decide whether the new transmission lines, substations, and generation get billed to that class or spread across everyone. Consumer advocates argue that spreading the cost amounts to households subsidizing some of the world’s wealthiest companies; utilities and operators counter that large, steady loads can actually lower average system costs by spreading fixed expenses over more kilowatt-hours. Both arguments have evidentiary support in different circumstances, which is precisely why the allocation fight has been so contentious.

    A tax is a blunter instrument than a rate class. Utility ratemaking assigns costs based on engineering studies of who causes them; a tax is a legislative judgment that a category of consumption should contribute more to public coffers, whatever the cost-causation math says. Whether Virginia’s measure funds grid infrastructure specifically, flows to the general fund, or offsets residential bills will determine whether it functions as genuine cost allocation or as a revenue measure wearing cost-allocation clothing. The initial reporting does not say — and that distinction is the single most important thing to watch as details emerge.

    What It Means for Operators, Tenants, and Competing States

    For data center operators, a per-unit levy on power lands directly on the largest line item in their operating budgets. Colocation providers will face the classic question of how much they can pass through to tenants under existing contracts; hyperscalers running their own facilities will absorb it as a marginal cost increase on Virginia capacity relative to other markets. The competitive effect depends entirely on magnitude: a modest levy on power in the market with the best fiber connectivity in the country changes few siting decisions, while a heavy one accelerates the diversification toward Ohio, Texas, Georgia, and the Carolinas that grid constraints were already driving.

    Competing states now face a strategic choice of their own. Some will advertise the absence of such a tax as a recruitment tool. Others — facing identical ratepayer politics as AI load arrives on their grids — may treat Virginia’s measure as proof of concept. It is worth remembering that Virginia’s data center equipment tax exemption was copied by more than thirty states. Policy that starts in the world’s data center capital has a history of traveling.

    A Precedent That Cuts Both Ways

    The industry has long argued, with some justification, that data centers are exceptional taxpayers — Loudoun County’s budget depends heavily on data center property tax revenue — and that layering new levies on top risks punishing a sector for succeeding. That argument deserves a fair hearing, and it will get one in the rate cases and legislative fights ahead. But the industry has also benefited from a bargain in which states competed to reduce its tax burden while the public bore growing grid costs, and Virginia’s move suggests that bargain is being renegotiated rather than abandoned.

    The measured takeaway: this is neither the end of Virginia’s data center industry nor a trivial development. It is the first formal acknowledgment, in statute, by the market that matters most, that data center power consumption is a distinct fiscal category. How the tax is structured — and whether it stabilizes the industry’s social license to operate or simply raises its costs — will determine whether operators come to see it as the price of durable acceptance or the start of an unwelcome trend.

    Background

    Virginia’s data center industry dates to the early internet era, when network interchange points in Northern Virginia made the region a natural home for hosting infrastructure. Over two decades, aided by a state sales-and-use tax exemption on data center equipment, Loudoun and neighboring counties grew into the world’s largest data center cluster, and data center property taxes became a pillar of local budgets. The AI boom then supercharged demand: utilities serving the region have projected sustained, historic load growth, and interconnection wait times stretched to years.

    That growth turned data centers into a live political issue in Richmond. A December 2024 state legislative audit examined the industry’s fiscal benefits and energy costs, and subsequent General Assembly sessions produced a stream of bills on data center siting, ratepayer protection, and tax treatment. The power tax reported in June 2026 is the most consequential product of that debate to date — the first time the industry’s electricity consumption itself has been made a taxable category.

    Source: Virginia Approves First-Ever Data Center Power Tax — Data Center Knowledge, June 23, 2026, reporting Virginia’s approval of the first U.S. tax targeting data center power consumption.

  • Why Data Center Investors Are Buying Power Developers Outright

    Why Data Center Investors Are Buying Power Developers Outright

    Reuters reported on June 22, 2026 that investors in data centers are acquiring power developers outright — not merely signing supply contracts with them — as competition to build new compute capacity intensifies. The report frames the trend as a race in which control of electricity generation has become as strategically important as control of the data center itself.

    Executive Summary

    According to Reuters, the capital behind data center construction is moving up the energy supply chain: rather than waiting in utility interconnection queues or negotiating power purchase agreements (long-term contracts to buy electricity from an independent producer), data center investors are simply buying the companies that develop power projects. Ownership gives them the pipeline of sites, permits, equipment orders, and grid connection positions that a developer has assembled — assets that have become scarce as AI-driven demand outruns the grid’s ability to deliver new supply.

    The significance is structural. For decades, digital infrastructure and power generation were separate industries connected by contracts. If investors now find contracts insufficient and are acquiring generation capability outright, the boundary between the compute business and the energy business is dissolving. That changes who competes for power projects, what those projects are worth, and how quickly new data center capacity can realistically come online.

    Power, Not Land or Chips, Is the Binding Constraint

    A data center is, economically, a machine for converting electricity into computation. In recent years the hardest input to secure has shifted from real estate and even from processors to firm electric capacity — a guaranteed, always-available supply of megawatts. Connecting a large new load or a new power plant to the transmission grid requires passing through an interconnection queue, the utility and grid-operator study process that determines what upgrades are needed; those processes are widely understood across the industry to take years. A power developer’s real inventory is its queue positions, land control, permits, and equipment reservations. Buying the developer is a way of buying time — the years of lead work already done.

    Seen that way, the behavior Reuters describes is rational sequencing. When an input is scarce and the market for it is slow, firms integrate backward into it. Railroads bought coal mines; aluminum smelters built dams. Data center capital buying power development capability is the same industrial logic applied to the AI build-out.

    From Contracts to Control

    The traditional instrument linking the two industries is the power purchase agreement. A PPA transfers energy and price risk, but it does not transfer control: the developer still decides which projects advance, on what schedule, and who else gets served. In a seller’s market for capacity, contract counterparties compete for the developer’s attention. Ownership removes that competition — the acquirer directs the entire pipeline toward its own loads and captures the development margin rather than paying it.

    The trade-off is that data center investors are taking on a business with a very different risk profile. Power development involves permitting risk, supply chain exposure for equipment such as turbines and transformers, community opposition, and regulatory processes that money alone cannot compress. Vertical integration internalizes those risks instead of leaving them with a specialist counterparty. Whether the acquirers can manage them as well as standalone developers did is an open execution question, and the answer will vary by acquirer.

    Winners, Losers, and the Ones in Between

    The clearest immediate winners are power developers themselves and their backers: an asset class that was priced against utility-scale project returns is now being bid for by buyers who value it against AI infrastructure returns. Sellers of development pipelines are exiting into unusual demand. Conversely, buyers of power who lack that capital — smaller data center operators, industrial users, and potentially ordinary utility customers — face a market in which the deepest-pocketed players are locking up future supply at the source.

    Utilities and grid operators sit in the middle. Well-capitalized customers willing to fund generation can accelerate supply additions, which helps everyone connected to the grid. But if acquired pipelines are steered toward dedicated or behind-the-meter service (generation wired directly to a facility rather than through the shared grid), the public grid may see less of that new supply than the raw development numbers suggest. How regulators allocate costs and capacity between hyperscale loads and everyone else was already contentious; concentrated ownership of development pipelines sharpens the question rather than settling it.

    What This Signals About the AI Build-Out

    Strategically, the trend is a statement about expectations. Buying a developer only makes sense if you believe demand for compute — and therefore for power — will remain strong past the multi-year horizon on which power projects are built. It is also a statement about the grid: participants with the most information about future load evidently do not expect conventional utility processes to deliver capacity fast enough, and are paying to route around the wait. Both signals are worth registering, with the usual caution that aggressive capacity bets made near the top of an investment cycle are precisely the ones that look overextended if demand growth moderates.

    Background

    Data centers — the facilities housing the servers behind cloud services and AI — have historically obtained electricity the way other large customers do: from utilities, supplemented by long-term purchase contracts with independent power producers. The surge in AI computing that began in the early 2020s changed the balance, pushing projected data center power demand up sharply while new generation and transmission remained slow to permit and build. Operators responded first with ever-larger contracts and reserved grid capacity; the acquisitions Reuters describes are the next step, moving from buying a developer’s output to buying the developer itself.

    Reuters is a global news agency whose energy and infrastructure coverage is widely used as a market reference, and its June 2026 report distills a pattern visible across the sector rather than a single transaction.

    Source: Data center investors buy up power developers in race to build — Reuters, June 22, 2026, reporting that data center investors are acquiring power development companies outright amid the race to build compute capacity.

  • FERC’s Data Center Interconnection Decision: What It Means for Speed to Power

    FERC’s Data Center Interconnection Decision: What It Means for Speed to Power

    The Federal Energy Regulatory Commission (FERC) — the U.S. agency that oversees the interstate transmission grid — has issued a decision on how data centers and other very large electricity loads interconnect to that grid, according to a June 21, 2026 Utility Dive analysis distilling the ruling into six takeaways. The decision lands in the middle of the defining constraint of the AI buildout: data center campuses now requesting hundreds of megawatts, and in some cases gigawatts, of power from a grid whose connection processes were never designed for loads of that scale.

    Executive Summary

    For most of the grid’s history, connecting a new factory or office park was a routine utility matter. AI-era data centers broke that model: single campuses now ask for as much power as a mid-sized city, and the question of how — and how fast — they plug into the high-voltage grid has escalated from a paperwork exercise into a national policy fight. FERC’s decision, as covered by Utility Dive, speaks directly to that question of large-load interconnection.

    Why it matters: ‘speed to power’ has become the number-one site-selection criterion in the data center industry, ahead of land, fiber, and even tax incentives. Any FERC ruling that clarifies the rules of the road for large-load interconnection reshapes where capital flows — which utilities and regions can credibly promise fast connections, which co-location strategies (siting data centers next to power plants) remain viable, and who pays for the grid upgrades these loads trigger. The six-takeaways framing of the trade-press coverage signals a decision with multiple moving parts rather than a single yes/no outcome; the specifics of each takeaway are not enumerated in the source material available to us, and we flag that plainly in the gaps below.

    Why the Grid’s Referee Stepped Into the Load Line

    FERC regulates the interstate transmission system and the wholesale power markets that run on it, while states regulate retail electric service. Data centers sit awkwardly across that seam: they are retail customers, but at gigawatt scale their connections have unmistakable effects on the interstate grid — congestion, reliability margins, and the cost of upgrades shared across entire regions. That is why disputes over large-load and co-located interconnection have been climbing toward FERC for the past two years, most visibly in the PJM region (the 13-state mid-Atlantic grid operator), where fights over siting data centers behind the meter at existing power plants forced the commission to examine the rules directly.

    The deeper issue is asymmetry. FERC’s Order 2023 overhauled how new generators queue up to connect — moving to clustered, first-ready-first-served studies — but no equivalent standardized federal framework existed for very large loads. Each utility and regional grid operator improvised its own process, producing wildly different timelines and study requirements. A FERC decision on data center interconnection is significant precisely because it addresses that gap: it tells utilities, grid operators, and developers what the referee expects when a gigawatt-class customer knocks on the door.

    Speed to Power Is the Whole Ballgame

    In today’s market, the scarce input for AI infrastructure is not chips or capital — it is energized megawatts on a firm date. Interconnection timelines of four to seven years for large loads in constrained markets have pushed developers toward workarounds: co-locating next to nuclear or gas plants, contracting for on-site generation, or chasing secondary markets with spare grid headroom. Every one of those strategies is priced off the baseline question of how long a conventional grid connection takes, which is exactly the variable a FERC interconnection ruling moves.

    The economics cut both ways. Clearer, faster, more standardized processes would compress project timelines and reduce the option value of exotic workarounds. But greater rigor — more demanding studies, firmer cost-allocation rules, or requirements that large loads demonstrate readiness — could slow the most speculative requests. That would be a feature, not a bug, for grid planners: utilities report far more requested data center load than will ever be built, as developers file duplicate requests across multiple territories, and ‘phantom load’ distorts forecasts and infrastructure spending that ratepayers ultimately fund.

    Winners, Losers, and the Cost-Allocation Question

    Watch three constituencies. Hyperscalers and large developers benefit from any added certainty, even if the rules tighten — sophisticated players with real projects and balance sheets clear readiness screens that speculative filers cannot. Utilities in load-growth regions gain a firmer basis for the tens of billions in transmission investment that data center demand justifies, but inherit whatever process obligations the decision imposes. Existing ratepayers have the most at stake and the least voice: the central distributive question in every large-load proceeding is whether the data center pays the full cost of the grid capacity it triggers or whether some of it socializes into everyone’s bills.

    There is also a competitive-geography effect. Interconnection friction has been quietly redistributing the data center map away from saturated hubs like Northern Virginia toward regions marketing surplus grid capacity. A federal ruling that harmonizes how large-load requests are handled would narrow the arbitrage between jurisdictions — good for national planning coherence, less good for regions whose pitch was procedural speed rather than physical capacity.

    What a Six-Takeaways Ruling Usually Signals

    When the trade press needs six takeaways to summarize a decision, the outcome is rarely a clean win for any single party — it typically indicates a framework ruling that resolves some questions, defers others to compliance filings or regional processes, and draws jurisdictional lines that will themselves be tested. Readers should treat the decision as the start of an implementation phase, not the end of the argument: FERC orders of this consequence routinely draw rehearing requests and appellate challenges, and the practical effect on connection timelines will depend on how grid operators and utilities translate the ruling into tariff language over the following months. We note candidly that the source material available for this article does not enumerate the six takeaways themselves; the analysis here reflects the well-documented context of the proceeding rather than the order’s specific holdings.

    Background

    The road to this decision runs through two years of escalating conflict between the AI buildout and the grid. FERC’s Order 2023 modernized interconnection for generators but left large loads without a standardized federal process. Then the co-location fights began: high-profile disputes in the PJM region over siting data centers behind the meter at existing power plants — including the commission’s closely watched 2024 rejection of an expanded arrangement at a nuclear station — pushed FERC to open proceedings examining large-load and co-located interconnection directly. Meanwhile, utility load forecasts, flat for two decades, turned sharply upward on data center demand, making the question of how these loads connect one of the most consequential in U.S. energy policy.

    Utility Dive, the trade publication behind the six-takeaways analysis, is a widely read source of daily coverage of the U.S. electric power sector, and its framing of commission orders is a common first read for industry professionals tracking regulatory developments.

    Source: 6 takeaways from FERC’s data center interconnection decision — Utility Dive’s June 21, 2026 analysis of the commission’s ruling on how large loads connect to the grid.

  • Tesla’s ‘Megapod’ Reportedly Turns AI Data Centers Into a Turnkey Product

    Tesla’s ‘Megapod’ Reportedly Turns AI Data Centers Into a Turnkey Product

    According to a June 20, 2026 report from Electrek, Tesla plans to sell modular AI data center hardware under the name ‘Megapod’ — a productized, containerized package that would bundle power infrastructure and AI compute into a turnkey unit customers can buy, rather than a facility they must design and build. The report identifies the plan and the product name; specifications, pricing, capacity, and launch timing were not disclosed.

    Executive Summary

    The reported move would take Tesla from building AI infrastructure for itself to selling it as a product. Tesla already manufactures grid-scale battery systems (the Megapack, a factory-built container of batteries and power electronics that utilities buy by the unit) and has built large GPU clusters for its own self-driving and robotics programs. A ‘Megapod’ — the name deliberately echoes Megapack — would apply that same factory-built, buy-by-the-unit model to AI computing itself.

    Why it matters: the hardest part of deploying AI compute today is not buying chips, it is securing power and building the facility around them — a process that routinely takes years. A credible turnkey product that arrives with power conversion, cooling, and compute pre-integrated would compress that timeline and create a new class of competitor to traditional data center developers. That said, the report is thin: it establishes intent and a name, not a spec sheet, and the concept’s viability rests entirely on details Tesla has not yet made public.

    From Megapack to Megapod: Selling the Bottleneck

    Tesla’s energy business grew by productizing something that used to be a construction project. Before Megapack, grid-scale battery storage meant custom engineering on every site; Megapack turned it into a manufactured unit with a price, a lead time, and an order page. The reported Megapod applies the same logic to AI infrastructure, where the analogous pain is acute: demand for AI compute has outrun the industry’s ability to build the powered, cooled buildings that house it.

    If the product is what its name and the report’s framing suggest, the pitch writes itself — skip years of design-build and receive integrated capacity as freight. Tesla is plausibly positioned to attempt this because it already manufactures most of the non-chip ingredients at scale: battery storage, power electronics, thermal management, and high-volume factory assembly. It has also been its own first customer, having built large GPU clusters for training its driver-assistance and robotics models, which is where lessons about powering and cooling dense compute tend to be learned.

    The Market It Would Land In

    Modular and containerized data centers are not new — vendors have sold prefabricated modules for over a decade, and hyperscalers use prefabrication internally. What has changed is the customer base. AI demand has created buyers — enterprises, sovereign AI programs, GPU cloud startups — who need substantial compute quickly but lack the in-house expertise of a hyperscaler. That is the natural audience for a turnkey unit, and it is the same audience today served by colocation providers and data center developers.

    The competitive question is where such a product would sit relative to the existing stack. A Megapod would presumably still need land, grid interconnection or on-site generation, network connectivity, and operations — things a box does not include. That suggests the more likely outcome is complement rather than replacement: developers and colocation operators could themselves become customers, using prefabricated units to shorten construction. The disruptive scenario — buyers bypassing traditional facilities entirely — depends on how much of the surrounding problem Tesla actually packages, which the report does not say.

    What Would Have to Be True

    The economics of an integrated power-plus-compute product are unforgiving in one specific way: compute depreciates on a different clock than power infrastructure. GPUs turn over on a two-to-three-year cadence as new generations arrive, while switchgear, batteries, and cooling plant are fifteen-to-twenty-year assets. A well-designed modular product has to let the fast-aging part be swapped without stranding the slow-aging part; whether Megapod is architected that way is unknown.

    There is also a supply question the report leaves untouched: whose compute goes inside? Tesla has designed its own AI chips for in-house use, but a commercial product would more plausibly need to accommodate the accelerators customers actually want — which puts Tesla in the position of reselling scarce third-party silicon inside its own enclosure. And there is a focus question that applies to any company entering an adjacent market: manufacturing, selling, and supporting mission-critical infrastructure for enterprise customers is a service-heavy business with uptime obligations, a different muscle from selling vehicles or even utility batteries. None of this makes the product implausible — it defines the checklist the eventual announcement should be judged against.

    Background

    Tesla, founded in 2003 and best known for electric vehicles, has spent two decades building an energy division alongside its car business. Its Megapack — a shipping-container-scale battery system for utilities — became one of the company’s fastest-growing product lines, manufactured at dedicated ‘Megafactory’ plants. In parallel, Tesla became a major AI infrastructure operator in its own right, building large GPU training clusters and designing custom chips to train the neural networks behind its driver-assistance software and humanoid robot program.

    The reported Megapod arrives amid an industry-wide scramble: AI demand has made powered data center capacity one of the scarcest commodities in technology, with grid connections and construction — not chips alone — as the binding constraints. That scarcity has drawn manufacturers, utilities, and startups toward prefabricated and power-integrated designs, the space a Megapod would enter.

    Source: Tesla plans to sell modular AI data center hardware called ‘Megapod’ (Electrek) — June 20, 2026 report that Tesla intends to offer packaged power-plus-compute AI data center units as a product.

  • Castor Bill Would Shield Ratepayers From Data Center Costs

    Castor Bill Would Shield Ratepayers From Data Center Costs

    On June 20, 2026, U.S. Representative Kathy Castor (D-FL) introduced a bipartisan bill aimed at preventing American electricity ratepayers from being charged for the grid investments needed to serve new data center development. The announcement was made via her official congressional office.

    The bill enters Congress amid a rapidly widening debate over how the cost of accommodating hyperscale and AI data centers on the U.S. power grid should be allocated between utilities, developers, and residential and small-business customers.

    Executive Summary

    Castor’s bill frames a question that state utility regulators have been grappling with for at least two years: when a utility must build new generation, transmission, or substations to serve a data center campus, who pays the bill? Historically, grid upgrades have been socialized across a utility’s customer base under cost-of-service ratemaking. As individual data center loads have grown from tens of megawatts to, in some proposed cases, more than a gigawatt, that default has become politically and economically untenable in a growing number of jurisdictions.

    The measure matters because it moves the debate from state public service commissions — where rules vary widely — toward a federal floor. If enacted, it could reshape how hyperscalers negotiate site selection, how utilities file rate cases, and how quickly gigawatt-scale AI campuses can be energized. It also signals that the ratepayer-impact narrative has crossed party lines, which changes the political risk calculus for the data center industry.

    The release itself is short on legislative text, cost estimates, and cosponsor detail, so the substantive analysis below is bounded by what the announcement establishes: the bill exists, it is bipartisan, and its stated aim is ratepayer protection.

    Why The Cost-Shifting Debate Reached Washington

    State-level friction over data center power costs has been building. Regulators in several large data center markets — including Virginia, Georgia, and Ohio — have opened dockets on whether large-load customers should be placed on their own rate class, post collateral, or pay directly for dedicated infrastructure. The core concern is that a residential customer pays, through their monthly bill, a share of transmission upgrades primarily driven by a single hyperscale campus down the road. Castor’s bill is the first high-profile federal attempt this cycle to answer that question with statute rather than tariff filings. Its bipartisan framing is notable: ratepayer bills are a pocketbook issue that tracks poorly along traditional partisan lines.

    What A Federal Floor Would Change For Operators

    Assuming the bill’s operative mechanism aligns with its stated purpose — the release itself does not publish text — the practical effect on operators would depend on how narrowly “data center development” is defined and how “paying” is measured. A strict interpretation could require that incremental generation and transmission tied to a specific large load be recovered from that load through dedicated tariffs or contracts. That would push more risk onto developers, favor sites with existing headroom, and reward operators who can bring their own generation (behind-the-meter gas, on-site solar plus storage, or eventually small modular reactors). It would disadvantage speculative site development that assumes utility-funded grid expansion.

    Winners, Losers, And The Middle Ground

    If the bill advances in something close to its announced spirit, the clearest beneficiaries are residential and small-commercial ratepayers in high-growth data center corridors, and utilities that have already moved toward large-load tariffs — those companies are ahead of a rule they may soon have to comply with. The clearest exposure sits with developers whose underwriting assumes socialized grid costs, and with utilities whose integrated resource plans lean heavily on load growth from a small number of very large customers to justify generation buildout. A likely middle path, and one Congress has taken before on infrastructure cost allocation, is a rule that permits recovery from general ratepayers only for costs demonstrably shared with the broader system — leaving significant interpretive work to FERC and state commissions.

    The Political And Narrative Risk

    The industry’s public messaging has emphasized economic development, tax base, and national competitiveness in AI. Those arguments remain intact, but they answer a different question than the one Castor is asking. A bipartisan bill signals that “data centers raise my power bill” has become a durable political frame, not a partisan talking point. Even if this specific bill does not pass, its introduction changes the baseline expectation for future state and federal action, and it gives regulators political cover to tighten large-load cost-allocation rules now. Operators and their trade groups will want to engage on the substance — cost causation, contribution to system reliability, willingness to pay for firm capacity — rather than dismiss the concern.

    Background

    U.S. data center power demand has grown sharply in the last several years, driven first by cloud consolidation and then, more intensely, by AI training and inference workloads. Individual hyperscale campuses now routinely request hundreds of megawatts of interconnection, and some proposed sites approach or exceed one gigawatt — comparable to the load of a mid-sized city. That growth has strained interconnection queues, generation adequacy, and, increasingly, the political consensus around who pays for the resulting grid buildout.

    Rep. Kathy Castor represents Florida’s 14th congressional district and has been active on energy and consumer-protection issues. The bill announced on June 20, 2026 is her office’s entry into a debate that has, until now, been fought primarily in state public service commission dockets and utility rate cases.

    Source: U.S. Rep. Kathy Castor Introduces Bipartisan Bill Protecting Americans from Paying for Data Center Development — announcement from Rep. Castor’s official congressional office, dated June 20, 2026.

  • Baseten Nears $1.5B Round as AI Inference Demand Surges

    Baseten Nears $1.5B Round as AI Inference Demand Surges

    AI inference platform Baseten is nearing a funding round of roughly $1.5 billion, according to a June 19, 2026 report from PYMNTS. The report ties the raise directly to surging demand for inference — the work of running trained AI models in production — rather than for model training.

    Terms, investors, and valuation were not detailed in the headline-level report, and the round had not been confirmed as closed at publication time.

    Executive Summary

    According to the report, Baseten — a company that helps businesses deploy and serve AI models at scale — is close to raising approximately $1.5 billion in new capital. For a company that was a mid-sized startup only two years earlier, a raise of this magnitude would rank among the largest ever for a dedicated inference provider.

    The significance is less about one company than about where AI infrastructure money is now flowing. For the first few years of the generative-AI boom, capital chased training: the enormous one-time compute jobs that create frontier models. A $1.5 billion round for an inference specialist signals that investors now see the recurring, usage-driven business of serving models to end users as the larger and more durable prize.

    That said, the source is thin. A single report of a round that is ‘near’ closing establishes investor intent and market temperature, but not final terms, valuation, or how the money will be spent. Those distinctions matter for anyone reading this as a market signal.

    Inference Becomes the Center of Gravity

    Training a large AI model is a one-time capital event; inference is a bill that arrives every time anyone uses the model. As AI applications have moved from demos into daily production use, the aggregate compute spent answering queries has grown continuously, while training runs remain episodic and concentrated among a handful of frontier labs. A near-$1.5 billion bet on an inference specialist is a bet that this recurring workload — not the headline-grabbing training runs — is where sustained revenue accumulates.

    This inversion matters for the whole infrastructure stack. Training clusters favor a few gigantic, tightly coupled GPU installations. Inference favors distributed capacity closer to users, high utilization, and relentless cost-per-token optimization. If the money is following inference, demand patterns for data center capacity, networking, and power will follow it too.

    Why Inference Platforms Command This Kind of Capital

    Inference sounds simple — run the model, return the answer — but doing it profitably at scale is an engineering discipline of its own: batching requests, compiling models to specific chips, autoscaling against spiky traffic, and squeezing latency low enough for real-time products. Companies like Baseten sell that discipline as a service, sitting between raw GPU suppliers and application builders who don’t want to run their own model-serving operation.

    The catch is that the business is capital-hungry in both directions. Serving customers requires reserving expensive GPU capacity ahead of demand, and competing on price requires continuous optimization investment. A $1.5 billion war chest, if the round closes as reported, is plausibly less about runway than about locking up compute supply and engineering talent before rivals do.

    Winners, Losers, and the Squeeze in the Middle

    The clearest beneficiaries of an inference-led cycle are the layers underneath: GPU vendors, specialized AI clouds, and the data center and power providers that host distributed serving capacity. The most exposed parties are undifferentiated middlemen — inference is a market where hyperscalers (Amazon, Google, Microsoft), well-funded independents, and open-source serving stacks all compete, and per-token prices have fallen steadily across the industry.

    That competitive pressure cuts both ways for Baseten. A massive raise validates the category but also raises the stakes: the company would need to convert capital into durable advantages — proprietary optimizations, enterprise trust, sticky deployments — faster than falling inference prices erode margins. Investors appear to be betting that scale itself becomes the moat. That thesis is credible but unproven, and the report offers no revenue or margin data to test it against.

    Background

    Baseten was founded in 2019 in San Francisco, initially building tools that let software teams deploy machine-learning models without specialized infrastructure staff. The generative-AI boom transformed that niche into one of the industry’s fastest-growing markets, and the company raised successive venture rounds through 2025 that reportedly pushed its valuation past $2 billion.

    The broader market context is a widely discussed shift in AI economics: as chatbots, coding assistants, and AI-powered products moved into everyday production use, industry attention moved from training models to serving them. Inference specialists — alongside GPU clouds and the data center operators beneath them — became prime beneficiaries of that shift, setting the stage for the mega-round reported here.

    Source: Baseten Nears $1.5 Billion Funding Round as Inference Demand Surges — PYMNTS report, June 19, 2026, on Baseten’s reported near-$1.5 billion raise amid surging AI inference demand.

  • FERC Steps Into the Data Center Interconnection Fight

    FERC Steps Into the Data Center Interconnection Fight

    Politico reported on June 18, 2026 that the Federal Energy Regulatory Commission (FERC) — characterized in the piece as “not the old sleepy agency” — is diving into the escalating fight over how data centers connect to the U.S. power grid. The report frames the once low-profile regulator as an increasingly active and decisive player in disputes over data-center interconnection, the process by which large new electricity loads are studied, approved, and physically wired into the grid.

    Executive Summary

    The headline itself is the story: a Washington energy regulator that historically operated far from public attention is now central to one of the most consequential infrastructure questions of the decade — how, where, and on what terms the data centers powering artificial intelligence get their electricity. Politico’s framing, that FERC is no longer “the old sleepy agency,” signals that the commission is taking an assertive posture in interconnection disputes rather than leaving them to utilities, regional grid operators, and states to sort out.

    For the data-center industry, this matters because grid access — not land, capital, or chips — has become the binding constraint on new capacity in many U.S. markets. Whatever rules FERC shapes for connecting very large loads will influence project timelines, cost allocation, and site selection across the country. The report we are working from is a headline-level summary rather than a full text, so the specific proceedings, orders, or disputes Politico describes are not detailed here; our analysis focuses on why FERC’s posture matters and what remains to be confirmed.

    Why the Grid Regulator Suddenly Matters to AI

    FERC regulates interstate electricity transmission and wholesale power markets — the high-voltage backbone of the grid — and oversees the regional transmission organizations that run much of it. For decades that made it consequential mainly to utilities and power traders. The AI buildout changed the audience. Data centers are now proposing loads measured in the hundreds of megawatts and even gigawatts, on par with heavy industry or small cities, and connecting loads of that size raises exactly the questions FERC referees: who gets studied first, what upgrades are required, and who pays for them.

    The “sleepy agency” framing in Politico’s headline captures a real shift in stakes. When interconnection was routine, the rules governing it were obscure. When interconnection becomes the gating item for a multi-hundred-billion-dollar industry, the same rules become front-page policy — and the body that writes them becomes a power broker whether it seeks the role or not.

    The Interconnection Bottleneck Is the Business Story

    Interconnection — the engineering and contractual process of plugging a new generator or large customer into the grid — has become notorious for multi-year queues in many U.S. regions. For data-center developers, an interconnection timeline is effectively a revenue timeline: a site that cannot energize cannot sell capacity. That is why disputes over queue rules, study procedures, and arrangements such as co-locating data centers directly at power plants (sometimes called behind-the-meter siting, where the load connects at the plant rather than through the wider grid) have turned into hard-fought regulatory battles.

    How FERC resolves these fights will shape winners and losers. Clear, faster federal rules would favor developers with strong utility relationships and sites near existing capacity. Restrictive or unsettled rules push projects toward states and utilities perceived as easier to work with, toward on-site generation, or toward markets abroad. Utilities and existing ratepayers, meanwhile, have a direct stake in ensuring that grid upgrades driven by data-center demand are paid for by the companies that cause them rather than spread across household bills — a cost-allocation question that sits squarely in FERC’s lane.

    An Assertive FERC Cuts Both Ways

    An engaged regulator is not automatically good or bad news for the industry. On one hand, federal clarity could standardize how very large loads are treated, reducing the state-by-state and utility-by-utility uncertainty that currently complicates siting decisions. On the other, active federal scrutiny can slow novel deal structures — such as dedicated supply arrangements between power plants and data centers — while the commission works out reliability and fairness implications for everyone else on the grid.

    It is also worth noting what FERC does not control. Siting of the data centers themselves, retail electricity rates, and most generation permitting remain state matters. So even a maximally assertive FERC is one decisive player among several, and the practical outcome for any given project will depend on how federal interconnection policy interacts with state regulation and utility planning. The Politico headline tells us the referee has taken the field; the source available to us does not detail which specific calls it is making.

    Background

    FERC traces its lineage to the Federal Power Commission, created in 1920, and has long operated as a technical regulator of interstate power transmission, wholesale electricity markets, and natural-gas infrastructure. Its rules govern the regional transmission organizations — such as PJM in the mid-Atlantic — that manage the grid across much of the country, and its interconnection procedures determine how new generators and, increasingly, very large customers plug in.

    The agency’s rising profile tracks the AI-driven surge in electricity demand. After roughly two decades of flat U.S. power consumption, forecasts turned sharply upward in the mid-2020s as hyperscale data centers multiplied, and disputes over connecting them — including high-profile fights over siting data centers directly at power plants — began landing at FERC’s door. The June 2026 Politico report captures the resulting role reversal: an agency once known mainly to energy lawyers is now a decisive venue for the infrastructure economics of AI.

    Source: ‘Not the old sleepy agency’: Energy regulator dives into fight over data center connections — Politico’s June 18, 2026 report on FERC’s growing role in data-center interconnection disputes.

  • Baseten’s Reported $1.5B Raise Puts AI Inference in the Spotlight

    Baseten’s Reported $1.5B Raise Puts AI Inference in the Spotlight

    AI inference provider Baseten is reportedly raising $1.5 billion in new funding, according to a June 18, 2026 report from SiliconANGLE. The report describes a round in progress rather than a closed deal, and terms such as valuation, investors, and structure were not disclosed in the source material.

    If the figure holds, it would rank among the largest financings yet for a company focused specifically on inference — the business of serving AI models to end users — rather than on training them.

    Executive Summary

    The headline fact is simple: Baseten, a platform that helps companies deploy and run AI models in production, is reported to be raising $1.5 billion. Because this is a media report of an in-progress raise rather than a company announcement, the number should be treated as provisional until confirmed.

    The significance is less about one company and more about what the capital is chasing. For the past several years, the biggest checks in AI infrastructure went to training — the enormous, one-time computation of building frontier models. A ten-figure round for an inference specialist suggests investors now believe the durable, recurring revenue sits in serving models at scale, every second of every day, to real applications.

    For infrastructure operators, that shift matters. Inference workloads have different economics than training: they run continuously, they are latency-sensitive, they favor geographic distribution over single giant campuses, and they reward efficiency per query rather than raw peak compute. Where the money goes, data center design, power planning, and network architecture tend to follow.

    From Training to Serving: Why the Money Is Moving

    Training a large AI model is a capital event — vast, concentrated, and episodic. Inference is an operating expense that scales with usage: every chatbot reply, code completion, and document summary is an inference call. As AI products mature from demos into deployed software with paying users, the volume of inference grows with adoption, and it never stops. Investors underwriting a reported $1.5 billion round are, in effect, betting that this recurring workload — not the next training run — is where sustainable revenue accumulates.

    That thesis has a sound structural basis. A model is trained once but served millions or billions of times, so over a product’s life the cumulative compute spent on inference can dwarf what was spent creating the model. Companies that sit in the serving path — optimizing latency, managing GPU fleets, autoscaling with demand — collect a toll on every one of those calls.

    What a War Chest Buys in the Inference Business

    Inference platforms are capacity businesses as much as software businesses. To guarantee customers low latency and high availability, a provider must secure GPUs — either owned, leased from cloud providers, or contracted from specialized GPU clouds — ahead of demand. That is capital-intensive, and it is the most plausible use for a raise of this size: locking up compute supply, expanding into more regions to cut round-trip latency, and funding the engineering that squeezes more throughput out of each accelerator.

    Scale also buys negotiating power. Larger committed volumes typically mean better pricing on hardware and colocation, which flows through to more competitive per-token pricing for customers. In a market where inference is increasingly bought like a commodity — priced per million tokens — cost structure is strategy.

    A Crowded Field, and the Hyperscaler Question

    Baseten does not operate in a vacuum. Dedicated inference providers compete with one another, with GPU-cloud operators moving up the stack, and — most importantly — with the hyperscale clouds, which bundle inference into broader platforms, and with model developers offering their own hosted APIs. The bear case for any independent inference company is that serving becomes a thin-margin utility captured by whoever owns the most silicon.

    The bull case is specialization: enterprises running open-weight or fine-tuned models often want performance tuning, deployment control, and price transparency that general-purpose clouds don’t prioritize. A raise of the reported magnitude suggests at least some sophisticated investors find the bull case credible — though it is worth remembering that a reported raise reflects investor conviction, not proven unit economics. The release-level information here does not tell us Baseten’s revenue, margins, or utilization, and those are the numbers that will ultimately decide the argument.

    Background

    Baseten emerged in the wave of machine-learning infrastructure startups that formed as companies moved AI models out of research labs and into production applications. Its focus is the deployment layer: rather than training models or selling raw GPU time, it provides the tooling and managed infrastructure to run models as reliable, scalable services — a niche that grew rapidly once generative AI created mass demand for model serving.

    The broader context is a maturing AI infrastructure market. The first phase of the boom concentrated capital on training compute and the data centers to house it. By 2026, attention had broadened to inference — the operational layer where AI meets users — drawing large financings to companies across the serving stack, from GPU clouds to optimization software.

    Source: AI inference provider Baseten reportedly raising $1.5B in funding — SiliconANGLE, a June 18, 2026 report on Baseten’s in-progress funding round.

  • FERC Pushes Grid Operators to Overhaul Data Center Interconnection Rules

    FERC Pushes Grid Operators to Overhaul Data Center Interconnection Rules

    The Federal Energy Regulatory Commission (FERC), the top US energy regulator, is pressing the nation’s grid operators to overhaul the rules governing how large data centers connect to and draw power from the electric grid, according to a Reuters report dated June 17, 2026. The push targets the regional transmission organizations that manage most of the US high-voltage grid, and lands in the middle of an unprecedented wave of AI-driven electricity demand.

    Executive Summary

    According to Reuters, FERC is urging grid operators to rewrite their rules for connecting large data center loads — the procedures, studies, and cost arrangements that determine how quickly a gigawatt-scale computing facility can plug into the transmission system and on what terms. The report frames this as a directive from the regulator to the regional grid operators rather than a finished rule, which means the substance will be worked out in filings, stakeholder processes, and likely litigation over the months ahead.

    Why it matters: interconnection has become the single biggest bottleneck in the AI infrastructure buildout. Chips can be bought and buildings can be raised in quarters; grid connections for very large loads are quoted in years. Whoever writes the rules for large-load interconnection — how costs are allocated, whether data centers can co-locate with power plants, and what reliability obligations big loads must accept — will effectively set the pace and geography of AI data center construction in the United States. A FERC push to standardize those rules is therefore one of the most consequential regulatory developments the industry has seen this cycle, even before its details are settled.

    Interconnection Is Now the Gating Factor for AI Capacity

    For most of the grid’s history, the hard problem was connecting new generators; large customer loads arrived gradually and were absorbed through routine utility planning. AI has inverted that. Individual data center campuses now request hundreds of megawatts — in some cases more than a gigawatt, roughly the draw of a mid-sized city — and they request it on construction timelines the traditional load-forecasting process was never designed to handle. Grid operators have responded with a patchwork: some regions created special large-load study tracks, others applied generator-style queue rules to loads, and others negotiated case by case. A federal push to overhaul and presumably harmonize these rules is a recognition that the patchwork itself has become a source of delay and dispute.

    For data center developers and their tenants, the near-term effect of any rule rewrite is uncertainty, but the medium-term prize is predictability. A standardized process — with defined study timelines, transparent cost estimates, and clear rules on what a large load must commit to — would let operators of digital infrastructure make siting decisions on engineering and economics rather than on which utility territory offers the friendliest ad hoc deal.

    The Fights Underneath: Co-Location, Cost Allocation, and Curtailment

    Three unresolved disputes sit beneath any large-load rule overhaul. First, co-location — siting a data center directly beside a power plant and buying its output behind the meter. The arrangement can bypass years of transmission upgrades, but regulators and utilities have questioned whether such configurations pay their fair share for the grid that still backs them up; FERC itself has been wrestling publicly with co-location frameworks since high-profile disputes over data centers sited at nuclear plants in the PJM region. Second, cost allocation: when a multi-hundred-megawatt load triggers new transmission lines or substations, someone pays — the developer, the utility’s general ratepayer base, or some blend. Consumer advocates in several states have argued that ordinary households risk subsidizing AI growth; developers counter that they routinely fund dedicated upgrades. Third, flexibility and curtailment: grid operators increasingly want large loads to accept interruption or demand-response obligations during system stress in exchange for faster connection. Each of these is a genuine economic contest between reasonable positions, and the Reuters report does not indicate which way FERC is leaning on any of them.

    Winners, Losers, and the Federal–State Seam

    If the overhaul produces faster, standardized large-load interconnection, the clearest winners are hyperscale cloud and AI companies with capital ready to deploy, and the transmission-rich regions able to absorb them. Utilities gain too, if the rules convert speculative or duplicative connection requests — a real problem, since developers often file in multiple territories for the same project — into firm, financially committed ones. The pressure lands on grid operators, which must rewrite tariffs under regulatory deadline while managing record demand growth, and potentially on smaller data center operators, if new rules impose financial-commitment thresholds sized for hyperscalers.

    There is also a jurisdictional seam worth watching. FERC governs wholesale markets and the interstate transmission system, but retail electric service and most siting decisions belong to the states, and Texas’s ERCOT grid sits largely outside FERC’s reach altogether. A federal overhaul can standardize how regional operators study and connect big loads, but it cannot by itself resolve state-level fights over who pays or where facilities are built. Buyers should expect a more legible federal process layered over a still-fragmented state landscape, not a single national rulebook.

    Background

    FERC, created in its modern form in 1977, oversees the interstate transmission system and the wholesale power markets run by regional grid operators. Its interconnection rules historically focused on generators — culminating in a 2023 queue-reform order aimed at the enormous backlog of power plants awaiting connection. Large customer loads, by contrast, were left mostly to individual utilities and states, an arrangement that held until AI demand broke it.

    From roughly 2024 onward, gigawatt-scale data center requests, contested co-location deals at nuclear plants in the PJM region, and warnings from grid operators about record demand growth pushed large-load interconnection onto FERC’s docket. The June 2026 push reported by Reuters is the continuation of that arc: the federal regulator moving from case-by-case dispute resolution toward pressing for systematic rules on how the grid absorbs the AI buildout.

    Source: Top US energy regulator pushes grids to overhaul data center power rules — Reuters, June 17, 2026, reporting FERC’s push for grid operators to rewrite large-load interconnection rules.

  • Google Open-Sources a Liquid-to-Air Cooling Sidecar for Air-Cooled Data Centers

    Google Open-Sources a Liquid-to-Air Cooling Sidecar for Air-Cooled Data Centers

    Google has unveiled an open-source liquid-to-air cooling sidecar designed for air-cooled data center environments, as reported by Data Center Dynamics on June 17, 2026. The design targets one of the most pressing constraints in the industry: modern AI accelerators increasingly require direct liquid cooling, while the vast majority of existing data center floor space was built to move heat with air alone.

    A sidecar of this type is a heat-exchanger cabinet that sits beside a rack of liquid-cooled servers, circulating coolant through the chips in a closed loop and then rejecting that heat into the room’s existing airflow — no facility water piping required. By publishing the design openly, Google is inviting vendors and operators to build and adapt it rather than keeping it proprietary.

    Executive Summary

    The announcement matters less for what the hardware is than for where it lets liquid cooling go. Direct-to-chip liquid cooling has become effectively mandatory for the densest AI training hardware, but deploying it normally requires facility-level infrastructure — coolant distribution units, piping loops, and water connections that most operating data centers simply do not have. A liquid-to-air sidecar sidesteps that requirement: the liquid loop stays local to the rack, and the building’s existing air-handling systems carry the heat away as they always have.

    That makes this a retrofit play. Enterprises, colocation tenants, and smaller operators sitting on air-cooled capacity gain a path to host at least some liquid-cooled equipment without construction projects. It is also a continuation of Google’s recent posture of contributing cooling designs to the open hardware ecosystem rather than treating them as competitive secrets — a bet that standardizing the plumbing layer accelerates the whole market Google’s cloud and AI businesses depend on.

    The report available at the time of writing is brief, and the announcement as covered leaves key engineering and availability details unstated — including the design’s cooling capacity, its publication venue and license, and whether it reflects hardware Google runs in production. Those specifics will determine whether this is a broadly useful reference design or a niche one.

    The Retrofit Gap Is the Industry’s Quiet Bottleneck

    Headlines about AI data centers focus on new gigawatt-scale campuses, but most of the world’s installed data center capacity is older, air-cooled space designed for racks drawing 5 to 15 kilowatts. Current AI server racks can draw many times that, and the chips inside them ship with cold plates that expect liquid, not airflow. Operators of existing facilities face an unattractive menu: leave AI workloads to someone else, undertake disruptive plumbing retrofits in live buildings, or find a bridge technology.

    Liquid-to-air sidecars are that bridge. Because the liquid never leaves the immediate vicinity of the rack, the facility itself does not need water loops, external coolant distribution plants, or new mechanical rooms. The trade-off is physics: the room’s air systems still have to absorb every watt the sidecar rejects, so total rack density remains bounded by the building’s air-handling and power envelope. A sidecar extends the life of air-cooled space; it does not turn a legacy building into a frontier AI facility.

    Why Give the Design Away?

    Google has form here. The company has run liquid-cooled custom TPU accelerators internally since roughly 2018, and in 2025 it announced it would contribute a production coolant distribution unit design to the Open Compute Project, the industry body through which hyperscalers share hardware specifications. Open-sourcing a sidecar fits the same logic: cooling hardware is not where Google differentiates, but an immature, fragmented cooling supply chain slows everyone — including Google and the customers of its cloud business.

    Open designs give equipment manufacturers a common reference to build against, which tends to lower prices, improve interoperability, and widen the vendor pool. For Google there is also a soft-power dividend: hyperscaler-authored designs shape industry standards, and the ecosystem that grows up around them tends to stay compatible with the author’s infrastructure choices. None of that makes the contribution less useful — but it is worth understanding open-source hardware as strategy, not charity.

    Winners, Losers, and the Honest Limits

    The clearest beneficiaries are operators of existing air-cooled facilities — enterprise server rooms, regional colocation providers, and edge sites — who gain an on-ramp to liquid-cooled hardware without capital construction. Cooling-equipment manufacturers get a design they can productize; some may welcome the demand signal, while vendors selling proprietary sidecar and rear-door heat exchanger products now face an open alternative that could compress margins.

    The honest caveat is that the announcement, as reported, is a design release, not a product with published performance data. Until the specification’s capacity, tested configurations, and licensing terms are public and third parties have built against it, the practical impact is prospective. Open hardware contributions have a mixed track record: some become de facto standards, others languish without a manufacturing ecosystem. Which path this design takes depends on details the initial coverage does not yet supply.

    Background

    Google is one of the world’s largest data center operators and has cooled its custom TPU AI accelerators with liquid since roughly 2018 — years before liquid cooling became an industry-wide necessity. In 2025 it began contributing pieces of that cooling stack to the open hardware ecosystem, announcing a production coolant distribution unit design for the Open Compute Project, the body through which hyperscalers share server and infrastructure specifications.

    The backdrop is a market-wide squeeze: AI hardware demand is rising far faster than new liquid-ready facilities can be built, leaving a large installed base of air-cooled data centers unable to host the densest equipment. Bridge technologies that bring liquid cooling into air-cooled buildings — sidecars and rear-door heat exchangers among them — have become one of the fastest-moving segments of data center engineering.

    Source: Google unveils new open-source liquid-to-air cooling sidecar for air-cooled environments — Data Center Dynamics report, June 17, 2026, on Google’s open-source cooling hardware release.