Pipelet
Pipelet / Products / OCPP Broker & Server
Integrators · CPOs

OCPP Broker & Server API token

WebSocket broker with digital twin, smart proxy and messaging for OCPP.

Open API docs → Got questions? Get in touch

No public UI — the API is documented and testable via a free developer token. Ask us for a sandbox.

OCPP orchestrator — charging infrastructure, Pipelet control layer, backends

Live from production

Truck HPC · 299 kW peak · 32 % → 100 %

A real fast-charging session from the Pipelet broker. Every session generates this analysis automatically — no configuration, straight from OCPP messages and MeterValues. Validity, SoC and energy curve, Wh per 1 % SoC, power curve and automatically detected derating events.

Session master data: start, end, duration, meter readings, energy delivered, SoC delta, validity flag, OCPP message count.
Session master data — validity, meter readings, SoC, message count
Line chart: delivered energy in kWh and state of charge in % over time, with the CC→CV transition marked.
Energy & SoC over time — CC→CV transition marked automatically
Chart: watt-hours per 1 percent SoC over time; visible kink at the transition into the constant-voltage phase.
Wh per 1 % SoC — battery cell health indicator
Charging-power curve in kW over time; peak at 299.2 kW, drop at 96 % SoC, taper at session end.
Power curve — 299 kW peak, automatic CV tapering
List of automatically detected derating events: sustained power drops ≥ 15 % from the running peak, classified as CV tail or anomaly.
Derating events — automatically classified (CV tail vs. anomaly)

OCPP Broker is the scalable WebSocket gateway between charge points and your backend. Persistent sessions into the four-digit range per node, digital twin layer with complete state cache, smart proxy for protocol normalisation.

Multi-backend routing per charger, per group, or per site. Zero-downtime migration through parallel operation. Session stabilisation when field communication is unstable — running charging sessions are protected, not aborted.

For integrators and CPOs that need robust OCPP infrastructure without being locked into a monolithic CPMS. The broker runs independently — you combine it with Pipelet CPMS, your own backend, or both in parallel.

What to expect

✓

Digital twin

Complete state cache for every charge point. Query the twin instead of the hardware — faster, more stable, resource-friendly.

✓

Multi-backend routing

Route per charger, per group or per site to different backends. Failover on outage, parallel operation during migration.

✓

Smart proxy

Protocol normalisation between OCPP 1.6 and 2.0.1 — charger-specific quirks are absorbed centrally instead of per CPMS integration.

✓

Session stabilisation

Running charging sessions survive network outages or backend glitches. Reconnect logic, message queue, automatic resync.

Common scenarios

1

Backend migration across 10,000 chargers

Legacy CPMS and new CPMS run in parallel. The broker routes 1% first, then 10%, then site by site — one click and the group is back on legacy if issues arise.

2

Heterogeneous hardware

Five manufacturers, five OCPP dialects. The broker normalises, your CPMS never sees the quirks. Tests against a homogeneous protocol.

How OCPP Broker & Server fits into the suite

Integrates with
OCPP Broker & Server https://developer.pipelet.com/api/ocpp-server/
Driver Portal Home charging with three data sources — wallbox, Fleet Portal Fleet management, driver management, RFID and bi CPMS Core The new operator UI: sites, charger commands, vo

Frequently asked questions

Is Pipelet available as source code?
Yes. Every module is available as a source-access package — complete with Docker Compose, documentation and an SLA support channel. You can audit, customize and self-host.
Which OCPP versions are supported?
Full OCPP 1.6 and 2.0.1 including Security Profiles, Smart Charging, and ISO 15118 Plug & Charge.
Can I use individual modules only?
Yes. Every module is standalone — you can deploy e.g. just the OCPP Broker as infrastructure and build your own CPMS on top.
What does onboarding look like?
We start with a 30-minute call to scope requirements. After that you get a concrete proposal with modules, timeline and price. Pilot typically live in 4–8 weeks.

Sounds like a fit?

No public UI — the API is documented and testable via a free developer token. Ask us for a sandbox.

Open API docs → Book a call

You might also like

All products →
Ev Drivers
Driver Portal

Home charging with three data sources — wallbox, CarData and PV inverter —, charging history and reimbursement: the EV-driver UI of the Pipelet suite.

Try for free →
Demo login
Fleet Managers
Fleet Portal

Fleet management, driver management, RFID and billing for commercial EV fleets.

Try for free →
Demo login
Cpo Operators
CPMS Core

The new operator UI: sites, charger commands, vouchers, OCPI, billing.

Try for free →