Entropy Relay
A public API backed by a private hardware noise source
If you are evaluating the project as part of the portfolio, the interesting bit is the split architecture: the Infinite Noise device stays on the local network, a small LXC sidecar batches whitened output, and Cloudflare D1 exposes a pool that can be served quickly without ever putting the hardware directly on the public internet.
What you can try
UUIDs, keys, test fixtures, bounded integers, dice rolls, and any small high-trust randomness task.
What to notice
Hardware output is prefetched into a pool, so each public request stays fast and the home lab never becomes the runtime bottleneck.
Fail-closed behavior
If the pool runs dry or the sidecar stops reporting, the public endpoints return `503` rather than pretending randomness is still available.
Entropy pool level
99,414,169 bytes
Pre-generated hardware entropy available for public API calls.
Total bytes served
12,135
Cumulative bytes delivered by the public TRNG endpoints.
Total API requests
84
Successful generation requests served from the entropy pool.
Device health
0.878 bits/bit
Estimated K: 1.837
1s ratio: 50.31%
Last refill time
2026-03-14T02:23:55.000Z
Most recent batch posted from the Proxmox LXC sidecar.
Online status
ONLINE
Healthy pushes received within the last 300 seconds.
What this page is showing
The page is meant to make the architecture and tradeoffs legible at a glance.
SERVICE_MODEL
- - Public reads come from a D1-backed pool, which keeps latency stable and avoids exposing the hardware or local network directly.
- - The health snapshot is fed by the same sidecar that refills the pool, so viewers can see freshness and entropy quality in the same interface.
- - Rate limits are intentionally visible here because protecting the pool matters just as much as proving the hardware integration works.
Latest health snapshot
Interactive demo
Try a few common request patterns and inspect the live responses without leaving the page.
LIVE_POOL
Random bytes
UUID v4
Generate a hardware-backed UUID v4 value for IDs, request correlation, or test fixtures.
Random integer
Dice roller
Coin flips
Encryption key
API reference
The endpoint table covers the public surface area; the sample commands and integration notes expand below.
/api/trng/generate
Raw bytes in hex, base64, or octet-stream.
Key params
bytes, format
/api/trng/uuid
One or more UUID v4 values.
Key params
count
/api/trng/integer
Uniform integer within a caller-supplied range.
Key params
min, max
/api/trng/dice
Dice rolling utility.
Key params
count, sides
/api/trng/coin
Coin flips for quick binary choices.
Key params
count
/api/trng/key
128-bit or 256-bit key material.
Key params
bits, format
/api/trng/stats
Pool, usage, and health telemetry.
Key params
none