Historical Ciright CyberONE hardware security card lineage (passwordless MFA, ECC, FIDO and workforce security themes) that Keyra builds upon.
Form factors: card
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.
Publicly evidenced today: Keyra consumer-facing messaging and technology pages on keyra.ie and app.keyra.ie, including TestFlight beta and Android early access pathways, plus the public keyra-java-sdk for partner integration patterns. Cyber One Card materials are historical. Vault Certified is a target architecture; Connected and V2X remain proposed.
Developers should use the intended developer portal at developer.keyra.ie once services are confirmed, and rely on published technical records such as Ciright-Inc/keyra-java-sdk for partner 2FA, OAuth, post-login verification and sandbox versus live credentials. cyberonecard.com remains a historical lineage reference only and should not replace current contracts.
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.
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.
A publicly evidenced SDK is Ciright-Inc/keyra-java-sdk, covering partner 2FA, OAuth, post-login verification and sandbox versus live credentials. Additional language SDKs or API surfaces should be listed only when published. Historical Cyber One developer SDKs on cyberonecard.com are lineage references, not automatic current Keyra contracts.
Per Joseph Callahan’s company declaration dated 5 September 2026, Keyra builds on more than 15 years of Ciright Cyber One Card technology lineage. The approved public wording states Keyra builds on more than 15 years of Ciright Cyber One hardware-security experience. Philly Codefest 2022 corroborates CyberONE developer activity in 2022 only and does not alone prove the full period.
Cyber One Card is the historical Ciright hardware-security card product lineage. Keyra is the current platform narrative that extends that lineage into SIM, eSIM and iSIM hardware-verified security. cyberonecard.com is the historical product reference; keyra.ie is the current public ecosystem entry.
cyberonecard.com hosts historical Ciright Inc CyberONE materials describing passwordless MFA, elliptic-curve cryptography themes, FIDO-oriented positioning, workforce security and developer SDKs. It is designated the historical product reference for the Keyra story. Treat feature lists as historical context, not automatic current Keyra guarantees.
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.
