---
title: "OCPI gateway for roaming operations"
description: "GridOS is an OCPI gateway for CPO and eMSP roaming: credentials, tokens, locations, sessions, tariffs, and CDRs across OCPI 2.1.1, 2.2.1, and 2.3.0 without bolting partner logic into your core product."
canonical: "https://gridos.co/solutions/ocpi-gateway"
keywords:
  - "OCPI gateway"
  - "OCPI gateway software"
  - "OCPI roaming gateway"
  - "OCPI 2.2.1 gateway"
  - "OCPI 2.1.1 gateway"
  - "eMSP OCPI gateway"
  - "CPO OCPI platform"
  - "EV roaming gateway"
---

# OCPI gateway for roaming operations

> An OCPI gateway is the operator-facing control plane for roaming partners and hubs. Buyers looking for OCPI gateway software need production module coverage, partner onboarding, and clean separation from charger OCPP traffic. GridOS provides that OCPI gateway layer alongside the OCPP gateway.

GridOS is an OCPI gateway for CPO and eMSP roaming: credentials, tokens, locations, sessions, tariffs, and CDRs across OCPI 2.1.1, 2.2.1, and 2.3.0 without bolting partner logic into your core product.

## Audience

CPO roaming teams, eMSP platform leads, and interoperability owners.

## Best for

Operators launching or stabilizing OCPI roaming who need a dedicated OCPI gateway rather than ad-hoc partner scripts.

## Pain points

- Partner onboarding stalls on unclear OCPI module scope and credentials.
- Token, session, tariff, and CDR behavior diverges across partners and hubs.
- Roaming logic is hard-coded into the CPMS, so every partner becomes a release risk.
- OCPP charger ops and OCPI partner ops share no clean operational boundary.
- CDR and billing disputes lack a single source of truth for exchange status.

## Outcomes

- OCPI gateway for bilateral and hub-style partner connections.
- Clearer credentials, versions, and module ownership per partner.
- Session and CDR flows that ops can monitor without diving into raw dumps only.
- Separation between OCPP charger control and OCPI roaming exchange.
- Faster path from pilot partner to production roaming.

## FAQ

### What is an OCPI gateway?

An OCPI gateway is software that implements the Open Charge Point Interface so Charge Point Operators and e-Mobility Service Providers can exchange locations, tokens, sessions, tariffs, and CDRs. It standardizes roaming connectivity so each partner is not a custom integration project.

### Is an OCPI gateway the same as an OCPP gateway?

No. OCPP connects chargers to a central system. OCPI connects operators and service providers for roaming and partner data. Many production estates need both: an OCPP gateway for the field and an OCPI gateway for partners.

### Which OCPI versions does GridOS support?

OCPI connectivity is built for OCPI 2.1.1, OCPI 2.2.1, and OCPI 2.3.0 workflows. Live module scope still depends on what each partner enables.

### Do I need an OCPI proxy as well?

Some teams use “OCPI proxy” for multi-partner routing or hub fan-out. GridOS’s OCPI gateway covers partner connectivity and operational control; multi-partner patterns are handled as gateway policy rather than a separate consumer product name.

### Can OCPI gateway work with my existing CPMS?

Yes. Keep your CPMS for charger ops and use the OCPI gateway for partner exchange, or run both OCPP and OCPI layers with GridOS depending on architecture.

## Related

- Guide: [OCPI complete guide](https://gridos.co/ocpi)
- Explain: [What is an OCPI gateway?](https://gridos.co/blog/what-is-an-ocpi-gateway)
- Ops: [OCPI roaming operations solution](https://gridos.co/solutions/ocpi-roaming-operations)
- Billing: [OCPI CDR billing integration](https://gridos.co/blog/ocpi-cdr-billing-integration)