versatica/mediasoup

Cutting Edge WebRTC Video Conferencing

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 8th, 2026
Created on December 12th, 2014
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 1,250
Total Stargazers: 7,356 (+0)
Total Subscribers: 218 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 27.9 days
90th percentile: 5.3 days
Tracked items: 151

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 23% of open issues come from outside the core team — the tracker reads mainly as internal planning. Only 6% of issues opened in the past year have been closed. Three people close 95% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 22
New in 7 days: 5
Closed in 7 days: 0
Avg open age: 447 days
Stale 30+ days: 14
Stale 90+ days: 9

Recent activity

Opened in 7 days: 4
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (73)
  • feature (32)
  • enhancement (27)
  • rust (3)
  • CI (1)
  • dependencies (1)

Detailed Description

mediasoup is a WebRTC Selective Forwarding Unit (SFU) server that handles real-time media routing for video conferencing and streaming applications.

The tool solves the problem of building scalable, low-latency video communication systems by providing a minimal media layer that routes WebRTC streams between participants without mandating any particular signaling protocol. It operates as a Node.js module or Rust crate on the server side, with a C++ media worker subprocess handling the actual stream processing. This architecture separates signaling concerns from media handling, allowing developers to implement custom signaling logic while relying on mediasoup for the complex media operations like ICE negotiation, DTLS encryption, RTP/RTCP handling, and stream forwarding.

The tool suits projects requiring group video chat, one-to-many broadcasting, or RTP streaming where developers need fine-grained control over media routing and signaling. Its super low-level API means you have flexibility in how you structure your application, but it also means you are responsible for implementing signaling, room management, and other application logic yourself. This approach differs from higher-level platforms that bundle signaling and media handling together. The project supports both WebRTC and plain RTP input and output, handles multiple streams over a single transport, includes simulcast and SVC support, and provides congestion control with bandwidth estimation and spatial/temporal layer distribution.

Development activity shows consistent engagement with the project. The codebase receives regular updates and maintenance across its core components. The project maintains active community channels including a support forum and social media presence. Documentation and examples are actively maintained, including a live demo application that showcases the platform's capabilities. The maintainers respond to issues and pull requests, indicating ongoing stewardship of the project.