Fail-safe by construction
Nothing auto-approves on uncertainty. Missing AI key, unavailable biometric stack, ambiguous document, unconfirmed liveness — every doubtful path lands in human review.
BAQSHI-KYC
Know your users are real people with genuine IDs — without handing their identity to a third party. Built in Aotearoa New Zealand, designed around NZ standards, usable by anyone.
Why this exists
Section titled “Why this exists”Every product that touches money, marketplaces, or age-restricted services eventually needs to answer one question: is this user a real, living person holding a genuine government ID? Most companies rent that answer from a verification vendor — and ship their users’ passports to someone else’s cloud to get it.
BAQSHI-KYC is the self-hosted alternative: the full pipeline — document authenticity, AI tamper inspection, biometric face match, active liveness — running on infrastructure you control, with storage designed so that even we can’t read what we hold without the keys, and deletion that works retroactively across offline backups.
Biometrics stay home
Face matching and liveness run locally on your server. Selfie frames are never sent to any third-party API — a requirement of NZ’s Biometric Processing Privacy Code, and just good practice everywhere else.
Deletion that actually deletes
Per-record envelope encryption means erasure = key destruction. One API call makes every copy of a user’s data unreadable — including archives already on offline media.
Suspicion is a first-class output
Tamper signals, MRZ check-digit failures, liveness anomalies and identity-swap detection are surfaced as structured reasons you can monitor, alert on, and tune. See Trust & safety.
The flow in one paragraph
Section titled “The flow in one paragraph”Your backend creates a verification and gets a QR-able handoff URL. The user — on the hosted web page or inside your Expo app — photographs their ID and completes a random pose challenge that photos and replayed videos can’t follow. The pipeline runs deterministic MRZ maths, AI document inspection, and biometric matching, then decides: approved, rejected, or manual review. Your backend gets a signed webhook and can request an Ed25519-signed attestation carrying only the claims it needs. Raw ID data stays in the encrypted vault, ages out to offline storage after 30 days, and can be cryptographically erased on request.