Modules

Pipelet is modular by design: 16 cleanly separated services and UIs that you can run independently or as a coordinated stack. Pick what you need, leave the rest, and integrate at any layer.

OCPP core

ocpp-broker

Message broker for OCPP 1.6 traffic. Owns the WebSocket connections to physical chargers. Pure aiohttp Python service.

ocpp-server

REST API and business logic on top of the broker. 39 documented operations covering OCPP 1.6, OICP roaming, Plug & Charge.

ocpp-chargersim

OCPP charger simulator. Spin up 1–10,000 virtual chargers, inject errors, mass-load-test your backend, stream OCPP messages over SSE.

Platform services

cpms-headless

Unified REST gateway. The friendly entry point for integrators. 43 operations, X-API-Key auth, 23 webhook event types, ships with a Python SDK.

mcp-server

Model Context Protocol server. Exposes 30 tools to LLM agents — connect Claude Desktop or any MCP client and let an AI operate the network.

automation-service

Workflow engine. Consumes broker outbox events and runs filter / payload-map / structured-log / webhook nodes.

automation-studio

TypeScript/React frontend for managing automation workflows, bindings, runs, and dead letters.

service-cardata

Vehicle data integration. Bridges car telematics (Tesla, Volvo, …) into the CPMS data model.

service-energy

Energy management — load groups, tariffs, hourly polling.

service-monitoring

Observability collection point — metrics, logs, alerts.

Portals & UIs

cpms-ui

Web dashboard for network operators. Flask/Jinja, lightweight, server-rendered.

admin-portal

Admin interface for Pipelet operators and support staff.

fleet-portal

B2B fleet management UI.

cpms-driver-portal

EV driver-facing portal — sessions, history, payments.

homepage

Marketing site (pipelet.com). Vanilla HTML + Directus CMS.

developer-portal

This site. Astro + Starlight.

---

Module categorization

Modules naturally fall into four categories that map to homepage filters:

Category	Modules
Traffic Control	ocpp-broker, ocpp-server, ocpp-chargersim
Operations	cpms-headless, mcp-server, automation-service, automation-studio
Interoperability	service-cardata, service-energy, service-monitoring
Platform	All UIs and the homepage/developer-portal

Pick what you need

You don’t have to run all 16. Common combinations:

• Minimal CPO backend: mysql + ocpp-broker + ocpp-server + cpms-headless. Four containers.
• API-first integration: cpms-headless only, hooked up to an existing broker.
• AI-assisted operator console: the minimal stack + mcp-server + Claude Desktop.
• Full platform: every module, deployed to one or more hosts.

See Self-Hosting → Docker Compose Quickstart for the four-container minimal stack.

Source code

Every module is a separate repo under github.com/pipelet. The flagship monorepo (pipelet-platform) bundles them as git submodules for coordinated releases.