← Directory

LiveKit

An open source project that provides scalable, multi-user conferencing based on WebRTC.

  • Media Applications
  • Other
  • Productivity
  • Tools & Utilities
An open source project that provides scalable, multi-user conferencing based on WebRTC. It's designed to provide everything you need to build real-time video audio data capabilities in your applications.

Platform availability

Available on 2 of 6 install platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

75/100 Good

Maintained
100last commit 3 days ago
Popular
8721,307 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
404 GB minimum RAM, runs on ARM
How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today, links checked 11 days ago

GitHub stars
21,307
Open issues
191
Last commit
2026-10-06
Latest release
v1.13.8
License
Apache-2.0
Activity
steady

Checked 3 days ago - source: GitHub (livekit/livekit)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 10 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add key, ports, and network address In `config.yaml`, add an API key and secret under `keys`, set the main `port` (commonly 7880), reserve a real-time media (RTC) port range such as 50000-60000, and set `bind_addresses` to `0.0.0.0` (listen on all network interfaces) if other devices need access. Without the key and secret apps can't log in, and without the media range or correct network address audio/video connections may fail. source
  • Install the LiveKit server first On Linux, run `curl -sSL https://get.livekit.io | bash`; on Mac, run `brew install livekit`. If LiveKit isn't installed, there is no `livekit-server` program to start or configure. source
  • Start LiveKit with your config file Run `livekit-server --config config.yaml` after filling in your settings. This starts the LiveKit server and keeps it running, so rooms, webhooks, and app connections can actually work. source

Fetched 10 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What must I set in config.yaml before other devices can connect to self-hosted LiveKit?

Add an API key and secret under keys, set the main port, commonly 7880, reserve an RTC port range such as 50000-60000, and set bind_addresses to 0.0.0.0 if other devices need access. Without the key and secret apps can't log in, and without the media range or correct network address audio/video connections may fail.

Why is the livekit-server command missing on a new host?

Install the LiveKit server first. On Linux, use the installer script; on Mac, use Homebrew. If LiveKit isn't installed, there is no livekit-server program to start or configure.

Can LiveKit and another service on separate devices share port 80 for TLS?

No, you can't port-forward TCP 80 to two different devices. With default Let's Encrypt certificate renewal, renewal will fail for either the other service's certificate or the LiveKit certificates if they are on separate devices.

Can self-hosted LiveKit be deployed from Docker Compose to Kubernetes?

Yes, the deployment guide starts with a single Docker Compose stack. It also covers moving to a Kubernetes cluster serving thousands of concurrent users.

How can I plan capacity for self-hosted LiveKit using real production data?

The community thread collects production details from people running LiveKit, including workload types and peak concurrent sessions. It is useful for comparing real self-hosted setups and planning capacity.

Answers sourced from celloip.com, community.livekit.io, github.com, github.com, www.reddit.com

Community

Collected 4 days ago - public community threads