Aculab Cloud vs Lifegence Voiceprint API

Aculab Cloud provides APIs for building applications that handle voice and video calls, messaging, and inbound or outbound fax. It supports calls to telephone numbers and SIP addresses, and its WebRTC interface can place live calling in a web page. Listed capabilities include live speaker detection, speech recognition, translation, text-to-speech, voice biometrics, SMS, and MMS. The REST API works with Python, C#, VB, Java, PHP, or other scripting languages; REST applications run on a web server you host. The UAS API supports Python, C#, VB, F#, and C++, with applications running in a User Application Server installed on your platform. Speech recognition uses Google Speech-to-Text, while text-to-speech supports Amazon Polly and Cepstral engines. Aculab Cloud runs on AWS; web services use HTTPS, UAS connections use SSL by default, and customers can encrypt media files with keys supplied at runtime. Accounts are assigned to Europe, USA-East, or USA-West (beta). The free Trial includes $10 in credit for one month. Production is pay-as-you-go, with rates shown in the Cloud Console; Premium usage is invoiced and requires contacting Aculab.

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.