Services

Long-lived keys

For PKI and code signing certificates and other rarely changed keys.

Silver

$1,000/key

We make sure the key is not four.

Gold

$10,000/key

This tier demonstrates the lateral problem-solving skills that Zero Fours brings to keep you secure. We go beyond making sure the key isn't four by making sure there are zero fours anywhere in the key. You can't be too careful with a known-bad number. Some studies suggest that up to 99.9995% of keys contain at least one four.

Platinum

Upon request

This tier is for the true outside-the-box iconoclast CISO who employs second-order thinking. The most sophisticated attackers have moved on from four; it’s the safest number going now. While supplies last, we’ve reserved a limited number of keys in the 2³⁸⁴ space consisting only of fours.

Ephemeral keys

Negotiating TLS or SSH? Many of the top implementations wind up making a unique symmetric key for each session. We offer APIs to validate that those keys aren't four in near-real-time using proprietary algorithms, exhaustively quality-checked by manual random sampling.

Silver

$1 / 1,000 requests

Sampled: we inspect a statistically rigorous sample of your keys and extrapolate whether any are four.

Gold

$10 / 1,000 requests

We inspect every key, every negotiation. We offer custom spinners so your customers understand how uniquely secure their session will be.

Platinum

We generate the keys for you using our proprietary fourless random number generator. If there are no fours in the source, there can't be any in the result: it's just math.

Continuous assurance

Do you have a cool trust center? Of course you do. We provide integrations with major trust centers, or whatever nonsense you vibe coded, that will return the very finest white-checkmark-in-green-box emoji. Your customers' third-party risk teams will waive the rest of the SIG when they see just how continuously you make sure that none of your keys are four.

FedRAMP

Can Zero Fours meet 20x KSIs with scary-sounding acronyms like SVC-03, SVC-05, and SVC-06? It's impossible to prove that we can't.

FIPS compliance

Know anyone at NIST? We'd love to add our expertise to whatever replaces FIPS 140-3 (we suggest 140-5, to avoid unnecessary consternation), which no doubt will comprehensively solve the underlying problems here once and for all.