DE Discuss your project
Neleso Developer

Public product documentation

Target model · 2026 status

Product 01 · Standalone

Route OCPP connections with control.

The Standalone Broker sits between charge points and a backend. It keeps station connections stable, forwards messages under explicit rules and makes routing decisions traceable.

Open Broker demo Target architecture
Alignment status Independent distribution

Protocols today: OCPP 1.6J and 2.0.1

Today’s standalone code is being aligned with the shared broker and server contract.

Use cases

What the product is designed for.

  • Connect an existing CPMS without migrating stations
  • Add a read-only observer to the primary backend
  • Run OCPP connections locally and under your control

Surfaces

The shared core, through the right surfaces.

01

Broker configuration per Charge Point ID

02

Connection and routing status

03

Diagnostics and recorded decisions

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.

Broker Control API

Connections, targets, routing rules and status.

OCPP Server API

Station state and OCPP commands inside the installation.

Runtime Swagger In preparation

The standalone build will adopt the same local OpenAPI and Swagger convention as the server editions.

View API model and paths →

Operations

Documentation is not a second product portal.

  • Customer-managed Linux host or VM
  • Containerised services and PostgreSQL
  • No separate documentation portal in the installation