Industry challenge
Closed CSMS stacks limit hardware choice.
Proprietary protocols inflate lock-in risk across multi-OEM fleets.
OCPP Compatibility
Open OCPP without lock-in
OCPP 1.6 on AWS IoT Core — keep vendor choice while standardizing operations across fleets and corridors.
Protocol posture
From closed CSMS stacks to standard OCPP
Fleets mix OEMs — proprietary protocols slow commissioning. Chargers uses a production OCPP 1.6 path on AWS IoT so mixed hardware stays open while one console operates the network.
DeviceNIQ Chargers
Standard OCPP path on AWS IoT.
Commission mixed fleets on open protocol while keeping one Chargers OS console.
- OCPP 1.6 production path on AWS IoT
- Cloud-native gateway for charger connectivity
- Vendor-flexible commissioning for mixed fleets
- Simulator uses the same open endpoint as production
Protocol first
Standard OCPP handoff so hardware choices stay open as your network grows.
Cloud native
AWS IoT Core connectivity designed for scale across multi-site deployments.
Prove early
Use the simulator to validate commissioning before chargers arrive on site.