operator console
~70%
less dashboard-hunt time using the AI copilot
Trust anchor · in production
If a national grid runs on it inside their own perimeter,
your app can too.
Slovenia's transmission system operator runs national-grid EV charging on WaveCharge today — fully self-hosted, NIS2-aligned, with AI agents handling operator queries and anomaly detection inside their perimeter. The TSO is the most demanding charging- infrastructure buyer in the EU. They picked WaveCharge.
customer
National TSO · Slovenia
workload
Grid-edge EV charging
deployment
Self-hosted · sovereign
agents
In production today
protocols
OCPP 1.6J + 2.0.1
compliance
NIS2 art. 21 + 23
Impact
Numbers we can share.
L2 support
~50%
faster root-cause identification via OCPP log triage
data residency
100%
of operational data resident in the customer perimeter
Absolute deployment numbers — charger count, session volume, incident-response times — pending NDA review.
Why it works
Agents are interesting
because the deployment is sovereign.
A TSO can't route charger telemetry through a third-party AI service. NIS2 makes it explicit; procurement enforces it. Most "AI for EV charging" products fail that test before the demo.
WaveCharge runs in the customer's environment, on the customer's database, with the model attached on-prem. Agent calls happen inside the perimeter. The audit log is customer-owned.
That's the whole game: the AI overlay is interesting precisely because the deployment is sovereign. SaaS CPMS competitors can't replicate either half.
Get the full case study under NDA.
Customer name, deployment scale, architecture diagram, operational metrics — available to qualified utility, DSO, TSO, and large-CPO buyers under mutual NDA.