- Type
- not stated
- Format
- Structured JSON message streams defined by open protocols — OCPI 2.3.0 (locations, tariffs, sessions, CDRs, tokens, Direct Payment), OCPP 1.6J / 2.0.1 station frames and OICP hub messages — rendered as inter-operator API traffic and settlement records rather than bulk files
- Volume
- est. 10^6-10^7 roaming session/CDR records per year across the connected CPO-MSP graph — a national hub integration alone generates a country's worth of cross-network session settlements, and each OCPI CDR is a compact structured record; underlying OCPP frame volume at bridged stations runs 10^8-10^10
- Users
- N/A to EVesto as a consumer brand — it is B2B middleware between CPOs and eMSPs, so drivers are registered with their own mobility service providers, not with EVesto. Effective user base is the union of the connected CPO/MSP customer populations, including all parties on the Portuguese Mobi.E hub it integrates with
- History
- 3 years
- Update frequency
- not stated
- Growth
- Active and commercialised — public pricing page, packaged segment-specific product lines (commercially-led, operationally-led, and 'EVesto for Data-Driven CPOs'), a Managed Roaming service line, a partner programme, an active job requisition (Sales Executive Benelux), a customer-stories section, and English/German site versions
- Launched
- ~2023-2024 — the company's web assets carry a 2025/06 brand-asset path and the corporate record is a 2024-vintage profile with no funding history, indicating a recent product build; the site publishes a public pricing page, indicating a packaged product rather than a pre-launch venture
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated