SR
Sunrock
Energy and deployment partner in large operational environments.
Connected Network
A growing network of parties already connected through EDX.
From hardware vendors and field infrastructure to deployment partners and living labs, EDX sits in the middle of real energy data flows. This page shows the organizations currently in the network and gives new parties a direct path to request a connector or start a conversation.
Hardware vendors
Software and data partners
Deployment and validation partners
Who is already in the network.
The current network spans device vendors, software and telemetry providers, and organizations where energy data infrastructure is being deployed or validated in real-world settings.
OD
ODOS
Connected software and data partner in the broader energy stack.
GB
GPSBuddy
Telematics and operational data source relevant to project environments.
SE
SolarEdge
Solar and inverter telemetry available through the connected layer.
GW
Growatt
Connected energy hardware used in live and validation environments.
JL
Joulz
Energy infrastructure and operational context in the connected ecosystem.
VC
Victron
Power conversion and storage systems represented in the connector layer.
EN
Envitron
Smart monitoring and telemetry partner in the connected network.
BN
Benext
Connected smart device and building-level energy integrations.
AB
ABB
Industrial and energy equipment relevant to broader connector coverage.
BM
BAM
Deployment and project partner where data continuity matters in practice.
GV
The Green Village
Living-lab environment for testing and validating data infrastructure at scale.
AU
Aurum
Dashboarding layer for teams that need operational and reporting visibility.
Request a Connector
Want your hardware or platform connected to EDX?
If your company builds hardware, operates connected energy assets, or needs access to a normalized data layer, the fastest next step is to show us the data source, protocols, and project context. We can then determine whether a connector already exists or what it would take to add one.
01
Tell us what needs to connect
Share the vendor, hardware type, API or protocol, and whether the need is for a pilot, deployment, or broader partner integration.
02
We review fit and existing coverage
We check whether the connector already exists, whether part of the work is reusable, and what the likely scope of rollout looks like.
03
Move into scoping or activation
If the fit is strong, we can move into a connector discussion, guided pilot, or a broader platform conversation depending on what you need.