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

Tag: open source

  • With 2,500 GW Waiting to Connect, OpenGrid Bets AI’s Power Delay Is Partly a Data Problem

    With 2,500 GW Waiting to Connect, OpenGrid Bets AI’s Power Delay Is Partly a Data Problem

    TL;DR · 30-second read

    The Short Version

    Before a new power plant or a big electricity user like a data center can plug into the grid, engineers must model what the connection would do to the network. Worldwide, projects equal to roughly 2,500 large power plants are waiting in line for that approval.

    The Linux Foundation, the nonprofit behind much of the free software the internet runs on, launched OpenGrid to help. Its argument: part of the wait comes from planning software that cannot share data, not only from a shortage of power lines.

    The Linux Foundation announced OpenGrid on October 7, 2026, at Open Source Summit Europe in Prague. OpenGrid is an open source initiative that builds a shared data and interoperability layer for electric grid planning. It includes open standards and schemas, programmatic APIs and a central hub of validated, model-ready datasets, so that the commercial and open source tools planners already use can work together. Its first flagship application, the OpenGrid Translator, is being developed for release in 2027 and is meant to move data and models between widely used commercial platforms and open source tools.

    According to the Linux Foundation’s announcement, distributed via PR Newswire, more than 2,500 gigawatts of generation, storage and large-load projects are waiting in grid connection queues worldwide. The initiative’s stated goal is for every country to have access to high-quality grid planning tools by 2030. Backers are Breakthrough Energy GRIDS, Global Grid Catalyst, Connected Grid Initiative and Google.org. Technical delivery partners are Open Energy Transition, Tapestry, TransitionZero and QXT Energy.

    Executive Summary

    OpenGrid does not build a new grid planning program. It builds the plumbing between existing ones: common data formats, connectors and a validated data repository. The Linux Foundation describes grid planning as a critical bottleneck as electricity demand rises, new industrial and data center loads come online, and more generation and storage projects request connection. It says that planning is constrained by fragmented data, incompatible software, and modeling capabilities that many institutions and countries cannot access.

    This matters for data center infrastructure because a large new load cannot energize until the utility or grid operator has studied it. Those studies run on network models. If the models are slow to assemble, hard to exchange or impossible for outside parties to check, every project in the queue waits longer. OpenGrid is betting that a shared, neutral data layer can reduce that friction. The announcement does not quantify how much time it expects to save, and software alone does not build the transmission lines the grid still needs.

    Why a Data Center’s Power Date Runs Through Someone Else’s Model

    The 2,500-gigawatt figure explains the mechanism behind this launch. It counts generation, storage and large loads such as data centers waiting for permission to connect. Each of those requests ultimately has to be represented in a grid model: a digital description of lines, transformers, substations and power flows that engineers use to test whether the network can absorb the new project safely. When a developer asks for hundreds of megawatts for an AI campus, the answer depends on that modeling work, and so does any list of upgrades the developer may be asked to fund.

    The release locates part of the delay in the modeling workflow itself. TransitionZero chief executive Matt Gray says that building the company’s own modeling software showed it “how much time is lost” moving data and models between formats. ESIG executive director Debbie Lew points to the need to integrate economic planning tools with reliability tools, and transmission planning (high-voltage, long-distance lines) with distribution planning (local networks). Each handoff between incompatible tools means manual conversion, re-validation and the risk of error. That is the friction OpenGrid’s Translator, schemas and data hub are designed to remove.

    The people affected sit on both sides of the queue. Utilities and system operators would get faster model exchange. Regulators and other stakeholders, in Alice Yake’s words, would gain the ability to examine “data that others cannot verify” today. Developers of data centers and generation would benefit indirectly if studies move faster or are disputed less. The claim is a modest one, and fairly stated: data friction is one contributor to the wait, not its single cause.

    A Translator, Not a Replacement

    The most consequential design choice is what OpenGrid says it will not do. It does not try to replace the commercial grid planning software that utilities and operators depend on. It offers a neutral layer that lets commercial and open source tools interoperate. That lowers the adoption barrier considerably. A planning department does not have to abandon validated workflows, retrain staff or re-certify methods to benefit. It can export a model, translate it and test it elsewhere.

    That approach mirrors how the Linux Foundation’s better-known projects gained traction: by standardising the layer underneath competing products rather than competing with them. The analogy has limits, though. Grid planning tools are a narrower, more specialised market than cloud software, and the value of a translator depends on how faithfully it handles proprietary formats. Karin Wadsack of the Global Power System Transformation Consortium frames neutral governance as a guard against vendor lock-in, meaning dependence on a single supplier. Whether incumbent vendors treat that as an opportunity or a threat will shape how useful the Translator becomes.

    The timeline is also worth noting. The Translator is targeted for 2027, and later additions are framed as future expansion: open solvers (the computational engines that run the simulations), no-code graphical interfaces, standardised planning workflows and AI-assisted data preparation. The present launch is a governance structure and a roadmap, not a shipping product.

    What Software Cannot Shorten

    The release’s own figures show the limits of a data-layer fix. It says annual grid infrastructure investment needs to roughly double to more than $600 billion by 2030, and that 80 million kilometres of power lines must be added or replaced by 2040. Faster, more transparent planning can help decide which lines to build and where, but it does not manufacture transformers, secure rights-of-way or finance construction. For a data center developer, a quicker study that concludes a major transmission upgrade is required still leaves a long wait for that upgrade.

    The global framing points to where OpenGrid may matter most. The release says emerging economies are expected to account for nearly 80 percent of global electricity demand growth through 2030, and that access to modern planning capabilities is especially uneven in fast-growing markets. In places where planning teams lack expensive licensed software or clean network data, open tools and validated datasets could change what is possible, not just make it a little faster. For operators siting AI and cloud capacity in those markets, the credibility of national grid plans directly affects where power can be promised.

    Background

    The Linux Foundation is a nonprofit that hosts open source projects including Linux, Kubernetes, PyTorch, RISC-V and the Model Context Protocol. Its model is to provide neutral governance so that competitors can jointly maintain shared technology. OpenGrid applies that model to electric grid planning, where utilities, grid operators and regulators rely on specialised software to simulate how networks behave as new generation and demand are added.

    Grid planning has become a pressure point as electrification, industrial growth and data center construction raise demand while large volumes of solar, wind and storage projects seek connection. Because planning tools often use different, sometimes proprietary data formats, moving a network model between organisations or programs can require significant manual work. That is the interoperability gap OpenGrid is designed to close.

    Sources

    Source: Linux Foundation lanza OpenGrid para crear una infraestructura para la red eléctrica mundial, the Linux Foundation’s announcement of the OpenGrid open source grid-planning initiative, also issued in English as Linux Foundation Launches OpenGrid to Build Open, Shared Infrastructure for the World’s Electric Grid.

  • Gold Eagle’s 4-Agency Clearinghouse Shows AI Bug-Finding Now Needs a Triage Desk

    Gold Eagle’s 4-Agency Clearinghouse Shows AI Bug-Finding Now Needs a Triage Desk

    TL;DR · 30-second read

    The Short Version

    The White House has set up a central office, called Gold Eagle, where government agencies and the companies that run essential services like power, water and communications networks can pool security weaknesses that artificial intelligence finds in software.

    Why it matters: artificial intelligence can now search huge amounts of software for weak spots, and different groups often find the same ones. Gold Eagle is meant to sort that pile, drop the duplicates and tell defenders what to fix first. Taking part is voluntary.

    On July 14, 2026, the White House announced Gold Eagle, a federal clearinghouse for sharing AI-derived cybersecurity vulnerability information between government agencies, “American critical infrastructure companies” and “open-source software partners,” Covington & Burling’s Inside Privacy blog reported. The clearinghouse was established under Executive Order 14409, “Promoting Advanced Artificial Intelligence Innovation and Security,” which directed the Secretary of the Treasury to form it in consultation with the National Cyber Director, the National Security Agency (NSA) and the Cybersecurity and Infrastructure Security Agency (CISA).

    According to the White House, Gold Eagle has already begun intake and prioritization of vulnerabilities “from across industries and sectors” and is coordinating “scanning verifications.” A day later, on July 15, CISA, the NSA and cyber agencies from the United Kingdom, the Netherlands and Japan issued joint guidance on coordinated vulnerability disclosure.

    Executive Summary

    Gold Eagle is a coordination body, not a scanning tool. Its stated purpose is to “leverage frontier AI capabilities to continue advancing faster than adversaries, reduce duplicative scanning efforts, and deliver prioritized and actionable threat and remediation information to defenders across the federal government and the private sector.” In practice, that means taking in software flaws surfaced by advanced AI models, verifying them, removing duplicates and handing defenders a ranked list of what to fix.

    The design matters because it signals where the government sees the problem. If AI has made finding vulnerabilities cheap and fast, the scarce resources become verification, prioritization and repair. For operators of critical infrastructure, including the data centers, network carriers and cloud platforms other sectors depend on, the practical question shifts from “what is vulnerable?” to “how quickly can we act on an authoritative must-fix list?”

    Participation is voluntary, and key operating details, including who has joined, how findings are protected and how quickly they are disclosed, had not been made public as of the announcement.

    Why AI Bug-Hunting Needs a Triage Desk

    Gold Eagle’s job, as described, is not to find vulnerabilities but to sort them. Executive Order 14409 structures it around four federal players, with Treasury leading in consultation with the National Cyber Director, the NSA and CISA, and tasks them to “coordinate and deconflict” the identification and remediation of software flaws. Deconflict is the telling word: it is what you do when many parties are working the same terrain and getting in each other’s way. The White House’s own framing, reducing “duplicative scanning efforts” and delivering “prioritized” information, points the same direction.

    The mechanism is straightforward. Frontier AI models, the most capable general-purpose systems from leading labs, can be pointed at large bodies of code and return candidate vulnerabilities in volume. When AI developers, agencies, security firms and independent researchers all scan the same widely used libraries, the same flaw can surface repeatedly, and every report lands on a maintainer or operator who has to check whether it is real. A clearinghouse that verifies once, collapses duplicates and ranks by severity turns a flood of raw findings into an ordered queue. The “scanning verifications” the White House says Gold Eagle is already coordinating are exactly that step.

    For critical infrastructure operators, the consequence is that the constraint moves downstream. A ranked advisory is only useful if the recipient can act on it: test a patch, book a maintenance window, push a firmware update (the low-level software built into hardware) to equipment that cannot simply be switched off. Gold Eagle can shorten the path from discovery to a prioritized warning; it cannot shorten an operator’s change-control process. The organizations that gain most will be those whose patching pipelines can absorb a faster, more authoritative stream of must-fix items. Those running always-on facilities with long approval cycles will feel the gap between knowing and fixing most sharply.

    Open-Source Maintainers Are the Pressure Point

    The announcement names “open-source software partners” alongside agencies and critical infrastructure companies, and that inclusion is significant. Much of the software running in data centers, telecom networks and industrial control systems is built on open-source components, freely available code often maintained by small teams or volunteers. If AI-driven scanning multiplies the number of credible reports, those maintainers carry the verification and repair burden before any operator can deploy a fix.

    The July 15 guidance addresses the other side of that exchange. CISA, the NSA, the UK’s National Cyber Security Centre, the Netherlands’ National Cyber Security Centre and Japan’s computer emergency response coordination center, five agencies from four countries, set out best practices for coordinated vulnerability disclosure: reporting a flaw privately to whoever can fix it and publishing details once a fix exists or an agreed deadline passes. The guidance urges software makers and online service providers to adopt transparent processes for receiving, evaluating and remediating reports. Read together, the two moves work both ends of the pipe: centralize intake of AI-found flaws, and press software producers to have a working front door ready when those findings arrive.

    Voluntary by Design, Concentrated by Nature

    Gold Eagle rests on voluntary collaboration with the AI industry and critical infrastructure operators, so its value will track who joins and how much they share. Information-sharing programs have long had to address the same hesitations: legal exposure, competitive sensitivity and the reputational cost of disclosing one’s own weaknesses. A new clearinghouse inherits those questions, and its early participation will be the clearest indicator of whether industry sees it as useful.

    A central store of verified, prioritized and not-yet-fixed vulnerabilities affecting critical infrastructure is also, by its nature, a high-value target. That is not an argument against the model, since coordination usually requires some concentration of information. But it makes the clearinghouse’s own security, access controls and disclosure timelines material design questions rather than administrative details, particularly for operators deciding whether to contribute findings about their own systems.

    Background

    The federal government has long encouraged private-sector sharing of cyber threat and vulnerability information, with CISA, part of the Department of Homeland Security, serving as the main civilian coordinator and the NSA contributing on the national security side. Critical infrastructure covers the systems society depends on, including energy, water, communications and information technology, which in turn rely on the data centers and networks that carry their traffic.

    The rise of highly capable AI models has changed the economics of finding software flaws: automated systems can now analyze large codebases at a scale that manual review cannot match. Gold Eagle, created under Executive Order 14409, is the Administration’s latest action on AI-enabled cybersecurity and an attempt to channel that capacity into a single, prioritized stream for defenders.

    Sources

    Source: White House Launches “Gold Eagle” AI Cybersecurity Clearinghouse, Inside Privacy (Covington & Burling), on the White House’s launch of a federal clearinghouse for AI-derived vulnerability information under EO 14409.

  • DeepSeek Open-Sources DSpark, Claiming Up to 85% Faster LLM Inference

    DeepSeek Open-Sources DSpark, Claiming Up to 85% Faster LLM Inference

    DeepSeek, the Hangzhou-based AI lab known for its unusually efficient open-weight models, has released DSpark, an open-source framework that it says can accelerate large language model (LLM) inference — the process of actually running a trained model to answer queries — by up to 85%, according to a VentureBeat report published June 28, 2026.

    The release continues DeepSeek’s pattern of publishing its internal efficiency tooling openly rather than keeping it proprietary, and lands at a moment when inference, not training, has become the dominant cost line for companies serving AI at scale.

    Executive Summary

    The announcement is straightforward on its face: DSpark is an inference framework, it is open source, and the headline claim is a speedup of “up to 85%.” What makes it noteworthy is who is making the claim. DeepSeek built its reputation on doing more with less — its earlier model releases were credited with achieving frontier-class results at a fraction of the compute budgets reported by Western rivals — so an efficiency claim from this lab gets taken more seriously than the average vendor benchmark.

    If the speedup holds up under independent testing, the implications run well beyond one company’s software stack. Inference speed translates almost directly into serving cost: a model that answers queries faster on the same hardware serves more users per GPU, which means fewer GPUs, less power, and less data center capacity per unit of AI demand. Because DSpark is open source, any operator — hyperscaler, neocloud, or enterprise running models in-house — can in principle adopt it without a licensing negotiation.

    The important caveat is that “up to 85%” is a ceiling, not an average, and the report available at publication does not detail the workloads, models, or hardware behind the number. That distinction should shape how buyers and investors read the news.

    Inference Is Where the Money Now Goes

    For the first years of the generative AI boom, the eye-watering costs were in training — the one-time process of teaching a model from massive datasets. That has flipped. Once hundreds of millions of people are querying models daily, the recurring cost of inference dwarfs the one-time cost of training, and it scales with every new user and every longer conversation. This is why the industry’s optimization energy has shifted to serving: techniques with names like speculative decoding, quantization, and KV-cache management all exist to squeeze more answers out of each GPU-hour.

    An 85% speedup, if achieved on realistic workloads, is not an incremental gain in this context. Serving capacity is the binding constraint for many AI providers, and GPUs remain supply-limited and expensive. Software that meaningfully raises throughput per chip is functionally equivalent to manufacturing more chips — without the fab, the lead time, or the export-control exposure that hardware carries.

    DeepSeek’s Open-Source Playbook, Continued

    DeepSeek has a track record here. The lab, spun out of the Chinese quantitative hedge fund High-Flyer, shook global markets in early 2025 when its R1 reasoning model demonstrated that frontier-adjacent capability did not require frontier-scale budgets. It followed up by open-sourcing chunks of its internal infrastructure code — low-level GPU kernels and communication libraries — rather than treating them as trade secrets. DSpark fits that pattern: release the tooling, let the ecosystem adopt it, and compete on the pace of research rather than on locked-down software.

    The strategic logic is worth spelling out. Open-sourcing inference tooling commoditizes the serving layer, which pressures companies whose business model depends on proprietary serving efficiency, while costing DeepSeek little — its own advantage lies upstream, in model quality and training efficiency. It also builds developer mindshare globally at a time when Chinese AI labs face restricted access to top-end accelerators, making software efficiency a competitive necessity as much as a virtue.

    What Cheaper Inference Means for Infrastructure Operators

    A natural first read is that faster inference is bearish for GPU and data center demand: if each chip does 85% more work, you need fewer chips and fewer megawatts. History suggests the opposite usually happens. Efficiency gains in computing have repeatedly triggered what economists call the Jevons paradox — when something gets cheaper, consumption expands enough to more than offset the savings. Cheaper inference makes previously uneconomic AI applications viable: always-on agents, AI in low-margin consumer products, long-context document processing at scale.

    For data center operators and connectivity providers, the more defensible conclusion is that efficiency software shifts demand rather than shrinking it. Lower serving costs favor deployment breadth — more applications, more regions, more inference happening closer to users — which tends to benefit distributed capacity and network infrastructure even if it moderates the growth rate of any single mega-campus. Operators planning around raw GPU scarcity should note that the scarcity premium softens every time the software stack gets meaningfully better.

    Reading an ‘Up To’ Claim Responsibly

    The 85% figure deserves the same scrutiny any vendor benchmark gets, and the fact that DSpark is open source cuts in its favor: the code can be tested independently, which is more than can be said for closed serving stacks making similar claims. Still, inference speedups are notoriously workload-dependent. Gains that appear on one batch size, sequence length, or model architecture can shrink dramatically on another, and the report available at publication does not specify the conditions behind the headline number.

    The practical test is adoption. The inference-serving field already has entrenched open-source incumbents — frameworks like vLLM and NVIDIA’s TensorRT-LLM ecosystem have large communities and production track records. DSpark’s real-world impact will be measured not by its launch benchmark but by whether major serving operations fold it, or its techniques, into production over the following quarters. DeepSeek’s prior open-source releases were rapidly picked apart and partially absorbed by the community; that is the most likely path here too, even if the framework itself does not displace incumbents wholesale.

    Background

    DeepSeek emerged from High-Flyer, a Chinese quantitative hedge fund, and stunned the AI industry in January 2025 when its R1 model matched much of the reasoning performance of leading Western systems at a reported fraction of the training cost — an announcement that briefly wiped hundreds of billions of dollars from AI-linked stocks as investors reassessed how much compute frontier AI truly requires. The lab has since maintained a strategy of releasing open-weight models and open-source infrastructure tooling, positioning efficiency as its core identity.

    The inference-serving market it is now entering more forcefully has its own history: open-source frameworks such as vLLM (from UC Berkeley researchers) and NVIDIA’s TensorRT-LLM became the workhorses of production LLM serving as the industry’s cost center shifted from training models to running them for hundreds of millions of users. Every meaningful gain in serving efficiency ripples outward into GPU procurement, data center planning, and the unit economics of AI products.

    Source: DeepSeek open sources DSpark, a new framework to speed up LLM inference by up to 85% — VentureBeat, reporting DeepSeek’s open-source release of its DSpark inference-acceleration framework, June 28, 2026.