Any charge point speaking OCPP 1.6J, which covers the large majority of AC and DC hardware deployed today. The platform is vendor-neutral by design — it connects to the charger's native protocol rather than a manufacturer's cloud, so a mixed-vendor network is a single network to us.

No, and this is deliberate. Every alert is raised by a versioned threshold rule with its inputs recorded, so any alert can be reproduced and audited months later. Language models are used only to explain and rank alerts that the rule engine has already raised, and to answer questions over a fixed catalogue of reviewed queries. A model never decides safety-relevant state.

Neither is required. EV Spectra runs as an intelligence layer alongside whatever you use for tariffs, roaming and settlement. It consumes the same OCPP stream your CPMS does and adds diagnostics, battery health and remote troubleshooting on top.

From the vehicle's own charge curves as observed at the charger — the shape of the power ramp, thermal behaviour under load, and how these change across a vehicle's session history. No dealer tooling or OEM API access is required.

The platform runs on standard PostgreSQL and can be deployed in the region of your choice, including inside your own cloud account. Telemetry is not pooled across customers.

A subset of your network is pointed at an EV Spectra gateway endpoint. Nothing is changed on the charger beyond the OCPP backend URL, and the deployment is reversible. Within a few weeks you have a session-level picture of how your network is actually performing.

EV Spectra is at MVP stage. The OCPP gateway, rule engine, agent layer and operator console run end to end today. We are actively seeking operator partners for paid pilots.