Skip to main content

CPO migration guide: switch backends site by site.

Migrate

Control EV charging infrastructure without lock-in

One OCPP gateway for mixed fleets. One OCPI gateway for roaming. Multi-backend routing and ChargerPilot AI so you can migrate systems without a big-bang cutover or a hardware reset.

Product tour

Connect once, route dynamically

Two and a half minutes on the gateway between your chargers and every backend you run.

Loads from YouTube on play
EV Cloud launch film cover — one gateway, every charger, every backend, with the charger to gateway to backend diagram
Interoperability

Supported protocols

OCPP gateway and OCPI gateway coverage for the versions operators ship in production, plus complementary site protocols.

Open Charge Point Protocol logo

OCPP

Open Charge Point Protocol between chargers and the central system. EV Cloud’s OCPP gateway supports OCPP 1.6, OCPP 2.0.1 and OCPP 2.1 for mixed fleets through one field entry point.

Open Charge Point Interface logo

OCPI

Open Charge Point Interface between CPOs and eMSPs for roaming, locations, tariffs, sessions, and CDRs. The OCPI gateway supports OCPI 2.1.1, OCPI 2.2.1 and OCPI 2.3.0 for hubs and bilateral partners.

EEBUS logo

EEBUS

Site-level energy management: EV Cloud reads EEBUS grid and building signals so charger limits follow available power.

Modbus logo

Modbus

Meter and controller integration: EV Cloud polls Modbus devices so load balancing and billing use measured values.

Developers

Build on EV Cloud

The same gateway your chargers talk to is scriptable. Provision chargers, launch a CPO bundle, or hand the whole fleet to an AI agent over MCP, with tokens issued from the dashboard Connect sheet.