Enleashed gives DNSPs and system operators a real-time coordination layer that resolves local constraints through designed market logic — reducing curtailment, deferring capex, and improving hosting capacity without replacing existing infrastructure.
As DER penetration rises, managing local network constraints through after-the-fact interventions is growing faster than the networks themselves.
The most common question we receive. The answer is architectural — Enleashed fills a gap that wholesale markets were never designed to occupy.
Forward scheduling, hedging, and investment signals at the timescale of hours and the spatial resolution of regions and zones. Does not see individual feeders or real-time local conditions. Was never designed to.
Takes wholesale schedules as a given input. Observes feeder-level conditions — voltage, congestion, available flexibility — and coordinates who gets access, when, and how much. Fills the gap wholesale cannot see.
Wholesale sets the upstream boundary conditions. Enleashed operates within them. It improves wholesale market outcomes as a side effect: by shaping the demand profile wholesale dispatches against toward one that is flatter, smoother, and better aligned with renewable availability.
One sentence: Enleashed takes wholesale schedules as inputs, resolves local constraints that wholesale cannot see, and publishes bounded coordination signals that flexible devices respond to — without modifying, replacing, or competing with wholesale market mechanisms.
Today’s markets implicitly assume that if energy is bought and flexibility is procured somewhere in the system, reliability will follow. In practice, it does not. What matters at the point of use is whether a household, EV, battery, or business is served when the network is under stress.
That missing dimension is reliability: the quality of service a participant receives when local constraints bind. Today, reliability is not something customers or devices explicitly choose. It is determined indirectly by feeder conditions, procurement rules, and operational interventions they cannot see.
Enleashed makes this explicit. Instead of treating flexibility as a standalone product procured separately from the customer experience, Enleashed allows the system to coordinate around the thing that actually matters: who gets access, when, and with what priority under stress.
In other words, Enleashed turns reliability into something that can be designed, priced, and delivered — while using flexible demand and distributed assets as the mechanism for delivering it.
Today, we procure flexibility and hope it delivers reliability.
Enleashed procures reliability directly — and uses flexibility to deliver it.
A DSO procures flexibility through a separate process. At 6pm, vehicles plug in, the feeder tightens, and some charging is reduced or deferred. The intervention works physically, but the link between what was bought and who experiences reduced service is indirect and opaque.
The feeder is coordinated in real time. Charging access is allocated continuously using local scarcity, network conditions, and available flexibility. Devices respond automatically, and service quality is delivered intentionally rather than emerging accidentally from a separate procurement process.
The result: better use of flexible demand, less unnecessary procurement, lower curtailment, and a clearer path from system coordination to customer experience. This is the shift from buying flexibility as a disconnected product to delivering reliability as a designed service.
The coordination engine runs on a rolling cycle aligned to dispatch intervals. No manual intervention required.
Consumes feeder topology, voltage time series, thermal limits, congestion indices, and dynamic operating envelope profiles from DNSP systems via API. Updated each interval.
Combines instantaneous supply–demand balance, forecast conditions, and physical network signals (voltage deviation, congestion) into a composite scarcity measure — per feeder, per interval. No centralised OPF required.
Maps scarcity to bounded buy/sell prices. High scarcity attracts supply and defers flexible demand. Surplus periods recruit flexible load to absorb renewables. Signals are bounded by design.
Determines who gets access, when, and how much — with fairness memory that ensures under-served participants are prioritised in subsequent intervals. Produces auditable settlement artefacts.
The same mechanism addresses the most pressing distribution network challenges.
Convert constraint envelopes into real-time price signals. Flexible demand responds automatically, resolving congestion before it requires curtailment or manual intervention.
Surplus periods generate sell signals that recruit flexible load. Rooftop solar and battery exports are absorbed rather than curtailed. Hosting capacity increases without augmentation.
EV charging loads respond to feeder-level coordination signals rather than static time-of-use tariffs. Peak demand is managed without manual intervention or individual device control.
Enleashed is the synthesis of what existing pilots proved possible and what they left incomplete.
Distribution-level flexibility markets can operate. Gap remaining: not continuous, not feeder-native. Enleashed closes this with a continuously operating coordination kernel.
Local dynamic price signals drive coordinated behavioural response. Gap remaining: limited scope. Enleashed extends this to feeder-level multi-participant allocation.
Coordinated DER can defer augmentation. Gap remaining: allocation was rule-based. Enleashed replaces rule-based allocation with continuously operating market logic.
The mechanism is grounded in PhD research at Imperial College London. Proven convergence, bounded pricing, and fairness compatibility — not a heuristic.
"The core problem is coordination. Today's markets cannot dynamically match supply and demand at the speed and granularity required. This results in wasted clean energy, higher system costs, and slower decarbonisation — and it is solvable."Shaun Sweeney — Founder & CEO · PhD Imperial College London About the team →
We're working with DNSPs, system operators, and flexibility aggregators on initial pilot deployments. If you're managing distribution-level constraints, we want to talk.