Skip to content
Start testing
About

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, CSMS releases, and roaming integrations at production scale. No hardware lab required.
A grid of identical virtual chargers runs off every edge. One of them, CP-201-008 on OCPP 2.0.1, sends BootNotification; the CSMS answers Accepted and its status changes from Booting to Available: one virtual charger came online among many, with no hardware lab.

Standards we follow

OCPPLab covers EV charging protocol testing from a single charger smoke test to high-volume load runs, from CSMS regression to OCPI partner-readiness checks. We track the upstream specifications continuously. Our test suites and protocol behavior are kept current against:

OCPP

Virtual charge points against your CSMS, from single-charger smoke tests to load runs

Specification: Open Charge Alliance (opens in a new tab)

  • OCPP 1.6Including the Security Whitepaper edition 2

    Status
    Shipped

  • OCPP 2.0.1

    Status
    Shipped

  • OCPP 2.1

    Status
    Shipped

OCPI

Roaming party as a CPO or eMSP, including connections to hubs such as GIREVE

Specification: EVRoaming Foundation (opens in a new tab)

  • OCPI 2.1.1

    Status
    Shipped

  • OCPI 2.2.1

    Status
    Shipped

  • OCPI 2.3.0Including the Payments module and the OCPPLab Bookings extension

    Status
    Shipped

OCPI modules: Credentials, Locations, Sessions, CDRs, Tariffs, Tokens, Commands, ChargingProfiles, HubClientInfo.

Adjacent standards

  • ISO 15118Plug and Charge

    Specification
    ISO (opens in a new tab)
    What OCPPLab does
    Plug and Charge certificate messages over OCPP only; the EV-to-charger ISO 15118 link is not simulated
    Status
    Partial

  • OICPHubject

    Specification
    Hubject (opens in a new tab)
    What OCPPLab does
    We do not simulate OICP; we prepare your OCPI side before Hubject onboarding
    Status
    Not simulated

How we work

  1. 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.

  2. Cloud, not lab

    Hardware labs are slow, expensive, and don't scale. We built OCPPLab so engineering teams can validate firmware, CSMS releases, and roaming integrations from a browser without coordinating physical chargers.

  3. 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.