Skip to main content

New. CPO Rollout Blueprint — evaluate migrations without lock-in risk.

Read blueprintRead
OCPP gateway · OCPI gateway · ChargerPilot AI

Control EV Charging Infrastructure Without Lock-In

Connect. Integrate. Control.

OCPP 1.6 · 2.0.1 · 2.1 · OCPI 2.1.1 · 2.2.1 · 2.3.0 · Zero vendor 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.

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

EEBUS is a protocol suite for the Internet of Things that aims to standardize the interface between electrical consumers, producers, storages and (logical) managing entities.

Modbus logo

Modbus

Modbus is a data communications protocol. It is a de facto standard communication protocol and widely used to connect industrial electronic devices.

What EV Cloud Solves

One infrastructure layer for charger control, roaming, and migration.

Use EV Cloud between chargers, roaming partners, and internal systems so you can launch new workflows without replacing everything at once.

  1. OCPP gateway & proxy

    Connect

    One OCPP gateway for mixed fleets—and an OCPP proxy path for multi-backend routing. Normalize OCPP 1.6, 2.0.1, and 2.1 traffic without reconfiguring hardware every time backend strategy changes.

    Learn more about OCPP gateway & proxy
  2. OCPI gateway

    Interoperate

    OCPI gateway for roaming: tokens, sessions, tariffs, and CDRs across OCPI 2.1.1, 2.2.1, and 2.3.0 without bolting partner logic into your core product. Bilateral and hub integrations with clearer boundaries.

    Learn more about OCPI gateway
  3. ChargerPilot AI agents

    Operate

    AI agents for OCPP and OCPI operations on gateway telemetry—anomaly triage, roaming exceptions, and multi-backend ops assistance without living in raw protocol logs.

    Learn more about ChargerPilot AI agents

Start here

Product pages and operator guides

Jump to commercial landings for gateway, proxy, and platform decisions—or into protocol guides and scorecards when you are still forming the shortlist.

FAQ

Frequently Asked Questions

Straight answers for teams evaluating an OCPP gateway, OCPI gateway, and AI-assisted ops layer—connectivity, roaming, coexistence, and migration risk.