Every charging network wants more drivers. One of the fastest ways to get them is to let drivers from other networks use your chargers, and to let your drivers use theirs. This is roaming, and it depends on interoperability: chargers, software and networks that work together through open standards.
The driver's problem
Without roaming, a driver on a long trip may need several apps and accounts, each with its own wallet. That friction pushes drivers towards the biggest networks and leaves smaller operators' chargers under-used.
How roaming works
Networks connect their platforms using OCPI, an open protocol. Once connected, a driver can find your station in their own app, start a session and pay through their usual account. The networks then settle payments between themselves. For the technical background, see what OCPI roaming is.
Why it matters for growth
- More drivers, same chargers: roaming partners' users become your customers without extra marketing.
- Higher utilisation: more sessions spread fixed costs, which is what decides profitability.
- Better coverage for your own drivers: your app becomes more useful because it covers more stations.
- Fleet business: fleets prefer partners whose drivers can charge widely on one account.
Interoperability starts with hardware
Roaming only works if your chargers and software follow open standards. Chargers that support OCPP can work with different management systems, and a management system that supports OCPI can connect to other networks. See OCPP and avoiding vendor lock-in.
What to agree with roaming partners
- Which locations and chargers are shared.
- How prices are shown to roaming drivers.
- Settlement terms and timelines.
- How live availability and faults are shared.
- Who supports a driver when something goes wrong.
Our approach
EVee Buddy is connected with several partner networks through OCPI, and our e-mobility services help operators join roaming without building the integrations themselves.