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

Tag: California

  • Up to $1.8B in Grid Upgrades: California’s AI Data Center Deal Is About Who Pays First

    Up to $1.8B in Grid Upgrades: California’s AI Data Center Deal Is About Who Pays First

    TL;DR · 30-second read

    The Short Version

    California lawmakers have agreed on new rules for data centers, the giant warehouses of computers that run artificial intelligence and everyday online services.

    The central idea: companies building them would pay upfront for the power lines and grid upgrades their electricity demands, instead of spreading that cost across everyone’s utility bills. State grid planners estimate those upgrades in one major utility’s territory could cost up to $1.8 billion.

    The deal comes as nearly three in four Californians say they oppose data centers in their own communities, and several cities have banned or paused them.

    California lawmakers reached a compromise on Friday, Aug. 28, on legislation regulating the electricity use of data centers, the Los Angeles Times reported. The package, from Sen. Steve Padilla (D-Chula Vista) and Assemblymember Rick Chavez Zbur (D-Los Angeles), directs the California Public Utilities Commission (CPUC) to create special rates and updated rules for data centers, including how the cost of new power and infrastructure upgrades is charged.

    The final package includes the approach from Padilla’s SB 886, sponsored by The Utility Reform Network (TURN), requiring data centers to pay up front for broader grid upgrades needed to serve their demand. TURN cited a California grid operator transmission plan projecting up to $1.8 billion in upgrade costs, including transmission lines, driven by data center demand in PG&E’s service territory, where most current and proposed California data centers are concentrated.

    Executive Summary

    California has chosen a cost-allocation answer to data center growth rather than a moratorium. The deal does not cap how many facilities can be built. It changes who pays for the grid capacity they need, and when. Under the upfront-payment approach carried over from SB 886, a data center’s share of transmission and distribution upgrades becomes part of the developer’s capital budget instead of a cost recovered later from the general customer base.

    That matters because the numbers are no longer small. The California Energy Commission expects data center electricity use, now about 2% of statewide demand, to double within ten years, and the grid operator’s plan puts potential data-center-driven upgrades in PG&E territory at up to $1.8 billion. Much of the practical detail, including rate design, thresholds and timing, is left to the CPUC. Meanwhile, a provision allowing utilities to strike their own agreements with data centers before the CPUC finishes its rules creates an interim window that developers and critics will both watch closely.

    For AI infrastructure planners, the signal is mixed. The state has set a clear principle that growth pays for itself, which may reduce political risk over time. It has also added cost in a market where high power prices, scarce land and limits on gas-fired generators already hold most projects below 100 megawatts.

    The Fight Was Never About Whether, But Who Pays First

    The core dispute in Sacramento was not whether California should host data centers. It was how much they should pay for power and grid infrastructure, and whether the Legislature or the CPUC should decide. The two options on the table amount to two different financing models. When a utility builds new substations and transmission lines to serve a large new customer, the cost can either be added to the utility’s rate base and recovered over years from all customers, or charged to the customer that triggered it before the work proceeds. SB 886’s approach, which made it into the final package, leans toward the second model.

    The scale comes from the grid operator’s transmission plan, which projects up to $1.8 billion in upgrade costs from data center demand in PG&E’s territory. Moving even a meaningful portion of that onto project budgets changes a developer’s math in three ways. More capital is needed before a building is energized. Grid upgrades shift from a utility’s problem to a line item that competes with land and equipment. And a site’s value depends more heavily on how much grid headroom already exists nearby. TURN’s Matthew Freedman framed the result as keeping data center costs from “being foisted on other customers.” PG&E, which favored a less stringent approach, warned that SB 886 would “risk higher costs for customers and delay critical infrastructure,” which is a reminder that upfront payment also affects how quickly utilities can build ahead of demand.

    The groups most directly affected are developers targeting PG&E territory, which covers most of the state’s data center pipeline including the San José market, and household ratepayers, whose exposure to data-center-driven upgrades is what the deal is designed to limit. How much protection they actually get depends on rate design the CPUC has not yet written.

    A Market Already Built Small

    California enters this regime with an unusual profile. Its data centers are typically under 100 megawatts, well short of the 500-megawatt-plus AI campuses rising in other states, because of high electricity costs and state limits on gas-powered generators. The 49.5-megawatt facility under construction in Vernon is representative. For operators already constrained this way, an upfront grid charge adds to a cost stack that the Data Center Coalition’s Khara Boender says is uncompetitive: she noted that dozens of states offer data center exemptions and California does not, and called added regulation “another signal that the state is a more challenging place for data center development.”

    That argument deserves a fair hearing, and so does the counterpoint. The Coalition opposed both bills for “singling out” one type of power user. Yet the premise of cost-causation pricing is that the customer creating a large, identifiable load pays for it, and data centers are unusually concentrated loads. The strongest case on the industry’s side is not that the principle is wrong. It is that the details, such as how “broader” upgrades are apportioned among several projects on a shared line, could make early movers pay for capacity later arrivals use. That question now sits with the CPUC.

    The Interim Window and the Self-Supply Gap

    Two late amendments drew criticism from Monica Embrey of the Affordable Energy Campaign. The first allows a utility to reach its own agreement with a data center in the period before the state finalizes its rules. In practice, that creates a window in which terms are negotiated bilaterally rather than set by tariff, and projects that sign during it may lock in arrangements that differ from what the CPUC ultimately adopts. The second is the absence of clean energy requirements for data centers that generate their own power.

    Together these point to where AI campus developers are likely to focus next. If grid-supplied power carries upfront upgrade costs while self-supplied power carries no clean energy obligation, on-site or behind-the-meter supply becomes relatively more attractive, within the limits California already places on gas generators. Whether that tilt is intended, and how regulators will treat it, is one of the more consequential open questions in the package.

    Local Opposition Sets the Ceiling

    State rate rules do not settle the land-use fight playing out city by city. A Public Policy Institute of California poll in July found 73% of residents oppose data centers in their own communities. Monterey Park voters banned them outright in June, at least four other San Gabriel Valley cities have adopted moratoriums, Coachella imposed a permanent ban, and Tulare County adopted a moratorium in August. In San José, the state’s main development hub, residents have pushed for a pause while the city updates its standards.

    Water sits on a parallel track. Newsom vetoed a water-disclosure bill from Assemblymember Diane Papan last year, citing “rigid” reporting requirements, but lawmakers have since approved separate bills requiring energy and water use disclosure. For developers, the combined effect is that a California site now has to clear a cost-allocation test at the utility, a disclosure regime at the state level, and a local political test that some communities have already answered with a no.

    Background

    California has not experienced the wave of very large AI data centers seen in states such as Texas. High power prices, limited land and restrictions on gas-fired backup and primary generation have kept most facilities comparatively small, with San José and the wider PG&E service territory hosting most activity. The CPUC, whose board is appointed by the governor, regulates investor-owned utilities such as PG&E and sets the rates they charge.

    Data center growth has nonetheless become a political issue in the state. Community opposition has produced a local ban in Monterey Park, moratoriums across the San Gabriel Valley, the Coachella Valley and Tulare County, and pushback against a proposed 75-acre project in Imperial Valley. In 2025, Gov. Gavin Newsom vetoed a water-disclosure bill, citing concern about rigid requirements on critical digital infrastructure, which left energy cost allocation as the main legislative battleground in the 2026 session.

    Sources

    Source: California lawmakers reach deal in high-stakes fight over regulating data centers (Los Angeles Times), on the legislative compromise directing the CPUC to set data center electricity rates and upfront grid-upgrade charges.

  • Imperial Valley’s 330 MW Lawsuit Shows Water Rights Can Gate AI-Era Capacity

    Imperial Valley’s 330 MW Lawsuit Shows Water Rights Can Gate AI-Era Capacity

    TL;DR · 30-second read

    The Short Version

    A company planning California’s largest data center, a huge building full of computers like the ones that run AI tools, was refused the water it needs to keep those machines cool. It is now suing the public agency that controls the local water.

    The water comes from the Colorado River. About 40 million people in seven states depend on that river, and drought has strained it. The company wants to take over water that farms use today.

    The court case could help decide whether water, not only electricity, limits where the AI boom can be built.

    BGR reported on August 12, 2026 that Imperial Valley Computer Manufacturing has sued the Imperial Irrigation District (IID), the public agency that delivers Colorado River water to California’s Imperial Valley. IID had denied the developer’s request to use the district’s water supply and wastewater to cool a planned 330-megawatt data center, which would be the largest in California. The facility is expected to require 287 million gallons of water.

    The developer plans to source that water by reallocating it from farmland. Its lawsuit argues there is “no rational basis” for IID to bar an industrial company from combining several fields into a single unit for water reallocation while allowing agricultural users to do the same.

    Executive Summary

    Most debate about where AI data centers can be built focuses on electricity: whether the grid can deliver hundreds of megawatts, and how fast. The Imperial Valley dispute puts a different constraint in front of a court. The developer’s cooling plan depends on moving existing farm water allocations to an industrial user, and the agency that controls those allocations has said no.

    The legal question is narrow, whether an industrial user may aggregate and transfer water the way farmers already can. The practical stakes are broad. If water rules can block a 330-megawatt project in one of the most water-contested basins in the country, developers eyeing arid regions will have to treat water rights as a gating item on par with a power connection, not as a permit to settle later.

    Sebastian Rucci, the figure leading the project, argues the data center would use about as much water as a 160-acre farm and would benefit the local economy. Critics counter that reallocating farm water puts rural communities at risk, and local residents broadly favor a moratorium on new data center construction.

    Why Water Rights, Not Just Megawatts, Gate This Project

    A data center’s electrical rating, here 330 megawatts, describes how much power its computers and support systems can draw. Nearly all of that electricity ends up as heat, which has to be removed continuously. Many large facilities do this with evaporative cooling, in which water is evaporated in cooling towers to carry heat away. That design is efficient on electricity but consumes water in proportion to the heat load, which is why a 330-megawatt campus arrives with a 287-million-gallon water requirement attached.

    In the Imperial Valley, that water has to come from somewhere already spoken for. IID delivers Colorado River water to the region, and the developer’s plan is to reallocate water currently tied to farmland. IID’s denial covered both its water supply and its wastewater, closing off reclaimed water as well as fresh. As things stand, the project’s cooling design cannot proceed on the terms the developer proposed, whatever its power situation. That is the mechanism the title points to: a local water agency’s allocation rules, not the grid, are the decision point currently holding up this capacity.

    The people affected extend beyond one developer. Anyone siting large facilities in the arid Southwest, where land and solar power are attractive, now has a live example of water access acting as a hard stop. Water agencies are affected too, since a ruling will signal how much discretion they have to treat industrial and agricultural transfers differently.

    The Legal Question: Can Industry Aggregate Water Like Farms Do?

    The lawsuit’s core argument is about equal treatment. According to the complaint as described, IID lets agricultural users combine multiple fields into a single unit for water reallocation but refused to let an industrial company do the same. The developer says there is “no rational basis” for the distinction.

    That phrasing echoes a well-established legal standard under which a government body’s line-drawing generally survives if any reasonable justification exists. It is typically a demanding standard for challengers. IID may point to its mandate to serve agriculture, drought conditions on the Colorado River, or the difference between water that stays in farming and water permanently moved to a new industrial use. The developer will argue that water is water and that the district cannot favor one class of user without a principled reason.

    Either outcome sets a marker. A win for the developer would suggest farm water allocations in the district can be assembled and redirected to data centers, which would change land and water economics in the valley. A win for IID would confirm that water agencies can effectively decide whether water-intensive data centers get built in their service areas.

    Testing the 160-Acre Farm Comparison

    Rucci’s claim that the facility would have as much impact as a 160-acre farm can be checked against the stated figure. Dividing 287 million gallons across 160 acres works out to roughly 1.8 million gallons per acre, or about 5.5 acre-feet, the unit water managers use, where one acre-foot covers an acre of land a foot deep. Whether that matches a typical Imperial Valley farm depends on the crop and on whether 287 million gallons is an annual figure, which has not been specified.

    The comparison also answers a different question from the one critics are asking. Their objection is less about the total volume than about where it comes from: water moved out of farming, in a region where agriculture sustains rural livelihoods, from a river that serves 40 million people across seven states. It also leaves open how much of the data center’s water would be consumed through evaporation versus returned to the system, a distinction that matters for downstream users.

    Local Opposition Is Part of the Siting Math

    Residents in the area generally favor a strict moratorium on new data center construction, according to the reporting, reflecting concerns about utility prices and water strain that have followed data center projects in other regions. Rucci has argued the project would bring economic benefits, but the specifics of jobs, tax revenue or community agreements have not been laid out.

    For the industry, the lesson is that community sentiment and water governance are converging into a single siting risk. A project that must win both a court case over water allocation and a skeptical local public faces a longer and less predictable path than one that secures water and community support before it announces its scale.

    Background

    The Imperial Valley sits in California’s southeastern desert and depends on Colorado River water delivered by the Imperial Irrigation District, much of it for farming. The Colorado River supplies roughly 40 million people across seven U.S. states and has faced years of drought, making any new large draw on it contentious.

    Data centers have become one of the fastest-growing sources of industrial demand for both electricity and water as companies build capacity for artificial intelligence. Their water use comes mainly from cooling, and communities in several regions have pushed back on new facilities over utility costs and water strain, making water sourcing an increasingly visible part of the siting process.

    Sources

    Source: The Largest Data Center In California Has Been Denied Water For Cooling — Now It’s Suing A Public Agency (BGR), on Imperial Valley Computer Manufacturing’s lawsuit against the Imperial Irrigation District over cooling water for a planned 330 MW data center.

  • As CISA Faces a 30% Cut, California Makes AI Cyber Defense of Utilities a State Job

    As CISA Faces a 30% Cut, California Makes AI Cyber Defense of Utilities a State Job

    TL;DR · 30-second read

    The Short Version

    California’s governor announced a plan on August 10 to use artificial intelligence to find and block hackers targeting the systems behind tap water, electricity and emergency phone lines.

    The timing is the story. The federal government has proposed cutting its main cyber defense agency’s budget by about 30 percent, and a monitoring service that small towns used for free for two decades has lost its federal funding and is starting to charge. California is taking on more of that protection itself. It has not yet said how much it will spend.

    On August 10, 2026, California Governor Gavin Newsom announced an AI Cyber Defense Program, which his office describes as first-in-the-nation, according to the announcement published on CA.gov. The Governor directed state agencies to set up the program inside the California Cybersecurity Integration Center (Cal-CSIC), using AI for vulnerability detection, network hardening and incident response; to expand AI-enabled cyber defenses to local governments and critical infrastructure partners; and to designate an AI Cybersecurity Officer in every state agency.

    The Governor’s office tied the move to AI-enabled attacks and to federal pullbacks: a proposed Fiscal Year 2027 cut of roughly $707 million, about 30%, to the Cybersecurity and Infrastructure Security Agency (CISA), the end of federal funding for the Multi-State Information Sharing and Analysis Center (MS-ISAC) in late 2025, and the winding down of the current funding phase of a $1 billion federal state-and-local cyber grant program.

    Executive Summary

    California is building a state-run layer of AI-assisted cyber defense for the systems residents depend on most: water, power, transportation and emergency communications. The program sits in Cal-CSIC, the state’s existing hub for threat intelligence and incident coordination, and extends beyond state agencies to local governments and critical infrastructure operators.

    The significance is less the technology than the division of labor. For two decades, small water districts, counties and cities leaned on free or grant-funded federal services for round-the-clock monitoring and incident help. With those services shrinking or moving to paid models, California is positioning the state as the provider of last resort for AI-era cyber defense.

    What the announcement does not yet include is a budget, a timeline or eligibility rules, so the scale of what the state can actually absorb remains an open question.

    Why Utility Cyber Defense Is Becoming a State Job

    The most consequential directive is not the AI itself but the second item on the list: expanding access to advanced cybersecurity capabilities, including AI-enabled defenses, for local governments and critical infrastructure partners. That commits the state, through Cal-CSIC, to supplying defensive capacity to organizations it does not run: municipal water systems, county networks, and the operators of the power, transportation and emergency communications services that Cal OES Director Caroline Thomas Jacobs named.

    The Governor’s office set this against three federal changes. The proposed FY2027 budget would cut CISA, the federal agency that provides field support, incident response and defensive tools, by roughly $707 million, about 30% below earlier levels. MS-ISAC, which for more than twenty years gave thousands of state, local, Tribal and territorial governments 24/7 monitoring and threat intelligence at no direct cost, lost federal funding in late 2025 and is moving to paid models. And the State and Local Cybersecurity Grant Program, launched with $1 billion under the Bipartisan Infrastructure Law, is nearing the end of its current funding phase. Each of these disproportionately served small jurisdictions, such as a water district with a handful of IT staff that could never run its own round-the-clock security operations center. When that free federal layer thins, those operators can pay, go without, or lean on the state. California is choosing to make the third option real.

    Two caveats keep this in proportion. The CISA figure is a budget proposal; Congress sets appropriations, and it has advanced bipartisan legislation to keep the grant program authorized. And the state has attached no dollar figure to its own program, so how much of the federal gap it can fill is unknown. The stakes are illustrated by the case federal officials recently flagged in Minnesota: a suspected Iran-linked operation touching more than 30 municipal water utilities in a single campaign, exactly the kind of many-small-targets pattern where limited local defenses matter most.

    What AI-Enabled Defense Means in Practice

    The program names three functions. Vulnerability detection means finding weaknesses, such as unpatched software or exposed services, before attackers do. Network hardening means closing unnecessary openings and tightening configurations. Incident response means containing a breach and restoring service. AI’s promise across all three is speed and scale: sorting thousands of alerts, scanning large inventories of systems, and flagging anomalies faster than a small team could.

    The Governor’s office grounds the urgency in disclosures by leading AI developers that advanced systems independently carried out sophisticated cyber operations in controlled testing, and in adversaries using AI to attack more cheaply and effectively. The logic follows: if the cost of attacking falls, defenders relying on manual processes fall behind, and automation is the natural counter. The announcement does not, however, name the tools, vendors or performance measures the state will use.

    Utilities are also harder to protect than office networks. Water treatment and the power grid run on operational technology, the industrial controllers that open valves, dose chemicals and switch circuits. Much of it is old and cannot be scanned or patched aggressively without risking the very service it runs. Whether the program reaches into those control systems or stays on the business-network side will largely determine how much protection it delivers to the services it names.

    Governance First: An AI Cyber Officer in Every Agency

    The third directive, an AI Cybersecurity Officer in every state agency, creates a named point of accountability across government. It aligns with Cal-Secure 2.0, the state’s 2026 cybersecurity roadmap, which already prioritizes workforce, coordination and wider use of AI-enabled security tools.

    It also completes a two-sided posture. Through Senate Bill 53, signed in 2025, the largest frontier AI developers must publish their safety frameworks and report certain critical safety incidents to the state. With this program, California is both regulating the developers whose models could be misused and deploying AI defensively. The state has not said whether incident reports filed under SB 53 will inform Cal-CSIC’s defensive work, which would be the most direct way to connect the two.

    What It Means for Data Center and Utility Operators

    Data centers, fiber networks and cloud facilities in California depend on the same grid and water systems the program targets, so a compromise upstream is an outage risk downstream. If private operators qualify as critical infrastructure partners, access to state threat intelligence and AI-enabled tooling could be a meaningful resource, particularly for smaller regional providers without large security teams.

    Until eligibility and terms are published, though, prudent planning assumes nothing. Local governments that relied on MS-ISAC’s no-cost services should budget for paid alternatives rather than count on state coverage arriving on a particular date. For security vendors, the program signals state demand for AI-driven detection and response, though procurement details have not been released.

    Background

    California has built out a state cyber apparatus over several years: Cal-CSIC as its threat intelligence and coordination hub, the Cal-Secure statewide cybersecurity roadmap (updated to Cal-Secure 2.0 in 2026), executive orders on artificial intelligence in 2023 and 2026, and SB 53, the Transparency in Frontier Artificial Intelligence Act, signed in 2025.

    Nationally, state and local cyber defense has leaned heavily on federal support: CISA’s field staff, incident response and tools; MS-ISAC’s no-cost monitoring for thousands of governments; and the $1 billion State and Local Cybersecurity Grant Program. All three are now shrinking, changing or facing uncertain funding, which shifts more of the burden to states and the local operators of water, power and communications systems.

    Sources

    Source: Governor Newsom announces new AI cyber defense program to protect California’s critical infrastructure, the Office of the Governor of California’s August 10, 2026 announcement of the AI Cyber Defense Program and related directives.

  • Offshore Nuclear Barges Eye California Ports and Data Centers

    Offshore Nuclear Barges Eye California Ports and Data Centers

    A concept for floating, offshore nuclear power barges is being pitched as a way to supply electricity to California ports and data centers, with proponents arguing that siting reactors in federal waters could avoid the state’s long-standing prohibition on new onshore nuclear plants. Fortune reported the proposal on June 16, 2026.

    Executive Summary

    The pitch pairs two trends: a resurgent interest in small, modular nuclear reactors and an acute shortage of firm, carbon-free power for AI-era data centers and electrified ports. By mounting reactors on barges moored offshore, developers argue they can deliver power directly to coastal customers behind the meter — meaning the electricity flows to the buyer without traversing the public grid — while operating under federal rather than state jurisdiction.

    The stakes are significant for California, where data center operators and port electrification programs are competing for the same constrained grid capacity, and where the state’s 1976 moratorium on new nuclear construction has effectively frozen a category of firm, low-carbon generation. Whether an offshore barge genuinely sits outside that moratorium — legally, politically, and practically — is the central question the proposal raises.

    Why Offshore, and Why Now

    The appeal is straightforward on paper. California data center demand is rising with generative AI workloads, and the state’s largest ports — Los Angeles, Long Beach, and Oakland — are under pressure to electrify cargo handling and shore power for docked ships. Both need round-the-clock electricity that solar and wind alone cannot provide without significant storage. A barge-mounted reactor delivered to a mooring can, in principle, be built in a shipyard, towed into place, and connected to a single large customer, compressing the multi-year permitting and construction timelines that plague land-based projects.

    Offshore siting also reframes the political map. State moratoria on new nuclear plants apply on land; federal waters begin three nautical miles from shore in most of California. A vessel-based reactor could plausibly be regulated primarily by federal agencies — the Nuclear Regulatory Commission and, for a marine platform, the Coast Guard — rather than the state. That is the crux of the sidestep argument, and it will be tested by lawyers long before it is tested by engineers.

    The Behind-the-Meter Economics

    Behind-the-meter power arrangements let a generator sell electricity directly to a co-located customer, bypassing utility tariffs and, often, transmission queues that now stretch years. For hyperscale data center operators, that shortcut has become the single most valuable feature of any new generation project, which is why they have signed deals for restarted nuclear plants and are exploring small modular reactors on their own campuses. An offshore barge extends the same logic to sites that lack the land for on-site generation.

    The economics still have to close. Marine nuclear platforms carry costs that land plants do not: marinization of equipment, mooring and undersea cable systems, corrosion management, and specialized crews. They also inherit the industry’s chronic problem — first-of-a-kind small reactors have consistently come in above their initial cost estimates. Whether the shipyard-build efficiencies proponents cite can offset those headwinds is unproven at commercial scale.

    Regulation, Siting, and the Politics of a Workaround

    Framing a project as a jurisdictional workaround invites the jurisdiction being worked around to push back. California has other levers even if the reactor sits in federal waters: the California Coastal Commission reviews activities affecting the coastal zone, cable landings require state and local permits, and the electricity buyer on shore is a regulated entity. A project marketed primarily as a way to avoid state law is likely to draw sharper scrutiny than one that engages the state on its merits.

    There are also legitimate questions to ask of critics as well as proponents. Opposition to nuclear in California has historically blended safety, seismic, and waste concerns with broader anti-industrial sentiment, and the coalition that upheld the 1976 moratorium is not monolithic. A fair debate requires pressing both sides: proponents on safety, security, and decommissioning of a marine reactor; opponents on what alternative firm, low-carbon supply they propose for the same coastal loads on the same timeline.

    Background

    California enacted its moratorium on new nuclear construction in 1976, tying future approvals to a federal solution for high-level radioactive waste that has not materialized. The state’s last operating commercial nuclear plant, Diablo Canyon, was scheduled to retire but received a life extension amid grid reliability concerns. Meanwhile, AI-driven data center demand and port electrification are straining coastal grid capacity.

    Interest in small modular reactors and factory-built nuclear designs has revived globally, with hyperscale technology companies signing power deals for restarted plants and exploring on-site reactors. Marine nuclear propulsion has decades of naval history, and Russia has operated a civilian floating nuclear plant since 2020, but no comparable commercial offshore reactor has been deployed in U.S. waters.

    Source: Offshore nuclear barges could power ports and data centers—starting with California, where nuclear is banned — Fortune reports on a proposal to moor small reactors offshore to serve California ports and data centers.