Can I run rtcstats.com locally?
Understand what parts of rtcStats can be self-hosted and what requires the SaaS platform.
This is one of the most common questions we get, and the answer is: partially, yes.
What you can run locally
The rtcStats ecosystem has two fully open-source components that you can run on your own infrastructure:
- rtcstats-js - the client-side SDK that collects WebRTC metrics from the browser. This runs entirely in the user's browser as part of your application
- rtcstats-server - the mediation server that receives data from rtcstats.js, stores it, anonymizes sensitive information, and extracts features into an SQL database
Together, these give you full data collection, storage, and basic feature extraction - all within your own environment. You own the data, you control the privacy, and you can query the database for BI and monitoring purposes.
What requires rtcstats.com
The following capabilities are only available on the rtcstats.com SaaS platform:
- Visualization engine - the interactive dashboard with themed charts across Overview, Connections, Streams, Devices, and Logs tabs
- Observations - our rules engine that automatically detects issues and flags interesting behaviors
- Deductions - the root cause analysis layer built on top of Observations
- Experience Score and other quality scores
- AI enrichment - AI-generated summaries and analysis of sessions
- Collaboration features - commenting, public sharing, multi-user accounts
These features are the result of years of WebRTC expertise baked into proprietary algorithms that run on our servers.
So what does this mean in practice?
You can absolutely collect and store all your WebRTC metrics locally using our open-source tools. Many of our users do exactly that. When you need to troubleshoot a specific session, you upload its file to rtcstats.com for the deep analysis, visualization, and AI-powered insights. To make sure we keep the privacy of your users, rtcstats-server itself strips out all PII related information before uploading anything to rtcstats.com.
Think of it this way:
- Open source = your data collection and storage backbone
- rtcstats.com = your analysis and troubleshooting powerhouse
Can I get the analysis engine on-premise?
We currently don't offer an on-premise version of the rtcstats.com analysis engine, though we do have ways to offer a private instance of the service and/or the database itself. If this is a requirement for your organization, contact us to discuss your needs - we'd love to understand your use case and work out a suitable solution for you.
See also
- rtcStats architecture - how the three layers work together
- Can rtcStats be used in closed environments?
- Data privacy and compliance
Was this page helpful?