Aculab Cloud

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

Aculab Cloud covers multiple communications channels and offers REST and UAS approaches for application development. New accounts have an outbound service limit, and premium-rate calls are unsupported.

It suits businesses building communications applications through APIs, including teams seeking voice, video, messaging, or fax capabilities without specialist telephony equipment. Developers can choose between REST and UAS application approaches.

Aculab Cloud is a communications API platform for businesses building voice, video, messaging, or fax workflows. It is best suited to development teams prepared to build and host their own applications. Its range of channels and speech tools is a strong draw, while the trial quotas and low starting outbound rate limit how quickly new accounts can scale.

Overview

Aculab Cloud connects applications to telephone numbers and SIP addresses, and its WebRTC interface can add live calling to a web page. It also handles inbound and outbound fax and supports sending and receiving SMS and MMS, subject to account and local requirements. That breadth is useful when a product needs several communications channels; businesses seeking a ready-made phone system should look elsewhere, since the emphasis is on APIs for building applications.

Teams can run REST applications on a web server they host or run UAS applications in a User Application Server installed on their platform. REST supports Python, C#, VB, Java, PHP, and other scripting languages; UAS supports Python, C#, VB, F#, and C++. The two approaches offer flexibility, but both expect developers to take responsibility for the application and its hosting.

Key features

Speech and voice capabilities

The feature set includes voice applications, live speaker detection, speech recognition, translation, text-to-speech, and voice biometrics. Recognition uses Google Speech-to-Text, while text-to-speech supports Amazon Polly and Cepstral engines. This combination can serve applications that need speech functions alongside communications APIs, though it is not a substitute for choosing and building the application workflow.

WebRTC enables browser-based live calling, and messaging covers SMS and MMS in both directions. Media files can be encrypted with keys supplied at runtime. The service runs on AWS; web services use HTTPS and UAS connections use SSL by default. These are relevant protections for teams handling communications data, while the customer-controlled media encryption option leaves key provision in the customer's hands.

Regions, support, and limits

Accounts are assigned to a cloud region; documented options include Europe, USA-East, and USA-West in beta. New accounts begin with a maximum of one outbound service per second. Support can raise the limit, but teams expecting high outbound volume should account for that initial constraint. The outbound provider does not support calls to premium-rate numbers, ruling out workflows that depend on them.

Free developer support includes documentation, quickstart guides, email support, and bug reporting. Paid contracts can add guaranteed response times and 24×7 emergency support, which matters for businesses that need defined support coverage.

Pricing

Aculab Cloud is paid for production use, with a free Trial account to start. The trial costs nothing and includes $10 free credit, expires after 1 month, and allows 5 inbound and 5 outbound services. Trial calls can cost up to 23c per minute to the user's validated number. The time limit, small service quotas, and validated-number restriction make it useful for initial development, not an open-ended free deployment.

Production has custom pricing and is billed Pay-as-you-go, with usage rates shown in the Cloud Console. It provides full feature access, requires the paid account to be kept in credit, and permits outbound calls up to 75c per minute to any number. This is the practical tier for teams moving beyond the trial, but they need to monitor usage and maintain account credit.

Premium also has custom pricing and is billed Invoiced for usage; customers must contact Aculab. It is described as like a Production account, with further details available from Aculab. That makes it the option to pursue for invoiced usage, while the published terms do not establish a specific feature advantage over Production.

Platforms

Aculab Cloud supports Android, iOS, web, API, and self-hosted environments, with cloud deployment. SDK platforms include Java, Python, PHP, and .NET. The range suits teams integrating communications into different application environments, with REST and UAS offering distinct hosting approaches.

Who it's for

This is a fit for businesses with developers who want to build communications applications without specialist telephony equipment, particularly when voice, messaging, fax, speech, and biometrics belong in the same workflow. It is less suitable for buyers who want an out-of-the-box calling product, need premium-rate outbound calling, or cannot work within the new-account outbound limit while requesting an increase.

Pros and cons

• Pros: Multiple channels—voice, video, SMS, MMS, and fax—let teams build varied communications workflows through one platform.
• Pros: REST and UAS support a broad set of programming languages and different application-hosting models.
• Pros: Trial credit gives developers a limited-cost way to begin, and free developer support includes documentation, email, and bug reporting.
• Cons: The Trial expires after one month and is capped at 5 inbound and 5 outbound services.
• Cons: New accounts start at one outbound service per second, and premium-rate numbers cannot be called.
• Cons: Production requires account credit, while Premium requires contacting Aculab for invoiced usage.

Alternatives

For a narrower focus on voice biometrics, compare the AI Voice Biometrics Software category. armour365 Voice Biometrics is worth considering when a lifetime-free developer plan matters: its Developers plan is free for life, and it also offers a free plan. Its Small Businesses Owners and Startups plan makes the first 10K transactions free, with a stated rate of $2.99/1K trans for 10K–100K.

Recognition Technologies Speaker Recognition is another paid option with a free trial and a broad set of supported platforms. Auraya ArmorVox, Kardome VoiceID, Voiceme VoiceKey, VoiceVantage VoiceCheck, AwareSDK Voice, and LumenVox Active Voice Biometrics are additional paid alternatives.

Verdict

Choose Aculab Cloud if your team can build and host its own applications and wants voice, messaging, fax, and speech capabilities through a choice of REST or UAS APIs. Its strongest case is the breadth of communications functions in a developer-oriented platform; look elsewhere if you need premium-rate calling, a ready-made phone system, or higher outbound capacity immediately on a new account.