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 — Ladeinfrastruktur, Pipelet Kontrollschicht, Backends

Live aus dem Betrieb

LKW-HPC · 299 kW Peak · 32 % → 100 %

Eine echte Schnellladung aus dem Pipelet-Broker. Jede Session erzeugt automatisch diese Auswertung — ohne Konfiguration, direkt aus den OCPP-Messages und MeterValues. Validität, SoC- und Energie-Verlauf, Wh pro 1 % SoC, Leistungskurve und automatisch erkannte Derating-Events.

Session-Stammdaten: Start, Ende, Dauer, Zählerstände, geladene Energie, SoC-Sprung, Validitäts-Flag, Anzahl OCPP-Messages. — Session-Stammdaten — Validität, Zählerstände, SoC, Message-Count

Liniendiagramm: gelieferte Energie in kWh und State-of-Charge in % über die Zeit, mit Markierung des CC→CV-Übergangs. — Energie & SoC über Zeit — CC→CV-Übergang automatisch markiert

Diagramm: Wattstunden pro 1 Prozent SoC über die Zeit; sichtbarer Knick beim Übergang in die Konstantspannungs-Phase. — Wh pro 1 % SoC — Batterie-Zellen-Health-Indikator

Ladeleistungs-Kurve in kW über die Zeit; Peak bei 299,2 kW, Drop bei 96 % SoC, Auslaufen am Sessionsende. — Leistungs-Kurve — Peak 299 kW, automatisches CV-Tapering

Liste der automatisch erkannten Derating-Events: dauerhafte Leistungsabfälle ≥ 15 % vom laufenden Peak, mit Klassifikation als CV-Tail oder Anomalie. — Derating-Events — automatisch klassifiziert (CV-Tail vs. Anomalie)

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

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.

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, charging history, CarData integra 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.