Callr vs Wazo Platform
Callr
callr.com
Wazo Platform
wazo-platform.orgSide by side
| Figure | Callr | Wazo Platform |
|---|---|---|
| Price from | €599/mo | Free |
| Free plan | — | Yes |
| Free trial | Yes | — |
| Open source | — | — |
| Web | Yes | Yes |
| Linux | — | Yes |
| iOS | Yes | Yes |
| Android | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 2 | 1 |
| Spec score · Voice APIs | 9.0 (#1) | 8.2 (#7) |
| Audience | Callr describes its platform as infrastructure for businesses embedding voice and messaging in products and for teams using calls in customer experience, sales, or marketing. | The site describes Wazo as a platform for developers to build solutions that fit business and technical requirements. |
| Founded | 2011 | 2016 |
| Integrations | Callr lists native connectors for Salesforce, HubSpot, Google Analytics, and Google Ads, plus a REST API and webhooks. | The maker says APIs can integrate third-party services, including billing capabilities, speech-to-text, AI, and sentiment analysis. |
| Security | Callr states that HTTPS, SIP TLS and SRTP encryption are included across plans. | The security guide says Wazo includes preconfigured fail2ban jails, but does not configure firewall rules and recommends configuring them. |
| Support | Callr describes 24/7 support as part of its service and lists premium customer support for Enterprise. | Wazo Platform is community supported through Mattermost, its forum, and JIRA bug tracking. |
Plans
In their own words
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.