A neutral OCPP and OCPI layer between chargers, roaming partners, and backends, so CPOs and eMSPs migrate without a big-bang cutover.
Protocols
OCPP1.6 · 2.0.1 · 2.1
OCPI2.1.1 · 2.2.1 · 2.3.0
Backed by
Station FEDHEC Entrepreneurs
The problem
EV Cloud
Chargers should not bind forever to one backend
Mixed OCPP fleets, roaming partners, and a CPMS cutover currently force field rewiring. Operators need a protocol layer that can sit in front of current and future systems.
01
Mixed fleets, one URL
OCPP 1.6 and 2.0.1 chargers still terminate on a single CPMS. A backend change means truck rolls and risk windows.
02
Roaming is an operating problem
OCPI 2.1.1 and 2.2.1 partner onboarding, tokens, tariffs, sessions, and CDRs stay manual once traffic is live.
03
Big-bang CPMS replacement
Billing, roaming, and support still depend on the current platform, so a one-step swap is too risky for operations.
Stabilize the field and partner edges first, then change downstream software.
