Open
protocol.
Open network
EVEON is a small team of engineers building the central system that chargers talk to. We think the operator should own the hardware choice, the tariff and the driver relationship — not the software vendor.
Most charging networks are locked to the software that came with the first charger. We built EVEON so that any OCPP charger, from any vendor, can join one network with one tariff, one wallet and one dashboard — and leave it just as easily.
Standards first
If OCPP has a message for it, we use the message. No vendor extensions a charger cannot leave with.
Drivers before dashboards
A session that starts in two taps beats a chart. We design the plug-side experience before the operator screen.
Boring reliability
A central system is infrastructure. Websockets stay up, MeterValues get stored, invoices add up — every night.
Your data is yours
Chargers, drivers, sessions and CDRs export as CSV or over the API at any time. Leaving should be as easy as joining.
How we
got here
Dates are placeholders
until the team fills them in.
- [2023]A broken charger and a spreadsheet
The founders ran a small car park's chargers by hand: RFID cards in a drawer, invoices in a spreadsheet, firmware updates over USB. The protocol was there; the software was not.
- [2024]First BootNotification
EVEON answered its first charger in production. OCPP 1.6J, one site, twelve connectors, and a dashboard that only showed what was plugged in.
- [2025]QR start and the prepaid wallet
Drivers could scan, see the price and charge without a card or an app install. Billing became something that happens, not something someone does.
- [2026]OCPP 2.0.1, white-label, 1,000 connectors
Security profiles 2 and 3, the device model, branded apps and receipts, and the first public network migrated off another CSMS without downtime.
- NextOCPI roaming and Plug&Charge
Sessions across networks, and cars that authorise themselves. In pilot with [partner].