zevOS started because the operators we were working with kept describing the same gap. The hardware was fine. The software either assumed a European market, or was a dashboard with no billing behind it, or was a billing system with no real protocol support. Nobody had built the whole thing for people running charging businesses in India.
What it does today
- OCPP 1.6J across mixed hardware, with vendor quirks handled rather than documented as limitations.
- Sessions, meter values and remote control — start, stop, reset, unlock, availability.
- Driver payments through Indian gateways, with wallets, receipts and refunds.
- Tariffs with time-of-day windows and idle fees, snapshotted onto every session.
- Site partner revenue sharing with statements the partner can see themselves.
- A driver-facing app and a public map, both able to carry an operator’s own branding.
What it does not do yet
We would rather say this than have you find out during an evaluation. OCPP 2.0.1 is in build and not yet generally available. Plug-and-charge is not implemented. Grid services and aggregation are not on the near roadmap. And the platform is currently deployed in a single region — appropriate for an Indian operator, not yet for a multi-region one.
Where it runs
Indian infrastructure, with operational data kept in-region. Payments run through Indian gateways, which means card details never reach the platform at all.