Getting started
How OCPPLab fits into an EV charging stack and where to go next.
OCPPLab is the gateway and control plane for EV charging: an OCPP gateway for charge points, OCPI for roaming, multi-backend routing, and Dashboard for day-to-day operations. It is not a full CPMS by default — use it beside your stack, dual-run during migration, or as the field entry point long term.
What you get
| Area | What it covers |
|---|---|
| OCPP | Connect stations (1.6 / 2.0.1), sessions, smart charging hooks |
| OCPI | Roaming with eMSPs and hubs (2.1.1 / 2.2.1) |
| Multi-backend routing | Two backends, dual-run, and cutover without hardware resets |
| OCPPLab product | Dashboard, multi-tenant orgs, webhooks, architecture |
| Dashboard | Maps, chargers, charge sessions, observability, org settings |
Recommended path
- Read the Introduction for product scope.
- Read Concepts so OCPP vs OCPI roles are clear.
- Run the Quickstart against a sandbox or local stack.
- Dive into OCPP or OCPI depending on your first integration — including full action and test-case references.
- When you need multi-CPMS routing, follow Multi-backend routing.
- Use Dashboard for operator workflows once chargers are online.
Related marketing content
Deep-dive essays and buyer guides also live on the public marketing site (OCPP and OCPI product pages). Product docs here stay operator- and integrator-focused.