Neleso Charging Platform
Community combines the OCPP Broker, OCPP Server, CPMS and station simulator in a self-contained platform being prepared for open-source publication. Enterprise extends this architecture for multiple tenants, large charge-point estates, billing, monitoring and integrations.
Two editions
Community and Enterprise share the central architectural principles but address different operational realities. Community is not a time-limited trial, and Enterprise is not merely a different hosting model for the same demo.
Community Edition
A self-contained single-tenant stack for one organisation – self-hosted, transparent and prepared for publication under Apache 2.0.
Enterprise Edition
Multiple broker instances, multi-tenant portals and the business processes required for production CPO, fleet and platform operations.
Comparison
Core communication remains transparent. Enterprise adds the capabilities required for multiple operators, business-critical continuous operation and commercial services.
| Area | Community Edition | Enterprise Edition |
|---|---|---|
| Audience | Development, test labs and one operating organisation | CPOs, fleets, platform providers and multiple tenants |
| Licence | Apache 2.0 prepared; publication follows approval | Commercial licence, source code included |
| Tenants | One tenant | Multiple tenants with central administration |
| Broker | One instance, up to 4,000 concurrently connected charge points | Multiple instances, horizontally scalable at n × 4,000 charge points |
| Routing | Station-specific forwarding to configured targets | Tenant-aware multi-backend routing, migration and parallel operation |
| CPMS | Cockpit, sites, charge points, sessions, RFID and Smart Charging | Full CPMS with roles, tenants, fleets and extended operational functions |
| Load management | Site caps and charging profiles | Cross-site load management plus energy and PV integration |
| Simulator | Integrated interactive station simulator in the CPMS | Functional tests plus tested load, charging and stability tests with up to 10,000 stations |
| Monitoring | Charge-point status, sessions, energy and basic health data | Server and performance metrics, connections, energy consumption, incidents and availability |
| Business processes | No billing, home charging or roaming | Billing, home charging, fleets, OCPI, Plug & Charge and partner integrations as modules |
| Branding | Neleso Community Edition | White label, custom domains and customer-specific portals |
| Operations | Self-managed with Docker Compose | SaaS, managed cloud, self-managed/on-premises and appliance |
| Support | After publication: GitHub Issues and Discussions, no SLA | Onboarding, migration, integrations and agreed response times |
| Demo | Open the Community demo | Open the Enterprise demo |
Broker scaling
Enterprise does not bundle every connection into one oversized process. Charge points, tenants and target systems are deliberately distributed across multiple broker instances.
Community
Charge points → Broker → OCPP Server → one tenant
Up to 4,000 concurrently connected charge points in the self-hosted reference configuration.
Enterprise
Charge-point groups → Broker 1 … n → Backends → Tenants
Every additional broker instance adds a clearly separated capacity unit.
Simulation and testing
The Community simulator models one virtual station with BootNotification, status changes, charging sessions, meter values and remote commands. Enterprise adds reproducible mass tests with up to 10,000 stations.
Choosing an edition
FAQ
No. It is a self-contained stack for one organisation and is being prepared for open-source publication. The protected preview deliberately uses lower protection limits and is not a measure of the capacity of a self-hosted installation.
No. 4,000 concurrently connected charge points is the design size of one self-hosted Community broker instance, not an artificial licence limit. Enterprise distributes larger estates across multiple broker instances.
Yes. Enterprise is available as SaaS, managed cloud, self-managed/on-premises and as an Edge appliance. Edition and operating model are separate choices.
Community is prepared for publication on GitHub under Apache 2.0. The repository is not publicly accessible yet. For Enterprise, source code is part of the commercial licensing model.
Next step