Skip to content
Patent portfolio

The engine is ours, and it can be yours.

Ninety-plus patents cover how Quside generates entropy from a physical process, extracts it at rate, and measures it while it runs. That position is what makes the engine licensable: it can move onto your silicon with a model of how it behaves, rather than as a black box you have to take on trust.

90+
Patents

Photonic entropy generation, extraction and runtime measurement

2012
Research start

Phase diffusion in semiconductor lasers, studied six years before the company was independent

2
Silicon platforms

Ruby™ N1 and Ruby™ S1, both in production and both shipping in products today

What it covers

What the portfolio covers.

The portfolio follows the same path the signal does: generate it physically, extract it at rate, measure it in service, and put all of that on a chip somebody can manufacture.

Entropy generation

Quantum phase diffusion in semiconductor lasers, and the VCSEL polarisation switching used in the compact engine. The physical processes the products are built on.

Extraction and conditioning

Turning a measured physical signal into uniform bits at rate, which is the part that decides whether a source is fast enough to be useful in a real system.

Runtime measurement

Estimating entropy and reporting a health state while the device is in service, rather than qualifying a sample once in a laboratory.

Photonic integration

Getting the above onto a chip that can be manufactured on a commercial line, packaged, and qualified as a component.

Licensing

How licensing usually starts.

Nobody licenses an entropy engine from a datasheet. The usual route runs from hardware in your lab to a module you qualify to the engine on your own board, and each step reuses the work of the one before it.

Step 1

Evaluate

Start with hardware you can measure: an evaluation card in your own lab, running your own workload, with the health output visible to your host.

Compare integration paths
Step 2

Qualify a module

Onyx puts the Ruby™ S1 engine on a module you qualify as a component. The software stack and the evidence carry across the family, so the qualification work is done once.

See Onyx
Step 3

Integrate the engine

Take the entropy source into your own silicon under licence, with the design support and the measurement model that make it assessable in your process.

The OEM path
Diligence

The detailed answers come under NDA.

Which families are granted where, what a licence covers, how the technology is owned and what it costs are all answered directly, in a conversation, with the people who hold the position. A website is the wrong instrument for it and a summary that sounds legal without being legal helps nobody.

Where the research came from, and how it reaches the parts you can buy, is public and is written up under research and programmes.

What a licensing conversation usually opens with

  • The process you are targeting, and whether the engine has to move to it.
  • The rate and the environment the source has to hold in your system.
  • The assessment your programme faces, and what your assessor will ask about the source.
  • Volume, and whether the part is one product or a family.