If you run charge points, your stack usually means a CSMS, a roaming hub, a payment provider, and a support desk that still gets called at 2am. Getting a new site live should not require a multi-month integration project before the first paid session.
easyplug’s operator platform is built around OCPP — the protocol chargers already speak — so you can connect hardware, publish tariffs drivers see before start, and open roaming without rebuilding your stack from scratch.
What we ship for operators
- OCPP onboarding — connect stations and see live status
- Tariffs drivers can understand before they hit Start
- Load balancing so your grid connection stays within limits
- Roaming so you are not limited to a single app’s install base
- Agent-aware support that can re-route a driver when a unit faults
The same reliability metrics that matter to drivers — start success, stop success, stuck cable rate — matter to you as utilization and support cost.
Free to start
The operator platform is free to begin with. We make money when sessions succeed and drivers stay happy — not by locking you into a multi-year CSMS contract before you have proven demand at a site.
A simple path
- Connect a charger over OCPP 1.6 or 2.0.1.
- Publish a tariff.
- Open roaming when you are ready.
- Watch sessions and tickets in one place.
If status is wrong or authorization is slow, every eMSP’s drivers will blame their app. Clean OCPI locations, accurate max power per EVSE, and healthy auth latency are shared infrastructure. We wrote about the driver-facing side of that in roaming authorization failures .
What’s next
Operators dealing with stuck latches and stop failures should read Stuck cable and sessions that won’t stop . For the driver product story, see Welcome to easyplug .