Introduction
What GridOS is, the problems it solves, and when to use protocol simulation instead of physical chargers.
GridOS is the EV Cloud platform for operating charge points and roaming partners. It speaks the same protocols a real charging stack speaks — OCPP 1.6, OCPP 2.0.1, and OCPI for roaming — so you can connect hardware, validate a CPMS, and exchange roaming data without reinventing protocol plumbing.
Why protocol docs live here
Physical chargers and live roaming partners are slow and expensive to test against.
A single device can only be in one state at a time, firmware varies by vendor, and
reproducing an edge case — a dropped WebSocket mid-transaction, a malformed
MeterValues, a boot during an active reservation — is painful on real hardware.
GridOS and these guides make those scenarios clearer and more repeatable:
- Connect fleets over OCPP 1.6 and 2.0.1 on the same gateway
- Reference every action and OCTT test case for compliance work
- Roam with eMSPs and hubs on OCPI 2.1.1 and 2.2.1
When to use this docs set
| Situation | Start here |
|---|---|
| New to GridOS | Quickstart |
| Connect a charge point | Connect a charger |
| OCPP message / test case reference | OCPP |
| OCPI modules and credentials | OCPI |
| Dashboard and platform architecture | GridOS product |
Next steps
- Quickstart
- Concepts
- Protocol deep dives under OCPP and OCPI
The left sidebar lists Overview, Actions, and Test cases only (not every message). Open the index pages below or use ⌘K search — hit labels include the protocol version (for example · OCPP 1.6) so same-named actions stay distinct.