Wazo Platform

Wazo Platform is a self-hosted telecom software stack for teams building their own voice, video and messaging services. It is best suited to developers who need programmable communications infrastructure; choose another product if you need a managed phone service or turnkey installation.

Overview

Wazo puts telecom capabilities behind APIs rather than packaging them as a finished business phone system. Its GPL-3 license permits commercial use at no software charge, but teams take responsibility for deployment, configuration and ongoing operation.

It can underpin audio and video calls, chat, conferences, voicemail and call centers. The beta SIP Router use case covers SIP routing, load balancing, NAT management and high availability, while the beta Session Border Controller focuses on security and protection. Those are explicitly beta use cases, so teams should weigh that status before depending on them in production.

Key features

Programmable communications

WebRTC, REST APIs, WebSockets and Webhooks give developers several ways to connect web and mobile experiences or build services around Wazo. OpenAPI specifications describe the APIs, and the microservices are developed in Python. This suits engineering teams extending communications workflows; it is less compelling for organizations that want to configure a ready-made product without development work.

Telecom core and integrations

Asterisk, RTPEngine and Kamailio form the telecom engine, supported by RabbitMQ, NGINX and PostgreSQL. APIs can connect billing and third-party services such as speech-to-text, AI and sentiment analysis. A Node-RED connector is part of the ecosystem, and configured contact-directory integrations can enable reverse number lookups, global search, calling directory contacts and favorites.

Deployment and security

Wazo can run on bare metal, virtual machines or containers. The documented all-in-one installation uses Debian 12 Bookworm and Ansible; a small production deployment for about 50 users has minimums of 2 CPUs, 4 GiB RAM and 50 GiB storage. That flexibility is useful for teams with infrastructure expertise, but the installation is not a one-click hosted service. Wazo includes fail2ban jails for Asterisk registration attempts, device provisioning requests and SSH brute-force attempts. It installs iptables without configuring firewall rules, so administrators must set those rules during installation.

Support is community based through Mattermost, a forum and JIRA bug tracking. Wazo Enterprise products add web or mobile applications and a web management console, but those are not part of the open-source platform plan.

Pricing

Plan	Price	What it includes
Wazo Platform	free	Open source, self-hosted on Debian, community supported

The free plan is a fit for teams able to provide their own hosting and technical support. There is no paid tier described for the platform itself; the trade-off for the zero software price is that the adopter handles deployment, firewall configuration and operations.

Platforms

Wazo supports Android, iOS, Linux, web, API and self-hosted use. That breadth reflects its role as an infrastructure platform with programmable interfaces, rather than a single end-user client.

Who it's for

Choose Wazo if developers need to assemble business communications around their own requirements, particularly when self-hosting and integrating billing or other services matter. Its unified communications capabilities can support calling, chat, conferences, voicemail and call-center use cases. It is a poor match for buyers who need managed deployment, preconfigured firewall rules or support beyond community channels.

Pros and cons

Pros

• GPL-3 licensing allows free commercial use, keeping software licensing costs out of the deployment.
• Multiple APIs and WebRTC support give developers options for integrating communications into web and mobile services.
• Bare-metal, virtual-machine and container deployment options suit teams with varied infrastructure preferences.
• Fail2ban jails cover several common attack surfaces, including SSH brute-force attempts.

Cons

• Self-hosting means the adopter must install and operate the platform, including configuring firewall rules.
• The documented all-in-one install targets Debian 12 Bookworm, which narrows the straightforward installation path.
• Community support may not meet the needs of organizations that require dedicated vendor support.
• SIP Router and Session Border Controller use cases are beta, a concern for teams relying on them for production-critical services.

Alternatives

For a narrower selection of tools, browse Interactive Voice Response Software or Business Phone Systems.

FreeSWITCH is another free, self-hosted communications platform, and may suit teams seeking an alternative open-source stack. Voicent offers a free allowance of 100 minutes/texts and a paid Starter plan, a better fit for buyers who want a packaged campaign-oriented service. Telnyx Text-to-Speech API is a usage-priced API option for teams focused on text-to-speech rather than building a broader telecom platform.

Twilio Studio offers 1,000 free flow executions per month and may suit teams building call flows without self-hosting a telecom stack. SIP.IO provides trial credit, a test number and access to call flows, queues and contact-center features, making it an option for evaluating those workflows. Asterisk is a free, GPLv2, self-hosted alternative for teams looking for an open-source telephony engine.

Telnyx TeXML is a pay-as-you-go service without a free plan, suited to teams willing to use published usage rates rather than operate their own platform. Avaya Aura Private Cloud uses pay-per-user pricing and may fit organizations seeking a private-cloud communications offering instead of self-hosted open-source software.

Verdict

Wazo Platform is a strong choice for developers who want a free, commercially usable foundation for custom communications services and can own the infrastructure work. Its programmable interfaces and deployment flexibility are the main reasons to choose it; the operational burden, firewall configuration and community-only support are the reasons to look elsewhere.