Connects to your existing infrastructure
ChargeVyne is protocol-first. We integrate over OCPP — the open standard every major charger manufacturer supports. Your hardware stays, your CPMS stays. ChargeVyne adds the intelligence layer.
OCPP version support
| Feature | OCPP 1.6 | OCPP 2.0.1 |
|---|---|---|
| SetChargingProfile (TxDefaultProfile) | Full | Full |
| Smart Charging (LoadProfile) | Full | Full |
| GetCompositeSchedule | Full | Full |
| Smart Charging Functional Block (CSMS) | N/A | Full |
| Device Management / Config | Partial | Full |
| MeterValues (power, SoC) | Full | Full |
| Remote Start/Stop | Full | Full |
| ISO 15118 (Plug & Charge) | Not applicable | In roadmap |
Charge Point Management System compatibility
Any CPMS exposing a standard OCPP interface works with ChargeVyne. The following have been verified in integration testing:
| CPMS | OCPP Version | Smart Charging | Status |
|---|---|---|---|
| EVBox BusinessLine | 1.6 / 2.0.1 | Yes | Verified |
| Chargepoint CPF25 | 1.6 | Yes | Verified |
| Schneider Electric EVlink | 1.6 | Limited | Testing |
| ABB Terra AC | 1.6 / 2.0.1 | Yes | Verified |
| Wallbox Quasar 2 | 2.0.1 | Yes | Verified |
| Other OCPP 1.6/2.0.1 hardware | 1.6 / 2.0.1 | Depends on vendor | Contact us |
Integration in 4 steps
OCPP Endpoint
Point your CPMS OCPP connection to the ChargeVyne endpoint. We support both WebSocket and WSS (TLS 1.2+).
Depot Config
Set transformer limit, grid connection type, and EPEX SPOT zone (DE/AT or other). 10-minute setup via web UI.
Vehicle Profiles
Import vehicle list via CSV or API. Set departure times and target SoC per vehicle, or sync from your fleet TMS via webhook.
First Schedule
The scheduling engine runs automatically on the next 15-minute cycle. First optimised charge profile is pushed to all chargers within minutes.