OCPP Proxy

Continue Using the Existing CSMS

After connecting charging stations to the OCPP Proxy layer, continue routing their communication to your existing CPO platform. Keep current operations running while the ChargenOS environment is prepared and avoid forcing the entire migration into a single cutover.

Central Backend Routing

Centrally control which CSMS receives charger connections through the OCPP Proxy. When ChargenOS is ready, change the backend routing at the proxy layer instead of reconfiguring the endpoint of every charging station again.

Phased Software Migration

Instead of moving the entire charging network at once, migrate selected charger groups to the new CSMS in stages. Start with pilot stations, validate operations and gradually expand the migration after successful verification.

Reduced Charger Reconfiguration

Once chargers are connected through the OCPP Proxy, reduce the need to reconfigure individual charger endpoints during subsequent backend changes. This helps lower operational effort, particularly across large and geographically distributed networks.

Controlled Migration for Multi-Brand Networks

Manage charging networks containing different brands, models and firmware versions in separate migration groups instead of forcing every device through one cutover. Validate each group and plan the OCPP Proxy and CSMS transition more carefully.

Routing Between Existing and New CSMS

Centrally control the target backend behind the OCPP Proxy during migration. Keep chargers operating with the existing CSMS and redirect selected stations or groups to ChargenOS when the new environment is ready.

Controlled Rollback

If an unexpected issue occurs on the new backend, make rollback more manageable by redirecting the proxy to the previous CSMS instead of changing individual charger endpoints again.

Backend-Independent Connection Layer

Use the OCPP Proxy as a stable connection layer instead of binding chargers directly to a specific CSMS endpoint. Reduce the dependency between physical charging infrastructure and backend software, making future platform changes easier to manage.