Virtual power plant software for aggregators and energy cooperatives
Virtual power plant software for aggregators, built in layers. The demand response module for Zeronest splits a call across metering points and reports each call hour 15 minutes after it ends. It runs in production. Cooperative settlement is built; Global Green orchestration is in development.
Tell us what your portfolio needs.
Send us your asset list and the markets you bid into, and we will bring the right engineers to the first call.
Custom virtual power plant software, built layer by layer
Virtual power plant software is the portfolio and market layer that turns many metering points, batteries and solar sites into one resource an aggregator can sell. For an aggregator the stake is concrete: in the Polish capacity market a failed DSR test costs the capacity payment and a penalty. We build the software layer by layer, as part of our energy software development work. Zeronest has an energy platform with a demand response module for aggregators and a separate settlement module for energy cooperatives, and we build its software. For Global Green, an operator of solar and battery storage sites, we build battery orchestration.
Buy a ready-made platform when your assets, markets and settlement rules match what the vendor supports. Build or extend your own when the rules you work under are local, such as Polish demand response (DSR) programmes or energy cooperative settlement, when you already run an energy management system (EMS) or a settlement system you want to keep, or when the platform is itself the product you sell.
Control of a single site or battery belongs to the energy management system. Buying and selling energy belongs to an energy trading platform.
How does demand response software split a call across metering points?
An aggregator creates one call across many metering points, and the module gives every point its own declared power and asks clients for slightly more than the call orders. A 5 MW call can require 5.25 MW from clients. The buffer makes the allocation safer: the call can still be delivered if some points deliver less than they declared. The API rejects a call whose total does not match the limit and the buffer, and splits power into whole kW, so a call cannot go out with numbers that do not add up.
Participants get an SMS and an e-mail with a confirmation link, and ten minutes after a call is created the operator gets a list of SMS messages that did not go out. In demand response, the baseline is the consumption a point would have had without the call, and it is corrected from the hours just before the call. The report for a call hour is ready 15 minutes after it ends, so a call from 14:00 to 15:00 is reported at 15:15. The call limit in the report is the sum of the points' limits.
In the Polish capacity market, PSE, the Polish transmission system operator, announces DSR call periods at least 8 hours in advance.
- Metering points grouped into aggregation units
- Unavailability notices for each point and each unit
- Operator sees all installations, client only its own, consultant acts for either
- A client sharing a call sees only the combined power of its own points
Energy cooperative software: hourly settlement for members
Energy cooperative software calculates, hour by hour, what each member and the cooperative as a whole owe and are owed. We built the energy cooperative module for Zeronest in 2026. It settles the group and each metering point and splits the energy of every hour into three streams: used by members on site, put into the deposit (unused energy carried over to later months) and exchanged with the grid. In July 2026 the operator got control of many installations at once, and in September 2026 the module added a new deposit settlement mode.
Polish law sets the rules the module settles by: up to 10 MW of capacity, at least 70% of the cooperative's own needs covered, energy fed into the grid set against energy taken at a 1:0.6 ratio on hourly data, and a deposit valid for up to 12 months. From October 19, 2026 the hourly data comes from CSIRE, Poland's central energy market information system.
- Settlements available through an API
- Membership checked for each hour
Balancing markets and grid operator commands
A battery on a balancing market has to deliver declared power within the market's activation time and stay within the limits set by the DSO. PSE gives full activation times of 30 seconds for FCR, 5 minutes for aFRR, 12.5 minutes for mFRR and 30 minutes for RR. Setpoints from trading, aFRR and the grid operator can disagree, and software has to settle that before anything reaches the inverter.
Since December 2025 we have been building an EMS for Global Green, an operator of solar and battery storage sites in Germany and Canada. It runs on an industrial computer on site and sends data to the cloud. Its orchestrator combines setpoints from trading, aFRR and direct control, resolves conflicts and only then splits the result across batteries. The initial implementation closed on June 29, 2026, and in September 2026 a new EMS version went onto the controller at one site.
Loss compensation raises discharge power and lowers charge power by a configured percentage. The commitment is then met at the grid connection point, within the battery's operating range and with every clipped value logged.
At Skyfri, a solar and battery asset management platform, our EMS does peak shaving and limits export at the DSO's request. By October 2024, DSO-requested export limiting, zero-export algorithms and a maximum load limiter had been tested on site together with the DSO.
- Orchestrator: MVP in progress
- aFRR pipeline migration to the new platform: in testing
Building for the Polish market
VPP software for Poland has to handle 15-minute balancing settlement and units from 0.2 MW, both introduced by the second reform of the Polish balancing market on June 14, 2024 (the minimum had been 1 MW). An aggregated scheduling unit (JGA) can range from 0.2 to 50 MW. PSE joined the European PICASSO platform for aFRR on July 11, 2025.
According to URE, the Polish energy regulator, no aggregator unit had been registered by June 30, 2025, so software for aggregator units has to work from the very first registration.
A call handled in production
Why aggregators build with us
We have developed the Zeronest DSR module since May 2025, and it handled a real call in production on March 23, 2026.
We add the missing layers next to the systems you already run.
How a project runs
From the first message to support under SLA
-
Contact
We reply to a message from the contact form within 48 hours on working days.
-
Free discovery workshop
Every project starts with a discovery workshop, and it is always free. Together we map your portfolio, the markets you serve and the systems you already run.
-
Build
Releases have an agreed scope. Building the Zeronest DSR call flow, from the first models to confirmation by SMS, took about three weeks, and the energy cooperative module about ten days. Code, designs and documentation belong to you by default.
-
Support
Maintenance runs under an SLA, 24/7: 15 minutes to first response on a critical incident and 30 minutes until an engineer is actively working on it.
The energy systems behind these layers
Case studies
Questions about VPP and demand response software
Platform scope, DERMS, DSR calls, cooperatives, balancing and the Polish market.
-
Order Group builds it layer by layer: demand response calls and reports and energy cooperative settlement for Zeronest, and battery orchestration for Global Green. Site control comes from the EMS at each site.
-
A VPP pools batteries, solar and flexible loads for an aggregator to sell on energy and balancing markets. A DERMS is software of the grid operator (DSO) that sends sites export and power limits, and a site EMS has to follow those limits as well as the VPP's commands.
-
A VPP does not replace the EMS. The EMS controls the devices at one site within that site's limits, and the VPP layers work on a portfolio of sites above it, sending each site a target that its EMS carries out.
-
A DSR baseline is the consumption a point would have had without the call. It is corrected by the average difference between consumption and the profile in the third, fourth and fifth hour before the call, capped between -20% and +20%, and the same factor covers the following hours of the call. After an outage the platform restores missing meter data.
-
Demand response is settled on interval data at settlement resolution, usually 15 minutes, for each metering point, with the history needed to build the baseline. The Zeronest prosumer app also works on smart-meter data alone.
-
A battery can do both when one orchestrator resolves the conflict between trading and aFRR setpoints. The controller that combines trading and aFRR on one battery has a finished design and is being implemented.
-
The Global Green EMS follows grid operator commands through separate controllers: a battery limit, a direct battery command and an export limit, all added in July 2026. The DSO is modelled in a simulator.
-
An energy cooperative needs hourly settlement of the group and each metering point under Polish rules, with a deposit and hourly data from CSIRE from October 19, 2026.
-
Units from 0.2 MW have been able to enter the Polish balancing market since the second reform on June 14, 2024, down from 1 MW.
Paweł Zieliński
Co-founder & Business Owner
Book a free consultation with an engineer
Thank you for your message.
We read every message ourselves and get back to you within 48 hrs on business days.
Something urgent? hello@ordergroup.co