Now piloting in Dubai — early sites shape the roadmap. Join the pilot →
Chargers stranded by a dead vendor app? Charger rescue is live →
Interoperability is not a feature bolted on afterwards — it is the product. Standards implemented to their depths, tested against real hardware, flowing in both directions.
Vendors differ, firmware lies, networks multiply. EnGe absorbs the mess on one side and presents a clean, standards-native layer on the other — so every connection behaves like it was born there.
Every charger model speaks OCPP with an accent. The layer normalizes firmware quirks, reconnect storms and offline queues before they ever reach your operations.
Add a vendor, join a roaming partner, respond to a grid signal — configuration, not projects. The data model was born OCPI-shaped and OpenADR-aware.
Telemetry rises; control returns. Sessions, tariffs and signals move through one governed pipeline with a full audit trail.
1.6J & 2.0.1
The contract between hardware and platform — and the place where charging networks quietly fail. We implement the full message surface and treat real firmware behaviour as a first-class engineering problem.
2.2.1
How networks meet: locations, tariffs, sessions and charge detail records shared between platforms. Ours is not an adapter bolted on — the data model was born OCPI-shaped.
demand response
The grid's language for asking politely. When utilities signal stress or surplus, connected charging responds automatically — turning networks from passive load into dispatchable flexibility.
plug & charge · ready
Identity in the cable: the car authenticates itself the moment it clicks in. Our architecture is certificate-ready for Plug & Charge as vehicle and charger support matures in the region.
Protocol depth is measured in the gap between documentation and firmware. We build for the street.
The spec says StatusNotification reports the connector state.
The street says some firmware reports Available with a session still open. We reconcile every state against StopTransaction — always.
The spec says offline chargers queue meter values and resend them.
The street says they flood on reconnect and double-count your billing. We rate-limit the replay and deduplicate before invoicing.
The spec says RemoteStopTransaction returns Accepted.
The street says Accepted means the charger heard you — not that it stopped. We trust nothing before the StopTransaction arrives.
Event-driven, multi-tenant cloud architecture with per-device authentication, encrypted transport and full audit trails. Built by engineers who have operated national-scale charging infrastructure and carry its lessons in the design.
Bring your hardware list — we'll tell you exactly how it behaves.
Contact engineering