Benchmarks H33 FHE H33 ZK APIs Pricing Token Docs About
Log In Get API Key

Performance Benchmarks v7.0

1.28ms post-quantum auth (AWS Graviton4). H33 ZKP Stark Lookup prove: 2.0µs, verify: 0.2µs (2.09ns Cachee cached). 12.5× faster than SEAL's FHE pipeline. All benchmarks verified on AWS Graviton4.

Security Parameters Appendix v4.0 →
1.28ms
Full Crypto Auth
12.5×
vs Microsoft SEAL
2.0µs
H33 ZKP Stark Lookup Prove
0.2µs
H33 ZKP Stark Lookup Verify

Benchmark Methodology

Benchmark Reports

February 14, 2026 | v7.0
LATEST

Post-Quantum Production Stack: 1.28ms full crypto auth on Production ARM hardware. BFV Encrypt (420µs) + FHE Inner Product (260µs) + Threshold Decrypt (330µs) + Dilithium Sign+Verify (106µs). H33 ZKP Stark Lookup prove: 2.0µs, verify: 0.2µs (2.09ns Cachee cached). 12.5× faster than Microsoft SEAL. View full methodology →

1.28ms
Full Crypto Auth
12.5×
vs SEAL
2.0µs
H33 ZKP Stark Lookup Prove
420µs
BFV Encrypt
Crypto Throughput
February 14, 2026
PREVIOUS

14-phase benchmark covering post-quantum cryptography, FHE operations, ZK-STARK proofs, batch processing, key pools, caching systems, and trust score engine. 100% of performance targets met across all categories.

33.3µs
ML-KEM Keygen
80.7µs
Dilithium Sign
2.0µs
H33 ZKP Stark Lookup Prove
104x
Pool Speedup
11x
Cache Speedup

The Math: 1.28ms Full Crypto Auth (v7.0)

H33 Production Pipeline (Feb 14, 2026 v7.0)

BFV Encrypt (Q-128)420µs33%
FHE Inner Product260µs20%
Threshold Decrypt330µs26%
H33 ZKP Stark Lookup~2µs<1%
Dilithium Sign+Verify106µs8%
FULL AUTH TOTAL1,280µs100%

Production ARM hardware (Graviton4). H33 ZKP Stark Lookup prove: 2.0µs, verify: 0.2µs (2.09ns Cachee cached). ~180KB proof.

H33 vs Microsoft SEAL

Encrypt420µs680µs1.6×
FHE Compute260µs1,530µs5.9×
Relin (SEAL) / Threshold (H33)330µs490µs1.5×
Decrypt150µsH33 uses threshold
Pipeline Total1,280µs2,850µs2.2×

Measured: 2.2× faster single-thread (apples-to-apples). At production scale with SIMD batching: 12.5× faster.

Blink comparison (300,000µs):
Full Crypto Auth (1.28ms): 300,000 ÷ 1,280 = ~234 auths per blink
Cached Session (25.6µs): 300,000 ÷ 25.6 = ~11,700 cache hits per blink
Throughput (AWS Graviton4, 96 cores):
Full Crypto Auth:
Cached Sessions: 497M ops/sec
Biometric (batch-64): 46K/sec
H33 ZKP Stark Lookup Performance:
Prove: 2.0µs | Verify: 0.2µs (2.09ns Cachee cached)
Proof Size: ~180KB
Batch Throughput: 55K proofs/sec

Full Stack Throughput Benchmarks (Feb 14, 2026)

Enterprise-scale performance on Production ARM hardware (96-core single-socket Graviton4). Full QR stack: FHE (BFV) + H33 ZKP Stark Lookup + Kyber768 + Dilithium3 + Blockchain Audit

Hardware Tiers

AWS Graviton4Full crypto auth1.28ms
AWS Graviton4Throughput
Cachee Pipeline (batch-64)Cached sessions497M ops/sec

Production Pipeline Breakdown (AWS Graviton4)

StepLatency% of Total
BFV Encrypt (Q-128)420µs33%
FHE Inner Product260µs20%
Threshold Decrypt330µs26%
H33 ZKP Stark Lookup~2µs<1%
Dilithium Sign+Verify106µs8%
FULL AUTH TOTAL1,280µs100%

Throughput Tiers

TierLatencyThroughputWhat It Does
Full Crypto Auth1.28msFHE + H33 ZKP Stark Lookup + Dilithium
Cached Session25.6µs497M ops/secCachee L1 hit
Biometric (batch-64)varies46K/sec512-D encrypted matching
H33 ZKP Stark Lookup (batch-64)varies~500K/secZK proof generation

Note: All numbers from Security Parameters Appendix v4.0 (Feb 14, 2026) on AWS Graviton4.

H33 vs Microsoft SEAL

H33 Full Pipeline1,280µs
Microsoft SEAL (FHE only)2,850µs
Single-Thread Speedup2.2×
H33 at Scale (96 cores, SIMD batch)1,148,018 auth/sec
Production Scale Speedup12.5× faster

Cachee L1 Cluster Stats

Workers64 (ports 6380-6443)
Read throughput497M ops/sec
Write throughput57K/sec
Routingdjb2 hash sticky routing
Batch API5000 keys/request