jitsi/jitsi-meet

Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 16 minutes ago
Added to GitGenius on September 1st, 2026
Created on December 16th, 2013
Open Issues & Pull Requests: 142 (+0)
GitHub issues: Enabled
Number of forks: 8,022
Total Stargazers: 29,883 (+0)
Total Subscribers: 522 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 53
New in 7 days: 5
Closed in 7 days: 2
Avg open age: 1,027 days
Stale 30+ days: 36
Stale 90+ days: 25

Recent activity

Opened in 7 days: 5
Closed in 7 days: 2
Comments in 7 days: 16
Events in 7 days: 40

Top labels

  • stale (455)
  • feature-request (268)
  • confirmed (38)
  • wontfix (30)
  • ui/ux (10)
  • web (10)
  • mobile (9)
  • accessibility (6)

Detailed Description

Jitsi Meet is a WebRTC-based video conferencing platform that you can deploy as a standalone application or embed within your own web application.

The project addresses the need for self-hosted, privacy-respecting video communication by providing a complete conferencing solution built on open standards. It uses a Selective Forwarding Unit architecture to handle media routing, allowing it to scale across multiple participants while maintaining end-to-end encryption capabilities. The platform handles signaling, media transport, and user interface through a unified codebase, eliminating dependency on third-party conferencing services.

Jitsi Meet suits organizations that require control over their infrastructure, cannot rely on cloud-hosted services, or need to embed conferencing directly into existing applications. It works well for deployments ranging from small team meetings to larger conference scenarios. The project provides both a ready-to-use web interface and programmatic APIs for integration, making it flexible for different deployment models. Teams evaluating adoption should understand that self-hosting requires infrastructure management and operational overhead compared to managed services, though this trade-off provides data sovereignty and customization control.

The project maintains active development across its core components, with regular updates to both the frontend TypeScript codebase and backend systems. Contributors engage consistently with issues and pull requests, indicating responsive maintenance. The development activity shows sustained effort in addressing bugs, implementing feature requests, and adapting to changes in WebRTC standards and browser APIs. The project's architecture supports modular contributions, with clear separation between the client application, signaling server, and media components, allowing focused work on specific areas.