PlugEV: OCPP 1.6-J EV Charging Management System

PlugEV runs on OCPP 1.6-J, the JSON-over-WebSocket variant, which is what the vast majority of chargers deployed in India speak today. We built a per-vendor compatibility layer because real chargers rarely implement the spec cleanly. OCPP 2.0.1 is a larger protocol shift, so if you need it we scope that as a separate piece of work rather than assuming it out of the box.

The current production deployment runs 40+ chargers across 2 cities, and the Go gateway holds many concurrent WebSocket connections per instance without strain. Scaling to a few hundred chargers is mostly a matter of sizing the gateway and database, not rewriting anything. For very large networks we would talk through load and redundancy before committing to a number.

Riders can pay per session through UPI or cards via the Razorpay integration, with GST invoices generated automatically. RFID cards give operators an offline-capable fallback so charging still works when the API gateway is unreachable, with per-card limits and per-station permissions. Both flows can run on the same network at the same time.

Yes. The rider flow and operator dashboard can carry your branding, domain, and pricing rules rather than ours. Because we build and maintain the platform directly, we can tailor the billing logic and UI to how your network actually operates. White-labelling scope is agreed up front so you know exactly what is yours.

The production system runs in the cloud on CloudNX, our own India-region cloud platform, which suits most operators who want us to handle uptime and updates. On-premise or a dedicated private setup is possible when there are data-residency or network requirements, though it changes cost and support expectations. We will recommend the option that fits your team rather than pushing one model.

For a network using chargers we have already worked with, a straightforward rollout is typically a few weeks from kickoff to live sessions. New charger brands add time because we validate their OCPP quirks against our compatibility layer first. We give an indicative timeline after a short discovery call, once we know your hardware and billing needs.