HubPilot
OCPI roaming for your network
A driver should not need your app to use your chargers. HubPilot speaks OCPI 2.2.1 — the protocol operators use to accept each other's drivers — so someone with a partner's app can charge on your stations, and yours can charge on theirs.
In developmentNot available yet, and not deployed. We are looking for operators with a real roaming partner to build it against.
What roaming actually involves
Four pieces, in the order a partnership needs them. OCPI is a protocol between operators, not between a charger and a CSMS — so none of this replaces OCPP, it sits beside it.
Credentials handshake
OCPI's mutual registration: two operators exchange tokens and version endpoints, and each discovers what the other supports. It is the step that turns a partner agreement into a working connection.
Locations and tariffs
Publish where your chargers are and what they cost, in the shape partners' apps already read — so your sites appear in their maps without a bespoke integration each time.
Session exchange
A visiting driver's session, reported to their home operator while it runs. Both sides see the same charge in progress rather than reconciling it afterwards.
Charge detail records
The CDR is the billing artefact — the final, signed account of one session that settles money between operators. It is the record a roaming dispute is argued from, so it is the one that has to be right.
Beside OCPP, not instead of it
OCPP is how a charger talks to your CSMS. OCPI is how your CSMS talks to another operator's. A network needs both to accept a visiting driver: OCPP to start the charge, OCPI to tell the driver's home operator it happened and what it cost.
That is why HubPilot is a separate product rather than a feature of ChargePilot. The roaming edge faces partners and holds no charger credentials, so a partner integration cannot reach your hardware.
Bring us a roaming partner
Roaming is only real once two operators agree, so this is being built with operators rather than ahead of them. If you have a partner in mind, we want to hear which one and which OCPI version they run.
Or join the waitlist for early access: