H33 is not a SaaS product. It's a five-tier machine: a portability thesis, an atomic primitive, six named subsystems, a product surface, and a layer of live demos. This page is the map of the whole machine.
TIER 1 — THESIS ← buyer-intent Portable Artifact · Independent Verification · Evidence Portability Claims Evidence · Verifiable AI Decisions · Public Integrity Layer Privacy Layer · Post-Quantum │ ▼ TIER 2 — PRIMITIVE ← the atomic substrate H33-74 (Evidence Root) · H33-Root (Authority Root) │ ▼ TIER 3 — SUBSYSTEMS ← the named "machine parts" Cachee · Upstream · Agent Zero · Q-Sign · HATS · FHE-IQ │ ▼ TIER 4 — PRODUCTS ← acquisition surfaces H33-Vault · H33-Shield · H33-Share · Verifier · Attestation · ArchiveSign · Tokenize · WireProof · Biometrics · Encrypted Search │ ▼ TIER 5 — DEMOS ← interactive proof surfaces Trust Card · Verifier (browser) · HATS Demo · Avalanche Demo AI Audit Trail · VES · BitBonds Demo · What If H33 Disappears
Q: What problem does H33 actually solve?
Eight gravitational pages — each answers one form of the buyer's "why care" question. They are concept-oriented, not implementation-oriented. The fastest way to understand H33 is to pick the thesis page that matches your role and read it end-to-end.
Q: What's the smallest, most reusable unit of trust H33 produces?
H33-74. Seventy-four bytes per attestation — small enough to embed on-chain, in a packet header, in a credential, in an FHE proof, in a PQ seal. Every subsystem above is, at its core, a different way to produce or consume H33-74 primitives. If you want to understand H33 deeply, start here.
Q: What are the named modules H33 ships, and what does each do?
Six named subsystems. Each is its own buildable component on top of H33-74. They compose: a HATS attestation can run through Cachee for caching, Upstream for source-of-record proof, FHE-IQ for encrypted computation, and Q-Sign for the post-quantum signature. The subsystems are how H33 actually delivers the thesis.
Q: What does H33 sell, and where do I integrate it?
Products are how subsystems get to market. Auth, biometrics, encrypted storage, signed releases, audit infrastructure — each draws on one or more subsystems but presents a single integration surface. If you're an engineer trying to add H33 to a specific stack, this is where you land.
Q: Can I see this work in 60 seconds?
Eight live demos in the browser. Each surface runs real cryptography — real SHA-256, real envelope structural verification, real PQ signature parsing, real FHE/STARK pipelines simulated end-to-end. You can tamper any of them and watch the verdict flip to FAIL. This is the layer that produces meetings.
A reader's journey through the site mirrors the architecture. They arrive on a Tier-1 thesis page (why care). They land on a Tier-5 demo (can I see it work). They sign off on a Tier-4 product (where do I integrate). And under it all, Tier 2 and Tier 3 are doing the actual work.
THESIS Portable Artifact → answers "why care about portability?" │ ↓ Primary CTA DEMO Trust Card → renders a real bundle in browser │ ↓ Post-demo bridge Schedule an Evidence Architecture Review → auth-api.z101.ai PRIMITIVE H33-74 ← the substrate every demo and thesis sits on SUBSYSTEM Cachee ← the receipt cache the bundle is delivered from SUBSYSTEM Q-Sign ← the signature scheme the bundle uses SUBSYSTEM FHE-IQ ← the encrypted compute the bundle records PRODUCT Verifier ← the binary the regulator runs PRODUCT Attestation← the document type the verifier produces