EV charging platforms, from the charger protocol to the driver’s wallet.
Inople builds OCPP-based charging platforms for charge point operators. That means the charging station management system (CSMS) that talks to chargers, the operator CRM with live telemetry and remote diagnostics, and the driver app with reservations, dynamic pricing and wallet billing. We also help operators decide whether to build or buy.
What is OCPP, and what is a CSMS?
OCPP, the Open Charge Point Protocol, is the open standard chargers use to talk to a central system. A CSMS (charging station management system) is that central system. The CSMS starts and stops sessions, reads meter values, pushes tariffs and firmware, and receives fault alerts. A CPMS usually means the same thing with more emphasis on the operator’s business side.
What does an EV charging platform include?
An EV charging platform has three parts. The OCPP backend talks to the chargers. The operator CRM shows live charger status, faults and revenue. The driver app lets people find a charger, reserve a slot, start a session and pay. Our team has built all three, including sessions that stop on their own at the driver’s limit or wallet balance.
- OCPP backend
- Charger connections, session control, meter values and remote commands. We work with OCPP 1.6 and 2.0.1.
- Operator CRM
- Live station map, telemetry, fault alerts, remote diagnostics and per-site revenue.
- Driver app
- Station search, slot reservation, live session metering, wallet top-up and automatic stop.
- Pricing and billing
- Peak and off-peak tariffs, per-kWh or time-based pricing, and wallet or card billing.
Should a charge point operator build or buy a CSMS?
A charge point operator should usually buy a white-label CSMS at first and build only when per-charger fees or product limits start to hurt. Codibly and OCPPLab put the break-even for a custom platform somewhere between 2,000 and 10,000 chargers. A common middle path is a custom driver app and billing layer on top of an existing CSMS.
| White-label SaaS (e.g. AMPECO, Monta) | Custom CSMS | |
|---|---|---|
| Time to launch | Weeks | MVP in 3 to 4 months, production in 12 to 18 months (Codibly, OCPPLab) |
| Cost model | Per-socket monthly fees plus transaction fees | Upfront build, then hosting and maintenance |
| Fits best | Small and mid-size networks, standard products | Large networks, unusual pricing or hardware, own brand |
| Control | Vendor roadmap | Your roadmap and your data |
Which rules shape charging software in the US and the UK?
In the US, federally funded NEVI stations must follow 23 CFR 680: OCPP 2.0.1 between charger and network, OCPI 2.2.1 between networks, ISO 15118 Plug & Charge, and average port uptime above 97%. In the UK, the Public Charge Point Regulations 2023 require 99% reliability on rapid chargers, open data over OCPI and contactless payment.
Both regimes turn into software requirements. The CSMS has to record charger status accurately enough to prove uptime, publish live data over OCPI, and keep tariffs and payment flows within the rules. FHWA reissued NEVI guidance in August 2025, but the Part 680 standards still apply to NEVI projects, so check your state DOT’s current plan.
| United States (NEVI, 23 CFR 680) | United Kingdom (Public Charge Point Regulations 2023) | |
|---|---|---|
| Who it covers | Stations built with NEVI federal funds | Public charge points, with most rules on 8 kW+ and rapid (50 kW+) units |
| Charger protocol | OCPP 2.0.1 required from February 28, 2024 | No OCPP version set by the regulations |
| Data and roaming | OCPI 2.2.1 between networks; station data free to third parties by API | OCPI open data, status changes within 30 seconds; roaming at all public charge points |
| Uptime | Average port uptime above 97%, measured monthly over 12 months | 99% average reliability across a rapid network over the calendar year |
| Payments | Price shown before the session starts, based on $/kWh | Contactless on new 8 kW+ and existing 50 kW+ units; maximum price in pence per kWh |
Where can AI help an EV charging network?
AI can help an EV charging network find patterns a person would miss in charger data. Useful builds include predicting faults from OCPP logs before a charger goes offline, flagging billing sessions that do not reconcile, and suggesting tariffs by site and time of day. Session control and billing rules should stay as plain, predictable code.
Is there demand for charging software in Africa?
Yes, though the market is still small. South Africa has a few hundred public charging sites run by a handful of operators, and its chargers use OCPP. Kenya’s growth is in electric motorcycles and battery swapping, where the software need is fleet, swap station and mobile money billing rather than classic car charging.
Frequently Asked Questions
How long does it take to build an OCPP backend?
Industry benchmarks from Codibly and OCPPLab put an MVP at about 3 to 4 months and a production-grade platform at about 12 to 18 months. The range depends on OCPP version, charger hardware mix, roaming and billing needs.
OCPP 1.6 or 2.0.1: which should we implement?
Support both. Many installed chargers still run OCPP 1.6, and the two versions are not compatible, so the backend has to speak each one. OCPP 2.0.1 adds mandatory security profiles, a device model and better smart charging, and it is required for NEVI-funded US stations. OCPP 2.1 builds on 2.0.1.
What is the difference between a CSMS and a CPMS?
Both refer to the central software that manages chargers. CSMS is the term used in the OCPP specification. CPMS (charge point management system) is often used by vendors and tends to include more of the business side such as pricing, customers and reporting.
How does wallet billing work for EV charging?
The driver tops up a wallet in the app. When a session starts, the platform reserves funds, meters energy through OCPP, and stops the session automatically when the driver’s limit or balance is reached. The final amount is charged from the wallet.
Can you build only the driver app on top of our existing CSMS?
Yes. If your CSMS exposes APIs, we can build a branded driver app and billing layer on top of it. This is often the fastest way to own the customer experience without replacing the backend.
Do you support roaming with OCPI?
OCPI is the protocol for roaming between charging networks. We can include an OCPI integration in scope. Our past platform work centered on OCPP and the driver and operator apps.
Tell Us What You’re Building
A first call is free. You talk to the people who would lead the work, and you leave with a clearer plan whether or not we work together.