Product 02 · Open source
The self-hosted Charging Platform for one organisation.
Community adds a local operator cockpit, CPMS functions and open extension points to the OCPP core. Data and operations remain in your own environment.
Protocols today: OCPP 1.6J, 2.0.1 and 2.1
Broker and server are being migrated towards the shared core contract step by step.
Use cases
What the product is designed for.
- One organisation operating its own charging infrastructure
- Self-hosted development and integration
- Transparent extension through core APIs and webhooks
Surfaces
The shared core, through the right surfaces.
Operator cockpit for stations and sessions
Configuration, tokens and local operations data
Local OCPI Test Lab for supported paths
APIs & Swagger
Contracts generated from product code.
The central documentation explains purpose and stability boundaries. Where already available, local Swagger is the exact reference for the installed release.
CPMS Core APIStations, sessions, tokens and configuration in the open core.
WebhooksForward events to your own applications and automation.
OCPP commandsSupported station commands through the local Community management API.
Community generates its local OpenAPI specification from the product routes actually registered at runtime and serves Swagger without a CDN dependency.
Open live Swagger → View API model and paths →Operations
Documentation is not a second product portal.
- Self-managed Docker Compose stack
- One organisation per installation
- No second documentation or user portal