01 ↗
Connect once.
Move further.
Exchange locations, tariffs, tokens, sessions, and charge detail records through a central OCPI connection.
Inside the infrastructure ↗ THE EV ROAMING CONNECTION LAYER
The connection
behind every
charge.
Great charging experiences start with connected networks. We bring charge point operators and mobility services together through one intelligent OCPI hub.
Built on open standards.Built for the real world.
CONNECTED BY DESIGN01 — NETWORK VIEW
↗chevohubONE CONNECTION. MORE POSSIBILITY.
⌁
Charge point operatorsInfrastructure → opportunity
↗
Mobility servicesAccess → experience
ϟ
Charging networksLocations · tariffs · availability
◎
Roaming partnersAgreements · authorization
OCPI 2.2.1 / 2.2
Sessions ↔ CDRs
Independent networks.Shared possibilities. ↗
CONNECTED ECOSYSTEM.OCPI 2.2.1 + 2.2
For charge point operators
For e-mobility providers
For roaming partners
01 / THE PLATFORM
LESS FRICTION. MORE CONNECTION.One integration.
A world of connections.
EV roaming is more than an API handshake. ChevoHub brings the technical exchange and the partner relationship into one operating layer.
Connect once.
02 ◎
Your network.
Your relationships.
Choose your roaming partners. Propose agreements, manage contracts, and control who can exchange data with whom.
Roaming agreement Active
Operator ↔ Mobility provider
EXPLICIT ACCESS. CLEAR ACCOUNTABILITY.03 ⌁
Complex operations.
Clear oversight.
Bring partner connections, charging activity, and technical diagnostics into a single administration workspace.
Locations & EVSEs↗
Sessions & CDRs↗
Partner access & audit trails↗
02 / YOUR PLACE IN THE NETWORK
Different roles.
Shared momentum.
Infrastructure that connects the people building the future of charging.
FOR CPOs
Put your charging network
on more journeys.
Make your infrastructure available to connected mobility providers, while keeping control over your roaming relationships.
- Share locations, availability, and tariffs
- Receive authorizations and remote commands
- Exchange sessions and charge detail records
- Define access through active agreements
03 / ENGINEERED TO CONNECT
OPEN STANDARDS. SERIOUS INFRASTRUCTURE.Open at the core.
Precise in every exchange.
A purpose-built Go core handles OCPI exchange. A dedicated partner workspace brings the operational context around it.
PROTOCOL EXPLOREROCPI / 2.2.1
// The start of a connected ecosystem
GET /ocpi/versions
{
"status_code": 1000,
"status_message": "Success",
"data": [
{ "version": "2.2.1" },
{ "version": "2.2" }
]
}
GET /ocpi/versions
{
"status_code": 1000,
"status_message": "Success",
"data": [
{ "version": "2.2.1" },
{ "version": "2.2" }
]
}
Based on the public discovery response ↗
The charging lifecycle, connected.
Credentials, locations, tariffs, tokens, sessions, CDRs, and commands — with sender and receiver interfaces across the core data modules.
Access follows the agreement.
Explicit, directional roaming agreements govern partner visibility. Party-scoped workspaces keep each partner’s operations in context.
Built for operational reality.
Background synchronization, retry handling, request logging, rate limiting, and multi-country OCPI identities support real integrations.
CredentialsLocationsTariffsTokensSessionsCDRsCommands
04 / FROM HELLO TO ROAMING
Your next connection
starts here.
Introduce your network
Start partner onboarding. Tell us about your business, your role, and your OCPI infrastructure.
Make the connection
Exchange credentials, register your OCPI identities, and verify the data flows relevant to your integration.
Activate your relationships
Establish roaming agreements with partners and bring your charging connections into operation.
A FEW THINGS, CLARIFIED.
Good questions.
Clear answers.
What is an OCPI roaming hub?+
A hub connects charge point operators (CPOs) and e-mobility service providers (eMSPs) through the Open Charge Point Interface. It routes charging data and interactions between connected partners, reducing the need to maintain a separate technical integration for every relationship.
Which OCPI versions does ChevoHub support?+
ChevoHub advertises OCPI 2.2.1 and 2.2. Supported core modules include credentials, locations, tariffs, tokens, sessions, CDRs, and commands. Your onboarding process establishes the capabilities used by your connection.
Do I keep control over my roaming partners?+
Yes. Roaming access is governed by explicit agreements between parties. The platform supports partner proposals, agreement lifecycles, versioned contract documents, and click-through signing.
Is ChevoHub a charging app or a charge point backend?+
ChevoHub is the roaming infrastructure between networks and mobility services. It complements your existing charging backend or customer application by connecting it to other OCPI partners.
How do we get started?+
Use the partner onboarding portal to introduce your organization. We’ll work through your OCPI connection, relevant modules, and roaming relationships with you.
THE NEXT CHAPTER OF CHARGING IS CONNECTED.