Built on Open Source
rtcStats grew out of the WebRTC open-source community. The core libraries that power our platform are MIT-licensed and available on GitHub - because we believe WebRTC observability should be accessible to every developer, not locked behind a black box.
We maintain open-source tools for collecting, transporting, and analyzing WebRTC statistics. The rtcStats cloud platform builds on top of these foundations with additional analysis, AI enrichment, dashboards, and team collaboration features.
Our Open-Source Projects
Everything public under the rtcstats GitHub organization is MIT-licensed. The main repository is our rtcstats monorepo:
rtcstats monorepo
rtcstats-js
Client-side SDK that collects WebRTC performance metrics from your application and sends them to rtcstats-server for analysis.
rtcstats-server
Server endpoint that receives collected stats and persists them to cloud storage and PostgreSQL for downstream processing.
rtcstats-features
Analysis engine that processes raw WebRTC dumps and extracts key performance indicators and important insights.
Why Open Source
Transparency
WebRTC monitoring and debugging tools run inside your infrastructure and touch sensitive data. You should be able to read every line of code that collects, transports, and processes your stats.
Community roots
WebRTC itself is open source. The developers who build on it expect their tooling to be auditable, extensible, and free from lock-in. We honor that expectation.
Better software
Public code invites scrutiny. Bugs get found faster, edge-cases get reported by real users, and contributions from the community make the tools better for everyone.
No vendor lock-in
You can self-host the collection pipeline, inspect every data transformation, and switch to your own backend at any time. The rtcStats cloud service earns your business on merit, not on lock-in.
Standing on the Shoulders of Giants
rtcStats wouldn't exist without the open-source projects that power the modern web and the WebRTC ecosystem.
Get Involved
Star a repo, open an issue, submit a PR, or just use the tools and tell us what you think. The WebRTC community is what drives us forward.