01About zevOS
Charging networks fail on software, not on hardware
zevOS exists because the difficult part of running EV charging in India was never the chargers. It was everything that had to work around them.
Anyone can install a charge point. Making it earn is a different problem: drivers have to be able to pay without downloading anything, tariffs have to reflect a landed electricity cost that includes demand charges, receipts have to satisfy GST, the site owner has to be paid a share they can verify, and somebody has to know the moment a unit stops working — at two in the morning, four hours from the nearest technician.
None of that is the business an operator set out to be in. All of it is required before that business exists at all.
We build the platform that handles it. zevOS connects chargers over OCPP, runs the driver payment flow from a QR code without an app install, prices sessions by energy, time and audience, settles revenue with site partners, and gives operations teams the diagnostics to fix faults from a desk instead of a van.
We are deliberately narrow. zevOS does not manufacture hardware, does not operate its own charging network, and does not compete with the operators who run on it. The only way we grow is if their chargers earn more — which is why the commercial model has no subscription, and why the platform fee applies to sessions that actually happened.
What we will not do
The refusals are the position
Anyone can list features. What actually shapes a platform is what it declines to become.
We will not manufacture chargers
A platform that sells hardware has a reason to make other vendors work slightly worse. Ours is the only business model where your hardware freedom costs us nothing.
We will not operate a network
The moment we run our own chargers, we are competing with the operators on our platform for sites and for drivers. So we do not.
We will not own your drivers
Your merchant account, your descriptor, your app, your receipts. We do not market to your drivers and we do not appear to them.
How we work
Six things we actually hold to
Not a poster. These are the arguments we have internally when a decision is close.
The operator owns the relationship
The driver app, the receipts, the portal and the merchant account carry the operator’s name, not ours. We are the engine, never the badge on the bonnet.
Measure it or do not claim it
Uptime, utilisation and realisation are numbers we can produce with the records behind them. We would rather publish an honest 95% than an unverifiable 99.5%.
Hardware-agnostic, permanently
Locking an operator to a charger brand transfers our commercial problem onto their balance sheet. We speak OCPP and we intend to keep it that way.
Money is not a feature
Payments, tariffs, settlements and invoices are handled with the care of a ledger, not the enthusiasm of a product demo. Sessions reconcile or we fix it.
Built where it is used
GST, UPI, DisCom tariffs, demand charges, Bharat connectors and the realities of an Indian monsoon are not localisation work bolted onto a European product. They are the starting assumptions.
Ship for the second year
The decisions that matter — data model, tenant isolation, event architecture — are the ones that are expensive to change later. We take them slowly and then move quickly on everything else.
How it grew
What was built, in the order it was built
Origins
Built from operating, not from theory
zevOS began inside an EV charging operation, as the internal system for running real chargers, real drivers and real settlements — which is why the awkward parts, like partner revenue share and GST invoicing, were in it before the pretty parts.
Platform
A multi-tenant charging platform
The system was rebuilt as an isolated multi-tenant platform so other operators could run on it, with tenant scoping enforced in the data layer rather than trusted to individual queries.
Commerce
Payments, tariffs and settlements
QR-to-browser charging, pre-authorisation with automatic refunds, composable tariffs with time-of-day windows, and contract-driven partner settlement with session-level statements.
Operations
Diagnostics, smart charging and uptime
Remote triage, firmware over the air, per-EVSE charging profiles re-applied on boot, and availability measured per connector with the outage list retained.
Interoperability
OCPI roaming and OCPP 2.0.1
Roaming in both CPO and eMSP roles, and coexistence of OCPP 1.6J and 2.0.1 behind a single operational surface.
Now
Copilot and the next layer
A conversational layer over an operator’s own data that answers with the records behind the answer — in preview.
The entity
Who operates zevOS
zevos.ai and the zevOS platform are owned and operated by White Stripe Innovations Private Limited, incorporated in India.
Registered office: Plot No 361, Industrial Area Phase 1, Chandigarh - 160002, India
Talk to us
There is no sales process attached to asking a question
If you are working out whether a site is viable, which charger to buy, or how to structure a host agreement, we are happy to help with that whether or not you ever become a customer. Most of our best conversations start that way.
support@zevos.ai · +91 97797 57625
See what we have built
A walkthrough against your own chargers, tariffs and partner structure — not a canned demo tenant.