Products / Storax OCSP Server
The internet has never been able to answer the one question that keeps it safe — “is this certificate still valid, right now?” — for everyone, at once. Signing a fresh answer billions of times an hour was never affordable, so real-time status stayed a promise the web engineered around. Storax OCSP makes live, per-request certificate status practical — at internet scale, and post-quantum from day one.
The status gap
OCSP was designed to ask a certificate authority “has this been revoked since it was issued?” in real time. But signing a fresh, trustworthy answer for every request, at internet scale, was never affordable on CPUs and HSMs — so it was never truly deployed at scale. Browsers softened it, then dropped it; the web leaned on stapling, ever-shorter certificates, day-old blocklists — and fail open. A compromised, revoked certificate can keep the padlock for days.
Possible. And affordable.
A single GPU signs well over a million fresh OCSP responses a second — hundreds of thousands on a mixed real-world keyring. Capacity scales linearly: every GPU and every box behind your load balancers adds its full throughput, with no architectural ceiling. Live certificate status stops being a research problem and becomes a line item.
Per-GPU figures; throughput and capacity scale linearly with additional GPUs and boxes.
Hyperscale by design
Throughput is independent of how many domains you serve — capacity is bound only by memory, and keys are a rounding error, so a server keeps millions of domains' keys resident at once. Serving volume then scales linearly across the fleet: add GPUs, add 10-gigabit front-ends, add boxes behind your load balancers, and capacity grows in proportion.
Every issuer's delegated signing key lives GPU-resident. Throughput doesn't care whether it's ten domains or ten million.
Throughput grows in direct proportion — add a GPU, add a box behind the load balancer, and the fleet does more. No architectural bottleneck, no diminishing returns.
Assurance
This isn't a classical service with a quantum retrofit later — post-quantum is native from the start. Classical and PQC in one engine — ECDSA, RSA, Ed25519, ML-DSA and Falcon, every signature byte-exact against the standards — so the moment your CAs migrate to post-quantum, live revocation is already there, at scale. Post-quantum signing is considered heavy — larger signatures, more compute, the very reason many fear the migration will break high-volume services. Not on our box. Delegated keys are HSM-wrapped and GPU-resident; the CA's roots never move. And it's built to FIPS 140-3 — every deployment picks its posture:
Maximum throughput for the everyday internet — the default that makes live status affordable.
Side-channel-resistant signing for regulated and high-security deployments, a switch away.
The hyperscaler story
Hyperscalers terminate most of the world's TLS and run certificate estates in the hundreds of millions. When a certificate is compromised, “revoked” has to mean something in seconds — not days spent waiting on a stale list. And they are the ones leading the post-quantum migration. That combination — internet-scale volume, real-time freshness and post-quantum — is exactly the workload OCSP could never carry. Storax OCSP carries it: live, post-quantum certificate status across the whole estate, scaling linearly with the fleet they already run.
Every domain, device and workload behind their edge — kept answerable in real time, growing linearly with the fleet, not fighting it.
A compromised certificate stops being trusted the moment it is revoked — not after the next day-old list ships. Real-time trust, at their scale.
The migration to post-quantum starts at the edge they run. Storax OCSP is post-quantum from day one — revocation is ready before the certificates are.
Revocation doesn't have to be a stale list and a hope. Storax OCSP makes live, signed, per-request certificate status cheap enough to run everywhere.
Request a demo