Our History

The Road to Keyra

More Than a Decade of Persistent Engineering

Keyra was not invented overnight. Keyra evolved from years of engineering surrounding programmable credentials, secure physical cards, mobile connectivity, secure elements, identity, authentication, and human authorization. The Keyra platform represents the latest generation of that journey—not a product invented solely for the AI age.

Talk to KeyraExplore technology

The core story

From many cards to verified human authorization

Early question

Early smart-card companies attempted to solve: How can several cards become one card?

Where it led

Ciright’s engineering journey ultimately evolved toward: How can one secure hardware endpoint establish that a real human authorized a digital action?

Publicly verified industry history · Ciright company history / internal engineering chronology (where public documentation is limited)

Core evolution

  1. 2012 — Multiple cardsthen
  2. Programmable cardthen
  3. GoNow generationthen
  4. Stratos / connected card generationthen
  5. Ciright ONEthen
  6. Ciright Secure Card Platformthen
  7. Java Card + Secure Elementsthen
  8. CyberONEthen
  9. Hardware authenticationthen
  10. Hardware-rooted identitythen
  11. Human authorizationthen
  12. Keyrathen
  13. Human trust infrastructurethen
  14. Agentic AI era

Technology timeline

Expand each milestone for the problem, technology, what Ciright learned, what survived, and how it led to Keyra.

  1. The Problem

    People carried too many plastic cards. Startups asked whether several credentials could live behind one physical endpoint.

    The Technology

    Programmable multi-credential cards, phone-linked provisioning, early mobile/card interaction, and experiments in power, storage, and lifecycle control.

    What Ciright Learned

    • Multiple credentials behind one endpoint introduce provisioning and revocation complexity
    • Phone–card interaction and power management dominate real-world UX
    • Reader compatibility and manufacturing constraints shape what ships
    • Consumer expectations collide with secure storage realities

    What Survived

    • Credential abstraction concepts
    • Lifecycle thinking (provision, update, revoke)
    • Physical endpoint as trust surface

    How It Led to Keyra

    Programmable credentials evolved toward secure digital identity—not merely payment consolidation.

    Publicly verified history

Ciright Secure Card Platform

Ciright applications and secure-card architecture may operate using established secure-element and Java Card technologies where applicable. Ciright does not claim ownership of Java Card itself.

  1. Ciright Secure Card Platformthen
  2. Secure Elementthen
  3. Java Card environmentthen
  4. Applet architecturethen
  5. Credential Managerthen
  6. Cryptographic Key Managementthen
  7. NFCthen
  8. FIDOthen
  9. Biometricsthen
  10. Device Bindingthen
  11. Identity Applicationsthen
  12. Authentication Applicationsthen
  13. Enterprise Applicationsthen
  14. Cloud Provisioningthen
  15. Lifecycle Managementthen
  16. Ciright Core

Keyra trust assertions

WHO

Who is the human?

WHAT

What action is being authorized?

WHERE

Which hardware, device, or session is involved?

WHEN

When was authorization granted?

PROOF

What cryptographic evidence establishes the authorization?

Brand eras

  1. 2012One Card.
  2. 2016One Secure Credential.
  3. 2021One Hardware Identity.
  4. 2026One Verified Human.

KEYRA

The Trust Layer for Human Communication.

Built through years of persistent engineering. Designed for the Agentic AI Era.

Built through years of persistent engineering

Built through years of persistent engineering. Designed for the Agentic AI Era.

Talk to KeyraExplore technology