Ciright is an enterprise technology company that architects, integrates and operates the technology infrastructure of the Trusted Enterprise — with Keyra establishing trusted authority, and Cyber One making that authority physical.

What is the Trusted Enterprise?

A Trusted Enterprise is an organization in which people, applications, devices, machines and AI can interact while identity, authority, policy and consequential actions remain governed and attributable.

What is Keyra's role?

Keyra is Ciright’s trust and authorization infrastructure. It is designed to establish trusted relationships around identity, credential, device, authority, policy, intent, action and evidence.

Cyber One is a physical hardware-rooted credential designed to bring trusted identity and authorization closer to the person. It is a delivery modality of Keyra, not a separate company and not a payment product.

What is authorization?

Authorization determines what may happen next. Authentication only identifies who is present. Ciright treats identity, authority, policy, action and evidence as one relationship.

How does Ciright approach AI governance?

Ciright’s position is architectural: AI can act, and authority still matters. Agents may read, recommend, communicate, initiate, transact and coordinate under policy. Consequential actions remain attributable. This is conceptual architecture, not a claim of a specific production agent deployment.

KEYRA / DIGITAL TRUST

Bring evidence and authority to sensitive decisions.

Keyra focuses on hardware-rooted trust and the approval of sensitive actions. For banks, telecom operators, and enterprises, evaluation starts with a specific workflow: what must be verified, which deployments are supported, and who has authority to approve the action. Explore the technology and define what a responsible integration would require.

Discuss a Trust Use Case Review the Approach

EXPERIENCE / EXECUTION / ACCOUNTABILITY

Decades of engineering. Focused on the work ahead.

Ciright brings decades of enterprise technology experience to complex operating challenges. That experience shapes how we approach new work: understand the systems already in place, define responsibilities, work through constraints, and make progress reviewable.

Understand the environment.Start with the systems, policies, and people the organization already relies on.
Make responsibility clear.Agree scope, owners, dependencies, and acceptance criteria before expansion.
Stay accountable to the work.Review issues, decisions, and outcomes throughout the engagement.

The difficult details deserve experienced attention.

Company background

What you can explore

Explore Keyra's published approach and developer resources through the official links below.

What we would scope together

The decision to support, evidence required, participating systems, supported hardware and provisioning, approval policy, and recovery responsibilities.

A convincing request still needs a trustworthy decision process.

A familiar voice, a phone number, a device, or a valid session can each provide context. Sensitive actions also require the right authority, the right approval, and a record of what was decided. The controls must fit the institution's existing policies and operating environment.

Identity evidence

What can be established about who or what is present.

Authentication

How a session or credential is established.

Permission

What an authenticated actor is allowed to do in policy.

Action approval

How a specific consequential action is authorized before execution.

For Banks & Financial Institutions

Make the decision clearer. Keep authority with the institution.

Choose a sensitive workflow where identity evidence, permission, and approval must work together. Explore where Keyra could contribute within a supported integration, how the bank would retain control, and what evidence a pilot should produce. Define the exception paths as carefully as the successful outcome.

What business problem are we solving?

One specific workflow and its intended control improvement.

What changes in our environment?

The proposed connection point and systems affected.

Who approves and executes?

The bank retains its authorization policy and authority to release an action.

What happens if verification fails?

No silent approval or invented fallback guarantee.

How do we review the relationship?

A concrete technical and supplier-diligence conversation.

Illustrative opportunities — payment-instruction approval, sensitive beneficiary changes, employee privilege changes, and account-recovery steps — are candidate integration use cases until the exact product behavior is demonstrated.

For Telecom Operators

Define the trust opportunity around your network and subscribers.

Start with a defined subscriber or enterprise journey. Evaluate the supported signals, hardware, provisioning, and service responsibilities that could make a trust offering useful. Establish eligibility, lifecycle handling, support effort, and commercial assumptions before expanding the scope.

Where does this fit?

Define the role alongside the operator's existing identity and network services.

What has to be provisioned?

Supported devices, SIM/eSIM profiles, applets, and participating services where evidenced.

Who controls the keys and lifecycle?

Confirm the actual mechanism and custody model for generation, rotation, and recovery.

Which customer situations need handling?

Device changes, SIM changes, number recycling, dual-SIM use, roaming, and service loss.

How would it become a service?

Scope enterprise distribution, customer support, charging, and reconciliation.

Discuss a Carrier Integration

Trust flow

Identify
Who or what is present.
Authorize
What may happen next.
Authenticate
How trust is confirmed.
Act
What is executed under policy.
Audit
What evidence remains.

Conceptual integration

Request context → supported verification → institution policy → approval decision → recorded outcome.

Explicitly separate what stays with the institution from what a proposed provider processes. Clarify data categories, custody, availability dependencies, recovery, and whether the design requires carrier participation.

Trust Trace

Identity, authority, policy, action and evidence as one inspectable sequence.

Actor: Person, device, application or agent
Authority: —
Policy: —
Action: Presents as a participant
Evidence: Identity asserted

Detailed cryptographic methods, interfaces, support policies, retention, and recovery tests belong in the approved technical review. Keyra Developer Platform has current integration information.

Modalities

One engine. Multiple supported deployment paths.

Cyber One

A physical credential designed to bring trusted identity closer to the person.

Explore Cyber One →

SIM

Carrier-linked identity composed into the same trust engine where supported.

Discuss →

eSIM

Provisioned identity for supported devices and programs—coverage varies by operator and profile.

Discuss →

Institution credentials

Bank, enterprise, or government credentials under one authorization layer where scoped.

Discuss →

A defined path from use case to evidence

Start with a priority your team can name. Define the operating constraints, responsibilities, and evidence needed to evaluate a solution. Use a controlled pilot to decide what should change, what should stay, and whether to expand.

01Understand — Agreed use-case brief and baseline
02Design — Architecture and responsibility map
03Prove — Pilot results with limitations and unresolved issues
04Introduce — An agreed release or adoption plan
05Review — Decision to improve, expand, pause, or exit

Book a technical briefing.

Bring one priority and the constraints around it. Discuss what a solution would need to connect with, who would own each decision, and what evidence would justify the next step.

Book a Technical Briefing Explore Cyber One

CONTINUE WITH KEYRA

Explore Keyra. Build trusted interactions.

Visit Keyra to explore the company and its approach to digital trust. Open the developer platform for technical resources and integration guidance.

Ciright