Plum Fuse vs Wazo Platform
Plum Fuse
plumvoice.comWazo Platform
wazo-platform.orgSide by side
| Figure | Plum Fuse | Wazo Platform |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | — | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Interactive Voice Response Software | 7.0 (#16) | 8.2 (#4) |
| Founded | 2002 | 2016 |
Plans
In their own words
Plum Fuse
Plum Fuse is a visual, low-code flow builder for production-grade IVR applications, available through web and API with cloud deployment. It targets CX leaders and non-technical teams without VoiceXML expertise, while producing full VoiceXML 2.1 output. More than 37 production-ready templates and NLU-powered conversational AI are included. API connections can link CRM, billing, scheduling, and internal systems in real time. Integrations include Google Dialogflow, Amazon DynamoDB, and Amazon S3, with S3 used only for call recordings. PCI-compliant DTMF masking keeps payment card digits out of agent views and call recordings. The Fuse API handles outbound and bulk call queues, status, cancellation, and call-log retrieval. Recorded audio remains temporarily in memory and is deleted when calls end; it is not stored. Session logs remain for one rolling year, while detailed call logs remain five days. Plum Voice states that it holds PCI DSS Level 1, SOC 2 Type II, Cyber Essentials, and ISO 27001 certifications, with a 99.9% uptime SLA. Pricing is on request.
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.