id3 Face SDK

id3 Face SDK is a developer toolkit for adding face biometrics to self-hosted applications. It suits teams building identity workflows across server, mobile or edge devices, rather than buyers seeking a finished authentication app. The broad biometric toolset is balanced by licensing that must be planned for each deployed device.

Overview

The SDK spans face capture, facial analysis, liveness checks and recognition, letting development teams build multiple stages of a biometric workflow around one toolkit. Self-hosted deployment gives teams control over where their application runs, but the SDK is a component for developers to integrate, not a ready-made end-user service.

id3 Technologies says it was founded in 1990 near Grenoble, France, and that its face-recognition algorithm has been evaluated in the NIST Face Recognition Technology Evaluation. The company also provides API references, integration guides and code samples for developers.

Key features

Capture and analysis

Compatibility with cameras from a wide range of manufacturers gives teams flexibility in selecting capture hardware. Analysis includes landmarks, pose estimation, mask detection and ICAO-compliant facial attribute determination. That breadth is useful for applications needing more than a basic face match, though the features still need to be integrated into the team's own product.

Liveness and matching

Passive and active liveness detection are intended to help guard against presentation attacks using photos or videos. Recognition supports both one-to-one comparisons and one-to-many database searches, covering verification and identification patterns. Those capabilities make the SDK relevant to teams building biometric checks, but the SDK itself does not remove the need to design and operate the surrounding workflow.

Developer and licensing requirements

The product supports C, C++, C#, Python, Java, Kotlin, Swift and Dart; documentation also names F#, Objective-C and VB.NET. A developer license is required to build an application, and each end-user device where it is deployed needs a runtime license. Licenses are locked to a device using a hardware code, so changes to relevant hardware or system properties can invalidate them. Perpetual, temporary and online license models are described; online licenses need regular internet access and generally provide a 30-day offline grace period.

Pricing

The Evaluation plan costs nothing and provides a 30-day trial, limited API calls, community support and a single platform. It is the entry point for evaluation, but the call cap and platform restriction make it a poor fit for production or a cross-platform rollout. The licensing documentation separately describes a full-featured 60-day trial license; teams should distinguish that evaluation license from the 30-day plan terms.

Professional uses custom pricing and includes unlimited API calls, all platforms, email support and a 1-year license. It fits teams that need broader platform coverage and ongoing support, though the per-device runtime licensing remains important to deployment costs. Enterprise also uses custom pricing, adding volume licensing, priority support, custom integration and an SLA guarantee; it is aimed at larger deployments that need those commitments. Pricing is on request, so budget comparisons require a direct quote.

Platforms

id3 Face SDK supports Windows, Linux, macOS, Android and iOS, with server, desktop, laptop, mobile and edge deployment. This spread is a strength for teams maintaining biometric features across device classes. Its self-hosted model is suited to teams prepared to integrate and operate the software themselves.

Who it's for

The SDK is a strong fit for developers building self-hosted applications that need capture, liveness and face matching across multiple platforms. It is less suitable for organizations wanting a turnkey authentication product, a fixed published price, or licensing without per-device deployment considerations.

Pros and cons

Pros: Covers capture, analysis, liveness and one-to-one or one-to-many recognition in one SDK, reducing the need to combine separate biometric components.

Pros: Broad platform and language support gives development teams options across mobile, desktop, server and edge projects.

Cons: Each deployed end-user device requires a runtime license in addition to the developer license, which complicates rollout planning.

Cons: Device-bound licensing can be invalidated by relevant hardware or system changes, and custom-priced plans require a quote before costs can be assessed.

Alternatives

Neurotechnology VeriLook is worth considering when a one-time SDK purchase and perpetual license are preferable: its Standard SDK is €339, paid once and includes SDK development and deployment licensing. StrongKey FIDO Server is an alternative for teams seeking a free, open-source FIDO server with unlimited users, applications and transactions stated for its Community Edition. HYPR Authenticate may suit buyers who prefer an access product with a published $3 a month plan rather than a custom-priced SDK. Bitwarden offers a free password-management plan with unlimited devices and passwords, a different option for buyers focused on password management. Daon IdentityX offers configurable identity services that can be selected individually. Ory is a freemium alternative with a Developer tier and a Production plan at $770 a year. Credenti is another paid alternative. Sensory TrulySecure is a free alternative for teams evaluating face-based authentication across desktop and mobile platforms. For a wider category comparison, see Biometric Authentication Software.

Verdict

Choose id3 Face SDK if your team is building a self-hosted biometric workflow and needs face capture, liveness and recognition across varied platforms. Its breadth and developer resources are the main reasons to shortlist it. Look elsewhere if per-device runtime licensing, device-bound activation or custom pricing conflicts with your deployment or budgeting needs.