Government, defense & critical infrastructure

YQ Line

Qualify, secure, and govern entanglement links for mission-critical quantum networks.

YQ Line evaluates Bell-state, photon-rate, fidelity, swap, uptime, and observation-window evidence to determine whether a quantum link is pilot-ready. It also protects the classical control path with ML-KEM-768 and preserves reviewable evidence without retaining shared-secret material.

The authenticated post-quantum control path is operational. Quantum-link assurance remains pending until calibration is complete. The interactive workspace needs authorized access.

Security specifications

Public cryptographic architecture

Standards, verification boundaries, and customer-visible controls are public. Private keys, shared secrets, customer data, proprietary calibration methods, and raw failed measurements are not.

Primary algorithm

ML-KEM-768

FIPS 203 algorithm profile for key establishment.

Session derivation

HKDF-SHA-256

Separate directional traffic keys are derived with distinct labels.

Traffic protection

AES-256-GCM

Authenticated encryption uses persisted directional nonce state to prevent reuse.

Hybrid transition

ECDH P-256 when required

A policy-controlled classical component can be bound into the negotiated transcript.

Key confirmation

Transcript bound

Protocol, policy, endpoints, nonces, algorithm profile, and ephemeral material are bound into confirmation.

Endpoint model

Approved endpoint pairs

Organization-scoped endpoints with controlled ownership and link evidence.

Exchange evidence

Persisted metadata

Status, fingerprints, timestamps, and opaque references without returning shared-secret material.

Deployment

Managed, dedicated, or customer-controlled

Final topology and operating controls are defined during technical review.

Security boundaries

These are current product boundaries, not blanket certification or authorization claims.

Open the Trust Center
  • Shared secrets are confirmed but are not returned to the browser or stored as customer records.
  • Customer records and endpoint operations are authenticated, organization-scoped, and access-tier controlled.
  • Production activation requires customer-approved architecture, downgrade behavior, monitoring, and rollback controls.
  • Use of ML-KEM-768 is not itself a claim that a deployment or cryptographic module has CMVP validation.

Product brief

What the organization is buying

Treat each entanglement link as a governed quantum service. Teams can evaluate measured photon performance, test quantum and classical interoperability, and carry acceptance evidence into authorization, pilot operation, and procurement.

Commercial unit

Protected line/month or program coverage

Exact pricing remains quote-based until pilot scope, deployment, and service requirements are validated.

Primary buying group

Program executives, CISOs, mission owners, infrastructure leaders, and procurement teams

High-value use cases

  • Agency-to-approved-system service connections
  • Mission and field-environment interoperability testing
  • Critical-infrastructure control-plane transition planning
  • Long-lived confidentiality and harvest-now-decrypt-later preparation

Measurable outcomes

  • 1A named, owned connection with an explicit cryptographic policy
  • 2ML-KEM-768 key-establishment and confirmation evidence
  • 3A documented path from inventory through test, authorization, rollout, and rollback
Contact Yoon Labs

Turn YQ Line into a bounded, measurable pilot.

A useful first conversation defines the buyer, system boundary, measurable outcome, deployment posture, and diligence requirements. We will bring the technical team into that conversation from the start.

YQ Line pilotTechnical diligenceSecurity review

Talk with Yoon Labs

The prepared email asks for only the information needed to scope the first conversation.

Start the conversation

Do not send classified, export-controlled, regulated, or customer-confidential technical data in the first email.