AwareSDK Voice vs LumenVox Active Voice Biometrics

AwareSDK Voice is a paid SDK for adding mobile voice authentication on iOS and Android. It provides speaker-recognition algorithms, libraries, user interfaces, reference programs and documentation for multifactor authentication. Biometric templates can be stored and matched on the device or on a server, and recognition is described as language-independent. Authentication supports static and dynamic passphrases. Voice recognition can be combined with other biometric modalities; Aware’s Knomi framework pairs facial recognition with voice authentication. Aware positions the SDK for remote identity authentication, contact centers and mobile applications, and says it helps detect replay and synthetic-voice attacks. Developer downloads include Android and iOS voice-capture demos, but a release key is required for those projects to work. The company describes its APIs as configurable and its technical support as collaborative. Aware began in 1993 and is headquartered in Burlington, Massachusetts. The product page invites demo scheduling; pricing is available by demo or contact, with no public price or trial terms listed.

LumenVox Active Voice Biometrics provides text-dependent voice authentication for enterprises seeking identity assurance beyond passwords, PINs, and security questions. Containerized microservices run on Kubernetes on-premises, in private or public clouds, or across hybrid environments. A deep-neural-network engine supports active, passive, and hybrid authentication. Enrollment and verification can use any passphrase and language supported by the corresponding ASR engine. Playback, liveness, synthetic-speech, and fraud-watchlist checks address presentation attacks. APIs create, retrieve, disable, re-enable, and remove identities and query enrollment status. Biometrics, Speech, Management, and Reporting APIs are exposed through gRPC and REST. Supported channels include contact-center IVR, smartphone and web applications, desktop applications, virtual assistants, video calls, messaging platforms, and conversational AI. Enrollment requires at least three separate utterances. Audio must be headerless base64 PCM-16, A-law, or μ-law at 8 kHz. Data is encrypted at rest and in transit, with customer-controlled keys and TLS between components. Pricing is on request.