Wazo Platform

Wazo Platform is an open-source telecom platform for developers building programmable voice, video, messaging and presence services. Its microservices can support communication infrastructure for calls, chat, call centers, conferences and voicemail, with custom call routing and an auto attendant. Interfaces include WebRTC, REST API, WebSockets and Webhooks, described as mobile- and web-friendly. The services are developed in Python, and the APIs are described through OpenAPI specifications. Asterisk, RTPEngine and Kamailio form the telecom engine, with RabbitMQ, NGINX and PostgreSQL in the technical core. Deployment options include bare metal, virtual machines and containers. The documented all-in-one installation uses Debian 12 Bookworm and Ansible; minimums for a small production installation of about 50 users are 2 CPUs, 4 GiB RAM and 50 GiB storage. Licensed under GPL-3, Wazo is free to use, including commercially. It is community supported through Mattermost, a forum and JIRA.

Wazo provides a self-hosted, open-source foundation for building communications services. Its documented deployment requirements and community-support model are important considerations for teams planning an installation.

Wazo suits developers and organizations building communication services around their business or technical requirements. It is also relevant to teams deploying and managing their own telecom infrastructure.

Wazo Platform is an open-source telecom toolkit for teams building their own calling, video, messaging and presence services. It suits developers who want control over communications infrastructure and can run it themselves. Its software is free for commercial use, but deployment and community-based support make it an engineering-led choice.

Overview

Wazo supplies telecom building blocks rather than a finished business phone service. Teams can use it to create audio and video calls, chat, conferences, voicemail and call centers, then shape those services around their own requirements. That flexibility is valuable when a standard phone system is too restrictive; it also means the adopter must own the installation and operation.

The project is GPL-3 licensed and self-hosted. Its beta SIP Router use case covers SIP routing, load balancing, NAT management and high availability, while its beta Session Border Controller use case is focused on security and protection. The beta status is a meaningful consideration for teams evaluating those components for production.

Key features

APIs for custom communications

WebRTC, REST APIs, WebSockets and Webhooks give developers several ways to connect web and mobile experiences. OpenAPI specifications describe the interfaces, and the microservices are developed in Python. This is a capable base for teams building tailored workflows, but it favors organizations with development resources over buyers looking for a ready-to-configure application.

Telecom engine and integrations

Asterisk, RTPEngine and Kamailio form the telecom engine, with RabbitMQ, NGINX and PostgreSQL in the technical core. APIs can connect third-party billing and services such as speech-to-text, AI and sentiment analysis. Configured contact directories can support reverse number lookups, global search, calling contacts and favorites. Together, these options allow a team to assemble a broader communications service, while the resulting integration work belongs to that team.

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; for a small production deployment of about 50 users, the guide gives minimums of 2 CPUs, 4 GiB of RAM and 50 GiB of storage. These concrete requirements help with capacity planning, though they also make clear that Wazo is infrastructure to operate, not a hosted service.

Preconfigured fail2ban jails cover Asterisk registration attempts, device provisioning requests and SSH brute-force attempts. Wazo installs iptables but does not configure firewall rules, and its security guide recommends configuring them during installation. Teams must therefore include firewall setup in their deployment work.

Pricing

Wazo Platform: free. The plan is open source, self-hosted on Debian and community supported. GPL-3 permits commercial use, so the software can serve commercial deployments without a license fee. The trade-off is that teams provide their own hosting, installation, operations and development effort; support comes through Mattermost, a forum and JIRA bug tracking.

There is no paid Wazo Platform plan described here. Wazo Enterprise products add web or mobile applications and a web management console, but their pricing is custom.

Platforms

Wazo is listed for Android, iOS, Linux, web, API and self-hosted environments. Its interfaces are described as mobile- and web-friendly, while the installation guide centers on Debian 12. The platform flexibility suits teams assembling their own client experience and infrastructure; it should not be read as a turnkey application for each platform.

Who it's for

Wazo is aimed at developers building communications solutions to fit business and technical requirements. It is a strong candidate for teams that want to own their telecom stack, connect APIs and services, and have the infrastructure skills to deploy and maintain it. Organizations that need vendor-operated hosting, configured firewall rules or a finished phone system should look elsewhere.

Pros and cons

Pros

• No software charge, including commercial use: the GPL-3 license permits free use, while self-hosting leaves teams in control of deployment.
• Broad communications foundation: voice, video, messaging, presence, conferences, voicemail and call-center use cases can be built on the platform.
• Multiple integration paths: WebRTC, REST, WebSockets, Webhooks and OpenAPI descriptions support custom clients and service connections.
• Deployment choice: bare metal, virtual machines and containers let teams fit Wazo into different infrastructure setups.

Cons

• Operational work falls to the adopter: installation is Debian- and Ansible-based, and the security guide leaves firewall configuration to the deploying team.
• Support is community-based: help is through Mattermost, a forum and JIRA rather than a described vendor support plan.
• Some use cases are beta: the SIP Router and Session Border Controller applications carry that status, a concern for production-critical deployments.
• Building a complete solution takes engineering: Wazo is a developer platform, not a finished communications application.

Alternatives

For a different approach to communications software, consider Avaya Aura Private Cloud, which uses pay-per-user pricing and has no stated limit on user scalability; pricing details come through Avaya. Asterisk is another free, open-source, self-hosted option, licensed under GPLv2. Teams comparing broader open-source telephony stacks can also consider FreeSWITCH, which is free to download, modify and run in production under MPL 2.0 with community support.

For visual call-flow automation, Twilio Studio offers a free tier with 1,000 flow executions per month and a pay-as-you-go plan. Voicent provides a free allowance of 100 minutes or texts and a Starter plan at $179 a month, billed monthly, with 6,500 minutes or texts per month and unlimited campaigns. These plans may suit readers comparing usage-based or campaign-focused options.

Telnyx Text-to-Speech API is a focused API alternative with a free pay-as-you-go plan, no monthly minimum and automatic tier discounts. Telnyx TeXML combines TeXML calls with SIP trunking on published pay-as-you-go rates and requires no contract. For another API and web option, SIP.IO has a free trial tier with a test phone number and access to call flows, queues and contact-center features.

Readers comparing categories can browse Interactive Voice Response Software and Business Phone Systems.

Verdict

Choose Wazo Platform if your team wants a free, commercially usable foundation for building and operating its own communications services, and has the engineering capacity to manage the stack. Its APIs and flexible deployment options are the central advantages. Look elsewhere if you need managed infrastructure, vendor-led support or a ready-made phone system.