31-nanosecond cache reads. Post-quantum attestation. One command.
The fastest way to get started
brew tap h33ai-postquantum/tap
brew install cacheeManual install from GitHub Releases
curl -L https://github.com/H33ai-postquantum/cachee-cli/releases/download/v0.1.0/cachee-0.1.0-aarch64-apple-darwin.tar.gz | tar xz
sudo mv cachee /usr/local/bin/Enterprise deployment with consolidated billing
Subscribe through AWS for consolidated billing and enterprise support.
View on AWS MarketplaceAfter installing, you are five commands away from sub-microsecond cache reads.
cachee init # Generate config + PQ keypair
cachee start # Start daemon on port 6380
cachee set mykey "hello" FP abc123 # Store with computation fingerprint
cachee get mykey # Retrieve value (31ns reads)
cachee getverified mykey # Full trust envelope (fingerprint + verification + provenance)
cachee bench # Run built-in benchmark That's it. Cachee is running on localhost:6380. Your PQ keypair is generated and ready for attestation.
Turn on post-quantum cryptographic attestation for every cached entry.
cachee attest --enable # Every SET gets a 58-byte H33-74 receipt
# signed by ML-DSA-65 + FALCON-512 + SLH-DSAWith attestation enabled, every cached entry carries a cryptographic proof of origin. Three independent post-quantum signature families -- ML-DSA (lattice), FALCON (NTRU lattice), and SLH-DSA (hash-based) -- must all be simultaneously broken to forge an entry. Cache poisoning becomes mathematically impossible.
Cachee speaks RESP -- any Redis client works. Zero code changes.
import redis
r = redis.Redis(host='localhost', port=6380)
r.set('session:abc', '{"user": "alice"}', ex=3600)
r.get('session:abc') # 31ns via Cachee L0Drop-in replacement. Point your existing Redis client at port 6380 instead of 6379. Your application code stays exactly the same -- Cachee handles PQ attestation, CacheeLFU eviction, and sub-microsecond reads transparently.
Deploy Cachee across your infrastructure with enterprise support, SLAs, and consolidated AWS billing.