Starting point
DepotCharge delivers depot charging solutions from a single source – from hardware to operations. The heart of the offering, the operating platform, was not supposed to run on third-party SaaS under someone else’s terms: roadmap, data access and conditions would have been outside their control.
At the same time, DepotCharge did not want to build its own platform team just to run a backend, updates and monitoring. What they were looking for was both at once: full data and cost sovereignty in their own cloud – and a partner who takes over platform operations.
Approach
We deployed the NeLeSo stack – OCPP Broker, OCPP Server and CPMS modules – directly in DepotCharge’s Azure instance, as separate dev and prod environments. The cloud resources run in the customer’s subscription; every cost item stays transparent.
The DC chargers of DepotCharge’s depot customers connect to the OCPP Broker as a decoupling layer. From there, charge points are routed either to the integrated CPMS – or to an existing backend of the respective depot customer. This lets DepotCharge serve both worlds without ever reconfiguring a charge point.
Updates, monitoring and operations support are delivered as a managed service: signed releases pass through the dev environment first, then roll into production in a controlled way.
Outcome
Today DepotCharge runs its own platform under its own brand – in its own Azure, with full sovereignty over operational and customer data, without having to build a platform team of its own.
New depot customers can be onboarded flexibly: with the integrated CPMS, or keeping their existing backend via the broker. There is no longer any dependency on a third-party SaaS roadmap.
Building blocks used
OCPP Broker as the decoupling layer, OCPP Server as the backend core and modules from the CPMS toolkit – operated in the managed-cloud model: deployment, signed updates and operations support by NeLeSo, cloud resources and data with the customer.