01Why zevOS
Five reasons, and three cases where you should pick something else
Comparison pages that only argue one way are worth nothing to a buyer. This one includes where the alternatives genuinely win.
The case for
What is actually different
The business model does not conflict with yours
We do not manufacture chargers, so we have no reason to make a competitor’s hardware work slightly worse. We do not run our own network, so we are not bidding against you for sites or drivers. And there is no subscription, so we only earn when your chargers earn. Those three are structural rather than featural, which means they cannot be copied by a competitor next quarter without changing what they are.
Built for the Indian market from the first line
GST invoicing with place-of-supply logic, UPI as a first-class payment method, per-kWh and per-minute tariffs with DisCom-shaped time-of-day windows, demand charges in the load-management model, and Bharat and LEV connectors for the segment where India’s electrification volume actually is. None of that is localisation applied to a European product.
Money handled like a ledger
Payments, refunds, wallet movements and partner settlements post against the session they belong to, and every aggregate traces back to the rows that produced it. Tariffs are snapshotted onto sessions at start, so repricing tomorrow never rewrites yesterday’s invoice. This is unglamorous and it is the part that decides whether your month-end closes.
Operations designed around the cost of a van
The marginal cost of a charging network is field dispatches, and a large share of them end with nothing more than a power cycle. Decoded faults, a remote triage ladder, diagnostics pulled before dispatch and firmware over the air exist because that is where the money goes.
You can leave
Full data export through the console and the API, at any time, without asking. Hardware that speaks OCPP can be pointed at another endpoint. Your merchant account, your drivers, your brand. Portability is a property of the platform rather than a concession negotiated at renewal — which also means we have to keep earning it.
The case against
When something else is the right answer
If one of these describes you, we would rather say so now than three months into an evaluation.
Build it yourself
Good when
You have an engineering team, a genuinely unusual requirement, and enough scale that platform fees exceed the cost of the team.
What it costs you
An OCPP gateway, a payments and refunds engine, a tariff resolver, a settlement ledger, GST invoicing, driver surfaces and an operations console — before you sell a single unit of energy. Most teams underestimate the billing edge cases, not the protocol.
A global CSMS platform
Good when
You operate across several countries, need certifications we do not yet hold, or have a European roaming-first business model.
What it costs you
GST, UPI and DisCom tariff structures arrive as configuration rather than as first-class concepts, subscription pricing lands before your utilisation does, and support runs on a timezone that is not yours.
Your charger vendor’s software
Good when
You have a single-vendor estate, modest ambitions for pricing and partner structures, and you value one throat to choke.
What it costs you
Your platform choice is now tied to your hardware choice permanently. Changing vendor means changing systems, which quietly removes your negotiating position on every subsequent purchase order.
Ask us the hard question first
Bring the requirement you think will disqualify us. That is a more useful thirty minutes than a feature tour.