Let your chargers fix themselves.
GridLink is reliability software for EV charging. It watches your chargers and everything they depend on, and fixes what software can fix before anyone drives out. The rest reaches your team with the diagnosis attached.
2 faulted sessions restarted, 1 stalled start recovered.
Charger 2: power stage fault. Diagnosis attached to the ticket.
How GridLink keeps chargers charging.
Otto is GridLink’s reliability operator, watching every charger you run. It works every issue the same way, whether it broke a session this morning or has been costing you power for months.
- EVSE-0421Connector lock stuckResolved03:14:41
- EVSE-0198Payment terminal timeoutResolved04:02:09
- EVSE-0307Derated below rated powerWatching04:51:20
- EVSE-0442Station offline over 5mEscalated, diagnosis attached05:26:38
- Connector lock stuck31
- Payment terminal timeout18
- Derated below rated power12
- Station offline over 5m7
Issues surface the moment they start
GridLink reads your chargers' data continuously. A stuck connector shows up here before a driver calls it in, and so does the unit that has been charging below its rated power for a week.
Otto works out what actually failed
Charger, vehicle, session, or the connection underneath: the diagnosis names the failing side and shows the evidence. Otto also follows each charger across its lifetime, so a slow decline in performance gets explained as readily as an outage.
Fixes run automatically and get verified
Resets, retries, and configuration changes go out on their own, and Otto confirms the charger came back before the issue closes.
Everyone hears about it in plain language
Drivers and site staff get alerts they can act on, not diagnostic logs. Someone standing at a charger that will not start can get help on the spot.
When a charger does need hands on site, the escalation goes out with the diagnosis attached: to your service provider, or to a technician from GridLink’s partner network if you need one.
GridLink connects to the systems you already run.
A session only finishes when every layer underneath it works. GridLink reads them all in one place, and works through the systems you have, not around them.
Your CMS
Sessions, billing, driversConnectivity
Link healthChargers
Charger telemetryElectrical infrastructure
Power at the circuitVehicles
The other side of the plugResults from live deployments.
Industry first-session success sits between 75 and 85%[1][2], and a majority of charging session issues can be fixed remotely with software.
- 91→97%
- first-attempt-to-charge success after Otto went live
- 60%
- of tickets resolved automatically, before anyone is dispatched
- 45%
- of fixes land off-hours, when no one was on site anyway
Measured across GridLink deployments.
Frequently asked questions
A restart you send by hand still needs you to notice the fault, pick the fix, and check that it worked. Otto runs that whole loop on its own, at 3am, through the CMS you already have.
Some teams start there. Then every charger-vehicle pair turns out to have its own edge cases, and hand-coded fixes stop keeping up. Otto is the engine we built after hitting that wall on our own charging network.
No. If a charger has lost all connectivity, no software can reach it. That is not the end of it. Otto works out what dropped, the unit, the site connection, or the backend, and texts whoever reported the fault to walk them through the physical checks, which is how a tripped breaker or dead site power gets cleared without a visit. What survives that goes to your tech with the cause attached, so the one site visit carries the fix.
Your CMS starts sessions, handles billing and payments, authenticates drivers, and balances load. Otto sits alongside it with one job: keeping chargers completing sessions. It reads what the charger reports, the connection layer underneath it, and what your CMS sees, then acts through your CMS's own API.
Through the API of the charge point management system you already run, plus whatever you use for ticketing and messaging. Nothing gets installed on the charger. When a driver reports a problem on site, that report lands in the same loop and gets checked against the telemetry.
NEVI reporting is built around uptime, and a charger can hold its uptime number while still turning drivers away: it answers the network, reports itself available, then fails the session. Otto works the other side of that gap. It clears the faults that break sessions and keeps the record of what failed and what fixed it. Uptime is what you report; first-attempt success is what drivers experience.
Most charger downtime has a software fix.
We’ll connect to your charger data, show you what has been failing and why, and put the fixes on autopilot.