Post-quantum security is only as strong as its entropy. This is the only entropy source you can watch at work.
The appliance — physical entropy you can watch
Tap a component pin to explore, or press Run sequence to walk through the operation start to finish.
The EaaS API — entropy delivered as a service
The appliance never leaves Real Random's hands. It publishes entropy to an EaaS Server, and your applications draw it down over a simple REST API — metered per protected endpoint. Tap a node to see its role.
TRNG appliance
Publishes its entropy to the EaaS Server over REST using a unique device ID and secret. If no central server is configured, it can serve entropy directly from its own local store through the same API.
EaaS server
Securely stores entropy from one or more generators and services consumer requests. Tracks available entropy, publish and consume activity, and accounting per application — with configurable daily caps.
Your application
Any authorized application that needs true entropy. Request any amount over REST using an API ID and secret, issued through the Real Random website or your administrator.
RRUA mobile app
Configures devices over Bluetooth at install time — network setup, credentials, configuration changes — and provides fetch, health statistics, and factory reset.
Entropy is never reused. Once your application draws entropy from the server, it is deleted. Every request is served fresh from the hardware — and usage is metered per protected endpoint.
In practice — wolfSSL running on Real Random entropy
wolfSSL is a TLS library deployed across embedded and IoT systems. This recording shows an integration test where wolfSSL's random number generation is routed through the Real Random EaaS client — every key, nonce, and handshake in the stack drawing on hardware entropy.
Real Random wolfSSL integration test — recorded terminal session.
Initialize
The test registers the Real Random RNG and confirms it is ready.
Generate
Requests of 1 to 256 bytes each return fresh entropy, shown in hex.
Route wolfSSL
wolfSSL is configured to use realrandom_generate_block() for all RNG operations — a direct call to the custom RNG succeeds.
Prove the fallback
With the entropy server deliberately unreachable, the fallback path still returns 32 bytes — the integration degrades safely instead of failing.
All tests pass
Cleanup completes and the suite reports every check green.