1. NFC provisioning
A tag UID and protected key material establish a hardware-specific identity. Diversified keys help avoid treating every tag as the same secret.
Our platform combines NFC provisioning, Bluetooth device context, and passkey authentication so a physical interaction can become a verifiable, auditable workflow.
A tag UID and protected key material establish a hardware-specific identity. Diversified keys help avoid treating every tag as the same secret.
Mobile-device context can accompany the hardware event, helping an operator connect the physical action to the device and workflow involved.
Passkeys add phishing-resistant user verification around the hardware event, while role-aware workspaces keep administration and operations separate.
physical tag → NFC UID
↓
diversified key + device context
↓
passkey verification
↓
authorized workspace actionBridge hardware is intended to connect compatible legacy interfaces to modern authentication and synchronization workflows. Final dimensions, interface support, power requirements, and pricing depend on the target deployment and will be published with each supported model.
Designed around the legacy access point or controller being integrated. Compatibility is validated per model and installation.
The bridge should minimize exposed legacy functionality and keep secrets and authorization decisions under controlled software paths.
Every installation should document power, enclosure, connectivity, recovery, and maintenance requirements before rollout.