The open network

Open by design. No vendor lock in.

EVUNITY speaks the open standards your hardware and your roaming partners already use. Drivers, chargers and networks just work together.

To chargers

OCPP 1.6J

The most deployed open charging protocol. Any OCPP 1.6J charger connects to EVUNITY by serial. Start, stop, reset, availability, status and meter values all flow in real time.

To partners

OCPI 2.2.1

EVUNITY operates as an eMSP under OCPI 2.2.1. Drivers in our app can roam to partner networks, and hosts on EVUNITY can welcome drivers from partner networks. One wallet, one history.

What that means for drivers

Roam across partner networks with a single app and a single wallet. No card per network juggling.

What that means for hosts

Use standard hardware you already own. Reach more drivers via roaming without new boxes or proprietary stacks.

What that means for partners

Interconnect with EVUNITY through standard OCPI flows. Become a roaming partner →

Architecture

How the pieces fit together.

Three open conversations: chargers to EVUNITY, drivers to the EVUNITY app, EVUNITY to roaming partners.

Chargers OCPP 1.6J
EVUNITY core sessions, wallet, routing
OCPI partners OCPI 2.2.1
Driver app find · scan · pay
Why open

No proprietary stack. No vendor lock in.

Standard hardware works

Any OCPP 1.6J charger speaks to EVUNITY out of the box. You are not tied to a brand, a firmware vendor, or a special box.

Drivers stay in one app

OCPI 2.2.1 roaming lets one EVUNITY wallet pay on partner networks, so drivers do not collect a wallet per network.

Partners interconnect cleanly

Roaming uses documented OCPI flows. New partners onboard against the same spec, not bespoke integrations.

Honest about scope

EVUNITY currently targets OCPP 1.6J on the charger side and OCPI 2.2.1 on the roaming side. We do not over claim spec support beyond that.

Roaming partners

Become a roaming partner.

If you run a charging network and want to exchange drivers with EVUNITY via OCPI 2.2.1, let us know and we will scope the connection.

OCPI 2.2.1eMSP role on the EVUNITY side, with documented flows.
Talk to engineeringWe will route you to the right person to scope and test.
Thanks. Your message is on its way. We will be in touch.