Oz Liveness Review 2026: Pricing, Features & Alternatives

PrimeBiometry Assessment

Oz Liveness – also marketed as OZ Biometry, oz-forensics, ozliveness, and Oz Forensics liveness SDK – is a passive liveness detection SDK by Oz Forensics, founded 2017. All names refer to the same product from the same company.

This is a component product, not a full identity verification suite. The intended use is embedding a certified liveness check inside an existing IDV pipeline or authentication flow. Organizations buying a complete KYC platform should look at Sumsub, iDenfy, or ComplyCube instead.

The credential that separates it: ISO 30107-3 Level 1 and Level 2 PAD certification. Most vendors list “liveness detection” as a feature; Oz Forensics holds formal anti-spoofing certification from an accredited testing laboratory, which is a different thing. SOC 2 Type II is current. A 5/5 Capterra rating from a small review base adds modest independent signal.

Try Oz Liveness free: Oz Forensics publishes a live passive liveness demo at ozforensics.com/trynow – no account required. Run it against a photo attack and a real face before requesting a commercial quote.

Pricing Analysis

Pricing is custom and contact-based with no public tiers, standard for a component SDK sold to enterprise buyers and IDV platform builders. Cloud API deployments typically price per liveness check by volume. On-premise SDK licensing usually runs as an annual flat fee, cost-efficient at 100K+ monthly checks but harder to justify below that.

Before requesting a quote, nail down two numbers: expected monthly check volume and deployment model (cloud vs. on-premise). If you are evaluating Oz Liveness as a layer on top of an existing platform, model the combined cost against integrated vendors like Jumio or iDenfy that bundle certified liveness in their per-verification fee. The separate SDK only makes financial sense if your current platform lacks ISO 30107-3 Level 2 PAD certification.

How to Integrate Oz Liveness SDK

Oz Liveness supports three deployment paths: Cloud API, Mobile SDK (iOS/Android), and Web SDK. Integration steps are the same regardless of platform:

1. Request credentials – sign up at ozforensics.com for a free trial API key. No credit card required; the trial runs on the production system.
2. Choose deployment model – Cloud API (per-check billing, fastest to integrate) or On-premise SDK (annual flat fee, appropriate at 100K+ monthly checks where per-check cost exceeds licensing cost).
3. Add the SDK – iOS via CocoaPods/SPM, Android via Maven, Web via npm or script tag. Flutter and React Native wrappers are available; confirm the current version during technical evaluation.
4. Initialize with API key – pass your credentials and configure the capture parameters: resolution, timeout, and passive vs. active liveness mode.
5. Handle the result callback – the SDK returns a liveness score and pass/fail decision. Route passing sessions to your next IDV step (document check, selfie match); reject failing sessions or route to human review.
6. Test against spoofing – Oz Forensics provides test assets (printed photo, video replay) to validate your PAD configuration before go-live.

Typical integration time is 1–3 days for Cloud API, 3–5 days for native mobile SDK with UI customization.

FAQ

What is ISO 30107-3 certification and why does it matter? ISO 30107-3 is the international standard for Presentation Attack Detection (PAD) in biometric systems. It defines how liveness detection systems resist spoofing attacks: photos, videos, and 3D masks. Level 1 covers standard attacks; Level 2 covers more sophisticated adversarial scenarios. Oz Liveness holds both, which matters in regulated procurement where the certification level is a gate.

Is Oz Liveness a standalone product or an SDK for embedding? Primarily an SDK. Oz Liveness is designed to be embedded into existing applications and identity verification flows via API or mobile SDK, not used as a standalone end-user product.

Does Oz Liveness support passive liveness detection? Yes. Oz Liveness uses passive liveness detection (no user action required beyond looking at the camera) combined with real-time environment analysis. No blink, no head turn. This matters for conversion: active liveness steps add drop-off in high-volume consumer flows.

What platforms does the Oz Liveness SDK support? Web, iOS, and Android. Cross-platform compatibility is confirmed; verify React Native and Flutter support during technical evaluation since framework-level bindings vary by SDK release.

How does Oz Liveness handle poor lighting or low-quality cameras? Real-time environment analysis is a core listed feature, indicating the system adapts to suboptimal capture conditions. For high-fraud-risk deployments, request FAR and FRR benchmarks under degraded conditions from the vendor directly.