NeLeSo Charging Platform
Starter, Professional and Enterprise are commercial plans of the same Charging Platform. Depending on the project, the application runs as SaaS, on-premises or an appliance; capabilities, limits, support and price are committed for the offered release.
Three plans
The plans are not separate source forks. NeLeSo positions the right plan based on operations, integrations, organisation and support needs. Specific capabilities, quantities and prices are not inferred from a plan name.
Starter
Commercial plan · individual quotation
For a clearly bounded production start with an agreed operating, integration and support scope.
Professional
Commercial plan · individual quotation
For projects with broader integration, process or operating needs. The committed scope follows the specific quotation and release.
Enterprise
Commercial plan · individual quotation
For tenant-aware and integration-intensive operating models. Approved portals, roles, data spaces and processes are described precisely in the quotation.
Portfolio
The Charging Platform operates charging infrastructure. The OCPP Gateway observes, routes and migrates an existing backend. Developer Kit and Sandbox are explicitly not production products.
NeLeSo OCPP Gateway
Charge point → Gateway → primary backend + read-only Observer
The commercial product for routing, observation, auditability and controlled cutover. Production operations and real migration pilots are paid.
NeLeSo Developer Kit
Schemas · SDKs · simulator · fixtures · conformance tools
For development and testing only, not production. Publication and licensing remain pending until rights, dependency, trademark and security reviews are complete.
NeLeSo Sandbox
Synthetic data · resettable · no production credentials
The Sandbox is publicly available and reset regularly. It accepts no customer data, production credentials or external station connections, carries no production SLA and does not enable production station or transaction traffic.
Architecture
OCPP connections, station states, sessions and commands follow versioned contracts. Customer-facing statements always apply to the exact offered release. Security patches and protocol corrections are not plan differentiators.
Non-binding plan guidance
These criteria support initial self-qualification. Capabilities, limits, support and price only become binding in the specific quotation.
| Selection criterion | Starter | Professional | Enterprise |
|---|---|---|---|
| Typical starting point | One clearly bounded production use case | Several integrations or operating processes | A tenant-aware, integration-intensive organisation |
| Organisation model | One compact operator organisation | Several roles or teams | Multiple tenants, brands or data spaces |
| Integration need | A few clearly defined interfaces | Several system and process integrations | Complex or cross-organisation integrations |
| Billing and roaming | Clearly bounded need | Broader process requirements | Tenant- or partner-spanning processes |
| Operating responsibility | Clear handover and ownership | Jointly aligned operating processes | Individual governance and operating handover |
| Support need | Agreed entry scope | Broader support and response requirements | Individually aligned operating and support model |
| Deployment | SaaS, on-premises or appliance subject to approval | SaaS, on-premises or appliance subject to approval | SaaS, on-premises or appliance subject to approval |
| Binding scope | In the specific quotation | In the specific quotation | In the specific quotation |
| Next step | Discuss Starter | Discuss Professional |
Optional NATS JetStream integration: scope and administration
Production Launch
Architecture, installation, device compatibility, migration, operating documentation and go-live are scoped for the project. Scope and price are set in the binding quotation before the project starts.
Operations cockpit
The cockpit brings together sites, charge points, sessions, energy, server health and support context. The agreed product scope determines which roles, data spaces, integrations and processes are enabled.
Simulation and testing
Simulators and repeatable load, charging and stability tests support release decisions. A concrete capacity or compatibility result applies only to the documented release, tested infrastructure and respective message profile.
FAQ
Yes. Production use is commercial from the first production station or transaction. Developer Kit and Sandbox are separate non-production paths.
They are plans of the same Charging Platform. The binding quotation assigns capabilities, limits, integrations, support and price; these are not inferred from the plan name alone.
Depending on the project, the Charging Platform may be offered as SaaS, on-premises or an appliance. These are deployment modes of the same application, not separate products.
The Gateway is for organisations with an existing charging backend that need to connect a primary backend, observe it independently in read-only mode or perform a controlled migration.
Not as a published distribution yet. It remains non-production, and publication and licensing require completed rights, dependency, trademark and security reviews.
Yes. The public Sandbox supports synthetic, resettable evaluation and is reset regularly. Customer data, production credentials, external station connections, and production station or transaction traffic are not enabled; there is no production SLA.
Next step
