Learn what Wazo Platform offers as an open source unified communications and PBX system, its architecture, pricing, and use cases.
Wazo Platform is an open source unified communications and PBX system for building programmable IP telephony infrastructure. Rather than functioning as a closed, proprietary phone system, Wazo is designed API-first, giving developers REST APIs, WebRTC, and webhooks to integrate calling, messaging, and video into their own applications and workflows.
The project traces its roots back to XiVO, an open source telephony system started in France in 2005, which later merged with Avencall before its team relaunched as Wazo in November 2016 out of Quebec City, Canada, following the shutdown of Proformatique Inc.
Wazo is built on the Asterisk PBX engine combined with Kamailio and RTPEngine, and its core distinctive components are released under the GPLv3 license, making the platform free to self-host, inspect, and modify.
Wazo delivers class 5 telephony features including audio and video calling, voicemail, presence, and mobility for remote or softphone users, comparable to what a carrier-grade phone system provides.
Team chat and conferencing tools support internal collaboration alongside traditional voice calling within the same platform.
Call center functionality includes queues and routing logic suitable for support and sales teams handling inbound call volume.
An API-first architecture exposes REST APIs, WebRTC, WebSockets, and webhooks so developers can build custom integrations, embed calling into other software, or automate communications workflows.
Flexible deployment supports bare metal servers, virtual machines, or containers, giving organizations control over where and how the platform runs.
A related commercial offering, Wazo.io, provides a white-label version of the platform aimed at managed service providers and carriers who want to resell hosted UC services under their own brand.
The core Wazo Platform is free and open source under the GPLv3 license, so there is no license fee to self-host and run the system; costs come from your own infrastructure and any internal engineering time needed to deploy and maintain it.
Organizations that want commercial support, managed hosting, or a white-label multi-tenant offering can use the Wazo.io commercial product, which is aimed at MSPs and carriers and is typically priced per deployment or per seat through direct sales rather than published self-serve pricing.
Because Wazo is infrastructure software rather than a typical SaaS product, total cost of ownership depends heavily on deployment scale, hosting choices, and whether an organization opts for community support or a paid support contract.
The core Wazo Platform is free and open source under the GPLv3 license. Commercial hosting, support, and white-label offerings through Wazo.io are separately priced.
Wazo is built primarily on the Asterisk PBX engine, combined with components like Kamailio and RTPEngine for call routing and media handling.
Wazo is used by developers building custom communications products, telecom-savvy organizations wanting to avoid vendor lock-in, and managed service providers reselling hosted UC services.
Wazo originated from the XiVO open source telephony project started in France in 2005 and was relaunched as Wazo in November 2016 by a team in Quebec City, Canada.
Yes, Wazo can be deployed on bare metal servers, virtual machines, or containers, and organizations are free to self-host the open source platform.
Yes, Wazo supports audio and video calling, team chat, and conferencing alongside its core telephony features.
The open source project at wazo-platform.org is the free, self-hostable core, while Wazo.io is a commercial, white-label version aimed at MSPs and carriers who want hosted, brandable UC services.