Skip to content
Features

Product features for OCPP and OCPI operations

The signed-in workspace for chargers, virtual chargers, OCPP proxy, roaming, health checks, and the operator assistant. Protocol coverage is OCPP 1.6 / 2.0.1 / 2.1 and OCPI 2.1.1 / 2.2.1 / 2.3.0.
Start your testingBook technical demo

Charging

Operate charge points from the charger list, OCPP map, and station detail. Status comes from the live OCPP messages your chargers send.

  • Charger list for stations in the workspace
  • OCPP map for geographic station context
  • Station detail for connectors and commands
  • Managed chargers when you onboard hardware

Virtual charger

Run hardware-free OCPP simulation from fleet, sites, logs, workflows, and playgrounds, including load-testing scenarios.

  • Fleet and site layouts for virtual charge points
  • Session and protocol logs you can share
  • Workflows and playgrounds for repeatable checks
  • Load tests with up to 100 virtual chargers at once

OCPP proxy

Route charger traffic through backends, tokens, and routes. Inspect the message log when an integration fails.

  • Backend and token setup for proxy paths
  • Route configuration for charger traffic
  • Message log for request and response traces
  • Reproduce failures before they reach production CSMS paths

Roaming

Work OCPI partners, catalog, sync, commands, and charging profiles in one place. Coverage is OCPI 2.1.1 / 2.2.1 / 2.3.0.

  • Partner handshake and credentials
  • OCPI catalog for locations and tariffs
  • Sync, commands, and charging profiles
  • Logs for exchanges you actually ran

Observability

Watch protocol health across your paths. Metrics with no data show as unknown, never as zero.

  • Health hub for charger, CSMS, and roaming paths
  • Probe results when a check is configured
  • Empty or unknown states instead of fake zeros

Operator assistant

Ask the operator assistant on the home screen about your charging data once you sign in.

  • Chat from the home screen after sign-in
  • Ask about chargers, sessions, and protocol logs
  • Review proposed OCPP actions before sending
  • Docs cover fleet chat; dashboard URLs stay session-gated

Workspace areas and protocol coverage

The signed-in operator workspace covers charging, virtual charger, OCPP proxy, roaming, observability, and the operator assistant. Protocol coverage is OCPP 1.6 / 2.0.1 / 2.1 and OCPI 2.1.1 / 2.2.1 / 2.3.0.

Supported vendor and partner coverage

OCPPLab covers OCPP 1.6 / 2.0.1 / 2.1 and OCPI 2.1.1 / 2.2.1 / 2.3.0, plus the vendor and roaming contexts that show up in real projects.

  • OCPP protocol coverage

    Coverage
    OCPP 1.6, OCPP 2.0.1, and OCPP 2.1
    Typical proof path
    Transactions, status flows, smart charging, security profiles, and device-model behavior.

  • OCPI roaming coverage

    Coverage
    OCPI 2.1.1, OCPI 2.2.1, and OCPI 2.3.0
    Typical proof path
    Credentials, locations, sessions, CDRs, tariffs, ChargingProfiles, and hub-oriented workflows.

  • Vendor-oriented testing

    Coverage
    ABB, EVBox, Wallbox, Alfen, and mixed-fleet profiles
    Typical proof path
    Use vendor-specific integration pages and CSMS regression flows to validate compatibility before rollout.

  • Partner and hub validation

    Coverage
    OCPI CPO and eMSP roaming paths, including hub-routed objects and HubClientInfo
    Typical proof path
    Validate onboarding, hub-mediated flows, and partner-readiness before certification or go-live.
Representative scenarios

Two evaluations buyers run before they sign.

Two example paths buyers run during a typical evaluation. Use them as a checklist for what to verify in the trial, not as customer case studies.

Scenario 01

CSMS release team

Mixed-fleet OCPP regression before production rollout

Your backend team needs proof that a CSMS release will not break charger onboarding, transactions, or smart charging on the legacy fleet or the new one.

What they usually verify

  • Run OCPP 1.6, OCPP 2.0.1, and OCPP 2.1 chargers side by side. ABB, EVBox, Wallbox, and Alfen-style profiles in the same workspace.
  • Replay BootNotification, Authorize, MeterValues, TransactionEvent, reconnect, and remote-command flows. Inspect raw protocol logs as they happen.
  • Decide whether Starter, Pro, or Enterprise matches your charger volume, automation depth, and deployment needs.
OCPP 1.6 testingOCPP 2.0.1 testingOCPP 2.1 testingCSMS testing workflow

Scenario 02

Roaming interoperability team

OCPI partner onboarding before hub or bilateral go-live

Your roaming team validates credentials, tariffs, sessions, and CDR exchanges before a new OCPI connection touches a real partner or a certification path.

What they usually verify

  • Exercise credentials, locations, tokens, sessions, CDRs, and tariff sync. OCPI 2.1.1 / 2.2.1 / 2.3.0 in one workspace.
  • Connect to OCPI hubs such as GIREVE as a CPO or eMSP party, or test bilaterally. ChargingProfiles and HubClientInfo included.
  • Confirm in the first demo whether OCPPLab fits direct partner validation, certification prep, or wider roaming regression testing.
OCPI 2.1.1 testingOCPI 2.2.1 testingOCPI 2.3.0 testingOCPI roaming workflow

Dashboard guide

Workspace, chargers, virtual charger, proxy, roaming, and observability in docs.

Virtual charger guide

Fleet, sites, logs, workflows, and playgrounds without hardware.

Browse protocol pages

OCPP 1.6 / 2.0.1 / 2.1 and OCPI 2.1.1 / 2.2.1 / 2.3.0 coverage pages.

Compare pricing

See which plan fits your team size, charger volume, and automation needs.

Ready to open the app?

Open the operator workspace for chargers, virtual chargers, proxy, roaming, and health checks. Sign-in required.

Start your testingBook technical demo

Last updated: