Auraya ArmorVox vs LumenVox Active Voice Biometrics

Auraya ArmorVox is a voice biometric engine for identity verification and fraud detection. It supports text-dependent, text-independent, text-prompted and digit-independent enrollment and verification, and can maintain identity assurance through a user session. Its adaptive learning engine updates voiceprints as voices change. For fraud defense, it can flag potential synthetic-voice and recorded-playback attacks, and compare users against voiceprints in near real time to identify duplicates and impostors. Organizations can tune background voiceprint models and set speaker-specific thresholds. Example uses include contact centers, digital apps, password resets, voice e-signatures and fraudster management. Integrations named for cloud contact centers include Amazon Connect, Twilio, Five9, Avaya and Genesys; platforms that can post an audio WAV file to its server can integrate. ArmorVox works with cloud-based or on-premise platforms. Auraya says encrypted voiceprints and recordings stay within the organization’s secure infrastructure and are inaccessible to Auraya. It is listed for Android, iOS, Linux, macOS, Windows, web, API, extensions and self-hosted deployment. Pricing is on request.

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.