Public CPO
For public CPOs — corridor, fast charging, street-level

Add intelligence to your charging network.
Without blowing up your platform.

For public CPOs managing uptime, OCPI roaming and OEM cooperation on €30k–€300k assets. Modular, beside your existing stack or as a full replacement.

Hot-standby uptimeLIVE
SLA 99,9%switchover
laatste 32 polls100.00% uptime
(01) The problem

Sound familiar?

01

A DC charger down for six hours costs €10k+ in revenue and one furious tweet. Your CPMS has no hot-standby. Migrating to something better? Not on a corridor site, not without zero-downtime tooling.

02

Your hardware vendor wants diagnostic access for warranty claims. You can't hand over CPMS credentials — security risk. And yet the OEM points the finger when the unit fails.

03

AFIR 2027 deadline: contactless payment on every >50kW charger. Plus OCPI 2.2.1 for cross-border roaming. Plus ISO 15118 Plug & Charge for Audi, Porsche, VW. Who's leading?

(02) What ihomer does for you

You don't have to replace your CPMS today.

Our Koppelvlak layer sits between your existing CPMS and your chargers, giving you three things you don't have today: hot-standby continuity (no more 6-hour outages), scoped OEM access (no credential sharing), and audit-grade event streaming (for billing disputes and warranty claims). When you do want a full replacement, ihomer Laadbeheer is there — built by the same people who co-author OCPP and OCPI via the Open Charge Alliance and EV Roaming Foundation.

(03) What you use

Capabilities that fit here.

Lead
ihomer Koppelvlak

Orchestration layer under your existing CPMS — uptime, OEM proxy, audit logs.

ihomer Laadbeheer

Full CPMS — for when you do want to switch entirely.

ihomer Roaming

OCPI 2.2.1+ broker — one connection to Plugsurfing, Shell Recharge, NewMotion and more.

ihomer Migratie

Zero-downtime migration. Proven approach for Etrel and Everon shutdowns.

Proof
99.9%+
uptime with hot-standby orchestration

A DC charger down for six hours costs more than a year of Koppelvlak licensing.

Tech lead, ihomer
  • OCPP and OCPI co-author via OCA + EV Roaming Foundation
  • Contributor to EVerest libocpp — OCPP 2.0.1 + 2.1 + Plug & Charge
  • Existing customer Alfen (passthrough) as anchor in public segment
  • Multi-vendor support: ABB Terra, Alpitronic Hypercharger, Kempower, EKOENERGETYKA
(05) Honest objection

We've built our own CPMS. Is this for us?

Especially then. Our Koppelvlak layer is designed to run beside your existing platform, not replace it. You keep your investment, you keep control of your data, and you get the layer in-house teams rarely build themselves: hot-standby, OEM proxy and audit-grade logging.

Uptime below 99.9% or OEM questions you can't answer?

Book a 30-minute architecture review with our tech lead.

HonestlyNot the cheapest, not the biggest, not the most international. The deepest in standards — and the only player giving you an orchestration layer without ripping out your CPMS.
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