Built by one engineer.
Shipped to mainnet.
zkRune is privacy-preserving verification infrastructure. We make it cheap and safe for any app to verify users without becoming a data target. This page is the short story behind it.
zkRune is a one-person operation. The full stack — circuits, SDK, widget, hosted verifier, Android proving runtime, and the three mainnet verifier deployments — was built end-to-end by Louis. Background spans applied cryptography (Groth16, BN254, Powers-of-Tau), Rust on-chain programming, and TypeScript / WASM toolchains.
Being a solo team is a constraint we name openly. It is also how the project moved from zero to three mainnet verifiers and 14 circuits in a few quarters without a stand-up, a steering committee, or a token-distribution rationalisation. Grant funding and pilot integrations extend that runway. Acquisition conversations are welcome.
Concrete artefacts, not roadmaps.
Everything below is live today. Roadmap items live on the roadmap page and are labelled accordingly.
- 14 production Groth16 circuits, with multi-party trusted setup artefacts published
- Mainnet verifier contracts on Solana, Ethereum (Base L2), and Sui
- Client-side proving in WASM — proofs generated in 0.4–5 seconds on commodity hardware
- Open-source TypeScript SDK (zkrune-sdk) and embeddable widget (zkrune-widget)
- Hosted verification API and dynamic-content docs at /docs
- Android proving runtime (signed APK) and PWA install path
- Published trust model classifying every circuit by production / self-asserted / experimental
Four principles that are easy to verify.
Open by default
Source, circuits, ceremony artefacts, and the trust model are all public. If a buyer or auditor wants to verify a claim on this site, the code is one click away.
Honest about boundaries
Every circuit is labelled with its trust level. The /trust page lists what we have proved and what we have not. No hand-waving, no "trust us".
Ship to mainnet, not testnet
Three mainnet verifiers carry real users today. We don't write blog posts about cryptography we haven't deployed.
Privacy by architecture
Private inputs never leave the user's device. The hosted verifier sees proofs and public signals only. PII retention is structurally impossible, not just policy.
Seven compliance verticals, one ZK primitive set.
Same 14 production circuits underneath all of them. Per-vertical landings have buyer-relevant mapping tables; the regulations matrix is the universal filter.
EU AI Act — Article 12
→High-risk AI vendors facing the 2 August 2026 record-keeping mandate.
Proof of Agent
→AI agent platforms, enterprise AI ops, governance vendors. Authority · Agent Passport · Constraint · Human-in-loop.
EUDI Wallet — eIDAS 2.0
→Wallet implementers, attestation issuers, relying parties. ARF-aligned selective disclosure.
MiCA + Travel Rule
→Crypto-asset service providers, ART/EMT issuers, AML technology integrators.
Age-gating
→Dating, social, adult, gambling platforms in scope of DSA Art. 28 + UK OSA + US state laws.
DORA + NIS2
→Financial entities, ICT third-party providers, NIS2-adjacent critical infrastructure.
US Privacy + Sectoral
→Multi-state SaaS, AI vendors under Colorado AI Act, HIPAA / COPPA / GLBA / FCRA-regulated operators.
Pilot partners, compliance teams, grants, and the right acquirer.
Pilot integrators
Web2 or web3 apps with an age-gating, membership, KYC-lite, eligibility-verification, or agent-attestation problem. We work hands-on with the first integrations.
Enterprise compliance teams
DPOs, compliance leads, and engineering teams in scope of any of the seven regimes above. See /regulations for the full matrix and /enterprise/* for per-vertical landings.
Grant partners
NLnet, Solana Foundation, EU NGI, and privacy-aligned grant programmes. Outputs are released under permissive open-source licences.
Acquisition conversations
Strategic acquirers in the privacy-compliance, identity-proofing, or developer-tooling space. Reach out via email.
Get in touch.
One inbox, one founder. The fastest way to evaluate whether zkRune fits your problem is to write a short email describing it.
zkruneprotocol@gmail.com · @rune_zk on X