We spoke with Enoch Lenge, Partner for the US e-Mobility & Energy practice at Codibly, about what they do, why they joined Mercury, and where they see the next five years going.
What Codibly Does
Codibly is a technology consultancy and software development firm enabling the energy transition through interoperable, grid-ready software. Codibly’s core work is end-to-end platform development: Charging Station Management Systems (CSMS/CPMS), e-Mobility Service Provider (eMSP) platforms, Dynamic Load Management systems, and DERMS/flexibility orchestration platforms. These are the operational layers that charge point operators, utilities, DERMS/aggregators, and device manufacturers rely on to connect physical assets to commercial and grid services.
To reduce the cost of that work, Codibly has developed pre-built software accelerators for key protocols, including OCPP, OpenADR, IEEE 2030.5, OCPI, and ISO 15118 (Plug & Charge). Where a bespoke integration might take months, these accelerators compress the timeline and reduce the risk of inconsistent implementation across different hardware vendors.
Their primary markets are in the US and Europe, working with utilities, charge point operators, and technology providers on EV charging infrastructure and demand-response programmes.
Why Codibly joined the Mercury Consortium
Codibly joined the Mercury Consortium because the problem Mercury is trying to solve sits directly in their day-to-day work.
“Defining functional guidelines is essential,” Enoch told us, “but many organisations struggle to translate them into reliable, production-ready software.”
That translation problem is common. A standard can be technically sound and still fail commercially if the implementation layer is under-resourced, inconsistently applied, or blocked by integration debt from previous one-off builds.
That’s exactly why Codibly joined Mercury. Their role is to give manufacturers and operators the engineering capability to meet requirements quickly, avoid vendor lock-in, and get to market without rebuilding the same work for each new customer. Mercury defines what good interoperability looks like. Codibly builds the software that delivers it.
Where the opportunity is
Codibly’s high-level focus is fleet electrification. The coordination of EV charging with on-site generation, battery storage, and Energy Management Systems creates the conditions for peak demand reduction and VPP participation at scale.
That coordination requires the kind of vendor-agnostic, protocol-fluent software that Codibly builds.
Within Mercury specifically, Codibly is most engaged with the technical interoperability guidelines and the certification and compliance work. Both connect directly to their focus on faster market access for hardware manufacturers and reliable, scalable interoperability for charge point operators. Codibly provides real-world experience and lessons learned connecting, testing, and scaling interoperability protocols to the ecosystem of key industry players.
What this means for Mercury members
Codibly is one example of what the Mercury member network looks like in practice. Alongside manufacturers, utilities, and flexibility providers, Mercury includes organisations whose primary value to the consortium is the ability to take what Mercury defines and turn it into working, production-ready software.
If your organisation is working on EV charging infrastructure, energy flexibility, or smart energy integration, and you want to understand what Mercury membership involves, reach out to our membership team: membership@mercuryconsortium.com