A 100% open-source, carrier-grade observability framework for real-time SIP, VoIP, and RTC packet capture, monitoring, and troubleshooting.
HOMER is a 100% open-source observability framework for real-time monitoring and troubleshooting of SIP, VoIP, and WebRTC communications. It captures packets, events, logs, and statistics, transforming them into searchable and correlatable data to help operators diagnose issues and ensure service quality. It solves the problem of managing and analyzing massive volumes of real-time communication data in scalable, carrier-grade environments.
Voice network operators, VoIP service providers, telecommunications carriers, and enterprises running large-scale real-time communication services who need deep visibility into signaling and media performance.
Developers and operators choose HOMER because it's a fully open-source, battle-tested solution that handles insane data volumes, supports modern observability standards, and offers end-to-end correlation without vendor lock-in. Its unique selling point is being a carrier-grade framework that seamlessly bridges traditional VoIP monitoring with contemporary logs, metrics, and traces tooling.
HOMER - 100% Open-Source SIP, VoIP, RTC Packet Capture & Monitoring
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports distributed capture servers and agents across any OS/platform, making it suitable for large enterprises and operators with massive data volumes, as highlighted in its carrier-grade deployment capabilities.
Transforms VoIP data into standard logs, metrics, and traces, seamlessly integrating with tools like Grafana and qryn for visualization, aligning with industry standards for comprehensive analysis.
Captures and processes SIP, RTP/RTCP reports, RTC events, and custom protocols, providing extensive coverage for real-time communications troubleshooting and monitoring.
Retains full backwards compatibility with HEPv3 while adopting modern observability standards, ensuring smooth transitions for existing users without losing features.
Requires configuring multiple components like heplify-server and homer-app, along with external databases and visualization tools, which can be time-consuming and challenging for non-experts.
As a headless observability solution, HOMER 10 lacks a built-in interface, necessitating additional setup with Grafana or similar for data visualization, adding to the implementation overhead.
Relies on the HEP/EEP encapsulation protocol, so data sources must support or be adapted to this format, potentially limiting integration with non-compliant systems and requiring extra configuration.