Virtual chargers
Start without hardwareDeploy a browser-based OCPP simulator with locations, connectors, sessions, logs, firmware, certificates, and OCPP configuration in one workspace — no physical EV charger required.
The browser-based emulator for EV charging software. Spin up virtual charge points and roaming connections instantly. Test, debug, and validate your system at scale without buying physical hardware.
Spin up a virtual EV charger in 2 minutes. Point your software at it, simulate OCPP and OCPI traffic, and inspect every message in real time.
A quick view of the browser-based OCPP simulator and OCPI testing workspace your team uses to validate EV charging software against a CPMS.
EV charger profile catalog
Simulate the EV charger profiles your team actually deploys.
Vendor-style profiles with realistic connector layouts, current types, supported kWh, and OCPP behavior for CPMS testing.
The core EV charging and energy protocols OCPPLab speaks, from charger-to-backend communication through roaming, smart energy, and industrial device control.
The Open Charge Point Protocol is an application protocol for communication between electric vehicle charging stations and a central management system.

The Open Charge Point Interface is a protocol that connects charge point operators and e-mobility service providers, enabling EV roaming, location and tariff data, and the exchange of charging sessions and billing records between networks.

EEBUS is a protocol suite for the Internet of Things that aims to standardize the interface between electrical consumers, producers, storages and (logical) managing entities.
Modbus is a data communications protocol. It is a de facto standard communication protocol and widely used to connect industrial electronic devices.
Virtual chargers, protocol routing, roaming validation, and monitoring probes. One workspace, no hardware.
Deploy virtual chargers, run a roaming backend, and stress-test your system at scale in minutes.
Simulate any charger brand. Test your software compliance across OCPP 1.6 and OCPP 2.0.1 without physical hardware.
“Hardware labs still matter, but they should confirm behavior you already rehearsed. Make the first integration failure happen in a browser, not during a field rollout.”
An OCPP and OCPI simulator to deploy chargers, route traffic, test roaming, monitor health, and turn repeated checks into release workflows.
Deploy a browser-based OCPP simulator with locations, connectors, sessions, logs, firmware, certificates, and OCPP configuration in one workspace — no physical EV charger required.
Route charger traffic through OCPPLab, inspect every OCPP message, and reproduce CPMS integration failures before they reach production infrastructure.
Use the OCPI simulator to validate partner-facing locations, EVSEs, connectors, tokens, sessions, commands, charging profiles, and CDR-style workflows before go-live.
Send OCPP and OCPI actions from the browser, inspect responses, then turn repeated checks into reusable release workflows.
Run synthetic probes across EV charger, CPMS, and OCPI roaming paths so boot failures, slow responses, and broken endpoints show up early.
Ask questions about charging data, generate charts, inspect query results, and review proposed OCPP actions before sending them.
Test the protocol versions your team actually ships: OCPP 1.6, OCPP 2.0.1, OCPI 2.1.1, and OCPI 2.2.1. From the OCPP 2.0.1 simulator to OCPI testing for roaming, keep charger behavior, roaming flows, and regression coverage in one place.
Hardware labs and partner sandboxes are still important, but they are slow places to discover basic integration bugs. Use the OCPPLab simulator earlier in the release cycle for CSMS testing and to validate the behavior your team controls.
Replay the charger, authorization, transaction, or roaming path that failed without waiting for the same hardware state.
Create model-like EV charger profiles, connect them to your CSMS, and verify setup before devices arrive on site.
Check OCPI data and commands before a real CPO, eMSP, hub, or network partner is on the critical path.
Turn repeated manual checks into workflow runs with logs your team can inspect after every product change.
Point your CPMS at one OCPP endpoint. Our OCPP simulator runs OCPP 1.6J and OCPP 2.0.1 flows against virtual EV charger profiles, so you start CPMS testing without touching physical hardware.
Choose EV charger profiles for an interop run, or spin up virtual roaming partners with the built-in OCPI simulator to test OCPI before the real network goes live.
Send OCPP and OCPI actions from the browser, inspect responses, and save repeated EV charger or roaming checks as release workflows.
Use live dashboards, replayable logs, and shareable traces to show what passed, what failed, and what changed between releases.
Charger onboarding, CPMS release QA, OCPI roaming checks, and hardware proxying — from the same workspace.
Exercise BootNotification, Authorize, transactions, MeterValues, and charging profiles against virtual EV chargers before each release. Run CPMS testing and OCPP load testing with many concurrent stations, and replay failed sessions instead of rebuilding hardware state.
Validate model-like EV charger profiles, connector layouts, and OCPP configuration against your CPMS before hardware arrives on site.
Spin up virtual partners for OCPI roaming testing and walk through Locations, Tokens, Sessions, Commands, Tariffs, and CDR flows before connecting to a live OCPI hub.
Route a physical EV charger through the OCPP proxy, inspect every message, and reproduce field failures with replayable logs your team can share.
Before you book a demo, check the pieces that matter: OCPP and OCPI simulator coverage, charger profiles, roaming workflows, product screens, pricing fit, and support options.
OCPP 1.6, OCPP 2.0.1, OCPI 2.1.1, OCPI 2.2.1
Version pages, supported modules, and example flows are on the site. Verify protocol scope before you book a sales call.
Review the protocolsABB, EVBox, Wallbox, Alfen, OCPI hub-style workflows
Vendor-profile and roaming workflow pages show whether OCPPLab covers the charger and OCPI paths your team validates today.
See the integrationsLogs, workflow runs, charger profiles
The site shows protocol logs, reusable workflow runs, and charger-profile surfaces. Decide if OCPPLab is operationally useful, not only conceptually interesting.
Explore the featuresStarter, Pro, Enterprise
Pricing and plan-fit sections spell out which plan matches early validation, release QA, or enterprise-scale rollout work.
Compare plansCloud now, on-prem or hybrid when needed
Smaller teams start in the cloud. Enterprise buyers walk through on-premises or hybrid deployment, plus dedicated support, before procurement begins.
Talk through deploymentSelf-serve trial or scoped demo
A technical buyer starts on the free Starter plan for early validation, or books a scoped demo when vendor coverage, roaming, or support requirements get complex.
Book technical demoAnswers about protocols, charger profiles, scale testing, security, and pricing.
Book a 30-minute demo and run a real scenario against your stack with our OCPP simulator. Or start free and launch your first virtual EV charger in minutes.

How OCPP AI agents automate EV charging across 5 use cases — fault diagnosis to smart charging — plus architecture, guardrails, and how to test them safely.
Read guide →

LLM vs SLM for EV charging software: when to use each across OCPP fault triage, edge monitoring, and AI agents, plus a hybrid pattern for 5,000+ chargers.
Read guide →

Compare the 4 best OCPP simulators and emulators for CPMS testing: cloud platforms, open-source libraries, and field tools for OCPP 1.6 and 2.0.1 workflows.
Read guide →