NG-Key NG-Key

Control points decide locally.

NG-Key publishes identities and grants. Accena readers and Edge decide at doors, gates, and barriers on site; events return to the audit trail.

Log in to NG-Key Platform and access

Operating posture

  • European operations, data, and AI inference
  • Route of trust from factory to device
  • CRA and NIS2 — product security and operator evidence, not a stamp

From enrolment to evidence.

Cloud administers policy. Enforcement happens where the access path requires it. Audit follows every decision.

Illustration of enrolment, credential issuance, a door decision, and an audit trail.

  1. 01

    Enrol

    Bring people into identity. Bring Accena readers online with Q-Air. Enrolment is part of access, not a side process.

  2. 02

    Issue

    Author DESFire or LEGIC structures, design front and back, encode and print from the station client. Issue FIDO2 NFC keys, NG-Key mobile keys, and Apple or Google Wallet QR passes — including for visitors who should not carry plastic.

  3. 03

    Enforce

    Accena readers and Edge decide locally for cards, Wallet QR, and FIDO2 NFC. FIDO2 runs on the reader or transparently over Edge. Passkeys and Access QR stay cloud-evaluated.

  4. 04

    Audit

    Every decision is recorded. The ledger keeps a tamper-evident chain so history cannot be quietly rewritten.

What NG-Key governs.

Access, credentials, buildings, parking, charging, and workplace operations — including from the employee’s own phone.

Platform and access

Q-Air enrolment, Accena readers, access policy, and administration in one model.

Hardware fleet

Accena readers, NG-IO modules, Edge gateways, and Accena cabinet handles — signed OTA and a factory-to-door trust path on every device.

Credentials and media

Ausweis-Studio authors the chip: DESFire applications, LEGIC advant bound to physical master tokens, and LEGIC neon via Trusted Service VCPs. The graphical designer prints the face. Windows and Mac station clients encode; printer control and Accena USB stay on Windows.

Security and trust

Doors decide locally. Device identity starts at the factory. Credential secrets stay sealed. The ledger records the trail. The copilot stays in Europe and does not open a door.

Operations and buildings

Time attendance after a granted door, shared entrances, parking occupancy and license plate recognition, floor rights, door IO, bookings, and a passkey-gated phone hub.

Integrations

Identity directories, OSS-SO offline locks, OCPP charging on the same credentials, and tenant APIs — no second policy store.

Employee hub

Bring your own device. On a passkey-gated mobile hub, employees present keys, open Wallet passes, book rooms and charging, and request leave — the same grants as a card.

CRA & NIS2

Signed updates and device identity for EU product law. Operators use the same record under NIS2. Not a certificate, and not conformity by purchase.

Start with the security model.

If you evaluate access platforms for production, this is the page to read next.

Read security and trust