Why DYDON
Not one piece of the stack. The whole stack, coordinated.
Energy software tends to specialise: a charging platform, a storage optimiser, a home VPP, a building EMS. Each does its piece well and none of them see the others. DYDON was built to be the layer that coordinates all of it.
Five things we do that the pieces cannot
None of these is unusual on its own. Doing all five in one platform is what makes the difference.
Hardware neutral
Partners ship the hardware. DYDON runs the software.
AI that acts, not just reports
Commands go to the asset, not a dashboard.
Multi-asset by design
EV, storage, solar, load and fleet in one model.
Connected to the market
From device control to VPP and market settlement.
Protocol driven, multi-market
Open protocols. Same platform, every market.
Where the pieces stop
This is how we think about the categories we are usually compared with. Each is good at what it was built for; the gap is what happens between them.
Traditional building and site EMS
Monitoring and building control on a single site.
No coordination across sites and no connection to energy markets.
EV charging platforms
Sessions, billing and driver experience for one asset class.
Transactions rather than coordination. Storage, solar and load are someone else's problem.
Storage optimisers
Utility-scale trading and dispatch of large batteries.
Behind-the-meter sites with several asset types are thin.
Residential VPP platforms
Aggregating homes into market programmes.
Limited reach into commercial, industrial and data centre sites.
Energy retailers
They own the customer relationship and the market access.
They rent software. That makes them our white-label partners, not competitors.
DYDON coordinates the whole stack
One platform across asset classes and site types, from control at the edge to participation in the market, deployed through the partners who already sell the hardware.
Built once at scale, then built again
The moat is not a feature. It is the combination of integration breadth, protocol depth, the edge-plus-cloud architecture and a team that has already run energy and mobility hardware at national scale.
- Multi-vendor integration platform
- Charging OS, multi-brand storage and solar, data centre power and electric fleets on one integration layer. Each vendor added makes the next one cheaper.
- Protocol depth
- OCPP in every version, OpenADR demand response, CSIP-Aus dynamic operating envelopes, Modbus and SunSpec for equipment. Implemented and run in production, not just listed.
- Edge plus cloud
- Safety and real-time control at the site, forecasting and market participation in the cloud. Most platforms have one or the other.
- A team that has done this before
- The founders built and operated battery-swapping and EV charging platforms at national scale before DYDON, from firmware to cloud.
See it against your own assets
The quickest way to judge the difference is a demo on the equipment you actually run.