QRNG and QKD, two quantum technologies solving different problems
A QRNG generates unpredictable numbers locally, inside the device that needs them. QKD distributes a shared key between two locations over a dedicated optical link. They solve different problems, and Quside builds the first and not the second.
The two problems
Generating a secret and sharing a secret are separate tasks. A QRNG answers "produce a number nobody can predict", which happens in one place and requires no counterparty. QKD answers "establish the same key at both ends of a link so that eavesdropping is detectable", which requires two endpoints and a channel between them.
The confusion is understandable — both use quantum optics and both concern keys — but the deployment consequences are not comparable. A QRNG is a component you put in a device. QKD is an infrastructure programme involving dedicated fibre, distance limits and trusted relay nodes.
What each one requires of you
- QRNG — install a card, a module or an IP block. No counterparty, no new link, no distance constraint. It improves key generation wherever it is placed.
- QKD — provision an optical path between exactly two endpoints, accept a distance limit, and either accept trusted relays for longer routes or restrict the topology to what a single span reaches.
Being plain about what we do not do
Quside does not build QKD systems. We build entropy sources. If your requirement is a shared key between two sites, we are not the supplier for it, and a vendor who claims both should be asked to be specific about which product does which.
Saying this plainly is worth more than the business it might cost. A supplier that will tell you what it does not do is a supplier whose other claims are easier to trust.
Where they meet, and where they do not
A QKD system needs good randomness internally — basis choices and key material both depend on it — so a QRNG can be a component inside QKD equipment. That is the real relationship: one is sometimes a part of the other, and they are not alternatives.
For protecting data against a future quantum adversary, the mainstream answer is not QKD but algorithm migration, which is the post-quantum pillar. The relationship between that migration and randomness is covered in PQC does not replace QRNG, and QRNG does not make you quantum-safe.
Keep reading
- Deployment and integration
QRNG for HSMs and PKI
An HSM generates keys that protect everything else, so the entropy source inside it is the root of the whole hierarchy. What matters for an HSM or a certificate authority is not only that the source is physical, but that its entropy claim is evidenced within the module boundary and can be demonstrated during evaluation and audit.
- Deployment and integration
QRNG form factors, from PCIe card to silicon IP
Quside supplies entropy sources as PCIe cards, FMC modules, embedded modules and licensable silicon IP. The choice is governed by where entropy needs to be generated relative to what consumes it, and by how many units you are building.
- Deployment and integration
Integrating a QRNG: C, Python, Rust and the Linux entropy path
On Linux a hardware entropy source is normally exposed through the kernel random subsystem, so applications keep calling getrandom() and inherit the better seed without changing. Direct access through a device interface or a library is available where an application needs entropy that has not passed through the kernel pool.