Neleso Developer
One platform foundation. Three products. One documentation source.
OCPP Broker Standalone, Community Server and Enterprise Server are converging on one shared broker and OCPP server core. This documentation defines the target, product boundaries and API publication status.
The shared core is the binding development direction. Differences in today’s products are stated explicitly.
- Languages
- DE · EN
- Reference
- Central
- Runtime
- Community & Enterprise: local Swagger
Target
The shared OCPP core supports all three products.
The product boundary begins above the protocol and routing layer: with user surfaces, tenancy, integrations and operating responsibility.
Products
Three clearly separated product layers.
Every product page follows the same structure: purpose, current alignment status, surfaces, APIs and operating boundaries.
OCPP Broker
Lean OCPP routing with its own configuration and local control API.
Product documentation → 02 · Open sourceCommunity Server
Self-hosted Charging Platform for one organisation and your own extensions.
Product documentation → 03 · CommercialEnterprise Server
Tenant-aware platform with additional portals, integrations and operating functions.
Product documentation →Single source of truth
Central guidance, local precision.
Neleso documents centrally
Product overview, target architecture, concepts and API publication status live here – publicly and in two languages.
Installations should expose Swagger
Community and Enterprise already provide local specifications. The Standalone Broker will adopt the same version-exact OpenAPI and Swagger convention.
Product code becomes the contract source
In the target model, OpenAPI is built from product code and feeds both the central reference and local runtime documentation.