lynckia/licode

Open Source Communication Provider based on WebRTC and Cloud technologies

View on GitHub ↗Jump to charts ↓

lynckia/licode has 3k+ stars and 950+ forks on GitHub, is written in C++, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on November 28th, 2012
Open Issues & Pull Requests: 313 (+0)
GitHub issues: Enabled
Number of forks: 997
Total Stargazers: 3,133 (+0)
Total Subscribers: 224 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 18.8 days
90th percentile: 37.5 days
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 415 days
Stale 30+ days: 11
Stale 90+ days: 7

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Licode is an open source communication platform that enables real-time audio, video, and data transmission using WebRTC technology. The project provides a server-side infrastructure for building communication applications, handling the complexity of peer-to-peer connections, media processing, and cloud deployment that developers would otherwise need to implement themselves.

The platform solves the problem of deploying scalable WebRTC applications by providing a complete backend system. Rather than building communication features from scratch, developers can leverage Licode's existing server components to manage signaling, media routing, and connection establishment. The architecture is designed around cloud technologies, allowing applications to scale across multiple servers and handle numerous concurrent connections.

Licode suits projects requiring a self-hosted communication solution where developers want control over their infrastructure and data. It is appropriate for teams building custom communication applications who prefer an open source backend over proprietary services. The project is particularly relevant for organizations that need to deploy on their own servers or integrate communication capabilities into existing systems.

The project shows active maintenance with regular updates to its codebase. Development activity demonstrates ongoing refinement of core functionality and responsiveness to issues raised by users. The team continues to address technical debt and improve the stability of the platform's media handling and connection management systems.