Lifegence Voiceprint API vs Voiceme VoiceKey
Lifegence Voiceprint API
github.comVoiceme VoiceKey
voiceme.idSide by side
| Figure | Lifegence Voiceprint API | Voiceme VoiceKey |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · AI Voice Biometrics Software | 7.1 (#17) | 7.5 (#12) |
| Biometric data | The security policy says embeddings should be treated as sensitive biometric data and calls for encryption at rest and TLS 1.3 in transit. | Voiceme says it stores mapping vectors rather than biometric audio or video files, and that customers define retention and deletion policies. |
| Deployment | The project provides a Docker Compose quick start for running the API server. | Voiceme says it is available as a SaaS or on-premises solution. |
| Purpose | It is a self-hosted REST API for speaker verification (1:1) and identification (1:N). | VoiceKey is a Secure Customer Authentication module for authenticating customers in digital properties using voice recognition, facial biometrics, and device information. |
| Security | The security policy recommends TLS 1.3 in transit, encrypted database storage, API-key access control, and storing embeddings rather than raw audio. | The FAQ describes asymmetric and symmetric encryption and encrypted data fragmentation as protections for transmitted and stored data. |
Plans
In their own words
Lifegence Voiceprint API
Lifegence Voiceprint API is a free, open-source, self-hosted REST API for speaker verification and identification. Enrollment records a speaker’s voiceprint; verification compares audio with one enrolled speaker for 1:1 authentication, while identification searches enrolled speakers for a 1:N match. SpeechBrain ECAPA-TDNN produces 192-dimensional voice embeddings. The documented inputs are WAV, MP3, WebM, and OGG recordings lasting 3 to 30 seconds, with 5 to 10 seconds recommended. Docker Compose starts the API with PostgreSQL 16 and pgvector plus Redis 7. Requests use API keys in the X-API-Key header. Enrollment includes consent fields, and a delete endpoint removes associated voiceprint data. The security policy recommends TLS 1.3 in transit, encryption at rest, and treating embeddings as sensitive biometric information. Rate limits are 10 enrollment, 60 verification, and 30 identification requests per minute. The current version has no liveness or anti-spoofing controls and does not guarantee perfect recognition accuracy.
Voiceme VoiceKey
Voiceme VoiceKey is a B2B module for authenticating customers in digital services using voice recognition, facial biometrics, and device information. Its voice models compare vocal characteristics with stored samples, while facial recognition compares extracted features with stored ones. For a liveness check, VoiceKey can ask a user to repeat a randomly generated sentence and use speech-to-text to check the response. The sentence can expire within seconds, working as a short-lived voice code. Companies can choose authentication factors and configure settings such as sentence lifetime, accuracy, word count, and whether users supply the sentence. The platform supports web, mobile, physical devices, chats, chatbots, and voicebots, and is integrated with WhatsApp. APIs and Android and iOS SDKs support integration with existing systems. Voiceme offers SaaS or on-premises deployment and makes technical materials and integration flows available on request. The company says it stores mapping vectors rather than biometric audio or video files; customers define retention and deletion policies. Voiceme describes encryption and encrypted data fragmentation as data protections. Pricing is available on request, and the page invites prospective customers to request a demo.