Demand Response Aggregator Software & Platform: Architecture, FERC 2222 & Aggregation Business Models
The demand response aggregator market is projected to grow from $2.85 billion in 2024 to $8.44 billion by 2033 — a 14.2% compound annual growth rate, according to Dataintelo’s market analysis. That is not speculative venture capital enthusiasm. That is the arithmetic of grid operators who need flexibility faster than they can build transmission lines, and distributed energy resources that can deliver it.
The opportunity exists because flexibility has become the critical commodity. Data centers, EV adoption, and building electrification are adding load faster than utilities can expand generation and transmission infrastructure. Meanwhile, FERC Order 2222 has mandated that wholesale markets open to aggregated distributed energy resources — meaning a demand response aggregator with 50 MW of enrolled commercial HVAC systems competes on equal footing with a 50 MW peaking plant.
For companies building or operating aggregation businesses, the question is straightforward: how do you capture value in this expanding market? The answer lies in understanding the revenue mechanics — and building technology platforms capable of executing on them.
Revenue Streams: How Aggregators Get Paid
Aggregators generate revenue through four primary channels. Each has different risk profiles, payment timing, and technical requirements. The most successful demand response providers participate across multiple streams simultaneously.
Capacity Payments
Capacity markets compensate resources for availability — the commitment to reduce load when called by the grid operator. PJM, ISO-NE, and NYISO all operate capacity markets where demand response competes directly with generation. Payments are structured as dollars per kilowatt-year, creating predictable recurring revenue.
The catch: performance requirements are strict. Fail to deliver the committed load reduction during a capacity event, and penalties can exceed the original payment. Energy aggregators who enroll resources without the technology to guarantee performance often discover that capacity markets punish unreliability severely.
Energy Market Arbitrage
Energy markets allow aggregators to dispatch enrolled resources based on wholesale price signals. When real-time prices spike — due to demand peaks, transmission congestion, or generation scarcity — aggregators reduce load and capture the spread between the wholesale price and any customer incentive payments.
This revenue stream is variable but can be substantial. A single high-price event during a summer heat wave can generate more revenue than months of capacity payments. The challenge is building dispatch systems fast enough to capture short-duration price spikes.
Ancillary Services
Frequency regulation, spinning reserves, and non-spinning reserves offer premium compensation for resources capable of fast response. These markets require automated, sub-minute control — a thermostat that takes 15 minutes to respond cannot participate in frequency regulation markets that settle in four-second intervals.
The barrier to entry is technical: virtual power plant software must translate grid operator signals into device-level commands within seconds, aggregate responses across thousands of endpoints, and report telemetry back to the market operator in real time.
Local Flexibility Markets
The EU Network Code on Demand Response, proposed by ACER in March 2025, mandates Local Flexibility Markets across member states. These markets compensate resources for relieving distribution-level constraints — voltage management, congestion relief, and local balancing. As distribution grids absorb more rooftop solar, EVs, and heat pumps, local flexibility becomes increasingly valuable.
For aggregators operating in Europe, local flexibility represents a new revenue layer that did not exist five years ago. For those operating globally, it signals where North American markets are likely headed.
| Revenue Stream | Payment Structure | Risk Profile | Technical Requirement |
|---|---|---|---|
| Capacity Payments | Recurring: $/kW-year for availability commitment. Predictable, contract-based. | Moderate: Reliable revenue, but performance penalties can exceed original payment if load reduction fails. | Enrollment & verification: Must prove committed capacity is available and deliverable when called. |
| Energy Arbitrage | Event-based: Captures spread between wholesale price and curtailment cost during spikes. | Variable: Highly dependent on price volatility. Single summer event can exceed months of capacity revenue. | Real-time dispatch: Systems must detect and respond to short-duration price spikes within minutes. |
| Ancillary Services | Premium rates: Frequency regulation, spinning/non-spinning reserves. Highest per-MW compensation. | Low volume, high value: Requires meeting strict response time thresholds (seconds, not minutes). | Sub-minute automation: Automated, sub-second device control and real-time telemetry reporting. |
| Local Flexibility | Emerging: Distribution-level constraint relief. EU Network Code mandates markets by 2027. | Growing: New revenue layer; market structure still forming in most jurisdictions. | EU compliance: Requires distribution-level visibility and coordination with local grid operators. |
FERC Order 2222 & DER Aggregation: The Regulatory Engine Behind the Market
FERC Order 2222, issued in September 2020, is the regulatory decision that made the modern demand response aggregator business viable at scale. The order directs every US regional transmission organization (RTO) and independent system operator (ISO) to allow distributed energy resources to participate in wholesale capacity, energy, and ancillary services markets — explicitly through aggregation.
Before Order 2222, an individual commercial building with 500 kW of flexible load was too small to participate in PJM’s capacity market, ERCOT’s reserves, or NYISO’s ancillary services. Aggregation was allowed in some markets for some products, but the rules were inconsistent and market design treated DERs as second-class participants. Order 2222 removed that distinction. A 100 MW aggregated portfolio of commercial HVAC, industrial process loads, battery storage, and residential demand flexibility now has the same wholesale market rights as a natural-gas peaker.
What Order 2222 Actually Requires
- Market eligibility: RTOs must allow DER aggregations to participate in any wholesale market product for which the aggregation is technically capable
- Minimum size: The minimum aggregation size is capped at 100 kW — small enough that commercial and industrial aggregators can build viable portfolios
- Distribution coordination: Aggregators must coordinate with the local distribution utility before dispatching resources, to prevent grid-level conflicts
- Metering and telemetry: Aggregations must provide market-grade metering and real-time telemetry on the same terms as conventional resources
- Double-counting prohibition: Resources cannot simultaneously earn wholesale market compensation and retail-level compensation for the same service from the same load reduction
ISO/RTO Implementation Status
Implementation varies by market. PJM, the largest US capacity market, filed its compliance plan and has begun onboarding DER aggregations through its Automated Demand Response and Capacity Performance programs. CAISO has operated DER aggregation rules since 2016 but is expanding them to meet the Order 2222 minimum standards. NYISO has approved its DER participation model and is onboarding qualified aggregators. ERCOT is not a FERC-jurisdictional market, but Texas is running parallel work through the ERCOT-ADER (Aggregated Distributed Energy Resources) task force, targeting equivalent outcomes via Texas PUC directives.
The implication for aggregator software is significant. Each ISO has slightly different rules on bidding, metering, telemetry cadence, and settlement — so an aggregator’s platform must support multiple market-specific workflows simultaneously. A DR aggregator building only for PJM will run into costly rework when expanding into CAISO or NYISO. This is the single biggest argument for building aggregator platforms around a market-abstracted core rather than a single-ISO implementation.
Multi-Market Participation: Revenue Stacking
Single-market participation leaves money on the table. An aggregator enrolled only in capacity markets forfeits energy arbitrage during price spikes. One focused solely on wholesale markets misses capacity payments during the 90% of hours when prices are stable.
The aggregators capturing the most value per enrolled megawatt are those with technology platforms capable of simultaneous multi-market participation. This requires optimizing dispatch decisions in real time based on which revenue stream offers the highest return at any given moment — a complex algorithmic problem that separates scalable businesses from constrained ones.
Consider a UK-based demand response aggregator operating across grid balancing services. With 2,000 sites connected and 3 billion data points processed, the platform handles 1,000 requests per second to coordinate real-time dispatch across capacity, energy, and ancillary markets. That throughput enables revenue stacking that would be impossible with manual operations or less capable technology.
For organizations building aggregation capabilities, the technology architecture matters as much as the commercial relationships. Codibly’s work with optimizers and aggregators demonstrates how platform design enables the multi-market participation that drives aggregator economics.
Technology Stack for Aggregator Success
The demand response business model depends on technology that most aggregators underestimate when entering the market. Four capabilities separate scalable platforms from constrained ones.
For a named-vendor view of how these four capabilities map to the DRMS, VPP, and cloud-native platforms aggregators actually evaluate — and where the four vendor archetypes diverge on protocol depth, ISO connectors, and FERC 2222 readiness — see our Demand Response Companies: 2026 Buyer’s Guide.
Demand Response Management System (DRMS)
The core platform must manage resource enrollment, dispatch scheduling, performance verification, and settlement calculation across thousands or millions of endpoints. Building this from scratch takes 18-24 months. Most successful aggregators either acquire DRMS capabilities or partner with technology providers who specialize in the domain.
Protocol Compliance
Market participation requires speaking the languages that utilities and grid operators mandate. OpenADR for utility-to-aggregator signaling. IEEE 2030.5 for inverter and battery communication. CTA-2045 for device-level appliance control. Each protocol requires distinct implementation, testing, and certification — complexity that creates barriers to entry but also competitive moats for those who navigate it.
A European VPP provider demonstrated this integration challenge when building energy market automation across Polish, Czech, and Hungarian markets. The platform required WIRE, OTE, and HUPX integrations — three different market operator systems with distinct APIs, settlement rules, and reporting requirements. The energy market automation case study illustrates the technical depth required.
Multi-Tenant Architecture
Demand response companies serving multiple utility or enterprise clients need platform architecture that isolates customer data while sharing underlying infrastructure costs. Multi-tenancy is straightforward in theory but complex in practice — especially when different clients have different protocol requirements, market participation rules, and settlement structures.
Real-Time Control
Revenue stacking requires sub-minute dispatch capability. Ancillary service markets settle in intervals measured in seconds, not hours. Platforms designed for day-ahead scheduling cannot capture the premium revenue available in real-time markets.
| Capability | What It Does | Build Timeline | Why It Matters |
|---|---|---|---|
| DRMS Platform | Core operations: Resource enrollment, dispatch scheduling, performance verification, settlement calculation. | 18–24 months from scratch. | Without a DRMS, aggregators cannot manage resources at scale or prove performance to market operators. |
| Protocol Compliance | Market language: OpenADR (utility signaling), IEEE 2030.5 (DER communication), CTA-2045 (appliance control). | 12–18 months per protocol from scratch; 6–8 weeks with accelerators. | Protocol certification is the gate to utility programs and aggregator partnerships. No certification = no market. |
| Multi-Tenant Architecture | Client isolation: Separate data, protocol configs, and settlement rules per utility or enterprise client. | 6–12 months to architect properly. | Aggregators serving multiple utilities need per-client isolation without duplicating infrastructure costs. |
| Real-Time Control | Sub-minute dispatch: Translates grid operator signals into device commands within seconds. | Ongoing engineering investment. | Revenue stacking into ancillary services is impossible without sub-second dispatch and telemetry. |
Demand Response Aggregator Software & Platform Architecture
Aggregator economics scale with software. A portfolio of 100 MW earns similar revenue whether it’s dispatched manually or algorithmically — but the manual operation costs ten times more to run, responds minutes slower, and cannot stack revenue streams across day-ahead, real-time, and ancillary markets. The difference between aggregators that scale profitably and those that stall at a few sites is almost always the platform underneath. Here’s how a production-grade demand response aggregator software platform is structured.
DER Onboarding & Telemetry Layer
Every DER joining the aggregation — commercial HVAC, industrial process, battery storage, EV charger, residential thermostat, solar inverter — must be registered, metered, and continuously monitored. This layer handles device discovery, telemetry normalization (1-second to 15-minute cadence depending on market rules), meter data validation, and baseline establishment for settlement. For industrial facilities and commercial buildings, this often integrates directly with the customer’s BAS or SCADA system via BACnet, Modbus, or OpenADR VEN flows.
Forecasting & Portfolio Optimization
A DR aggregator cannot bid into a wholesale market without a reasonable forecast of how much load reduction each asset can deliver at each hour. The forecasting layer combines historical load patterns, weather data, market prices, and asset-specific constraints (comfort deadbands on HVAC, process lockouts on industrial loads) to produce hourly capability forecasts per asset. The optimization engine then assembles those forecasts into a portfolio bid that maximizes expected revenue across the ISO’s day-ahead, real-time, and ancillary markets — accounting for the correlations between assets so the portfolio is not overcommitted during a single dispatch event.
Market Interface & Bidding
Every ISO has a different market-facing API for DER aggregation bids. PJM uses Markets Gateway and eSuite, CAISO uses SIBR and OMS, NYISO uses its DER participation portal, and ERCOT-ADER has its own market registration flow. The market interface layer of the platform must translate the portfolio optimization output into each ISO’s specific bid format, manage offer submission windows, and handle the exception flows (curtailment, forced dispatch, missed bids) that each market handles differently. For aggregators operating in multiple markets simultaneously, this layer is the single biggest source of engineering complexity — and the first place a poorly designed platform shows its limits.
Dispatch, Control & Verification
When the ISO issues a dispatch instruction, the aggregator has seconds to minutes to respond, depending on the product. The control layer fans out dispatch signals to individual DERs, typically through OpenADR 2.0b, OpenADR 3.0, or direct control APIs for BACnet/Modbus integrations. Verification runs in parallel: every 5 seconds to 15 minutes, the platform measures the actual load reduction against the baseline and assembles the settlement data the market needs to pay out. If verification fails, the aggregator loses payment on that dispatch — sometimes the capacity payment for an entire season.
Settlement & Revenue Allocation
The platform receives ISO settlement statements, reconciles them against internal dispatch and verification data, and allocates revenue back to individual DER owners according to the contracts in place — capacity payments, performance bonuses, commissions, and pass-through payments. This is where most bespoke aggregator platforms break: the revenue allocation logic for a portfolio of 500 commercial buildings, 30 industrial facilities, and 50,000 residential thermostats is a multi-tenant billing problem, not a simple ledger. A production platform treats settlement as a first-class subsystem with audit trails, dispute handling, and multi-currency support for aggregators operating across Europe and North America.
Industrial and commercial customers asking “who builds the software?” are the ones most in need of this architecture. Residential DR aggregators can often get by with a simpler stack. But for aggregators serving industrial facilities — where each asset is worth 5–20 MW, each dispatch is tracked individually by the ISO, and settlement disputes have seven-figure consequences — the platform architecture above is not optional.
Demand Response Aggregator Economics Start with Platform
The demand response aggregator market will nearly triple over the next decade. Capturing that value requires more than customer enrollment and utility relationships — it requires technology platforms capable of multi-market revenue stacking, sub-second dispatch control, and protocol compliance across fragmented standards.
The barriers are real but navigable. Organizations that invest in scalable DRMS platforms, achieve protocol certification, and build multi-market dispatch capabilities will define the aggregation market. Those that treat technology as an afterthought will find their margins compressed by competitors who engineered for scale from the start.
For aggregators evaluating build-versus-buy decisions for their technology stack, demand response program integration services offer a path to market participation without the 18-24 month timeline of internal development.
For a broader view of the demand response software vendor landscape — DRMS platforms, DR/VPP specialists, cloud-native platforms, and accelerator-plus-custom approaches — see our demand response software buyer’s guide.
Frequently Asked Questions
Demand aggregation is the business of enrolling multiple distributed energy resources — commercial buildings, industrial facilities, residential devices, battery storage systems — and presenting their combined load flexibility to grid operators and electricity markets as a single dispatchable resource. Aggregators serve as intermediaries between individual assets (too small to participate directly in wholesale markets) and the grid operators who need megawatt-scale flexibility. FERC Order 2222 mandates that aggregated resources receive market access equivalent to traditional generation.
Demand response providers receive compensation through four primary channels: capacity payments (recurring fees for availability, typically $/kW-year), energy market payments (compensation based on wholesale price differentials during dispatch events), ancillary service payments (premium rates for fast-response services like frequency regulation), and local flexibility payments (compensation for distribution-level grid services, primarily in European markets). Most aggregators take a commission on customer payments — typically 10-30% — while some operate on performance-based contracts where revenue depends on actual load reductions delivered.
Utility demand response programs are owned and operated by the utility itself — the utility enrolls customers, dispatches resources, and captures the grid benefit directly. Aggregators are third-party companies that compete with utility programs for customer enrollment. FERC Order 2222 ensures aggregators can participate in wholesale markets even if the local utility operates competing programs. From a customer perspective, aggregators often offer faster enrollment, more sophisticated technology, and better incentive structures than utility programs — though utilities have the advantage of existing customer relationships and billing integration.
A demand response aggregator needs a platform that handles five core functions: DER onboarding and telemetry (registering devices and collecting real-time meter data), portfolio forecasting and bid optimization (predicting load reduction capability and assembling market offers), ISO market interfaces (PJM Markets Gateway, CAISO SIBR, NYISO DER portal, ERCOT-ADER), dispatch and control (fanning out commands via OpenADR or direct device APIs), and settlement with revenue allocation (reconciling ISO statements and paying out individual DER owners). A production aggregator platform handles all five as integrated services — bolt-together point solutions hit scaling limits at 50-100 MW of managed capacity.
DR aggregators serving industrial facilities operate differently from residential or small commercial programs. Industrial customers have 1-20 MW of controllable load per site, process constraints that limit when and how much load can be shed, and existing automation systems (BAS, SCADA, PLCs) that the aggregator must integrate with. A typical engagement includes a site assessment to characterize flexible loads and constraints, installation of market-grade metering, integration with the facility’s control system via OpenADR 2.0b or direct protocol (BACnet, Modbus), and ongoing revenue sharing that reflects the specific market products the facility participates in. Industrial aggregation often has higher per-megawatt compliance costs than residential programs — which is why the economics only work above roughly 5 MW per site.
FERC Order 2222 is a US federal regulatory directive issued in September 2020 that requires every FERC-jurisdictional RTO and ISO to allow distributed energy resource aggregations to participate in wholesale electricity markets. Before the order, DER aggregations faced inconsistent rules and were often excluded from key market products. After the order, an aggregated portfolio of at least 100 kW has the same rights as a conventional generator — it can bid into capacity, energy, ancillary services, and reserve markets on equal terms. For DR aggregators, the practical impact is significant: new revenue streams in PJM, CAISO, NYISO, and MISO that were previously closed, plus regulatory pressure on ERCOT to implement equivalent rules via the ADER task force.