Integrations
Directories, offline locks, and charging without a second policy.
Integrations keep authorization consistent: identity, OSS-SO offline locks, OCPP chargers, and tenant APIs. They consume NG-Key policy. They do not replace it.
What NG-Key connects.
Named capabilities, not a logo wall. Each connection preserves authorization.
Identity cloud
Enterprise identity sources aligned to physical access identities and grants.
Offline locks
OSS-SO offline locks receive authorization from NG-Key. Encoding and updater paths stay under the same credential model.
APIs
Tenant APIs and webhooks for governed exchange — without a shadow integration layer.
EV charging on the same credentials.
ACS and session reporting. The charger is another resource in the access model, not a second identity store.
-
01
EV charging
Charge points authorize RFID and phone starts against the same people and media as doors. A door grant is not automatically a charge grant — purpose stays explicit.
-
02
OCPP on the site Edge
The Edge is the OCPP endpoint on site. Authorize and start are decided from the local policy cache. The cloud records sessions, energy, and ledger events for settlement export — not a CPO billing stack, not energy management, not Plug&Charge.
-
03
Start charging from the phone
Scan a charge QR, start from the passkey hub, or use Access QR at a mapped reader. Remote start and stop follow. Sessions export as CSV or JSON for settlement.