Benchmarks Docs Pricing Blog About
Log In Get API Key

ZK Proof Platform Comparison: H33 vs RISC Zero vs Aztec vs Succinct

General-purpose ZK platforms generate proofs in seconds. H33 generates ZK-STARK proofs in 2.0 microseconds and verifies them in 0.2 microseconds — the fastest zero-knowledge proof verification in production. No circuits. No trusted setup. One API call.

Get Free API Key See Benchmarks
Platform Comparison

H33 vs RISC Zero vs Aztec vs Succinct — Side by Side

How a purpose-built ZK authentication platform compares to general-purpose zero-knowledge proof frameworks.

Feature H33 RISC Zero Aztec Succinct
ZK Scheme ZK-STARK zkVM (STARK-based) PLONK / UltraPLONK SP1 (STARK)
Prove Time 2.0µs Seconds Seconds Seconds
Verify Time 0.2µs Milliseconds Milliseconds Milliseconds
FHE Integration Yes — 4 FHE engines (BFV, CKKS, BFV32, FHE-IQ) No No No
Post-Quantum Signatures Dilithium (ML-DSA) + Kyber (ML-KEM) No No No
Deployment REST API — one call Library / SDK L2 Network Library
Primary Use Case Auth / Identity / Biometrics General computation Financial privacy General computation
Trusted Setup No (STARK — transparent) No (STARK) Yes (PLONK) No (STARK)
Throughput 2.17M ops/sec sustained Varies by circuit Network-bound Varies by circuit
Pricing Per-operation ($0.033/auth) Open source Gas fees Open source
Why H33 ZK Is Different

Purpose-Built ZK for Authentication at Scale

2.0µs

Microsecond Prove Time

H33 generates ZK-STARK proofs in 2.0 microseconds — not seconds. Purpose-built STARK lookups for identity verification eliminate the overhead of compiling arbitrary programs into circuits. Verification completes in 0.2 microseconds. That is over 1,000x faster than general-purpose zkVMs.

FHE + ZK + PQ

Combined Cryptographic Stack

H33 is the only platform that combines fully homomorphic encryption, zero-knowledge proofs, and post-quantum signatures in a single API call. FHE biometric matching, ZK-STARK verification, and Dilithium attestation all execute in one pipeline — approximately 38.5 microseconds per authentication.

0 Circuits

No Circuit Development Required

RISC Zero requires writing guest programs in Rust. Aztec requires the Noir DSL. Succinct requires SP1 program development. H33 requires a single REST API call. No circuits to write, no proving keys to manage, no trusted setup ceremonies, and no ZK-specific programming languages to learn.

2.17M/sec

Production-Scale Throughput

Benchmarked at 2.17 million operations per second sustained on AWS Graviton4 with 96 workers. In-process DashMap caching delivers 0.059 microsecond lookups — 44x faster than raw STARK computation. Built for production workloads, not proof-of-concept demonstrations.

Developer Experience

Code Comparison: RISC Zero vs H33

A full RISC Zero proof cycle versus a single H33 API call with ZK proof included.

RISC Zero — Guest Program + Prove + Verify
// Step 1: Write a guest program (Rust)
// guest/src/main.rs
use risc0_zkvm::guest::env;

fn main() {
    let input: u64 = env::read();
    let result = verify_identity(input);
    env::commit(&result);
}

// Step 2: Compile to RISC-V ELF
// $ cargo build --release

// Step 3: Generate proof (host side)
let env = ExecutorEnv::builder()
    .write(&input)?.build()?;
let prover = default_prover();
let receipt = prover
    .prove(env, GUEST_ELF)?;  // seconds

// Step 4: Verify proof
receipt.verify(GUEST_ID)?;   // milliseconds
H33 — One API Call with ZK Proof
// One call. ZK proof included.
const result = await fetch('https://api.h33.ai/v1/verify', {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${apiKey}`,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    biometric: capturedTemplate,
    tier: 'h33-128'
  })
});

const data = await result.json();
// data.verified      → true / false
// data.zkProof       → ZK-STARK proof (2.0µs)
// data.attestation   → Dilithium signature
// data.fheMatch      → encrypted biometric result
//
// No circuits. No compilation.
// No trusted setup. No proving keys.
// SHA3-256 STARK — post-quantum secure.
FAQ

Frequently Asked Questions

How is H33's ZK different from RISC Zero?
H33 is purpose-built for authentication and identity verification, delivering ZK-STARK proofs in 2.0 microseconds with 0.2 microsecond verification. RISC Zero is a general-purpose zkVM that compiles arbitrary Rust programs into ZK proofs, which takes seconds per proof. H33 trades generality for extreme speed in its target domain: identity, biometrics, and credential verification. If you need ZK proofs for arbitrary computation, RISC Zero is a strong choice. If you need ZK proofs for authentication at scale, H33 is over 1,000x faster.
Does H33 support custom ZK circuits?
H33 provides pre-built ZK verification optimized for authentication, identity, and biometric use cases. You do not write circuits — you call a REST API. For custom circuits or general-purpose computation proofs, RISC Zero (zkVM), Aztec (Noir DSL), or Succinct (SP1) may be better fits. H33 excels when you need ZK proofs for identity verification at scale without cryptographic expertise.
Why is H33 so much faster than other ZK platforms?
H33 uses purpose-built ZK-STARK lookups for identity verification rather than compiling arbitrary programs into circuits. Combined with in-process DashMap caching at 0.059 microsecond lookup times (44x faster than raw STARK computation) and SHA3-256 based proofs, H33 achieves 2.17 million operations per second sustained on AWS Graviton4. General-purpose zkVMs sacrifice speed for flexibility — H33 sacrifices generality for extreme throughput in its target domain.
Is H33 a blockchain or L2 network?
No. H33 is a security API — not a blockchain, not an L2, not a rollup. Aztec is an L2 network on Ethereum that uses ZK proofs for transaction privacy. H33 is a REST API that returns ZK-STARK proofs, FHE-encrypted biometric matches, and Dilithium post-quantum signatures. H33 works with any blockchain, any backend, or entirely off-chain. There are no gas fees, no block confirmations, and no network dependencies.
Does H33 require ZK expertise to use?
No. H33 is a single REST API call. There are no circuits to write, no proving keys to manage, no trusted setup ceremonies, and no ZK-specific programming languages to learn. RISC Zero requires writing guest programs in Rust and understanding the zkVM execution model. Aztec requires learning the Noir DSL. Succinct requires SP1 program development. With H33, you send a JSON request and receive a verified ZK-STARK proof in the response.
Can I verify H33 ZK proofs independently?
Yes. H33 uses SHA3-256 based ZK-STARK proofs, which are transparent and publicly verifiable. There is no trusted setup — unlike PLONK or Groth16 based systems (such as Aztec). Any party can independently verify an H33 proof using the public verification data included in the API response. The SHA3-256 hash function is also post-quantum secure, meaning proofs remain sound even against quantum adversaries.

Ship ZK Proofs in One API Call

No circuits. No trusted setup. No ZK expertise required. ZK-STARK proofs in 2.0 microseconds.
Get Free API Key Read Documentation
1,000 free authentications per month. No credit card required.