Prove you’re you.
Reveal nothing else.
Build your first secure application with zero-knowledge proof authentication in minutes.

Three authentication methods, each with an explicit trust and recovery boundary.
Prove a password without sending it
The research flow derives a zero-knowledge proof locally and sends ZKAuth only proof material. V2 binds freshness to a one-time server ceremony; independent cryptographic review and a production ceremony are still required.
How the proof worksExchange keys, never the secret
A password-authenticated key exchange. The server holds an opaque credential it can never use to learn the password, even offline.
Read about OPAQUEHardware-backed sign-in
Hardware- and platform-backed passkeys through a backend proxy, so your project key never reaches the browser.
Set up passkeysThe experimental password proof is generated locally.
On the device
Argon2id and Poseidon derive a commitment; the research client generates a Groth16 proof locally.
Over the wire
ZKAuth receives proof and public-signal material rather than the plaintext password.
On the server
The experimental verifier checks the proof. Challenge binding and independent review remain required before production use.
A real login in a few lines.
Use the zkauth-client SDK, or call the HTTPS API from any language. The proof handshake happens for you.
// Browser: call your own backend. No project key here.await fetch('/api/auth/login', { method: 'POST', headers: { 'content-type': 'application/json' }, body: JSON.stringify({ email, password }),})
// app/api/auth/login/route.ts, server onlyimport { ZKAuthSDK } from 'zkauth-client'
const projectKey = process.env.ZKAUTH_PROJECT_API_KEYif (!projectKey) throw new Error('ZKAuth server key is missing')
const zkauth = new ZKAuthSDK({ apiKey: projectKey,})We’d rather be precise than impressive.
Security writing is easy to fake. So here is the exact boundary, in plain language, and endpoints you can call to check it.
- 01No SOC 2, HIPAA, or completed external audit.
- 02No post-quantum security.
- 03No broad WebAuthn authenticator guarantees.
- 04Pro billing is early access; refund and renewal evidence is still limited.
