The cloud testing platform for OCPP and OCPI
OCPPLab is built by engineers who work in the OCPP and OCPI specifications every day. EV charging teams use it to validate firmware, CPMS releases, and roaming integrations at production scale. No hardware lab required.
What we focus on
OCPPLab covers EV charging protocol testing from a single charger smoke test to high-volume load runs, from CPMS regression to OCPI partner-readiness checks.
OCPP protocol depth
We work daily with OCPP 1.6 and OCPP 2.0.1, including the OCPP 1.6 Security Whitepaper edition 2 extension. The platform models charger behavior, common implementation differences, and JSON Schemas published by the Open Charge Alliance.
OCPI roaming workflows
We've built end-to-end OCPI 2.1.1 and 2.2.1 implementations covering the full module set — Locations, Sessions, CDRs, Tariffs, Tokens, Commands, ChargingProfiles, and HubClientInfo — including hub-mediated integrations.
CPMS testing at scale
Our load-testing infrastructure is designed for high-volume virtual charge point checks against a CPMS. We validate CPMS proxy paths, real-time authorization flows, and offline transaction replay under sustained load.
Vendor and hub coverage
We maintain vendor-style charger profiles and hub-oriented roaming workflows so teams can rehearse likely integration behavior before field testing. The catalog grows as the EV charging market does.
How we work
Spec accuracy first
Every claim on this site — every field name, every enum value, every status code — is checked against the authoritative OCPP and OCPI specifications. We'd rather link to the OCA or EVRoaming Foundation than paraphrase.
Cloud, not lab
Hardware labs are slow, expensive, and don't scale. We built OCPPLab so engineering teams can validate firmware, CPMS releases, and roaming integrations from a browser without coordinating physical chargers.
Open ecosystem
OCPP and OCPI are open standards. We publish technical guides, reference content, and the OCPPLab blog so any team building EV charging infrastructure has the documentation they need — whether or not they're our customer.
Standards we follow
We track the upstream specifications continuously. Our test suites and protocol behavior are kept current against:
Open Charge Alliance: OCPP specifications
OCPP 1.6, OCPP 2.0.1, and the OCPP 1.6 Security Whitepaper edition 2.
EVRoaming Foundation: OCPI specifications
OCPI 2.1.1 and OCPI 2.2.1 with the full reference module set.
Vehicle-to-charger communication for Plug & Charge and ISO 15118-20 V2G.
Roaming hub integration patterns, certification requirements, and OCPI / OICP routing.
Want to go deeper?
Browse the technical blog or start testing your own integration today.