Mercury for OEMs and device manufacturers

Certify once. Work with every supporting utility. Get your engineers back on product.

‍

If you make EV chargers, home batteries, heat pumps or any connected energy device, you already know the problem. Your device supports OCPP. So does the utility. Yet every new utility connection still becomes its own integration project, because the protocol leaves too much open to interpretation.

The cost lands in two places. The first is your engineering plan: teams hired to build product spend their sprints on integration work and on bug fixes triggered by a utility upgrading its platform. The second is commercial, and it hurts more. When a utility launches a market-leading tariff, the OEMs whose devices are not compatible lose those sales to a competitor's hardware. At the exact moment demand peaks, you are locked out.

Mercury is not another protocol

There are enough of those. Mercury is a certification and conformance layer that makes the protocols you already use work consistently. It sits on top of OCPP rather than replacing it, so the OCPP investment your team has already made is preserved. Certification confirms that your device behaves predictably: response time, data granularity, meter accuracy and fail-safe behaviour, defined by class and tested the same way for every manufacturer.

One certification, every supporting utility

Today, entering five utility markets means five separate integration or certification efforts, each taking weeks or months. Mercury replaces that with a single pathway. A certified device works with any supporting utility through the same standard integration, so each new utility relationship expands your addressable market without new code.

Certification is independent. Devices are tested by DEKRA, not by Mercury itself and not by any member company. The first certified devices, the Octopus Charge, Zaptec Go 2 and Easee One, went through exactly that process.

And if your hardware is already in the field, the Class Alpha bridge specification was engineered for you. It supports OCPP architecture using your existing cloud as the communications relay, with a 12 month certification window. No device left behind.

Certification and membership are separate decisions

Certification is the technical compliance work: it puts the Mercury Mark on your device. Membership is how you shape where the standard goes next. Full Members lead and vote in working groups, sit on the Board of Directors and set the technical roadmap alongside the 40+ organisations already paying to build this, including Octopus Energy and E.ON, with backing from EPRI.

Where to start

Talk to us about your device roadmap and which class fits the markets you want to reach. The specification and governance documentation are published and open.

Join Mercury. Certify your product. Build the resilient energy future.

‍