Integrations with 3rd parties

rtcStats is built around the concept of smooth and simple adoption:

1. The rtcstats-js client SDK overrides the standard WebRTC JavaScript APIs, making integration transparent for most developers regardless of what framework or infrastructure you're using.
2. rtcstats-server is kept unopinionated and mostly generic about the infrastructure it uses, making it a suitable match across IaaS and on premise data centers

We've had experience integrating with quite a few 3rd party WebRTC frameworks and cloud platforms, so we created this section to explain how to get things running with each.

WebRTC Infrastructure

This is how to get rtcstats-js client SDK integrated with various WebRTC frameworks:

• Janus - Integrating rtcStats with the Janus WebRTC server
• Jitsi Meet - Add rtcstats-js to Jitsi Meet via the custom.js entry point
• LiveKit - Add rtcstats-js to a LiveKit app with a singleton wrapper and three insertion points
• React Native (react-native-webrtc) - Add rtcstats-js to a react-native-webrtc app by registering the WebRTC globals, then wrapping them via globalThis and connecting from your entry point
• mediasoup demo - Send mediasoup demo traffic to your own rtcstats-server in three steps
• Vonage Video - Add rtcstats-js to a Vonage Video React app (VERA) by wrapping globals before the SDK loads

IaaS

That's how to install and configure rtcstats-server in different IaaS environments:

• AWS App Runner - Deploy rtcstats-server on AWS App Runner in two stages
• DigitalOcean Apps Platform - Deploy rtcstats-server on DigitalOcean in two stages

NOTE: Can't find the tool you're using here? Let us know!