ihomer
nlen
Book a call
OEM
For charge-point hardware OEMs

Smarter chargers in the field.
Without building your own CPMS.

For charge-point hardware OEMs who want deployed-fleet visibility and post-sales differentiation — without sinking two years into a software stack.

Deployed fleet, liveLIVE
NL
8,420 unitsv2.4.1
DE
12,180 unitsv2.4.1
BE
3,640 unitsv2.3.7
FR
5,760 unitsv2.4.0
(01) The problem

Sound familiar?

01

30,000 chargers in the field across 40 CPOs. And you don't know how they're doing. Firmware issues reach you through support tickets — behind the curve.

02

Audi and Porsche require Plug & Charge. Your firmware is almost ready. But which CPMS do you validate against? "We're ready" says everyone — there's no shared testbed.

03

CPOs ask whether you have "smart features." The competition has a story. Do we build it (€2–€5M, 18–24 months engineering)? Or partner?

(02) What ihomer does for you

Two paths, both built on standards we co-author.

Path 1 — data access: our Koppelvlak layer gives you OCPP event streams from your deployed hardware, scoped so you don't need CPMS credentials. For remote diagnostics, warranty claims and firmware validation. Path 2 — white-label CPMS: license our Laadbeheer stack as the back-end for your hardware bundle, on a per-CP royalty model. Live 6–12 months sooner than building your own, on a proven OCPP 2.0.1 + ISO 15118 Plug & Charge implementation.

(03) What you use

Capabilities that fit here.

Lead
ihomer Koppelvlak

OCPP event streams from deployed fleet, scoped, no CPMS credentials.

ihomer Laadbeheer (white-label)

CPMS license as back-end for your hardware bundle, royalty model.

Proof
12 years
in OCA + EV Roaming Foundation

“We've been at the standards table for twelve years. For your firmware team that means shorter feedback loops and early access to what's coming in OCPP 2.1 and 3.0.”

— Standards lead, ihomer
  • OCPP and OCPI co-author since 2014
  • Contributor to EVerest libocpp — OCPP 2.0.1 + 2.1 + Plug & Charge
  • Peblar as anchor reference in the OEM segment
  • Energy King as prospect/pilot — OCPP proxy fit
(05) Honest objection

“Our competitors also use standards-based platforms. What's your real edge?”

That we co-author the standards. Sounds like marketing, but it's technically verifiable: check the OCA member list, the libocpp commit history, the OCPI working group. We've been in those rooms for twelve years. For your firmware team that means shorter feedback loops on edge-cases and early access to what's landing in OCPP 2.1 and 3.0.

Build or partner?

Book a 60-minute architecture review with our tech lead. We dig into your deployed fleet, your firmware roadmap and which path — data access or white-label — fits.

HonestlyNot the cheapest, not the biggest. The deepest in standards — and, if it matters, in the room where OCPP and OCPI are written.
Standards & coalitions
Open Charge Alliance
OCPP co-author since 2014
EV Roaming Foundation
OCPI working group
EVerest libocpp
Open-source contributor
NRG joint venture
Energy & grid context