Skip to content
Partners

An entropy source is never the whole architecture.

A trusted hardware layer sits between an optical supply chain underneath it and a cryptographic stack above it. These are the partnerships that make the seams explicit rather than leaving them to the integrator.

How they fit

Where a partner sits.

Below the source, above it, or around the deployment. Each relationship takes a specific piece of integration work off your programme.

Silicon and hardware

Lattice · Coherent

Partners in the part itself: the programmable logic a root of trust runs on, and the optical supply chain the entropy source is built from.

Cryptographic software

PQShield · Keyfactor

Partners above the source: post-quantum algorithm implementations, and the PKI and certificate lifecycle systems that consume key material at scale.

Deployment

Equinix

Partners around the deployment: the colocation and interconnection environments where a great deal of regulated infrastructure physically sits.

The partnerships

What each one does for your design.

What each relationship changes about the part you integrate, and what it leaves to you.

Lattice

FPGA and embedded root of trust
In the architecture
Lattice programmable logic is where a hardware root-of-trust function runs in a compact embedded design. Onyx™ X5 puts that logic and the entropy source in one module rather than in two parts on opposite sides of a bus.
What it changes for a customer
Fewer parts to qualify in a constrained system, and one supplier conversation about how the entropy source and the root of trust share a board.
Worth knowing
Two shipping embedded parts: Onyx™ S1, the source on its own at 50–100 Mbit/s, and Onyx™ X5, the source with the root of trust beside it. First Onyx units have gone to defence customers.

Coherent

VCSEL supply and photonics
In the architecture
Coherent supplies the VCSELs and material behind Ruby™ S1, which uses polarisation switching — the same device class used for face recognition and proximity sensing in phones.
What it changes for a customer
A consumer-scale optical supply chain underneath a security component, which is what makes the size, power and cost point of the Onyx™ line credible at volume.
Worth knowing
It also separates the two chip platforms cleanly: Ruby™ N1 is optimised for throughput on a dedicated photonic line, Ruby™ S1 for volume and cost.

PQShield

Post-quantum software
In the architecture
Post-quantum algorithm implementations sit above the entropy source. FIPS 203, 204 and 205 were finalised in August 2024, and every one of those schemes consumes randomness for key generation, encapsulation and signatures.
What it changes for a customer
PQC algorithms and entropy assurance solve different parts of the same cryptographic architecture. Pairing them makes the seam between the two explicit rather than leaving it to the integrator.
Worth knowing
Entropy quality is an input to every one of those schemes. If you are planning a migration, settle early where the seed comes from and what evidence you hold for it.

Keyfactor

PKI and certificate lifecycle
In the architecture
Certificate authorities and key management systems are among the heaviest consumers of key material in an enterprise, and they depend on strong seeding and appropriate reseeding from a trusted entropy source.
What it changes for a customer
A local entropy source inside the PKI trust boundary, reporting its own health, rather than a source whose quality is asserted once at procurement.
Worth knowing
Approved DRBGs depend on strong seeding, correct construction and appropriate reseeding. SP 800-90C, final in September 2025, describes how a validated source and an approved mechanism combine.

Equinix

Data-centre interconnect and deployment
In the architecture
Colocation and interconnection environments are where a great deal of regulated infrastructure physically sits — security appliances, HSMs, key management and PKI estates.
What it changes for a customer
That is where a locally installed Garnet™ PCIe card ends up: inside equipment already racked in those facilities. The entropy source stays local to the customer’s own device and inside their trust boundary.
Worth knowing
Quside does not deliver randomness over a network. Entropy that arrives over a link cannot be verified where it is used.
Work with us

Where a partnership usually starts.

Most partnerships start as one integration in one product, then spread across a family once the qualification work is done and the evidence can be reused.

If you build security appliances, network equipment, HSMs, satellite payloads or embedded platforms, the conversation is about which slot the entropy source occupies in your next design and what evidence your customers will ask you for.

Useful things to bring

  • The form factor you have room for: PCIe, FMC, or an embedded module.
  • The entropy rate your system actually consumes, and when it consumes it.
  • The certification or qualification scheme your customers hold you to.
  • Whether a root-of-trust function needs to sit in the same part.
  • The volume curve — one design today usually implies a cost target later.