NeLeSo Developer
Technical documentation for NeLeSo charging products
NeLeSo OCPP Gateway and NeLeSo Charging Platform are the two commercial production products. These pages cover architecture, product boundaries, APIs and integration while keeping Developer Kit and Sandbox explicitly separate from production runtimes.
Connections, state and commands follow versioned contracts. The Gateway addresses existing backends; the Platform operates charging infrastructure. Statements apply to the exact offered release.
- Languages
- DE · EN
- Reference
- Central
- Runtime
- Commercial, release-bound product contracts
Architecture
Shared OCPP services form the technical foundation.
The foundation handles station connections, state and commands. Routing scope and product-specific user interfaces, APIs and operating models follow each product boundary.
Products
Two production products for two different jobs.
The Gateway observes, routes and migrates an existing backend. The Charging Platform operates, integrates and accounts for charging infrastructure.
NeLeSo OCPP Gateway
A technical standalone package comprising the Broker runtime and integrated OCPP Server for routing, observation and migration.
Product documentation → 02 · CommercialNeLeSo Charging Platform
Production charging operations with Starter, Professional and Enterprise plans. The public Sandbox exposes a synthetic test release with regular resets; it is not a production system.
Product documentation →NeLeSo Developer Kit
Planned export of schemas, SDKs, simulator, fixtures, conformance tools and examples. Publication and licensing remain pending rights and security reviews.
Status: review pendingNeLeSo Sandbox
Synthetic evaluation with regular resets and no customer data, production credentials, external station connections, production station or transaction traffic, or production SLA.
Go to the guided Sandbox start →Single source of truth
One documentation source, version-specific API references.
NeLeSo documents centrally
Architecture, product boundaries, concepts and API status are documented here publicly in German and English.
Local Swagger for approved services
Installed product releases may expose their exact OpenAPI specification locally. A demo domain is not a public API contract.
OpenAPI follows the product code
Versioned OpenAPI specifications connect the central API documentation with the local runtime reference.