EV Cloud
Control EV charging infrastructure without lock-in. Chargers connect once; backends, roaming partners, and AI change behind the gateway.
Station F
EDHEC EntrepreneursOperators are locked to the first CPMS their chargers ever connected to
Operators stay on platforms they have outgrown because leaving is riskier than staying.
- Chargers point at one URL. Changing the backend means touching firmware config on every unit in the field.
- Mixed fleets speak mixed protocols. OCPP 1.6 and 2.0.1 units live side by side, and every backend handles them differently.
- Roaming is bolted on. OCPI partners, hubs, tokens, tariffs, and CDRs each get wired straight into the CPMS.
- Migration is a big-bang event. Switching CPMS means an estate-wide cutover on one date with no way back.
- Operations live in raw message logs. Diagnosing a stuck session means reading OCPP traffic by hand.
Illustrative internal model: a large CPO spends €200k+ a year on interoperability testing, labs, and manual regressions before any migration starts.
Who buys, and what triggers the purchase
One stable endpoint for every charger
Estate today: Mixed charger estate on one incumbent CPMS.
Trigger: Price hike, acquisition, or contract renewal.
One normalized OCPI layer for hubs and peers
Estate today: Bespoke OCPI wiring per partner and version.
Trigger: AFIR obligations, slow partner onboarding.
Routing between depot software and backends
Estate today: Multi-vendor chargers bought over several years.
Trigger: New depot software, load management.
Dual-run, reversible until cutover
Estate today: Migration equals downtime risk.
Trigger: Backend modernization.
The brownfield reality: three charger generations from two AC vendors and one DC vendor, OCPP 1.6 beside 2.0.1, and some sites on flaky cellular. All of it points at a backend the team has outgrown. EU AFIR and US NEVI add urgency.
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.
| Big-bang replacement | Gateway first with EV Cloud | |
|---|---|---|
| Cutover | Every charger re-registers on one date | Site by site, reversible per wave |
| OCPP 1.6 quirks (MeterValues on clock vs energy delta) | Handled differently by the new backend | Normalized once at the gateway |
| OCPP 2.0.1 device-model data | Depends on the new platform’s support | Captured before it reaches any backend |
| Flaky cellular sites | Reconnect storms hit the new backend on day one | Absorbed at the edge |
| Blast radius if a wave fails | Whole estate | One site |
| Field visits for stubborn firmware | Likely | Avoided: chargers never change URL |
| Lock-in after migration | Recreated with the new vendor | Chargers stay decoupled |
A mixed AC and DC fleet leaving its incumbent CPMS
A cheaper architecture with an expensive rollout is not cheaper. Ordering, not vendor choice, decides whether a rollout stays calm.
The costs a CPMS quote never prices: estate-wide cutover, charger-by-charger field work, rollback exposure, and new lock-in. Gateway-first removes them.
€5–6B
Global EVSE software
EV Cloud market model, investor deck3,000+ CPOs
~240 eMSPs, 100+ charger brands, 12M EVs on the road, 1.03M public charging points
€1–3M
From the European beachhead
Europe first: thousands of operators aging into mixed fleets under new mandates
Beachhead: European CPOs and CPMS vendors running mixed fleets, roaming, or a backend migration. Global EVSE software reaches €5–6B by 2030; the year-3 target is €1–3M ARR from the beachhead alone.
- Fleets are aging into heterogeneity. OCPP 1.6 and 2.0.1 units side by side, with 3 to 5 firmware updates per OEM per year.
- Regulation demands roaming and uptime evidence. EU AFIR (2023/1804) has applied since April 2024: ad-hoc payment and open data at public chargers. US NEVI (23 CFR Part 680) requires over 97% uptime per port plus OCPP 2.0.1 and OCPI 2.2.1, unchanged by the 2025 FHWA guidance.
- Charging is compounding. Public chargers worldwide doubled since 2022 to over 5 million; 1.3 million were added in 2024 alone.
- CPMS consolidation forces migrations. Acquired, merged, or outgrown operators need a safe path off the incumbent.
- Renewals are the trigger. Price hikes, acquisitions, and contract renewals put the incumbent CPMS on the table every 3 to 5 years.
Sources: EV Cloud market model (investor deck); EUR-Lex CELEX 32023R1804; eCFR 23 CFR 680.108 and 680.116; IEA Global EV Outlook 2025.
24 months from V1 to the reference platform
Shipped today: gateway, proxy, roaming, ChargerPilot, webhooks, observability, billing. Version claims stay honest: OCPP 2.1 and OCPI 2.3.0 are listed after docs and validation, not before.
V1 ready
Full OCPP 1.6 / 2.0.1, OCPI 2.1.1 / 2.2.1, ChargerPilot read-only.
3–5 demos, 2–3 proofs of concept
Market validation
Scenario library, CI/CD API, SSO / SCIM / audit logs, dedicated regions, load balancing and V2G start.
5 active paid accounts, first MRR
Scale
EU commercial launch, Growth and Enterprise plans, ChargerPilot live control with human approval.
10 pilots converted, €300–500k ARR
Expansion
US and Asia, hub partnerships, full CI/CD integrations, OCPP 2.1 and OCPI 2.3.0.
30 customers, ~€1M ARR
Live today: European regional CPO, 200+ chargers · US commercial fleet depot · Canadian hardware OEM.
The ask: €1M seed to capture the protocol layer
18+ months of runway to finish the enterprise rollout: CI/CD API, test harness, single-tenant VPCs. Convert 10 pilot customers and reach €300–500k ARR by month 18.
~€1M
Finish SaaS, active sales, 5–10 proofs of concept.
10 pilots converted · €300–500k ARR by month 18
€5–7M
Scale Europe, smart charging, V2G.
30 paying customers · ~€1M ARR
€5–10M
US and Asia, OCPP-Ready program.
Industry reference platform
- 65% engineering, 3 senior systems hires.
- Distributed protocol engineers (Rust/Go) to scale edge gateways and automated test harnesses.
- 25% go-to-market and solutions.
- A dedicated enterprise solutions engineer to lead CPO migration pilots.
- 10% compliance and operations.
- SOC 2 Type II certification and enterprise legal MSAs.
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.
Appendix: technical and financial deep-dives
Reference material for Q&A: edge gateway latency, regulatory penalty schedules, unit economics, protocol coverage, and capital allocation.
- Technical architecture and egress latency. Zero-copy WebSocket proxy, connection pooling, and sub-5 ms overhead.
- Regulatory timelines and penalties. EU AFIR (2023/1804) and US NEVI (23 CFR Part 680) enforcement.
- Unit economics and expansion model. Modeled 82%+ gross margin, cohort expansion, and negative churn mechanics.
- Protocol compatibility matrix. OCPP 1.6 and 2.0.1, OCPI 2.1.1 and 2.2.1, plus the 2.1, 2.3.0 and ISO 15118-20 roadmap.
- Capital allocation and runway model. €1.0M seed allocation, burn sensitivity, and Series A gates.
- Documentation suite. Investor FAQ and executive memo in the pitch-docs repository.
High-concurrency edge proxy architecture
Target architecture. Stateless proxy nodes terminate charger WebSocket connections at the nearest edge. They validate payloads against the OCPP 1.6 and 2.0.1 schemas and multiplex them to CPMS backends over persistent TLS pools.
- Zero-copy payload inspection. Design target of sub-5 ms latency overhead on round-trip commands such as RemoteStartTransaction and Authorize.
- Connection multiplexing. Thousands of concurrent charger WebSocket sessions consolidated into pooled keep-alive backend connections, modeled to cut CPMS server load by up to 70%.
- Schema-aware relay. OCPP 1.6 and 2.0.1 message schemas ship with the gateway, so malformed payloads stop at the edge. In-flight 1.6 to 2.0.1 translation is on the roadmap.
- Fail-safe offline mode. Designed so that if an upstream CPMS drops, the gateway answers Heartbeat and buffers offline sessions, and chargers avoid a local lockout.
| Regulation | Effective | Core technical requirement | Non-compliance risk |
|---|---|---|---|
| EU AFIR (2023/1804) | April 2024 enacted; April 2025 open data | Transparent ad-hoc pricing, dynamic status via National Access Points, OCPI 2.2.1+ | Statutory operating fines, exclusion from public highway concessions |
| US NEVI (23 CFR Part 680) | Active federal rule | >97% uptime per charging port, mandatory OCPP 2.0.1 and OCPI 2.2.1, automated reporting | Clawback of $5B federal grant allocations |
| UK Public Charge Point Regulations | November 2024 | 99% reliability on rapid networks, open data within one year, 24/7 helpline logs | Up to £10,000 civil penalty per non-compliant charger |
Regulatory enforcement timelines and mandates
Compliance carries statutory fines and subsidy disqualification. EV Cloud makes the evidence automatic.
- Automated uptime telemetry. Continuously computes and exports NEVI-grade >97% uptime proof.
- Normalized open data. Standard OCPI endpoints for the National Access Points EU member states require.
- Protocol future-proofing. Bridges legacy OCPP 1.6 hardware to mandated OCPP 2.0.1 standards without hardware replacement.
| Tier | Price | Scope (public caps) | Modeled gross margin | Expansion driver |
|---|---|---|---|---|
| Starter | $0 (free) | 300 online hours / month, 2 backends | 88% | Developer onboarding, pilots |
| Growth | $500/month ($6k/year) | 18,000 online hours / month, 4 backends | 84% | Regional pilot fleets, smart proxy routing |
| Enterprise | Custom ($25k–$80k / year) | Custom hours, unlimited backends | 82% | Estate-wide routing, custom VPC, 99.99% SLA |
SaaS unit economics and cohort expansion
COGS is cloud compute and egress bandwidth. Lightweight pooled WebSocket traffic keeps infrastructure cost per connected charger negligible, so the model holds software gross margin above 82%. Margins below are modeled, not yet twelve months of billing data.
- Charger volume expansion. CPOs grow their physical footprint 35–50% a year; software revenue scales with the connected estate.
- Protocol add-ons. OCPI roaming automation, ChargerPilot AI triage, and dynamic load balancing modules.
- The switching-cost moat. Once the EV Cloud endpoint is written into charger firmware, replacing the layer reintroduces the truck-roll risk operators set out to eliminate.
| Standard | Role in the ecosystem | EV Cloud support | Normalization function |
|---|---|---|---|
| OCPP 1.6 | Legacy charger-to-CPMS | Native gateway | Fixes missing timestamp keys, non-standard meter values |
| OCPP 2.0.1 | Modern secure standard | Native gateway | Device model mapping, security profile 3 enforcement |
| OCPP 2.1 | Energy coordination, V2G-ready | Roadmap | Listed after docs and validation ship |
| OCPI 2.1.1 | CPO-to-eMSP roaming | Handshake engine | Legacy roaming bridge, tokens and CDR normalization |
| OCPI 2.2.1 | Modern EU roaming | Handshake engine | Real-time tariffs, reservations, commands module |
| OCPI 2.3.0 | Latest roaming release | Roadmap | Version negotiation today resolves 2.3.0 peers to 2.2.1 behavior |
| ISO 15118-20 | Plug & Charge, V2G | Phase 4 roadmap | PKI certificate validation, bidirectional energy flow |
Protocol matrix and dialect normalization
OEMs implement optional fields differently, use proprietary error codes, or violate schemas. EV Cloud sits in the middle and normalizes these differences into clean, compliant protocol streams.
- Dialect filtering. Detects known firmware deviations across 100+ hardware models, such as invalid enums in StatusNotification or malformed MeterValues.
- In-memory sanitization. Rewrites payload structures before forwarding to the CPMS, preventing backend exceptions and transaction drops.
| Category | Share | Total | Key allocations and first hires |
|---|---|---|---|
| Engineering and product | 65% | €650,000 | 3 senior protocol engineers (Rust/Go, WebSocket edge, SOC 2 VPCs) |
| Solutions and GTM | 25% | €250,000 | 1 enterprise solutions architect (CPO migration onboarding and pilots) |
| Compliance and operations | 10% | €100,000 | SOC 2 Type II audit, enterprise MSAs, patent filings |
Capital allocation and 18-month runway model
€1M buys 18+ months of runway to reach 10 enterprise pilots and €300–500k ARR. Most of the capital goes into engineering to widen the protocol lead, with measured spend on solutions engineering to speed enterprise conversion.
- Initial net burn. ~€45,000 / month: founders, cloud infrastructure, and initial contractor support.
- Peak net burn after hiring. ~€65,000 / month with a fully staffed six-person team from month 6.
- Runway horizon. 18+ months of operational runway to the Series A inflection.
- Series A milestones, months 12–15. 10 enterprise pilot conversions, 15,000+ connected chargers, €300k–€500k ARR with net revenue retention modeled at 130%+.