What's in the platform.
The Enablement Platform includes five components. OEM partners license the components relevant to their product category — you don't need all five.
Reader Communication Module
HARDWAREA hardware module that handles NFC communication with mobile devices. The RCM manages antenna control, NFC field generation, session establishment, and raw data exchange with the phone. It's the NFC frontend that the Reader Library firmware runs on.
For: Reader manufacturers building NFC-capable access control readers.
Relationship: The RCM provides the NFC hardware layer. The Reader Library provides the firmware layer. Together, they turn a reader into a "KeyShare Ready" identity verification endpoint.
Specifications
Lock Communication Module
HARDWAREA hardware module for electronic lock manufacturers. Handles NFC communication with guest phones and communicates with the lock's controller to trigger lock/unlock operations.
For: Lock manufacturers building electronic locks with NFC capability.
Specifications
Reader Library
FIRMWAREEmbedded firmware for NFC-capable access control readers. Handles ISO 18013-5 identity verification — NFC session, selective disclosure, cryptographic signature verification — and reports via OSDP v2.2.
For: Reader manufacturers integrating identity verification.
Integration model: HAL (Hardware Abstraction Layer). Reference implementation on TI CC26X2R1. Full detail →
Specifications
Panel Application
CORE SOFTWARE — CENTERPIECESoftware that runs on access control panels. The intelligence layer between the reader edge and the PACS — receives verified identity data from readers via OSDP, derives a site-specific UUID, validates against a locally cached manifest, and passes a standard credential number to the PACS through the panel's native interface.
For: Access control panel manufacturers considering KeyShare integration.
Why this matters: Access decisions happen on the panel, not in the cloud. Doors open during cloud outages. The PACS is unchanged — it receives standard credential numbers.
Roadmap: Mercury Security (current) · HID (in progress) · Honeywell NetAXS (planned — gateway model)
Specifications
Mobile SDKs
iOS & ANDROIDNative iOS and Android SDKs for building applications that interact with the KeyShare Puck. The Wallet SDK (hotel brand apps) and Digital ID Mobile SDKs (citizen wallet apps) are part of the Enablement Platform when licensed by OEM partners.
For: OEMs building branded check-in terminals, kiosk applications, or guest/citizen-facing apps.
iOS 15+ · Android 8+
Full Puck feature parity
The Puck as reference implementation
The KeyShare Puck — the countertop NFC terminal — is the reference implementation of the Enablement Platform. It contains the RCM hardware, the identity verification firmware, and communicates with GEP via USB. See the Puck →
How the components fit together.
Key architectural properties
Panel Application makes all access decisions locally. No cloud round-trip for any door opening.
Reader processes identity in transient memory. No PII stored on reader or panel.
PACS receives standard credential numbers. No API changes to PACS.
Connect handles enrollment and manifest distribution. Never required for a door to open.
Cross-site tracking architecturally impossible. A UUID from one site cannot be correlated with another. Each deployment derives unique identifiers — correlation across sites is prevented by design, not policy.
Certification and go-to-market.
Every product built on the Enablement Platform goes through certification before going to market — validating protocol implementation, security requirements, and end-user experience.
KeyShare Ready
READER MANUFACTURERSReader Library integration. NFC session, OSDP communication, identity verification accuracy.
KeyShare Powered
LOCK / KIOSK / TERMINAL OEMsHardware module integration. NFC session, credential delivery, wallet provisioning.
Panel Certified
PANEL MANUFACTURERSPanel Application integration. Credential injection, manifest caching, UUID derivation, offline operation.
Licensing terms are structured per OEM partner's business model. KeyShare does not apply per-unit licensing that taxes hardware margins.
Discuss OEM partnership and licensing →Engineering support for OEM partners.
Dedicated integration engineer
Assigned for the initial development cycle. Available for architecture review, code review, and joint debugging.
Reference implementations
Working code on reference hardware platforms (TI CC26X2R1 for readers). Runnable on dev boards before committing to production hardware.
Sandbox environment
Simulated end-to-end testing: NFC session → OSDP → Panel Application → PACS. Cloud-connected for manifest sync testing.
Technical documentation
HAL specifications, API references, integration guides, architecture documents. Available under NDA upon partnership agreement.
OTA update infrastructure
Firmware updates delivered through the Panel Application over OSDP (readers) or through Connect (Panel Application). No direct cloud connection required.
Versioning protection
Semantic versioning with formal deprecation policy. OTA updates never break integrations. Major version upgrades coordinated with certified partners.
Ongoing escalation
Direct engineering escalation path for certified OEM partners.
Frequently asked questions.
Build with KeyShare.
Whether you're embedding NFC identity verification into a reader, adding wallet key delivery to a lock, or building a "KeyShare Powered" kiosk — the Enablement Platform provides the components, engineering support, and certification path.