LiveKit CLI

LiveKit CLI is a command-line tool for managing, testing, and interacting with LiveKit, an open-source real-time audio and video infrastructure platform.

  • Development
  • Infrastructure
  • Tools & Utilities
LiveKit CLI is a command-line tool for managing, testing, and interacting with LiveKit, an open-source real-time audio and video infrastructure platform. It supports room management, access-token generation, egress control, and participant load simulation, making it useful for developers and operators deploying or validating LiveKit-based services.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?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). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

71/100 Good

Maintained
100last commit 2 days ago
Popular
52385 GitHub stars
Easy to install
150 install platforms, install notes
Light to run
10030 MB minimum RAM
GitHub stars
385
Open issues
130
Last commit
2026-11-18
Latest release
v2.20.1
Activity
steady

Checked 2 days ago - source: GitHub (livekit/livekit-cli)

Resources & Compatibility

Minimum requirements: 30 MB RAM.

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

First-install notes

  • Create your API key and secret first Put your own API key and secret in the config before starting LiveKit. If these are missing or wrong, apps won't be able to join rooms or create sessions. source
  • Open the live audio/video port range Allow the configured RTC (realtime media) port range, like 50000-60000, in your firewall. If these ports are blocked, participants in different locations may fail to connect or lose audio and video. source
  • Keep the config file secret Your config can contain API keys, TURN (a helper media server) certificate files, and webhook settings, so don't share it or commit it to a public repo. If someone gets these secrets, they can create or join rooms, impersonate your server, or trigger webhook actions. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does LiveKit CLI help set up a new application?

It can bootstrap applications from template repositories. It uses your project credentials to set required environment variables and other configuration automatically.

What credential configuration must be correct before rooms or sessions can be created?

The API key and secret need to be in the LiveKit config before starting it. If they are missing or wrong, apps cannot join rooms or create sessions.

Which firewall ports should be opened for LiveKit media traffic?

Open the configured RTC port range, such as 50000-60000. If those ports are blocked, participants in different locations may fail to connect or lose audio and video.

Should the LiveKit config file be shared or committed?

Keep the config file secret because it can contain API keys, TURN certificate files, and webhook settings. Sharing it can let others create or join rooms, impersonate the server, or trigger webhook actions.

Answers sourced from github.com, github.com, github.com

Community

Collected 48 days ago - public community threads