Skip to content
Products

Start from the design you already have.

An appliance that serves the whole site, four parts that go inside your own hardware, and one measurement model. Give us the slot, the rate, the environment, the certificate your programme demands and the volume you are heading for, and the shortlist is short.

The families

Where each family fits.

Entropy Core serves a whole site from your own racks. Garnet and Nellite are built on the Ruby™ N1 engine; Onyx is built on Ruby™ S1. The physics, the runtime metrology and the software stack are shared, so integration and qualification work carries across the family rather than starting again.

Product finder

Tell us about your design.

Answer whichever ones you already know. Most buyers are fixed on one axis — a slot, a certificate, a launch date — and the rest follows from it.

Integration point

Where does the entropy source physically attach?

Useful throughput

How much entropy does the design actually consume?

Environment

What does the product have to survive?

  • Data centre

    Rack-mounted servers, security appliances and infrastructure, with a slot to spare or none at all.

  • Industrial

    Board-level integration where size, power and unit cost drive the design.

  • Defence

    Programme-managed systems with long lifecycles and sovereign trust boundaries.

  • Space

    Payloads and mission systems, including operation in GEO conditions.

    Space qualification evidence for Ruby™ N1 supports operation in GEO conditions. It is programme-specific evidence rather than a public certificate — ask which parts of it apply to your mission profile.

Security function

How much of the security architecture should the module carry?

  • Entropy only

    A local source feeding the cryptographic stack you already have.

  • Entropy + root of trust

    Ruby™ S1 paired with a Lattice MachXO5-NX root of trust, in one embedded module — Onyx™ X5.

    Onyx™ X5 is configured per programme. Bring the security function you need alongside the entropy source and we will scope it with you.

Assurance requirement

What evidence does your qualification path demand?

  • SP 800-90B

    NIST entropy certificate E178, scoped to Quside PCIe One and FMC One.

    E178 validates the entropy source. It does not validate a complete random bit generator, nor any system built on top of one. Confirm how its scope maps to the specific part you are qualifying.

  • ENS

    ENS Alta, the highest category of the Spanish national security framework, for Quside PCIe One and FMC One.

    Covers Quside PCIe One and FMC One at version 1.0. Ask which part number your programme is specifying.

  • Space qualification

    Qualification evidence for Ruby™ N1 supporting operation in GEO conditions.

Volume path

Where are you in the programme?

  • Evaluation

    One or two units on a bench, with drivers, to prove the integration in your own system.

  • One-site pilot

    One appliance on one site or cluster, with monitoring on from the first day, before sizing the rest.

  • Programme

    A qualified build for a named system, with assurance evidence attached to the bid.

  • OEM production

    Volume across a product family, reusing the same software and the same evidence for every unit in it.

  • Chip-down integration

    The entropy chip placed directly on your own board, designed in across a product generation.

If two axes point in different directions — a 1 Gbit/s appetite in an embedded power budget, say — put the tension in front of an engineer instead of picking a compromise off the table. Request an architecture review.

Compare

The same axes, side by side.

For when the shortlist is down to two and you need to know what actually differs.

Quside product families compared across integration point, throughput, entropy engine, host software, security function, assurance evidence, environment fit, volume path and lifecycle status.
AxisEntropy CoreGarnet™ PCIeNellite™ FMCOnyx™ embeddedRuby™ chips
Integration point1U rack or virtual appliance, on your networkPCIe Gen2 ×4, low-profileFMC LPC/HPC and FMC+Embedded moduleChip on your own board
Useful throughputSized per siteUp to 1 Gbit/sUp to 1 Gbit/s50–100 Mbit/sUp to 1 Gbit/s (N1)
Entropy engineIn the datasheet, on requestRuby™ N1 — phase diffusionRuby™ N1 — phase diffusionRuby™ S1 — polarisation switchingRuby™ N1 and Ruby™ S1
Host softwareREST HTTP API and QRNG Open API; no host driverLinux C and Python driversVHDL IP cores includedEmbedded host interface, defined per integrationOEM integration support
Security functionEntropy, shared across the siteEntropyEntropyEntropy (S1). Root of trust in the same module is per programme (X5)Entropy source
Assurance evidenceEntropy quality recorded per appliance and site ⁵SP 800-90B E178 ¹ · ENS Alta ²SP 800-90B E178 ¹ · ENS Alta ²Runtime health monitoring ³Space qualification evidence, GEO conditions ⁴
Environment fitData centre, one pool per siteData centre, appliancesDefence, space, secure communicationsEmbedded, industrial, defenceSet by the product you build around it
Volume pathOne-site pilot → per-site rolloutEvaluation → OEM qualificationEvaluation → programmeProgramme → OEM productionOEM production → chip-down integration
Lifecycle statusOne-site pilotsAvailableAvailableOnyx™ S1 available · X5 per programmeIn production
  1. ¹ NIST SP 800-90B entropy certificate E178 is scoped to Quside PCIe One and FMC One. It validates the entropy source, not a complete random bit generator and not systems built on top of it. Confirm how that scope maps to the part you are qualifying.
  2. ² Quside PCIe One and FMC One, version 1.0, are qualified at ENS Alta — the highest of the three categories of the Spanish national security framework, which therefore also covers Media and Básica. It is a qualification under a national scheme rather than a certification, and it runs to 31 December 2026.
  3. ³ Onyx™ S1 is built on Ruby™ S1 and reports runtime health the same way as the rest of the platform. The E178 certificate does not cover it; its scope is stated above.
  4. ⁴ Qualification evidence supporting operation in GEO conditions. It is programme-specific evidence rather than a public certificate.
  5. ⁵ Entropy Core carries no certificate of its own: E178 and ENS Alta are scoped to Quside PCIe One and FMC One and do not extend to it. What it provides is a running record of entropy quality, exposed to your monitoring.
For developers

Drop into your existing stack.

Entropy Core answers standard HTTP clients on your private network, so the hosts that use it need no driver. Linux C and Python drivers expose the entropy stream and the device health state on the PCIe products; VHDL IP cores bring both into an FPGA fabric. Whichever integration point you pick, the software work carries across the family.

What ships with the hardware

  • REST HTTP API · QRNG Open APIEntropy Core
  • Linux C / Python driversGarnet™ PCIe
  • VHDL IP coresNellite™ FMC
  • Embedded host interfaceOnyx™

Integration guides and driver packages are issued with the evaluation kit for the interface you are targeting.

Integrating above the driver

Most systems consume the card by seeding an approved deterministic mechanism from it and reseeding appropriately, then exposing the device health state to their own monitoring and audit path. Which cryptographic library or key-management platform sits above that is your architecture, and the integration notes are written for the one you are actually using.

Tell us the stack and the interface and an engineer will go through it with you.

Still between two of them?

Send the interface, the throughput you consume, the environment and the qualification date. An engineer comes back with the integration path that fits and what it takes to prove it in your own system.