EV Cloud

EV Cloud — Raw, schema-complete charge-point telemetry persisted as first-class storage rather than as a reporting view: every OCPP frame with timestamps (transactions, meter readings, status events), session duration, energy delivered, idle time, fault patterns and demand peaks, held in a vendor-independent operational schema that the customer can query with direct SQL and replicate via a read replica. EV Cloud's differentiating claim is precisely that it stores the raw event layer, not just aggregated dashboards, and that the store is portable across CPMS changes — meaning the company opera…

EV Cloud offers (Alternative, Supply Chain, Reference) — Volume per site is inherently high because the architecture keeps every OCPP frame: an AC charger emits a meter/status frame every few tens of seconds while plugged in, so 10^8-10^9 frames per 1,000 charge points per year is the natural order — but the number of sites EV Cloud itself hosts is undisclosed and, given a 2-person firm, likely small.

Any modelling that requires raw events rather than dashboards: demand-peak and load forecasting at connector granularity; fault-pattern and failure-prediction models built on unaggregated status/error events; idle-time and utilisation economics for charge-point siting; joining charging sessions to fleet telematics (the page names this join as the one most deployments cannot do); feeding real-time session data into billing or pricing engines; and longitudinal tender-grade panels — the page's own worked example is a finance team needing eighteen months of session-level data with charger and connector granularity, which aggregated monthly exports cannot supply

The data is with 2 years of history.

Coverage spans US; Application Software; alternative, supply_chain, reference; equities.