Self-host LiveKit with Levelrail
Open-source WebRTC server for real-time audio, video and data, with an API for rooms and tokens. The install form carries livekit.yaml as an editable file and generates the API key and secret.
- Authorlivekit
- LicenceApache-2.0
- Memory256 MiB
- Services1
How to self-host LiveKit
-
Pull the images
One image is pulled on your server.
Show images
livekit/livekit-server:v1.13.11
-
Create the app
One service starts in a single Compose app, on ports 7880, 7881.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Use the generated API key and secret with a LiveKit SDK to mint tokens. Media flows over TCP port 7881 here; UDP media ports are not published by this template.
LiveKit requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 7880, 7881
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then LiveKit. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the LiveKit docs page.
Deploy LiveKit your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy LiveKit from the CLI
levelrail-cli templates install livekit --name my-livekit Deploy LiveKit with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/livekit/install \
-d '{
"name": "my-livekit"
}' LiveKit configuration
LiveKit services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| livekit | livekit/livekit-server:v1.13.11 | 7880, 7881 | none |
LiveKit environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 7880, 7881
- Volumes
- none
LiveKit FAQ
How much memory does LiveKit need?
The catalog lists about 256 MiB of memory for LiveKit.
Does LiveKit run on arm64?
For LiveKit, arm64 support is not confirmed; amd64 is unknown.
What licence is LiveKit under?
LiveKit is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does LiveKit need configuration before it starts?
No. The template fills in its own defaults.
Which ports does LiveKit use?
LiveKit listens on ports 7880 and 7881 inside the stack.
Can I deploy LiveKit on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id livekit for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image livekit/livekit-server:v1.13.11 is what you deploy there.