NeLeSo Developer

Public product documentation

2026 status

Product 02 · Commercial

Operate charging infrastructure in production.

The NeLeSo Charging Platform combines OCPP services, CPMS, integrations and operating processes in one supported product. Starter, Professional and Enterprise are plans of the same application.

Product profile NeLeSo Charging Platform · commercial production product

OCPP support: OCPP support according to the offered release and support matrix

SaaS, on-premises and appliance are deployment modes of the same application. Capabilities, limits, support and price are committed for the plan and release. The linked Sandbox is a public, synthetic test installation with regular resets and no production SLA; customer data, production credentials, external charge points, and production station or transaction traffic are not enabled there.

Use cases

What the product is designed for.

  • Operate and integrate charging infrastructure
  • Cover CPO, fleet or platform processes
  • Organise production operations with agreed support

Surfaces

Product-specific interfaces for the shared core.

01

Operator, admin, driver and fleet surfaces as approved

02

Roles, data spaces and audit context by quotation

03

Operations, compliance and automation functions within the agreed scope

APIs & Swagger

Contracts generated from product code.

The central documentation describes purpose, contracts and stability boundaries. For approved services, the installed Platform also provides version-specific OpenAPI and Swagger references.

Headless CPMS API

Integration point for stations, sessions and configuration within the approved scope.

Fleet & Driver APIs

Partner surfaces for driver, energy and fleet processes in the offered release.

Gateway, Server & CPMS APIs

Version-exact runtime contracts for installed services.

Runtime Swagger Version-specific in the public Sandbox

The Sandbox specifications belong to the installed test release. They document that release but are not a public production contract; API keys and access are managed in the Platform.

Open demo Swagger → View API model and paths →

Operations

Product documentation remains central.

  • SaaS, on-premises or appliance subject to project approval
  • Starter, Professional or Enterprise without separate source forks
  • Local runtime reference and central product documentation