Entropy as-a-Service

A live REST API delivering QES-256 keys (Quantum Entropy Source) — 32-byte IBM Quantum hardware-derived entropy, every byte backed by a public Job ID your team can independently verify. Drop-in quantum entropy for any AES-256 deployment.

Try the Live API Enterprise Licensing

Combined across all three pools

912
Total measurements
3
Entropy pools
100%
Unique seeds
8,763
Entropy bits

What the service provides

Three tiers — from open API access to signed compliance reports.

Free

Public API Access

Rate-limited access to the QRNG endpoint. Generate quantum random bytes, integers, floats, and UUIDs. Verify IBM Job IDs publicly at no cost.

  • REST API — bytes, int, float, UUID, batch
  • Public attestation endpoint
  • IBM Job ID verification — auditable entropy provenance no PRNG can provide
  • No account required
Paid

Signed Attestation Reports

Cryptographically signed certificates documenting that your entropy originated from verified IBM Quantum hardware. A paper trail auditors can hold.

  • Signed per-job provenance chain
  • Audit-ready PDF + JSON reports
  • Higher rate limits + SLA
  • Billed per report or monthly
Enterprise

IP License

License the STEADYWATCH™ entropy seeding architecture for OEM integration into HSMs, security hardware, or enterprise platforms.

  • Full source license
  • White-label available
  • Exclusive or non-exclusive terms
  • Patent portfolio included

Who uses EaaS

Any system where the source of randomness needs to be proven, not assumed.

🔐
Security Engineers
Seed key generation, session tokens, and OTP with hardware-provable entropy instead of OS randomness.
📋
Compliance Teams
Produce audit-ready documentation proving cryptographic inputs came from verified quantum hardware — not a PRNG.
🏛️
Defense & Government
Critical infrastructure requiring post-quantum entropy sources with an independent, verifiable provenance chain.
🔬
Researchers
Access true quantum randomness with full IBM hardware job traceability for cryptographic research and benchmarking.

How the entropy is used

Every QES-256 key your system generates traces back to three independent IBM Quantum jobs — not a software RNG, not a single hardware source. The three pools are combined via SHA-256 into a single verifiable fingerprint, then expanded into the QRNG stream. The audit chain is public and unbroken.

VAULT (144) + VIPER (336) + LOTUS (432) SHA-256 fingerprint QRNG stream
Try the Live API →

The entropy infrastructure

Three prime-seeded IBM Quantum pools generate the randomness behind the service. Explore each one.

VAULT
p = 5
144
IBM Quantum measurements
Yield efficiency
91.7%
9.17 / 10.0 bits avg · ibm_marrakesh

The foundation entropy pool. Prime p=5 seeds the IBM Quantum circuit, producing 144 physically random, independent measurements. Every measurement is traceable to a real hardware job ID.

VIPER
p = 13
336
IBM Quantum measurements
Yield efficiency
96.0%
9.60 / 10.0 bits avg · ibm_marrakesh

The mid-scale entropy pool. Prime p=13 produces 336 measurements — wider distribution, higher entropy density. Same hardware-traceable provenance as VAULT, more than twice the measurement count.

LOTUS
p = 17
432
IBM Quantum measurements
Yield efficiency
97.6%
9.76 / 10.0 bits avg · ibm_marrakesh

The deepest entropy pool. Prime p=17 generates 432 IBM Quantum measurements — the largest and most distributed of the three. Combined with VAULT and VIPER, LOTUS completes the full 912-measurement harvest.