Skip to main content
productMarch 1, 2026

Introducing EV Cloud: The Universal OCPP Bridge

Today we're launching EV Cloud — infrastructure that connects any EV charger to any CPMS without code changes, lock-in, or protocol translation headaches.

At a glance

EV Cloud is an infrastructure layer for charger connectivity and backend routing. It gives operators one OCPP endpoint, protocol normalization, and stronger control over migration and data ownership.

CPO product teamsEV charging platform buyersSolution architects
  • EV Cloud sits between chargers and one or more management platforms.
  • The product is built to remove protocol friction and reduce vendor lock-in.
  • Multi-backend routing is a core operational use case, not just a migration trick.
  • The platform is positioned as infrastructure, not only as a dashboard product.
Y
Yacine El Azrak
Co-founder & CEO
2 min read

The problem with EV charging infrastructure today

If you've ever tried to integrate an EV charger with a Charge Point Management System (CPMS), you know the pain. OCPP versions proliferate — 1.5, 1.6, 2.0, 2.0.1. Each vendor implements it slightly differently. Each CPMS expects a specific dialect.

The result: integration projects that take months, bespoke translation layers that break with every firmware update, and entire engineering teams dedicated to keeping the plumbing alive.

We've seen this pattern dozens of times across fleets, parking operators, utilities, and eMSPs. It's not a skill issue. The protocol layer is genuinely broken.

What we built

EV Cloud is a network-level OCPP broker that sits between your chargers and your management systems. It handles:

  • Protocol translation — OCPP 1.5 ↔ 1.6 ↔ 2.0.1, transparently
  • Multi-CPMS routing — route messages to multiple backends simultaneously
  • Data ownership — every message is stored and queryable in your own schema
  • Lower lock-in pressure — reduce the need to reconfigure chargers when backend strategy changes

You connect once, then shape routing, translation, and downstream integrations as configuration instead of custom charger-by-charger plumbing.

Architecture overview

At its core, EV Cloud is a persistent WebSocket proxy with a stateful message router. Each charger maintains a long-lived connection. Messages are inspected, transformed if needed, and dispatched to the configured upstreams.

We store a full copy of every OCPP exchange — BootNotification, StatusNotification, MeterValues, StartTransaction, everything. This gives you a real-time event stream and a queryable history without any additional instrumentation.

Charger ──WebSocket──▶ EV Cloud Broker ──▶ Primary CPMS

                              └──────────▶ Secondary CPMS (optional)

                              └──────────▶ Your data warehouse

What's next

We're starting with OCPP 1.6 and 2.0.1 support. Over the next quarters we're adding:

  • Native OCPI integration for eMSP roaming
  • Smart charging profiles and load management APIs
  • Webhooks and streaming for real-time event processing

If you're evaluating vendors right now, read the OCPP platform buyer guide and the CPO RFP checklist. If you're already comparing alternatives, start with the comparison hub.

Frequently asked questions

Short answers for operators evaluating this topic in production.

Continue evaluation

Turn this topic into a buying decision

Use these pages to move from protocol research into shortlist design, migration planning, and commercial evaluation.

From content to rollout

Need help applying this in a live EV charging stack?

EV Cloud helps operators connect chargers, roaming partners, and internal platforms without rewriting their entire backend. Use the guide above for strategy, then use the product pages below for rollout planning.