Architecture decisions that other CPMS vendors will spend years on are already in production with Pipelet today: AI-native development through MCP servers, full source code in the delivery, SaaS operations or on-premise deployment, every component as a standalone module.
MCP server, cleanly isolated modules and documented APIs are the foundation, not an add-on. Claude, Copilot and Cursor work on Pipelet code like it's home turf — features ship in days, not months.
Every module ships with full source code. In Git, auditable, forkable, customizable. No vendor lock-in, no black box, no surprises on the upgrade path — your IT decides how deep it wants to go.
Pipelet runs hosted on pipelet.com, in your own data center, or on your VPC. Same code, same behavior, same update cadence. Migrating from one to the other is a deploy, not a project.
Take just the OCPP broker. Or just the EMP backend for roaming. Or the whole suite. Every module has its own URL, its own API, its own deployment path — and runs in isolation alongside your existing CPMS platform.
Home charging, charging history, CarData integration — the EV driver UI of the Pipelet suite.
Fleet management, driver management, RFID and billing for commercial EV fleets.
The new operator UI: sites, charger commands, vouchers, OCPI, billing.
Vehicle recognition, contract certificates and ISO 15118-20 flows — publicly through Hubject, at home with capable wallboxes.
Charge points, tariffs, OCPI, billing — the established operator console.
OTA firmware campaigns, ChangeConfiguration, maintenance windows.
Virtual OCPP 1.6 & 2.0.1 charge points for testing and demo — no login required.
API docs, OpenAPI specs, Postman/Insomnia collections.
Visual workflow editor for event automation across the entire suite.
WebSocket broker with digital twin, smart proxy and messaging for OCPP.
Model Context Protocol server — the Pipelet suite directly inside Claude, Cursor, Copilot.
Live status of all Pipelet services — publicly visible, no login required.
E-Mobility Provider portal: roaming partners, driver tokens, CDRs, tariff publishing.
OCPI testing against any CPMS: simulate roaming flows, provoke errors, validate payloads.
Meters, load management, smart charging on site — decides locally, monitored centrally.
Dynamic site-cap distribution: splits the available power across all connected EVSEs in real time.
Echte LKW-HPC-Session, 299 kW Peak. Validität, Energie- und SoC-Verlauf, Leistungskurve und Derating-Erkennung — automatisch aus jeder OCPP-Session, ohne Konfiguration.
Reichweite, gekoppeltes Fahrzeug, Strompreis und die Erstattung des aktuellen Monats — auf einer Seite. Self-Service Onboarding via Magic-Link, kein Passwort, kein Helpdesk-Ticket.
30-minute call: you describe your existing landscape and top pain points, we show exactly which Pipelet modules make an immediate difference — and where parallel operations make more sense than a big-bang migration.
