Every grid has heard some version of this pitch before. We have a different ending — let's talk about the two doors we need to open.
Non-wires alternatives, demand response aggregation, virtual power plants, peer-to-peer energy trading — the industry has run versions of "let a private asset stand in for grid infrastructure" for over a decade. Some of it worked. Most of it stayed small.
Con Edison's Brooklyn-Queens program is the case study everyone cites for non-wires success — and it took years of bespoke, hand-built contracting to pull off once. Demand response has spent a decade fighting over whether a curtailment actually happened, or just looked like it did on paper. Peer-to-peer trading pilots generated headlines and rarely outlived their grant funding.
The common failure mode wasn't the economics. It was trust — every deal had to build its own way to prove, to a skeptical utility or regulator, that the private asset actually did what it claimed.
Renewable Energy Certificates solved a similar problem twenty years ago: how does a buyer trust that a given megawatt-hour was actually generated the way a seller claims? The answer wasn't a bespoke audit for every transaction. It was a standardized, portable registry — certified once, trusted by everyone downstream.
That's the pattern we needed all along. Not another one-off deal structure. A verification layer built once, that any deal can plug into. Let's talk about where we apply it next.
Underneath both Front-of-the-Meter Netting and Rail-Switch Capacity is the same primitive: a tamper-evident record of which duty a physical asset is performing at a given instant, cryptographically signed, time-locked against manipulation, and readable by a grid operator without having to trust the asset owner's word.
Netting uses it to prove a load and a battery are behaving as one net position, so a large customer can BYOC to mitigate their curtailment exposure while they wait for grid upgrades. Rail-Switch uses it to prove a shared battery's reserved block wasn't touched by trading, so a utility can rely on it the way it would a wire. One asset, two jobs, built around trust and verify.
Same ledger. Same proof. Two different buyers for the certainty it creates.
Every prior non-wires or demand-response program had to re-litigate trust from scratch — a new contract, a new measurement-and-verification framework, years of one-off negotiation. A certified, standardized ledger removes that step. It gets proven once, then reused by any asset, any utility, any market that adopts the standard.
That's what actually turns "a battery can do two jobs" from a case study into a category — and why the two products below are applications of one protocol, not two separate inventions.
Pairs a load and a battery so they read as one net position — shielding a large customer from individualized curtailment.
See how it works →Splits one battery's duration into a reserved utility block and a merchant block on shared physical plant.
See how it works →Join the Global Capacity Alliance, and let's scale the solution.
Join the allianceThe spine above is the whole idea. These four sections are for anyone doing real diligence — regulators, utility teams, and standards bodies who want the specifics.
Non-wires alternatives, demand response, and virtual power plants share a structural problem: each deal needed its own measurement-and-verification framework, negotiated between one utility and one developer, often taking years to design and defend. That cost doesn't shrink with scale — the hundredth deal needs almost as much bespoke trust-building as the first.
Demand response in particular has been dogged by the baseline problem: proving a resource actually reduced consumption, rather than simply claiming a favorable counterfactual, has been a recurring regulatory and legal fight for over a decade.
None of this means the underlying economics were wrong. It means the trust layer was rebuilt from scratch every time, which is expensive, slow, and resistant to standardization.
Renewable Energy Certificate registries succeeded where many other energy-attestation ideas didn't, because they separated the proof from the transaction. A generator's output is certified once into a standardized registry; every buyer downstream trusts that certification without re-verifying it themselves.
The Duty Ledger applies the same separation to duty-state instead of generation attributes: an asset's current mode is attested once, in a standard format, and any counterparty — merchant trader or regulated utility — can rely on that attestation without building its own oversight process.
Trust alone doesn't explain every past failure. Three separate problems have stalled these deals historically, and this architecture answers each one distinctly: trust — solved by the Duty Ledger's cryptographic attestation; split incentive — solved by structuring utility payment as a Reserved Capacity Agreement tied to avoided capital cost, not a vague sustainability line item; and reliability liability — solved by the hysteresis lock and asymmetric degradation ledger, which keep a dispatch-triggered obligation from ever depending on a merchant trader's judgment.
The Ledger is the unifying piece, not the only piece. It's what makes the other two mechanisms provable to a skeptical counterparty instead of just promised.
A registry only works at scale if it's certified the way the industry already certifies things it trusts: SOC 2 Type II or ISO/IEC 27001 for the integrity of the ledger operator itself, a NAESB Wholesale Electric Quadrant standard for the data format so it's portable across ISOs, and independent technical validation — the same role DNV plays for storage bankability today — for the control mechanisms that feed it.
None of that requires inventing new institutions. It requires taking the Duty Ledger through the same certification path other trusted energy infrastructure has already walked. Come walk with us.