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

Performance Benchmarks v4.0

1.75ms NIST-compliant quantum-resistant auth. 29-34x faster than SEAL. +STARK audit trail optional (+1.5ms). All benchmarks verified on AWS c7i.

1.75ms
NIST Auth
29-34x
vs Microsoft SEAL
~650µs
Turbo Mode
+1.5ms
+STARK (Optional)

Benchmark Methodology

Benchmark Reports

February 4, 2026 | v4.0
LATEST

NIST-Compliant Quantum-Resistant Stack: 1.75ms authentication including PQC (236µs), FHE Standard (1.43ms, N=4096 128-bit). +STARK audit trail optional (+1.5ms). 29-34x faster than Microsoft SEAL at equivalent N=4096 security. View full methodology →

1.75ms
NIST Auth
29-34x
vs SEAL
~1.5ms
STARK Full Proof
1.43ms
FHE Standard
~650µs
Turbo Mode
February 2, 2026
PREVIOUS

14-phase benchmark covering post-quantum cryptography, FHE operations, H33 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
45.0µs
Dilithium Sign
5ms
H33 STARK Prove
104x
Pool Speedup
67x
Cache Speedup

The Math: 1.75ms NIST-Compliant Auth (v4.0)

H33 NIST-Compliant Auth (Feb 4, 2026 v4.0)

PQC (NIST L3)236µs
ML-KEM Encap + Decap41.0µs
ML-DSA Sign + Verify110.6µs
Other PQC ops~84µs
FHE Standard (N=4096)1,436µs
BFV Encrypt1,070µs
Euclidean distance133µs
BFV Decrypt233µs
Serialization75µs
NIST AUTH TOTAL1,747µs (1.75ms)
+STARK (Optional)+1.5ms

NIST Level 3 PQC + 128-bit FHE. STARK audit trail optional.

H33 vs Microsoft SEAL (N=4096, 128-bit)

Encrypt1.07ms~40-50ms37-47x
Add6.77µs~2,000µs295x
Subtract2.78µs~2,000µs719x
Multiply133µs~180,000µs1,353x
Full Auth1.43ms~50-60ms35-42x

Correct claim: 29-34x faster than SEAL

Blink comparison (300,000µs):
NIST Auth (1.75ms): 300,000 ÷ 1,747 = 171 auths per blink
Turbo (~650µs): 300,000 ÷ 650 = ~450 auths per blink
Speed advantage vs Microsoft SEAL (50-60ms FHE):
~55,000µs ÷ 1,747µs = 29-34x faster
Single-core throughput:
NIST Auth: ~571 ops/sec
Turbo: ~1,538 ops/sec
29-34x faster than SEAL at equivalent N=4096 security

Full Stack Throughput Benchmarks (Feb 3, 2026)

Enterprise-scale performance on AWS c7i. Full QR stack: FHE (BFV) + H33 ZKP Lookups + Kyber768 + Dilithium3 + Blockchain Audit

Hardware Tiers

c7i.4xlarge (16 vCPU)Single-request full QR latency911µs full auth
c7i.48xlarge (192 vCPU)Single request (estimated)~230µs
AWS Batched (1K batch)Full-stack QR throughput1.2M auths/sec

Full QR Stack Component Breakdown

Edge Encryption (AES-256-GCM)~50µsServer-side at gateway
FHE Biometric Auth (BFV Turbo)435µsN=1024, 100-bit security
H33 ZKP Lookups (SHA3-256)~0.2µsO(1) hash-based lookup
Kyber768 (FIPS 203)32µsKeygen 16µs + Encap 17µs
Dilithium3 (FIPS 204)145µsSign 106µs + Verify 37µs
Blockchain Audit (batched)~5µs5000x Merkle compression
HTTP + Cache + Routing~244µsAPI overhead
Combined PQC overhead177µsKyber768 + Dilithium3

Batch Scaling Results

Batch SizeThroughputLatencyNotes
1K batch1.2M/sec~25µs/authOptimal (fits L3)
10K batch~250K/sec~40µs/authGood scaling
50K batch~56K/sec~180µs/authL3 cache pressure

Note: Throughput declines at larger batches due to L3 cache pressure. 1K batch optimal for production.

FHE vs SEAL Comparison (Fair: N=4096)

H33 Precision (N=4096, 128-bit)618µs multiply
Microsoft SEAL (N=4096, 128-bit)~25ms multiply
Speedup (fair comparison)~40x

Cachee L1 Cluster Stats

Workers64 (ports 6380-6443)
Read throughput1.2M/sec
Write throughput57K/sec
Routingdjb2 hash sticky routing
Batch API5000 keys/request