It exists because stitching together separate cryptographic products is where enterprises get gaps. Enterprise Security composes them under one contract, with no classical crypto in the hot path.
RSA will be broken. NIST knows it. Your compliance team knows it. The question is whether your infrastructure will be ready. H33 is the only enterprise security suite built post-quantum from day one — FHE encryption, lattice-based signatures, and zero-knowledge proofs in a single API call.
Every RSA key, every ECDSA signature, every AES-wrapped secret your enterprise stores today is on borrowed time. The harvest is already happening.
Each product handles a specific security domain. Together, they form the only enterprise platform where zero classical cryptography touches the hot path.
Fully homomorphic encryption at N=8192, 256-bit security. Compute on encrypted data without decryption. BFV, CKKS, BFV-32, and FHE-IQ engines. Montgomery NTT with Harvey lazy reduction. FIPS 203 compliant.
Keys never exist in plaintext. FHE-encrypted storage with Dilithium-signed access logs. Manages Kyber, Dilithium, and FHE key material. Automated generation, rotation, revocation. HSM integration for hardware-backed storage.
Three native AI agents running in-process. Harvest detection flags HNDL patterns in 0.69µs. Side-channel analysis catches timing attacks in 1.14µs. Crypto health monitoring in 0.52µs. No external ML dependencies.
API key management with post-quantum rotation. Kyber hybrid key exchange for every handshake. Dilithium signatures for every operation. Drop-in replacement for RSA/ECDSA key workflows. Nested 3-key signing.
Post-quantum API gateway with built-in authentication, rate limiting, and DDoS protection. Every request verified with ZK-STARK proofs. Encrypted request routing via Kyber. Automatic PQ key negotiation with client SDKs.
Distributed key ceremonies with no single point of compromise. Lattice-based threshold signing, key generation, and secret sharing. Configurable k-of-n thresholds. Post-quantum secure at every step of the ceremony.
Enterprise Security is a product bundle — the six products above composed into one enterprise deployment with a single API, one contract, and zero classical cryptography in the hot path. It owns the enterprise procurement, integration, and operational-coverage workflow. It does not own, redefine, or reimplement the cryptography, key custody, monitoring, governance, or verification the bundled products and mechanisms provide; it composes them.
The product boundary. Enterprise Security owns the enterprise coverage-and-integration workflow and outcome. It uses H33 mechanisms and products for encryption, key custody, monitoring, governance, and verification; it does not redefine or own those mechanisms.
The H33-256 core and every field-level encrypted operation is fully homomorphic encryption. The bundle composes encrypted processing across products; it does not define or implement the FHE primitive.
Post-quantum key custody, rotation, and signing across Vault, Key, and MPC are the province of H33-Key. The bundle consumes custody and signing; it does not own the key-custody mechanism.
Gateway request proofs and independent confirmation come from Verification and ZK (ZK-STARK). The bundle requests and surfaces proofs; the proving and verifying are owned elsewhere.
H33-74 supplies the portable 74-byte post-quantum attestation for audit and evidence. The bundle attaches attestations to operations; it does not produce the attestation primitive.
Continuous control monitoring and claim-grade evidence over the deployment are HATS. The bundle is monitored by HATS; the in-process Shield agents are operational telemetry, not the control-monitoring or scoring mechanism.
Agent-008 governs any automated decisioning that acts within the deployment — preserving authority and preventing drift. The bundle is governed by it; it does not perform governance.
Replaceability test. If the bundle swapped its FHE engine for another confidential-computing technology, or a bundled product were substituted, it would still be Enterprise Security: the enterprise coverage-and-integration workflow and outcome are the product. Mechanisms and components are chosen, not owned.
Use the bundle when you need complete post-quantum coverage across encryption, key custody, perimeter, gateway, and threshold cryptography under one contract and one integration — not a single capability. Status is honest: the FHE pipeline and PQ APIs are live; FIPS 203/204 algorithms are NIST-standardized; SOC 2 and ISO 27001 status is stated per the compliance section, and throughput figures are illustrative benchmark numbers — verify on /benchmarks/.
If you need one capability rather than the bundle, go direct: H33-Key for key custody, FHE for encrypted processing, H33-74 for portable attestation. For custodial control over an individual or estate, use Digital SCIF. For durable evidence across organizational change, see Institutional Continuity. For a governed institutional transfer, use Tokenize.
v10 benchmarks from Graviton4 (c8g.metal-48xl, 192 vCPUs, 96 workers). 120-second sustained run. Every number links to the methodology.
One API key. One curl command. Full FHE + ZK + Dilithium pipeline. No cryptography PhD required.
# Check an encrypted payload for harvest-now-decrypt-later patterns curl -X POST https://api.h33.ai/v1/shield/analyze \ -H "Authorization: Bearer h33_pk_..." \ -H "Content-Type: application/json" \ -d '{ "payload": "'$(base64 encrypted_traffic.bin)'", "mode": "realtime", "agents": ["harvest", "sidechannel", "crypto_health"] }' # Response (2.35µs total agent latency): # { # "status": "clean", # "agents": { # "harvest": { "safe": true, "latency_us": 0.69 }, # "sidechannel": { "safe": true, "latency_us": 1.14 }, # "crypto_health": { "safe": true, "latency_us": 0.52 } # }, # "attestation": "dilithium_sig_...", # "zk_proof": "0x..." # }
// Generate a post-quantum key pair via H33-Vault const h33 = new H33Client({ apiKey: "h33_pk_..." }); // Keys never exist in plaintext outside the vault const key = await h33.vault.generateKeyPair({ algorithm: "kyber-1024", // ML-KEM (FIPS 203) rotation: "90d", // Auto-rotate every 90 days signing: "dilithium-5", // ML-DSA (FIPS 204) audit: true, // Dilithium-signed access logs }); // key.id = "vault_k_..." (reference handle, not the key) // key.publicKey = "..." (safe to distribute) // key.algorithm = "kyber-1024" // key.nextRotation = "2026-06-14T00:00:00Z"
We did the paperwork so you can skip the 6-month procurement committee debate about whether post-quantum is real.
Three deployment models. Same cryptographic pipeline. Pick the one that matches your security posture — not the one your vendor forces on you.
Access H33 via REST API. We handle infrastructure, scaling, and updates.
Deploy H33 inside your security boundary. Full control over data residency.
Cloud API for auth. Self-hosted Vault for key management. Keys never leave.
Free developer plan: 1,000 operations per month. No credit card. Full FHE + ZK + Dilithium pipeline from day one. Enterprise contracts with volume discounts and dedicated infrastructure.