zevOS

01Solutions · Operator type

From a hundred chargers to a thousand without a bigger team

The problems change shape at scale. Individually, every charger is manageable; collectively, they generate more exceptions per day than any team can chase by hand. What you need is not more dashboards — it is scoping, batching and defensible reporting, so the team grows slower than the network.

Scaling charge point operator

Does this sound familiar

Where you probably are right now

  • 01You run chargers across several cities or states, on multiple hardware brands.
  • 02You have field teams, city managers and a support desk who each need a different slice.
  • 03Landlords and lenders are asking for uptime numbers you have to substantiate.
  • 04Settlement across dozens of site partners is consuming your finance team.

What gets in the way

The problems, and what answers each one

Every answer links to the feature that does the work, so you can check the claim rather than take it.

01

Everyone can see everything

Station groups restrict staff to their own territory, with view / operate / manage permissions per group. Owners retain full visibility. Restrictions apply to exports and API access too, not just the interface.

02

Configuration drift across brands and vintages

Read configuration keys in bulk, compare against your standard, and push corrections. Firmware rolls out by model cohort with a window and a retry policy.

03

Uptime claims you cannot prove

Availability is measured per connector from the platform side and separated from mere connectivity, with maintenance windows excluded. Any period, any site, with the outage list attached.

04

Settlement is a monthly fire drill

Contracts encode the split. A settlement run produces every partner’s statement at once, each line traceable to its sessions, ready for approval and payout.

05

Sanctioned load caps how many connectors you can install

Per-EVSE default limits and site-level load sharing let you install beyond the simultaneous maximum, with the limit enforced on the charger and re-applied after every power cycle.

What changes

What you can do that you could not before

  • Add a city without adding a control-room shift
  • Give each partner a portal instead of a monthly email thread
  • Produce contractual uptime reporting on demand
  • Reprice a whole corridor in one change

Commercial shape

Volume-tiered usage pricing

At scale the platform fee per kWh matters more than any feature gate. Tiering keeps the marginal cost of the thousandth charger below the cost of the first.

How pricing works

Questions

What people in your position ask

Can we run multiple brands under one account?

Yes — sub-brands can carry their own driver-facing identity, tariffs and partner sets while sharing one operations backbone.

How does zevOS handle our existing data?

Historical sessions, drivers, tariffs and partner contracts can be imported, so your reporting does not restart at zero on migration day.

Can a city manager be prevented from changing tariffs?

Yes. Station group permissions separate view, operate and manage, and pricing and settlement approval are permissioned independently of day-to-day operations — so a city manager can reset a charger without being able to reprice it.

Talk through your scaling charge point operator setup

Bring the specifics — the sites, the hardware, the constraints. That conversation is more useful than a demo.