Introduction

OCPPLab is the gateway layer between chargers, roaming partners, and your existing systems. It is not a full CPMS by default. Chargers keep one stable field URL on the OCPP gateway; you route to one or more backends, exchange OCPI with hubs and eMSPs, and operate day to day from Dashboard — without a big-bang hardware cutover.

These docs cover the protocols and product surfaces operators ship against: OCPP 1.6 and OCPP 2.0.1, OCPI 2.1.1 and OCPI 2.2.1, proxy routing, and Dashboard guides.

Why protocol docs live here

Physical chargers and live roaming partners are slow and expensive to test against. A single device can only be in one state at a time, firmware varies by vendor, and reproducing an edge case — a dropped WebSocket mid-transaction, a malformed MeterValues, a boot during an active reservation — is painful on real hardware.

OCPPLab and these guides make those scenarios clearer and more repeatable:

• Connect fleets over OCPP 1.6 and 2.0.1 on the same gateway
• Route to multiple CPMS backends — dual-run and cutover without changing station firmware
• Reference every action and OCTT test case for compliance work
• Roam with eMSPs and hubs on OCPI 2.1.1 and 2.2.1

When to use this docs set

Next steps

1. Quickstart
2. Concepts
3. Protocol deep dives under OCPP and OCPI

The left sidebar lists Overview, Actions, and Test cases only (not every message). Open the index pages below or use ⌘K search — hit labels include the protocol version (for example · OCPP 1.6) so same-named actions stay distinct.