Built for operators who refuse lock-in
EV Cloud is built by OCPPLab, the team that runs production OCPP and OCPI operations for Charge Point Operators and eMSPs.
Why EV Cloud exists
Charge Point Operators should not have to rewire every charger when a backend, roaming partner, or billing system changes. Most CSMS platforms force a big-bang cutover: one vendor URL in the field, one data path.
EV Cloud adds the missing layer: an OCPP gateway for mixed fleets, an OCPI gateway for roaming operations, multi-backend routing for dual-run migration, and ChargerPilot AI agents that work from real protocol telemetry.
The product is infrastructure-first. We stabilize the field and partner edges so operators can change the stack behind them without truck rolls.
Built by
OCPPLab works only on OCPP, OCPI and the systems operators run around them. The same team owns product, protocol depth and support.
ocpplab.com (opens in a new tab)How we build
Migrate without a field cutover
Chargers keep one URL in the field while EV Cloud routes them to the old and new backend in parallel, so you switch when the data matches.
Protocol depth first
Production OCPP and OCPI coverage is the product. Dashboards and agents are only useful when the field layer is stable.
Operator data ownership
Charger events and roaming exchange should remain exportable and routable, not trapped inside a single vendor stack.
Next step
Ready to evaluate EV Cloud?
Talk through architecture with the team in a demo, or browse solutions for gateway, roaming, and migration.