🛡️ H33: 2.6ms Full Auth • Zero Data Exposure • k-of-n Threshold • Post-Quantum • 484M Auths/Day
📜 15 Patent Claims Pending • 1,540 Tests Passing
2.6ms. Zero data exposure. Military-grade authentication.
The only biometric auth where your template is NEVER decrypted.
k-of-n threshold · Post-quantum · 128-bit NIST L1 FHE security
"If You're Not Quantum Resistant in the Next Few Years, You're Out of Business" Why? →
SEAL: ~17.9ms. H33: 2.6ms. Same FHE. ~11x faster. Zero exposure. What's NIST? →
Microsoft SEAL FHE pipeline? ~17.9ms. H33 FHE: ~1.46ms. ~11x faster + zero exposure. See the math →
Ship military-grade Quantum Resistant Encryption this afternoon.
FHE-encrypted biometrics. Zero-knowledge proofs. Quantum signatures. One API call.
2.6ms
H33 (128-bit NIST L1)
Blink Test: 300ms blink ÷ 2.648ms = ~113 full crypto auths per blink. The only auth where your biometric is NEVER decrypted.
Performance Modes v6.0
| Mode |
Latency |
Security |
NIST Level |
| H0 |
212µs |
~57-bit |
Dev Only |
| H33-128 ⭐ |
2.6ms |
128-bit NIST L1 |
Zero Exposure |
| H-256 ✓ |
19.6ms |
256-bit (NIST L5) |
Zero Exposure |
H0 (N=1024) dev only (~57-bit). H33-128 and H-256 are NIST-compliant: H33-128 (N=4096) NIST L1 128-bit; H-256 (N=16,384) NIST L5 256-bit. All use bfv_params_override for compliance.
H0 Turbo Full Match (212µs) — Dev Only
Encrypt + distance + single-party decrypt only. No threshold, no PLOOKUP, no Dilithium.
| FHE Encrypt (BFV, N=1024) |
130µs |
61% |
| FHE Distance Compute |
48µs |
23% |
| FHE Decrypt (single-party) |
33µs |
16% |
| TOTAL |
212µs |
100% |
H33-128 CollectiveAuthority (2.648ms) — 128-bit NIST L1 FHE + Zero Exposure
| BFV Encrypt (Q-128 Standard) |
965µs |
36% |
| FHE Distance (encrypted space) |
199µs |
8% |
| k-of-n Threshold Decrypt (3-party Shamir) |
~700µs |
26% |
| Threshold Combine + SHA3 |
~350µs |
13% |
| Encode / Normalize / Quantize |
~300µs |
11% |
| PLOOKUP Prove |
7.3µs |
<1% |
| PLOOKUP Verify |
720ns |
<1% |
| Dilithium Sign + Verify |
138µs |
5% |
| TOTAL PIPELINE |
2.648ms |
Zero Exposure |
ZK Verification (Production: PLOOKUP)
PLOOKUP Verify: 720ns | Prove: 7.3µs (dim=128) | Proof: 105B
Legacy options: KZG 108ms (96B) | IPA 170ms (944B)
Blink = 300,000µs
H33-128: 300,000 ÷ 2,648 = ~113 full crypto auths per blink
H-256: 300,000 ÷ 19,600 = ~15 auths per blink
vs SEAL FHE: ~17.9ms | H33 FHE: ~1.46ms = ~11× faster + NIST L1 + zero exposure
Measured on c7i.metal-48xl (96 cores, Intel Xeon 8488C, AVX-512). Criterion.rs v0.5, 100+ samples. February 12, 2026.
Note: H33/H2 upgraded to N=4096 for NIST L1 compliance. Latencies being re-benchmarked.
const result = await h33.auth.verify({
userId: 'user_123',
biometric: faceData
});
const secure = await h33.auth.verify({
userId: 'user_123',
biometric: faceData,
mode: 'h-256'
});
Speed Comparison
H33 vs Microsoft SEAL
Same security. Complete pipeline. ~11x faster. Zero data exposure. k-of-n threshold means no single server sees your plaintext.
Same Security, Different Speed
| Operation |
SEAL BFV |
H33 H33 |
H33 Advantage |
| Encrypt |
500-800 µs |
965µs |
Comparable (H33 includes encoding) |
| Compute Distance |
4,720 µs |
199µs |
24x faster |
| Relinearize |
11,900 µs |
n/a (no relin) |
∞ (skipped) |
| Full Auth Pipeline |
~17,920µs |
2,648µs |
~11x faster + zero exposure |
Why the difference? SEAL is a general-purpose FHE library. H33 is purpose-built for authentication: shallow circuits, aggressive batching, no relinearization needed. Same BFV scheme, same security—just optimized for one use case.
Full Stack Auth Speed Comparison
| Stack |
H33 |
Competitors (Combined) |
H33 Advantage |
| H33-128 (CollectiveAuthority, 128-bit NIST L1) |
2.648ms |
~17,920µs (SEAL alone) |
~11x faster + zero exposure |
| ZK Proof (PLOOKUP) |
7.3µs |
~20ms+ (STARK alternatives) |
~2,740x faster |
Individual Component Breakdown (v5.1)
| Component |
H33 |
Alternative |
Notes |
| FHE Encrypt (H33 N=4096) |
965µs |
SEAL: 500-800µs |
Comparable encryption speed |
| FHE Compute Distance (Q-128) |
199µs |
SEAL: 4,720µs (general multiply) |
24x faster. Purpose-built vs general. |
| H33-128 Full Auth (CollectiveAuthority) |
2.648ms |
SEAL: ~17,920µs |
~11x faster + zero data exposure. |
| FHE Full Auth (H-256) |
19.6ms |
SEAL: ~15-20ms |
256-bit NIST L5. Highest NIST tier (L5). Zero exposure. |
| ZK Proof (PLOOKUP) |
7.3µs |
STARK: 20ms+ |
Production ZK. 105B proof. 720ns verify. PQ-safe. |
| Kyber768 Full KEM |
57.8µs |
liboqs: ~60µs |
Keygen 16.8µs + Encap 21.4µs + Decap 19.6µs |
| Dilithium3 Sign+Verify |
138µs |
liboqs: ~180µs |
Sign 102µs + Verify 36µs |
| Full Crypto Auth (H33-128 CollectiveAuthority) |
2.648ms |
~17,920µs (SEAL FHE alone) |
~11x faster + zero data exposure. |
Measured on c7i.metal-48xl (96 cores, Intel Xeon 8488C, AVX-512). Criterion.rs v0.5, 100+ samples. February 12, 2026. Dual-socket NUMA-pinned for throughput numbers.
Why H33
2.6ms. Zero Data Exposure. Post-Quantum.
The only biometric auth where your template is NEVER decrypted. H33-128 CollectiveAuthority uses k-of-n threshold decrypt so no single server ever sees plaintext. PLOOKUP prove: 7.3µs, verify: 720ns. ~11x faster than Microsoft SEAL.
965µs
BFV Encrypt (Q-128)
| Capability |
H33 (Feb 2026 v5.1) |
Industry Best |
H33 Advantage |
| H0 Mode (Turbo Full Match) |
212µs |
No comparison |
~57-bit security (dev only) |
| H33-128 (CollectiveAuthority, N=4096) |
2.648ms |
SEAL: ~17,920µs |
~11x faster + zero exposure |
| Merkle Verify (cached) |
21.70µs |
~100-500µs |
4-20x faster |
| PLOOKUP ZK Prove |
7.3µs |
~20ms+ (STARK) |
~2,740x faster. 105B proof. |
| H33-128 Full Auth (CollectiveAuthority) |
2.648ms |
~17,920µs (SEAL alone) |
~11x faster + zero data exposure + k-of-n |
| Dilithium3 (NIST L3) |
138µs |
liboqs: ~180µs |
Sign 102µs + Verify 36µs |
| Auths Per Blink |
~113 crypto auths |
N/A |
300,000µs ÷ 2,648µs |
| Throughput (96-core, dual-socket) |
5,600 auth/sec |
No comparable offering |
484M auths/day per instance |
| Cold Start (Full PQC) |
3.18ms |
N/A |
First auth (20% penalty vs warm) |
| PQC Overhead |
~196µs |
N/A |
Kyber768 57.8µs + Dilithium3 138µs |
| Cache Read Throughput |
~59K ops/sec |
~100K/sec typical |
Cachee L1 cluster, 100% hit rate |
Measured on c7i.metal-48xl (96 cores, Intel Xeon 8488C, AVX-512). Criterion.rs v0.5, 100+ samples. February 12, 2026. Dual-socket NUMA-pinned for throughput numbers.
Security
Enterprise-grade. Formally verified.
Post-quantum cryptography, 16 mathematical proofs, 7 defense layers. Security that doesn't slow you down.
7-Layer Defense in Depth
Layer 7: Post-Quantum Cryptography
Dilithium3 + Kyber768 • NIST Level 3
Layer 6: Zero-Knowledge Proofs
PLOOKUP • Privacy without exposure
Layer 5: Homomorphic Encryption
BFV/CKKS • Compute on encrypted data
Layer 4: Hardware Security (TEE)
Intel SGX • Fortanix EDP
Layer 3: Formal Verification
16 Kani Proofs • Mathematical guarantees
Layer 2: Network Security
WAF • DDoS • mTLS • Segmentation
Layer 1: Infrastructure
AWS • VPC • IAM • CloudTrail
Compliance Ready
Documentation
API Reference
Complete API documentation for H33's post-quantum authentication platform. Base URL: https://api.h33.ai/v1
Authentication
All API requests require authentication using your API key in the Authorization header.
Authorization: Bearer h33_live_xxxxxxxxxxxxxxxxxxxx
ℹ️
API Key Types
h33_live_* - Production keys, full access
h33_test_* - Test keys, sandbox environment (no auths consumed)
Full Stack Auth PATENT PENDING
One API call: biometric + FHE + ZK proof + quantum signature + blockchain attestation.
Complete 128-bit NIST L1 FHE biometric authentication in 2.6ms (H33-128 CollectiveAuthority). Zero data exposure: your biometric is NEVER decrypted on any single server. k-of-n threshold decrypt. PLOOKUP proof: 7.3µs, 105B.
2.6ms
H33-128 (Zero Exposure)
Request Body
| Parameter |
Type |
Required |
Description |
userId |
string |
Required |
Unique identifier for the user |
biometric |
object |
Required |
Biometric data (face, voice, or fingerprint) |
biometric.type |
string |
Required |
"face" | "voice" | "fingerprint" |
biometric.data |
string |
Required |
Base64-encoded biometric data |
product |
string |
Optional |
"h0" (212µs ⚠️dev) | "h33" (2.6ms, default) | "h-256" (19.6ms, max mode) |
Example
const result = await h33.biometric.verify({
user_id: 'user_123',
embedding: faceEmbedding,
product: 'h33'
});
Biometric APIs
FHE-encrypted biometric enrollment and verification. We never see or store raw biometric data.
Enroll a new biometric template (face, voice, fingerprint). Encrypted with FHE before storage.
Verify biometric against enrolled template. Matching performed entirely on encrypted data.
2.6ms
H33-128 (Zero Exposure)
FHE Encryption
Fully Homomorphic Encryption - compute on encrypted data without decrypting.
| Mode |
Latency |
FHE Security |
Use Case |
| H0 |
212µs |
~57-bit ⚠️ |
Dev/testing only |
| H33-128 ⭐ |
2.6ms |
128-bit NIST L1 + Zero Exposure |
Production default (k-of-n) |
| H-256 ✓ |
TBD |
256-bit NIST L5 + Zero Exposure |
NIST L5 (n=16,384) — highest tier |
Encrypt data using FHE. Supports BFV (integers) and CKKS (floating point) schemes.
Perform operations on encrypted data: addition, multiplication, comparison, Euclidean distance.
Zero-Knowledge Proofs
Prove statements without revealing underlying data. PLOOKUP for production auth, Circle STARK for infrastructure.
| Scheme |
Proof Size |
Verify Time |
Notes |
| PLOOKUP (Production) |
105 bytes |
720ns |
Production auth ZK. Hash-based, PQ-safe |
| KZG |
~200 bytes |
~3ms |
Biometric ZKP commitment scheme |
| IPA |
~1KB |
~10ms |
No trusted setup, biometric ZKP |
Generate a ZK proof. PLOOKUP for production auth. Prove age, location, credentials without revealing data.
Verify a ZK proof. PLOOKUP verification in 720ns. Returns true if proof is valid.
Quantum Signatures
NIST FIPS 203/204 compliant post-quantum digital signatures. Dilithium3: Sign 102µs + Verify 36µs = 138µs total.
🔐
Algorithms Supported
CRYSTALS-Dilithium - Primary (FIPS 204) • CRYSTALS-Kyber - Key encapsulation (FIPS 203) • FALCON - Compact signatures
Sign data using Dilithium3 (NIST Level 3) quantum-resistant algorithm.
Verify a quantum-resistant signature.
Blockchain Attestation
Immutable records on Solana. ZK-compressed logging (5000x less expensive than raw transactions).
Create immutable attestation record. Perfect for audit trails and compliance.
Mint a Soulbound Token (non-transferable NFT) for verified identity credentials.
KYC / AML
Privacy-preserving identity verification with Soulbound NFT issuance.
| Package |
Price |
Includes |
| KYC Basic + SBT |
$49 |
ID + Selfie + Liveness + Soulbound NFT |
| KYC Enhanced + SBT |
$79 |
Basic + Proof of Address |
| AML/PEP Screening |
$19 |
Sanctions, PEP, Adverse Media |
| Full Bundle |
$99 |
KYC + AML + Soulbound NFT |
const kyc = await h33.kyc.verify({
userId: 'user_123',
package: 'full_bundle',
documents: { idFront: idBase64, selfie: selfieBase64 },
walletAddress: 'Gh9ZwE...'
});
Error Codes
All API errors return a consistent JSON structure.
{ "error": { "code": "QUOTA_EXCEEDED", "message": "Monthly auth quota exceeded" } }
| Code |
HTTP |
Description |
INVALID_API_KEY |
401 |
API key is missing, invalid, or revoked |
QUOTA_EXCEEDED |
402 |
Auth quota exceeded for this billing period |
RATE_LIMITED |
429 |
Too many requests, slow down |
USER_NOT_ENROLLED |
404 |
No biometric template found for user |
PROOF_INVALID |
400 |
ZK proof verification failed |
Rate Limits
| Tier |
Requests/sec |
Requests/day |
| Trial |
10 |
1,000 |
| Starter |
10 |
10,000 |
| Growth |
100 |
100,000 |
| Business+ |
500+ |
Unlimited |