Cloud IVR vs Wazo Platform
Cloud IVR
ivr.roWazo Platform
wazo-platform.orgSide by side
| Figure | Cloud IVR | Wazo Platform |
|---|---|---|
| Price from | €8.33/mo | Free |
| Free plan | — | Yes |
| Free trial | Yes | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | — | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 3 | 1 |
| Spec score · Interactive Voice Response Software | 8.0 (#6) | 8.2 (#4) |
| Call routing | Users can configure departments and redirect incoming calls. | custom |
| Purpose | Cloud IVR is an interactive voice response service that handles caller voice or keypad input, routes calls, and can collect voice messages. | Wazo Platform is an open-source project for building carrier-grade programmable IP communication infrastructures. |
| Support | The terms list [email protected] for technical support requests. | Wazo Platform is community supported through Mattermost, its forum, and JIRA bug tracking. |
Plans
In their own words
Cloud IVR
Cloud IVR is a cloud interactive voice response service for incoming calls. Callers can respond by voice or keypad; configured departments can receive routed calls, and the system can collect voice messages. Setup takes place in a web interface without hardware devices, with a visual flow builder, multilingual interface, and reports on incoming calls. Voice prompts are generated from text, so advance recording is unnecessary, and message transcripts are sent by email. The Starter plan includes reporting, automatic voice generation, and work schedules for €99.99 a year. Pro costs €499.99 a year and adds API integration, advanced diagrams, and call-out sessions. Enterprise is billed on demand with custom voices and API integration. A free trial permits testing only from the user’s own phone number. Subscriptions renew automatically unless canceled; contracts can receive refunds within 14 days.
Wazo Platform
Wazo Platform is a free, open-source stack of telecom microservices for building programmable voice, video, messaging, and presence services. Its capabilities include audio and video calls, chat, call centers, conferences, voicemail, custom call routing, and an auto attendant. Interfaces include WebRTC, REST APIs, WebSockets, and Webhooks, described as mobile- and web-friendly. The microservices are developed in Python, and APIs are described through OpenAPI specifications. Asterisk, RTPEngine, and Kamailio make up the telecom engine; RabbitMQ, NGINX, and PostgreSQL support the technical core. Wazo can be deployed on bare metal, virtual machines, or 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. The GPL-3 license allows free use, including commercial use. APIs can integrate billing and services such as speech-to-text, AI, or sentiment analysis. Community support is available through Mattermost, a forum, and JIRA.