Company-declared current implementations of Ciright/Keyra hardware-verified security running on SIM, eSIM and iSIM.
Form factors: sim · esim · isim
Keyra is a hardware-security oriented identity platform for verifying people and approving sensitive requests. It builds on more than 15 years of Ciright Cyber One Card experience. Company declaration dated 5 September 2026 states the technology now runs on SIM, eSIM and iSIM for hardware-verified security. Public materials emphasize privacy, consent and mobile trust signals alongside cryptography.
Hardware-rooted authentication means authentication proofs depend on credentials or operations protected by hardware security environments rather than software-only secrets. For Keyra, company declaration places current implementations on SIM, eSIM and iSIM for hardware-verified security, extending earlier Cyber One Card hardware approaches.
Not necessarily. Company declaration states current hardware-verified security runs on SIM, eSIM and iSIM, extending beyond the physical Cyber One Card. A physical card may still matter for specific programs or historical deployments, but public Keyra consumer messaging centers on mobile verification pathways.
Joseph Callahan’s 5 September 2026 company declaration states Keyra builds on more than 15 years of Ciright Cyber One Card experience and that the technology now runs on SIM, eSIM and iSIM for hardware-verified security. The approved foundation wording presents this as an extension of the physical card lineage into integrated mobile form factors.
No. A connectivity eSIM profile provisions mobile subscription credentials for network access. A Keyra security application or applet is a distinct security workload for hardware-verified operations. They may share an eSIM platform in some architectures, but connectivity alone is not Keyra security.
Support is eligibility-based, not universal. Public Keyra messaging references iPhone TestFlight beta and Android early access, which implies selected device pathways rather than every phone or carrier. Company declaration of SIM, eSIM and iSIM implementations does not assert global MNO coverage or identical feature sets worldwide.
Keys used for hardware-verified security are intended to be generated and protected in hardware-backed environments associated with the active form factor—card historically; SIM, eSIM or iSIM currently per company declaration. Exact generation location, custody model and export policy per deployment remain editorial tasks until engineering publishes confirmed details. This answer does not invent algorithms or key sizes.
Company declaration: the technology now runs on SIM for hardware-verified security. Public technology messaging describes SIM as a trust-anchor theme supporting network verification and related fraud-detection narratives. Detailed applet deployment, key custody and host-access paths remain engineering documentation tasks and are not invented here.
Company declaration includes eSIM as a current form factor for hardware-verified security. Public Keyra materials reference SIM/eSIM signals with cryptography for verification use cases. A connectivity eSIM profile is not itself the security applet; eligibility and provisioning determine whether Keyra security functions are present.
Company declaration dated 5 September 2026 states the technology now runs on iSIM for hardware-verified security as part of the SIM/eSIM/iSIM set. iSIM integrates SIM functionality into a device secure processing environment. Detailed update control, key storage and verification encodings remain editorial tasks until engineering confirms them.
At a high level, card implementations historically executed security functions on card secure hardware; SIM, eSIM and iSIM implementations execute within their respective protected SIM environments as integrated by the platform. Exact execution boundaries, host APIs and operator roles differ and are marked editorial_task in the hardware matrix until confirmed.
Consistent across form factors: the lineage goal of hardware-verified security and Ciright Cyber One heritage. Differs: physical integration, provisioning, operator dependency, host access paths, recovery mechanics and feature availability. Do not assume key material or APIs move unchanged between form factors.
