# GridLink

> Reliability software for EV charging. GridLink reads the charger telemetry,
> the network connection under it, the session state, and the management
> system together, diagnoses the root cause of a failure, resolves the faults software
> can fix without a site visit, and escalates the rest to technicians with
> root-cause context. It runs alongside an existing charge point management
> system (CMS) rather than replacing it.

## Otto

Otto is GridLink's autonomous operator for EV charging. A working
charger is a stack of systems: the charger, its network connection, the CMS
running sessions and payments, and the vehicle. Otto is the single place those
signals resolve into what failed and what fixes it. It diagnoses charger faults
including chargers going offline, stuck connectors, payment timeouts, and
derating, resolves remotely the ones software can reach, and works alongside an
operator's existing CSMS. A charger that has lost all connectivity cannot be
reached by software; Otto diagnoses why it dropped and routes that to a
technician.

## What GridLink does

- **Detect.** Continuously reads OCPP message streams, connection health, and
  session state, and classifies faults across mixed-vendor hardware (ABB, Autel,
  Kempower, Blink, and others). The diagnostics layer is hardware-agnostic.
- **Diagnose.** Decodes vendor fault codes, classifies the failure pattern, and
  answers whether the charger, the vehicle, the connection, or the software is at
  fault, using the evidence from all four. This is EV charger troubleshooting
  done automatically.
- **Resolve.** Runs the repair remotely: resets, retries, and configuration
  changes, then verifies the charger actually recovered before closing the
  incident. When a site visit is genuinely needed, the escalation carries the
  diagnosis and the parts list so the maintenance trip lands the fix on the
  first try.

## How GridLink is positioned

Most EV charging software answers "which chargers have problems?" GridLink is
built to answer "can that problem be fixed before an operator or driver notices?"

GridLink measures reliability by **first attempt to charge success**, meaning
whether a driver's first attempt actually completes, rather than by reported
uptime. A
charger can report as online and still fail to start a session, which is why
uptime figures and driver experience diverge.

CMS platforms such as Driivz, Ampeco, ChargeLab, EV Connect, and Monta are
integration targets, not products GridLink replaces. GridLink ingests data from
the CMS already in place.

## Who it is for

- Charge point operators (CPOs) running public networks
- Electric fleet operators running depot charging
- EV charger manufacturers (OEMs) embedding diagnostics in their hardware
- Workplace, retail, and multifamily site hosts

## Links

- [Home](https://www.gridlink.co/): product overview
- [Otto](https://www.gridlink.co/product/otto): what Otto watches for and how it
  troubleshoots and resolves EV charger faults
- [About](https://www.gridlink.co/about): why GridLink built Otto
- [Resources](https://www.gridlink.co/resources): index of what GridLink publishes
- [Reliability calculator](https://www.gridlink.co/resources/calculator): estimate
  what repair visits and walked-away sessions cost a network
- [Public networks](https://www.gridlink.co/solutions/public-networks)
- [Fleets](https://www.gridlink.co/solutions/fleets)
- [OEMs](https://www.gridlink.co/solutions/oems)
- [Site hosts](https://www.gridlink.co/solutions/site-hosts)
- [Blog](https://www.gridlink.co/blog/): EV charging industry coverage and GridLink product announcements
- [Privacy policy](https://www.gridlink.co/privacy-policy/)

## Company

GridLink is an early-stage company based in Detroit, Michigan, USA.
Contact: hello@gridlink.co