Key2XS sits between your identity platforms and the physical key systems that run your sites. Don't take our word for it: run an identity event and watch it land.
Entitlements in Identity Security Cloud drive physical access end to end. One click to connect.
Groups and lifecycle state in Entra ID govern keys the moment HR does its work.
Okta workforce identities extend to cylinders, cabinets and sites without a parallel admin world.
Certification campaigns and approval flows in One Identity now cover the physical estate too.
Joiner, mover and leaver events in OpenText Identity Manager propagate to every key system.
Self-powered digital locking. Key validity and access rights orchestrated from identity.
Electronic keys and cylinders under identity governance, with validity windows per key.
High-security mechanical-electronic keys, governed by the same lifecycle as digital access.
ACCESS and PULSE digital locking, connected to the same identity lifecycle and audit trail.
Intelligent key cabinets with curfews and return control, issued against identity and policy.
Intrusion alarm systems under the same identity lifecycle: who may arm, disarm and enter, governed centrally and written to the same audit trail.
Esri ArcGIS supplies location and coordinate data for assets and access points, so every key, cylinder and cabinet is governed with its exact place on the map.
Every integration binds the system's native capabilities to identity, policy and one audit trail. The differences that matter:
| System | Keys | Cylinders | Cabinets | Remote update | Offline capable | Key2XS mobile app |
|---|
Capability map shown for review; each cell is confirmed with product before this page ships.
Key2XS speaks to each system through the manufacturer's official interface, and to your IAM through SCIM and APIs. No rip and replace, no locking-plan changes.
Identities, roles and policies map to keys, cylinders and cabinet positions. Who may open what, where, in which time window: defined once, enforced everywhere.
Joiner, mover and leaver events flow continuously. Provisioning, validity updates and revocations land in every connected system without an operator in the loop.
Every request, approval, issue and return is written to one audit trail. NIS2 and CER evidence becomes an export, not a project.
No. Key2XS is middleware. It orchestrates access rights through the standard interfaces of your existing key systems: iLOQ, ASSA ABLOY CLIQ, ASSA ABLOY Access and Traka. Locks, keys and the locking plan stay as they are.
Integrations run against each manufacturer's official interfaces and are validated with every vendor release. Identity-side connectors follow the platform vendors' supported APIs and SCIM profiles.
Connecting a system is measured in days. The real timeline is set by identity mapping and policy design, which we run as a structured onboarding with your IAM and facility teams.
It is the normal case. Key2XS was built for heterogeneous estates: one governance model and one audit trail across every connected system, including during migrations between systems.
Bring your IAM and your key systems; we bring the control plane. A 30-minute demo with your own scenario on screen.
