OCPP Software for EV Charging Networks
Run every OCPP 1.6J and 2.0.1 charger from one backend today, ready for OCPP 2.1 as your hardware moves on.
YoCharge is OCPP compliant EV charging software for charge point operators. Connect chargers from 60+ brands, roam with other networks over OCPI 2.2.1, and take payments straight into your account, all from one platform.
- OCPP 1.6J
- OCPP 2.0.1
- OCPI 2.2.1 roaming
- OCPP 2.1-ready
charger brands integrated
countries with live networks
uptime on AWS, Google Cloud and Azure
charging sessions
What is OCPP software?
OCPP (Open Charge Point Protocol) is the open standard that lets an EV charger talk to the software that runs it. The standard is maintained by the Open Charge Alliance. OCPP software, also called an OCPP backend, OCPP server, OCPP platform or CSMS (charging station management system), is that software: it starts and stops sessions, reads meters, sets tariffs, pushes firmware and keeps every charger visible from one dashboard. Because the protocol is open, you can mix charger brands and never be locked to one hardware vendor.
OCPP versions we run
Most installed chargers run OCPP 1.6J, and newer hardware ships with 2.0.1. YoCharge runs both side by side, and the platform is ready for OCPP 2.1.
| Version | On YoCharge | What it adds | Who needs it |
|---|---|---|---|
| OCPP 1.6J | Supported | The version most installed chargers run: remote start and stop, status, metering, firmware updates, smart charging profiles | Every network running today’s chargers |
| OCPP 2.0.1 | Supported | A richer device model, stronger security profiles, improved transaction handling and ISO 15118 support | Operators buying new hardware |
| OCPP 2.1 | Ready | The newest version, adding bidirectional (V2G) charging and more energy-management features | Networks planning ahead |
Versions aren’t backward-compatible on the charger side. Moving a charger from 1.6J to 2.x is a firmware change on the charger; your backend handles both. If you’re comparing OCPP 1.6J software options, ask how each vendor runs mixed fleets. OCPP 2.1 vs 2.0.1: upgrade guide
What the backend does for your network
An OCPP charging management system should do more than speak the protocol. Six things YoCharge does for every charger you connect:
-
Real-time monitoring. Live status, sessions and energy for every connector, from one dashboard.
-
Remote operations. Diagnose, reset and update chargers without a site visit.
-
24/7 alert management. Faults are detected and flagged as they happen, so your team fixes them first.
-
Load management and smart charging. Control the load limits and current so a site never trips.
-
Plug & Charge. ISO 15118 automatic authentication: plug in and charge.
-
Payments and invoicing. Tariffs, gateways and automated invoices.
Works with the chargers you already have
YoCharge is hardware-agnostic: 60+ charger brands are already integrated, AC and DC, so you choose hardware on price and service, not on whose software it runs. Any compliant charger connects by pointing it at your YoCharge OCPP endpoint. That’s the job of OCPP EV charger software: one backend for every make on your network. Hardware-agnostic charging
OCPP and OCPI in one platform
OCPP connects your chargers to your backend. OCPI connects your backend to other networks, so your drivers can charge elsewhere and other networks’ drivers can charge on yours. YoCharge runs OCPI 2.2.1 in the same platform, so you don’t need separate OCPI and OCPP compliant EV software. EV roaming with OCPI 2.2.1
Built for India, used in 25+ countries
The standard India runs on: 99%+ of public chargers operating in India currently run OCPP 1.6J, and YoCharge runs it natively, alongside 2.0.1.
Payments in India: with white-label, your own drivers’ payments, including UPI and UBC, go straight to your account.
Global coverage: live in 25+ countries on 6+ data centres across AWS, Google Cloud and Azure, with 99%+ uptime for mission-critical deployments.
One platform for 100+ CPO partners: if you’re comparing OCPP software in India, ask for a live demo on your own chargers.
Switch without replacing your chargers
Thinking about whether to change EV charging software? Your chargers stay where they are.
Point your chargers to YoCharge. A configuration change on each charger: the OCPP endpoint URL, no new hardware.
Move your data. We help migrate your back office: sites, tariffs and users.
Go live. On the YoCharge-branded platform you can be live in a day. A white-label launch takes 7 days on our side once your payment gateway and app-store developer accounts are ready; third-party approvals can stretch it to up to 6 weeks.
Two ways to run it
YoCharge Managed
- Who runs it
- YoCharge manages everything
- Brand drivers see
- YoCharge
- Driver payments
- Collected by YoCharge; your earnings are credited weekly
- Pricing
- Per kWh
White-label
- Who runs it
- You do; YoCharge is your technical implementation partner
- Brand drivers see
- Yours
- Driver payments
- Your own drivers’ payments, including UPI and UBC in India, go straight to your account
- Pricing
- Quoted for your region and scope
Charging only your own vehicles? The Forever Free plan covers 1 property and up to 5 chargers, YoCharge-branded, for your own charging only. EV-CMS plans · White label EV charging software
Who uses OCPP software
Charge point operators: run a mixed-brand public network from one backend.
Charger manufacturers: give your customers a ready backend for the chargers you sell.
Fleet charging: schedule depot charging around your vehicles and your grid limit.
Oil & gas and fuel retailers: add charging to your forecourts without building software.
Utilities and DISCOMs: see and shape charging load across your network.
Get the OCPP Playbook:
versions, message flows and what to ask a vendor, in one free guide.
Download the playbookOCPP software: questions buyers ask
What is OCPP software?
It’s the backend that chargers connect to over the Open Charge Point Protocol. It runs sessions, tariffs, payments, monitoring and firmware for every charger on your network, whatever the brand.
Which OCPP versions does YoCharge support?
OCPP 1.6J and OCPP 2.0.1, side by side on one platform. The platform is ready for OCPP 2.1.
OCPP 1.6J, 2.0.1 or 2.1: which do I need?
Match your chargers. Most installed chargers run 1.6J; new hardware often ships with 2.0.1. You don’t have to choose one for the whole network: YoCharge runs mixed fleets.
What’s the difference between OCPP and OCPI?
OCPP links a charger to its backend. OCPI links one network’s backend to another’s for roaming. YoCharge does both.
Which chargers work with YoCharge?
Any OCPP-compliant charger. 60+ charger brands are already integrated, AC and DC.
Can I switch software without replacing my chargers?
Yes. You point each charger to the YoCharge OCPP endpoint, and we help move your sites, tariffs and users.
How long does it take to go live?
On the YoCharge-branded platform, in a day. A white-label launch takes 7 days on our side once your payment gateway and app-store developer accounts are ready; third-party approvals can stretch it to up to 6 weeks.
Is OCPP mandatory in India?
No, OCPP isn’t mandatory, but it’s the standard nearly everyone follows: 99%+ of public chargers operating in India currently run OCPP 1.6J. Choosing OCPP chargers keeps you free to change software and mix hardware brands.
Is there a free plan?
Yes. Forever Free covers 1 property and up to 5 chargers, YoCharge-branded, for charging your own vehicles only. It can’t be used to sell charging.
See your chargers on YoCharge
Bring your charger list. We’ll show how your network runs on one OCPP backend.
Book a demoOr email sales@yocharge.com