Carrier dependencies, roaming, eligibility and integration discussions.
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.
Changing phone, number or carrier can affect subscription binding, security-application eligibility and recovery steps. Because Keyra hardware-verified security is declared on SIM, eSIM and iSIM, re-provisioning or re-enrollment may be required. Exact recovery flows that preserve the hardware trust boundary need product-confirmed runbooks.
Roaming may allow ordinary connectivity, but Keyra hardware-verified features depend on device eligibility, provisioned security applications and verifier reachability—not on roaming alone. Treat roaming support as conditional until a carrier or product guide confirms the feature set for your subscription plan.
Use official Keyra contact pathways from keyra.ie to request commercial quotes or carrier integration discussions. Provide your organization type, geography, form-factor interest (SIM, eSIM, iSIM or card lineage) and whether you need sandbox developer access. This FAQ does not publish private pricing.
Conditions are eligibility matrices—not universal support statements. Public evidence currently highlights iPhone TestFlight and Android early access pathways plus company-declared SIM, eSIM and iSIM implementations. Carrier provisioning, OS permissions and OEM iSIM availability vary by market, so publish detailed matrices only from confirmed partner documentation.
MNOs should separate subscription management from security-application enablement, plan provisioning and eligibility carefully, and engage Keyra through official channels for integration discussions. Company declaration affirms SIM as a current hardware-verified form factor, while commercial coverage, roaming behavior and applet lifecycle remain partner-specific.
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.
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.
iSIM security application updates require authorized management channels appropriate to the integrated SIM environment—typically constrained platform or operator-controlled processes rather than arbitrary app-store writes. Company declaration confirms iSIM as a current form factor; specific update authorization mechanics are not invented here and remain an editorial/engineering task.
