Technology Partners

Build products that work
with KeyShare.

KeyShare integrates with the hardware and software that buildings and hotels already use. If you manufacture locks, build PMS platforms, make access control readers, or design hardware products — there's a partnership path.

Become a Technology Partner Enablement Platform →

Not a technology vendor? Channel Partner Program →

Integration Programs

Four partnership tracks.

Lock Manufacturers

Add wallet key delivery to your lock platform. KeyShare's GEP orchestrates wallet key provisioning for hotel guest room locks — encoding and delivering a wallet key when a guest taps the Puck.

Current integrations: Assa Abloy Vostio (integrated), Salto (in progress), dormakaba (planned), Onity (planned).

Discuss Lock Integration →
Typical integration timeline:
PhaseWhat HappensTimeline
1. AssessmentKeyShare reviews your platform API documentation1–2 weeks
2. Adapter devKeyShare builds the adapter. Joint engineering review.4–8 weeks
3. Joint testingEnd-to-end: key provisioning, revocation, extension, edge cases2–4 weeks
4. CertificationJoint sign-off. Listed on compatibility page.1 week
5. Go-to-marketJoint press release, co-branded solution briefCoordinated

PMS Vendors

Give your properties identity-verified check-in. The GEP integrates via event-driven adapters and the Command API — your PMS remains the primary staff interface while GEP orchestrates silently.

Current integrations: Opera (OHIP), Mews, Apaleo (integrated). BookingCenter, Shiji, Cloudbeds (in progress).

Discuss PMS Integration →
Integration models:
ModelDescriptionYour Effort
WebhookPush reservation events to GEPImplement webhook dispatch
Command APIGEP triggers via your PMS UIImplement REST API calls
BidirectionalBoth webhooks and Command APIBoth of the above
Timeline:
API reviewJoint architecture call — 1 week
Adapter developmentKeyShare builds event adapter — 3–6 weeks
Joint testingReservation lifecycle + edge cases — 2–3 weeks
CertificationJoint sign-off — 1 week

Reader Manufacturers

Become KeyShare Ready. The Reader Library is embedded firmware that runs on NFC-capable access control readers — handling ISO 18013-5 identity verification at the reader edge and reporting results via OSDP v2.2.

Apply for KeyShare Ready Certification →

Licensing is structured to align with your business model — not to create a per-unit tax on reader hardware.

Hardware requirements:
ARM Cortex-M4 Flash 128 KB+ RAM 80 KB+ ISO 14443 A/B OSDP v2.2
ResourceMinimumRecommended
ProcessorARM Cortex-M4ARM Cortex-M4F (hardware FPU)
Flash128 KB available256 KB (for OTA staging)
RAM80 KB96 KB
NFCISO 14443 Type A/BWith ISO 18013-5 NFC engagement
OSDPv2.2 with SCSv2.2 with SCS
Certification process:
CompatibilitySubmit hardware specs — 1–2 weeks
IntegrationReader Library SDK + HAL integration — 4–8 weeks
TestingNFC → OSDP → Panel Application → PACS — 2–4 weeks
CertificationKeyShare Ready badge issued — 1 week

Hardware OEMs

Build "KeyShare Powered" products. The Enablement Platform is KeyShare's OEM toolkit — hardware modules, SDKs, firmware libraries, and the Panel Application — for manufacturers building products with embedded identity verification.

Certification programs: KeyShare Ready (readers), KeyShare Powered (locks/kiosks), Panel Certified (panel manufacturers).

Explore the Enablement Platform →
Platform components:
ComponentWhat It IsFor
Reader Communication ModuleNFC hardware module (PCB-mountable)Reader manufacturers
Lock Communication ModuleNFC hardware module for electronic locksLock manufacturers
Reader LibraryEmbedded firmware (C/MISRA C:2012). ISO 18013-5.Reader manufacturers
Panel ApplicationContainerized software for access panelsPanel manufacturers
Mobile SDKsNative iOS/Android SDKs for NFC interactionKiosk and terminal OEMs
Partner Support

How we support technology partners.

Technical Training

Integration workshop (4 hours) — your engineering team and ours.

API / SDK Access

Full API documentation, SDK packages, sandbox environments upon partnership agreement.

Engineering Support

Dedicated integration engineer for initial development. Ongoing escalation path.

Certification

Technology Partner badge upon completed integration and joint testing.

Co-Marketing

Joint press release, compatibility listing, co-branded solution brief.

Deal Registration

Register referral opportunities for referral fee.

Ecosystem

Technology ecosystem.

KeyShare integrates with the platforms and hardware that hotels and buildings already use.

Lock Vendors
  • Assa Abloy Vostio Integrated
  • Salto In Progress
  • dormakaba Planned
  • Onity Planned
PMS Platforms
  • Oracle / Opera (OHIP) Integrated
  • Mews Integrated
  • Apaleo Integrated
  • BookingCenter In Progress
  • Shiji In Progress
  • Cloudbeds In Progress
PACS Software
  • Genetec Integrated
  • LenelS2 Planned
  • Acre Planned
  • RS2 Planned
  • Access It Planned
KeyShare Ready Readers

The KeyShare Ready certification program is now accepting applications.

Be among the first →

Become a Technology Partner.

Tell us about your product and integration goals.

A technology partnerships lead will reach out within 5 business days.