Mercury for technology providers

One integration target for the whole smart energy market.

‍

If you build software for smart energy, your margin problem has a shape: every new utility or OEM customer brings its own integration work. The platforms feel it as engineering capacity disappearing into per-customer builds. The consultancies feel it as bespoke projects that never productise, so delivery never scales past the founding team.

One development that covers many is the whole case. Build to the Mercury standard once and you can work with the full network of Mercury-aligned utilities and certified devices without repeating the integration for each customer.

It strengthens what you have already built

Mercury is a certification layer on top of existing protocols, not a rival to them. Your OCPP and OpenADR implementations gain from Mercury conformance rather than competing with it. The class structure (A, B, C and the Alpha bridge) gives you a published technical anchor with defined response times, telemetry and fail-safe behaviour, and a release cadence you can see, so the dependency on the standards body is bounded and predictable.

Answer the procurement question once

Utilities increasingly ask which interoperability standards you support, and a weak answer can disqualify a platform before the product is even evaluated. When a customer asks you to support a specific certification, Mercury lets you answer once, for all customers, rather than treating each request as a one-off build. For consultancies, the same standard is the base for a repeatable practice: certified offerings carry better margin than bespoke integration projects, and the practice can grow beyond founder-level delivery.

Software economics work in your favour

Your cost to develop against Mercury is low compared with a hardware OEM's, so the return threshold is lower too. Fees scale with company revenue; a provider under $100 million in revenue pays $10,000 as a Full Member or $5,000 as an Observer. Full Members vote in working groups and shape the roadmap, which matters here more than for most segments: the network will be exactly as large as its technology provider members make it, and first movers set the trajectory.

Membership and certification remain separate decisions. Membership and roadmap engagement can begin immediately, with technical certification sequenced into your normal release cycle.

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

‍