Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Li
Self-host LiveKit
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A WebRTC media server (selective forwarding unit) for real-time audio, video and data, where people, devices and AI agents join the same room as participants. It is a server and SDK platform, not a finished meeting app: you build the interface with its web, mobile, desktop, embedded and server SDKs, and the separate LiveKit Meet example shows one. Features listed by the project include simulcast, speaker detection, end-to-end encryption, SVC codecs, webhooks, SIP telephony, JWT authentication and an embedded TURN server, shipped as a single binary or Docker image.
Pick LiveKit when you are building real-time audio or video into your own application or voice agent and want to run the media server yourself. It is a WebRTC selective forwarding unit, not a meeting app: people, devices and AI agents join the same room, and you build the interface with the web, mobile, desktop, embedded and server SDKs. The README lists simulcast, speaker detection, selective subscription, end-to-end encryption, SVC codecs, webhooks, SIP telephony and JWT authentication, as a single binary, Docker or Kubernetes, and the deployment docs add an embedded TURN server. It is Apache-2.0 Go built on Pion. Our snippet follows the production configuration from the LiveKit self-hosting docs, with the image pinned to `livekit/livekit-server:v1.13.11` (released 2026-10-25) and host networking as the docs recommend for Docker; the API key and secret come from the image's `generate-keys` command instead of the `--dev` mode's `devkey` and `secret`, and Redis, TURN and TLS are left out. The docs publish no RAM minimum and say scalability is bound by CPU and bandwidth, so our 512 MB floor is an estimate; the 20 MB we measured was with no clients connected. In the catalog, Jitsi Meet is a ready-made browser meeting, MiroTalk P2P is a peer-to-peer meeting with no media server, Nextcloud Talk lives inside Nextcloud, Screego only shares screens and OpenMeetings is a classroom-style server; LiveKit is the one you build on with SDKs, so it fits only if you are writing a client.
What you need
Any VPS with at least 512 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
About an afternoon — budget time for troubleshooting
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# LiveKit server — adapted from the production config in the LiveKit self-hosting docs (livekit.yaml, host networking), image pinned to livekit/livekit-server:v1.13.11# Changed from upstream: API key and secret from the image's generate-keys command instead of --dev's devkey/secret, no Redis (single node), no TURN and no TLS, which need a domain you ownmkdir livekit && cd livekitdocker run --rm livekit/livekit-server:v1.13.11 generate-keys > keys.txtecho "LIVEKIT_API_KEY=$(grep 'API Key' keys.txt | awk '{print $NF}')" > .envecho "LIVEKIT_API_SECRET=$(grep 'API Secret' keys.txt | awk '{print $NF}')" >> .env. ./.envcat > livekit.yaml <<EOFport: 7880log_level: infortc: tcp_port: 7881 port_range_start: 50000 port_range_end: 60000 use_external_ip: truekeys: ${LIVEKIT_API_KEY}: ${LIVEKIT_API_SECRET}EOFcat > docker-compose.yml <<'EOF'services: livekit: image: livekit/livekit-server:v1.13.11 command: --config /etc/livekit.yaml restart: unless-stopped network_mode: host volumes: - ./livekit.yaml:/etc/livekit.yaml:roEOFdocker compose up -dtimeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:7880/; do sleep 3; done'# → http://SERVER_IP:7880 (a WebRTC server with no web page of its own: connect SDK clients with LIVEKIT_API_KEY and LIVEKIT_API_SECRET from .env, over wss:// behind a TLS proxy for anything but localhost; open 7881/tcp and 50000-60000/udp)
LiveKit's README, deployment docs and sample configuration flag these before you rely on it:
non-negotiableThere is no web page to use. The server answers HTTP on port 7880 for clients and the API, and the README's livekit-server --dev mode and the example frontends (LiveKit Meet) are separate. Connecting needs an access token signed with the API key and secret, which our snippet generates into .env; keep the secret server-side.
non-negotiableThe deployment docs say a secure deployment needs a domain and a certificate signed by a trusted authority (self-signed certificates do not work) with HTTPS termination in a load balancer or reverse proxy, and that SDK clients connect over wss://. Our snippet has neither, so it is for local testing or a setup where you add the proxy.
non-negotiablePorts have to be reachable from clients: our config uses 7880/tcp, 7881/tcp and 50000-60000/udp, and the docs' firewall list also names 443, 80, 3478/udp for TURN and ingress ports. With use_external_ip: true LiveKit uses STUN to find the host's public IP, per the sample config, so the server needs outbound access. Host networking means Docker does not map or isolate these ports.
non-negotiableTURN is off. The docs say an embedded TURN server, optionally with TLS on a separate domain and certificate, improves connectivity for clients behind corporate firewalls that block UDP and non-secure TCP.
non-negotiableNo Redis is configured, so this is a single node; the sample config says setting redis makes LiveKit operate in a fully distributed way, and the docs say each room must fit on one node. Recording and stream import need Egress and Ingress, and SIP needs the SIP server; the docs list these as separate services and our snippet runs only the media server.
non-negotiableOur run only checks that port 7880 answers HTTP; we did not connect a client or publish media, so the idle 20 MB RAM says nothing about load.
LiveKit used 20 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 512 MB.
Is the LiveKit install snippet verified?
The LiveKit install snippet is marked verified on Ubuntu 26.04 (Nov 2026).