EV Cloud
A neutral OCPP and OCPI layer between chargers, roaming partners, and backends, so CPOs and eMSPs migrate without a big-bang cutover.
Station F
EDHEC EntrepreneursChargers 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.
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.
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.
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.
The hidden cost of charger lock-in
Operators stay on platforms they have outgrown because leaving is riskier than staying.
- €200k+
- on interoperability testing, labs and regressions per year
- Illustrative internal model, before any migration starts
- 2,500+
- engineering hours lost
- Internal estimate; senior teams diverted from product
- 1 URL
- per charger, set once at install
- Changing it means field visits and risk windows
Different buyers. Same lock-in.
Every operator eventually has to change a backend, add a roaming partner or absorb a new charger generation without touching the field.
- CPOs
- New charger generations, backend migrations and roaming launches
- eMSPs
- One normalized OCPI layer across hubs and direct peers
- Charger manufacturers
- One gateway endpoint across every central system
- Roaming platforms
- Partner onboarding across OCPI versions and dialects
One platform for the entire EV charging stack.
Chargers → OCPP → CPMS → OCPI → CPO → eMSP → roaming → AI agents. Connect, manage, monitor and operate from one place.
OCPP proxy, charger management, monitoring
One target for every charger, one inventory, every message kept.
OCPI roaming, hubs, SDKs
One gateway for peers and hubs, typed clients for your stack.
ChargerPilot, MCP, copilot
Read-only AI for operators, agents and support teams.
One secure gateway between every charger and every CPMS.
Chargers connect once to the EV Cloud proxy. Messages are inspected, logged and routed in real time to the backend you choose.
- OCPP 1.6 and 2.0.1 today. Both generations on one endpoint. OCPP 2.1 is on the roadmap, listed after docs and validation.
- Secure, reliable connectivity. TLS WebSocket from charger to gateway, pooled keep-alive connections to each CPMS.
- Real-time routing and inspection. Every message logged and routed by priority rule, per site, partner or rollout phase.
- Traffic monitoring and logs. The full OCPP exchange stored per charger and per session.
Change the backend by changing a route, not a charger.
Not a full CPMS/CSMS replacement by default. It sits alongside existing backends.
A complete charger management system, at any scale.
Connect, configure and control every charge point from one dashboard, whatever brand or backend it belongs to.
- Connect at scale. Onboard chargers by the site or by the thousand through one endpoint.
- Remote monitoring and control. Status, health, connectors and sessions live. Operators send reset, start, stop, unlock and configuration commands, and every response is logged.
- Any brand, any firmware. Vendor dialects are handled at the gateway, so chargers keep their hardware and settings.
- Centralized configuration. Charger settings, authorization tokens and ID routing managed in one place.
One inventory, one control surface, every charger.
See every request, response and error as it happens.
Real-time logs turn “the charger is down” into a specific message, timestamp and cause.
- Live OCPP logs. Requests, responses and errors per charger and per backend.
- Transaction monitoring. Sessions, meter values and outcomes tracked end to end.
- Protocol issue detection. Timeouts, rejected messages and dialect deviations visible in the stored exchange.
- Troubleshooting tools. Filter and compare exchanges when integrating a new charger or backend.
Diagnose from evidence, not from memory.
An AI assistant that manages charger assets and finds the fault.
ChargerPilot reads your fleet data, logs and OCPP messages, finds issues and recommends the next step, so operations and support teams act faster.
- Asset management. Ask about any charger, site or session in plain language, answered from your own data.
- Issue detection. Finds failed sessions, offline chargers and protocol anomalies in your telemetry when asked.
- Root cause analysis. Reads the OCPP exchange and names the charger, network or backend at fault.
- Recommendations. Suggests the next step for operators and support.
Read-only by design. People keep the controls.
A complete OCPI roaming solution.
Connect CPOs and eMSPs directly, run OCPI versions side by side, and validate partner flows before drivers roam.
- OCPI 2.1.1 and 2.2.1 today. Both versions on one network. 2.3.0 peers negotiate to 2.2.1; native 2.3.0 is on the roadmap.
- Peer to peer. Direct CPO to eMSP integration through the standard credentials handshake.
- Modules covered. Locations, tokens, sessions, tariffs and CDRs synchronized.
- Validate before go-live. Run the handshake and module sync against a partner before traffic is live.
Roaming as an operating task, not an integration project.
Hubs and brokers through the same gateway.
Connect to roaming platforms and brokers through the OCPI flow that already serves your direct peers.
Hubject, Gireve and others
Reached through the standard OCPI credentials flow. Pre-built hub connectors are on the roadmap.
CPO ↔ eMSP
One normalized layer whichever side of the transaction you are on.
Validate first
Exercise the partner handshake and module sync in a controlled environment before drivers roam.
The platform as a library.
Typed clients and APIs for charger and roaming integrations, so teams automate operations from code.
TypeScript SDK
Typed clients for chargers, sessions, routes, partners and CDRs.
Python SDK
On the roadmap. The same surface for Python stacks.
APIs and automation
Script operational workflows and plug into existing platforms.
Connect any AI agent to the charging platform.
The EV Cloud MCP server exposes chargers, sessions, proxy, observability, roaming and telemetry as tools, scoped to your organization’s token.
- Any MCP client. Cursor, Claude, or your own agent.
- Charger data and tools. Agents read the same data operators see.
- Automated diagnostics. Let agents run the first pass on failed sessions.
- Custom AI solutions. Build your own charging assistant on top.
Same data, same permissions, whether a person or an agent asks.
A copilot for charger support and integration teams.
The copilot reads OCPP and OCPI messages, searches the protocol documentation, and walks engineers through integration and debugging.
- Troubleshooting help. From ticket to charger to message in one thread.
- Message analysis. Explains what an OCPP or OCPI exchange did and where it broke.
- Documentation search. OCPP and OCPI specs, schemas and charger notes in one place.
- Guided integration. Step by step through new charger and partner integrations.
Knowledge stays with the team, not with one expert.
Turn charger estates into reversible plays
Connect
Point mixed fleets at one OCPP endpoint. OCPP 1.6 and 2.0.1. Chargers keep their hardware and firmware.
Detect
Map backends, protocol versions, and routing priority. This is the traffic split nobody documented.
Deploy
Run current and next systems in parallel on the operator’s own data. Cut over site by site and roll back by changing a route, not a charger. ChargerPilot assists, read-only.
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.
EV Cloud is a neutral OCPP and OCPI infrastructure layer that sits between charger fleets, roaming partners, and internal systems so Charge Point Operators and eMSPs can connect mixed fleets, launch roaming, and migrate backends without a big-bang cutover.
ChargerPilot AI for OCPP and OCPI: fleet SQL, diagnose evidence, and protocol how-to. Live station control is not shipped.
From mixed fleets to unified Routing
Chargers, roaming partners, and backends sit on separate stacks. EV Cloud is a neutral OCPP and OCPI layer between them so operators can connect mixed fleets, launch roaming, and migrate without a big-bang cutover.
Start with CPO and eMSP protocol infrastructure
EV Cloud focuses on the OCPP gateway, OCPI roaming and multi-backend routing layer.
The public product is an OCPP gateway, an OCPI gateway, and multi-backend routing, priced by estate and routing complexity.
- 1.6 / 2.0.1
- Mixed fleets
- One charger-facing gateway entry
- Any brand, any firmware, one endpoint
- 2.1.1 / 2.2.1
- Partner operations
- Tokens, tariffs, sessions, CDRs
- Hubs such as Hubject and Gireve, or direct peers
- $500/month
- Multi-backend
- Parallel systems, live migration
- Growth list price on ev-cloud.ai/pricing
Sources: Grand View Research, IEA Global EV Outlook 2024, EAFO, ACEA, ICCT / ZEV Alliance 2025
Connect once. Control without lock-in.
Stabilize the field layer first, then change downstream software. Multi-backend routing so current and future systems can run in parallel. The stack changes on the operator’s terms, one route at a time. Live today with a European regional CPO of 200+ chargers, a US commercial fleet depot, and a Canadian hardware OEM.
Team
Oumaima Bounouadar
5+ years scaling AI, enterprise data, and SaaS products. Leads product commercialization, enterprise go-to-market, and automated decision architectures for eMobility operators.
Yassine Elazrak
6+ years in distributed systems, cloud infrastructure, and EV protocol engineering. Author of the EV Cloud OCPP and OCPI guides; architect of the core proxy engine.
Founder-market fit: deep protocol systems and AI execution
Stabilize the field layer. Change the stack on your terms.
API gateways made web services replaceable. EV Cloud does the same for charging.
Connect once. Route anywhere. Roll back by changing a route, not a charger.