CSE: QSE
Quantum Secure Encryption Corp.
Book an assessment

Migration

qREK

The re-encryption bridge between legacy crypto and the PQC future.

Re-encryption key bridge for legacy systems migrating to post-quantum cryptography.

Talk to the product team See it in action

In action

Quantum entropy, straight into the kernel.

The qREK entropy daemon fetches quantum-random bytes from QSE’s Entropy API over TLS and writes them into the Linux kernel’s random pool, so keys generated on that host draw on quantum entropy. Pick a mode and watch it run.

qrek-linux-entropy-daemon · Linux host Simulation
# qREK entropy daemon (.env) QSE_LOG_LEVEL=INFO QREK_LOOPS=12 QREK_SLEEP_SEC=1 QREK_MAX_BYTES=256 # MODE TYPES: inject_loop, inject_once, mix, fetch QREK_MODE=inject_loop

Daemon log

strace -e write · what the kernel sees

Mode
Inject loop
Batch
0 / 12
Fetched
0 B
Injected
0 B
Kernel entropy_avail
256 bits
Latest 256-byte batch

Turn on JavaScript to watch the simulation. In inject-loop mode the daemon fetches 256 quantum-random bytes per batch from the QSE Entropy API and writes each batch into /dev/random.

  1. 01 · Fetch

    Quantum-random bytes arrive from the QSE Entropy API over TLS, 256 at a time.

  2. 02 · Mix

    Optionally combined with local randomness, with a SHA-256 fingerprint of each batch logged for audit.

  3. 03 · Inject

    Each batch is written into the kernel’s random pool through /dev/random, as the strace pane shows.

Simulation based on a recorded session. Host names, addresses and the API endpoint are placeholders.

Talk to the qREK team

Capabilities

What qREK ships with.

01

Hybrid envelopes

Wrap legacy RSA/ECC-encrypted payloads in ML-KEM envelopes without re-issuing data.

02

Proxy re-encryption

Translate between cryptographic regimes at the edge — no plaintext exposure.

03

Policy engine

Per-tenant, per-jurisdiction key handling and rotation policies enforced in hardware.

04

Migration telemetry

Live dashboards of remaining classical-crypto exposure across the estate.

Outcomes

What customers measure after deploying qREK.

  • Cut PQC migration timelines from years to months
  • Avoid full data re-encryption events on petabyte estates
  • Maintain interoperability with non-PQC counterparties

Specifications

At a glance.

Modes
Hybrid RSA+ML-KEM · ECC+ML-KEM · Pure PQC
Interface
KMIP · REST · gRPC sidecar
Throughput
Millions of re-wraps per second per cluster
Compliance
CNSA 2.0 migration profile

Get started

Put qREK to work.

Talk to the product team about deploying qREK in your environment.

Talk to the product team