Leneex - Hosting Provider
LiveKit

Deploy LiveKit on a VPS in One Click

Communication & chatAI & LLM tools

Self-hosted WebRTC server for real-time video calls, live streaming, and voice AI agents on your own infrastructure.

Deploy on a VPSAll apps
  • Ready in ~5 min
  • Free installation
  • We handle the setup
At a glance
Version
Latest (1.x)
Operating system
Ubuntu Server 24.04 LTS
Minimum RAM
2 GB
License
Apache 2.0
Addressing
IPv4, IPv6
GitHub
21,000
Deployment~5 min
Open source & self-hosted
VPS plans

Choose a VPS plan for LiveKit

Blazing-fast NVMe drives and powerful processors. Take a ready-made plan or build the configuration yourself.
Minex
Perfect for personal projects and small websites.
€3.20/mo
Save €0.80 per month
  • 1 vCPU core
  • 1 GB DDR5 RAM
  • 20 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 1 TB traffic
Basex
A great balance of power and affordable price.
€4.80/mo
Save €1.20 per month
  • 2 vCPU cores
  • 2 GB DDR5 RAM
  • 40 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 2 TB traffic
Most popular
Corex
For growing applications and businesses.
€7.20/mo
Save €1.80 per month
  • 4 vCPU cores
  • 4 GB DDR5 RAM
  • 50 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Midex
Resources for high-load projects.
€9.60/mo
Save €2.40 per month
  • 4 vCPU cores
  • 6 GB DDR5 RAM
  • 60 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Proex
Maximum power and scalability.
€12.00/mo
Save €3.00 per month
  • 6 vCPU cores
  • 8 GB DDR5 RAM
  • 70 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Scalex
Resources for scaling.
€16.00/mo
Save €4.00 per month
  • 6 vCPU cores
  • 10 GB DDR5 RAM
  • 150 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Maxex
A large reserve of power.
€44.00/mo
Save €11.00 per month
  • 8 vCPU cores
  • 16 GB DDR5 RAM
  • 200 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Apex
The top configuration.
€79.99/mo
Save €20.00 per month
  • 16 vCPU cores
  • 32 GB DDR5 RAM
  • 400 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic

What you can do with LiveKit

LiveKit is an open-source platform for building real-time video and audio apps using WebRTC, running as a WebRTC SFU (Selective Forwarding Unit) written in Go that routes media between participants without transcoding every stream. It's built for developers and product teams shipping video conferencing apps, live-streaming platforms, or voice AI agents rather than for end users looking for a ready-made calling app — LiveKit is infrastructure you build on top of, not a Zoom replacement out of the box.

What separates it from consumer video APIs is that authentication, room logic, recording (Egress), and external stream ingestion (Ingress) are all exposed as code you control, with client SDKs covering JavaScript, Swift, Android, Flutter, and Unity. Choosing LiveKit self hosted over LiveKit Cloud makes sense once media privacy, custom scaling, or per-minute billing become a concern — hosting for LiveKit on your own VPS means calls never route through a third party, and you pay for compute instead of metered participant-minutes.

Get started
The applications screen of the control panel with one-click install

LiveKit features

A server surrounded by app icons — applications running on a VPS

Beyond basic media routing, LiveKit ships a full set of services around the SFU — most of them run as separate processes you deploy alongside the main server, whether on bare metal or LiveKit VPS Docker containers.

01

SFU media routing

Forwards video, audio, and data tracks between participants with sub-second latency, without decoding streams in the middle.

02

Agents framework

A Go/Python runtime for building voice AI agents that pipe audio through STT, an LLM, and TTS in real time.

03

Egress service

Records rooms or individual tracks to file, or streams them out to RTMP/HLS endpoints.

04

Ingress service

Pulls external RTMP or WHIP sources into a LiveKit room, useful for bridging OBS or camera feeds.

05

End-to-end encryption

Encrypts media at the sender so it can't be read even by the server relaying it.

06

SIP integration

Connects rooms to regular phone lines for telephony use cases like call-center or IVR bots.

07

Webhooks

Pushes room, participant, and track events to your backend for custom automation logic.

08

Multi-language SDKs

Server SDKs for Node.js, Go, Ruby, Java/Kotlin, and Python for issuing tokens and managing rooms.

Requirements

Which server to run it on

Minimum requirements for LiveKit and the configuration worth starting with.
Minimum
  • CPU2 vCPU
  • Minimum RAM2 GB
  • Disk20 GB
Recommended
VPS Basex
  • CPU2 vCPU
  • Minimum RAM2 GB
  • Disk40 GB

Installation is free — you only pay for the server

Getting started

How to deploy LiveKit

Three steps and the app is running on your server.
Step 1
Choose a server

Pick a plan with headroom above LiveKit's minimum requirements, since SFU media routing is CPU-bound and scales with concurrent participants, not just room count.

Step 2
Pick the app

Select LiveKit in the marketplace and the platform handles the full LiveKit installation — pulling the server image, generating a config file, and opening the required WebRTC ports automatically, so you can install LiveKit on VPS without touching Docker manually.

Step 3
Get your credentials

Instead of a web login, you'll receive an API key and secret pair used to sign JWT access tokens for connecting clients, agents, or the CLI to your server.

Official websitelivekit.io
GitHub repositorygithub.com
Documentationdocs.livekit.io
Why us

Why Host LiveKit on Leneex

Speed, protection and support you can rely on — on every plan, with no hidden limits.
Deployment speed
An SFU server is useless until participants can actually connect — fast provisioning means your livekit.yaml, ports, and keys are ready in minutes, not hours of manual Docker setup.
Free installation
Getting LiveKit's server, Redis dependency, and port configuration right by hand is fiddly; a €0 one-click deploy removes that setup cost entirely, letting you go straight to building on the SDKs.
DDoS protection
A LiveKit server exposes public signaling and RTC ports by design, since any participant's browser must reach it directly — that public surface is exactly what needs shielding from flood attacks.
Control and support
Tuning TURN, port ranges, or Redis for multi-node scaling requires real root access to the box, not a locked-down panel — and 24/7 engineers matter when your video infrastructure needs a live fix during a call.
99.9% uptime with SLA compensation
Every dropped connection during a live call or streaming session is visible to end users instantly — an SLA-backed uptime guarantee matters more for real-time media than for background services.
Flexible payment
Whether you're a solo developer prototyping an Agents pipeline or a company billing clients for a video product, paying by card, crypto, or invoice keeps your VPS for LiveKit outside your usage-based Cloud billing entirely.
What to choose

LiveKit: Self-Hosted vs Cloud — Which to Choose

LiveKit has an official managed offering — LiveKit Cloud, with Build (free), Ship, and Scale tiers, plus Enterprise.
LiveKit Cloud
Self-hosted on LeneexRecommended
Resources and limitsBuild tier includes 5,000 WebRTC minutes, 50 GB egress, and 1,000 AI Agent minutes per month, billed beyond thatDedicated CPU/RAM, capped only by server specs
Control and accessManaged via dashboard and CLI, SFU configuration abstracted awayFull root access, your own livekit.yaml, TURN, any SDK version
Feature limitsAdvanced features like observability and telephony are available at lower volumes even on the free tier, but HIPAA compliance and region pinning are reserved for higher plansFull stack available: SFU, Agents, Egress, Ingress, SIP, no caps
ScalingAutomatic across LiveKit's edge infrastructure, no Redis setup requiredVertical — upgrade the VPS plan; horizontal — add Redis and more nodes
CostMetered by agent-session minutes (~$0.01/min), WebRTC minutes (~$0.0004–0.0005/min), and bandwidth ($0.10–0.12/GB) beyond plan quotasFixed VPS price regardless of call volume
Who it fitsTeams that need instant global scale without managing infrastructureProjects with stable or high, predictable load that need control over media flow and data

Self-hosted LiveKit on a Leneex VPS pays off when load is steady and predictable — instead of metered minutes, you pay a flat server price. LiveKit Cloud makes more sense when instant global scale matters more than per-unit savings — either way, both run the same open-source server code, so migrating between them doesn't require rewriting your application.

Frequently Asked Questions about LiveKit on VPS

What people ask most about LiveKit and our servers.

  • It depends more on total video track bitrate than headcount — a small VPS comfortably handles a handful of active video publishers in one room, but audio-only rooms or voice agents scale much further on the same hardware.

  • The base deploy sets up the core SFU server and its signaling port; TURN and a domain-bound TLS certificate for production use are configured separately once you point a domain at the server.

  • Upgrading resources on the same server doesn't require reinstalling LiveKit, but active WebRTC connections are dropped during the resize and reconnect once the server is back online.

  • You control updates yourself, since it's your VPS — LiveKit ships frequent releases, and pinning a stable version in your config avoids surprise breaking changes mid-project.

  • Yes — back up your livekit.yaml and API key/secret pair, since a fresh server just needs the same config and keys to keep existing client tokens valid.

What's already configured

The one-click deploy in your marketplace template installs LiveKit in one click by pulling the livekit/livekit-server image and applying a base livekit.yaml config with signaling on port 7880, WebRTC TCP on 7881, and WebRTC UDP on 7882. Whether the template also bundles Redis (needed for multi-node scaling, Egress, and Ingress) or the LiveKit Meet example app for quick testing is — check your deploy summary or the config file for a redis.

Getting your access credentials

LiveKit has no web admin panel to log into — access is entirely token-based, through an API key and secret pair generated during setup (LiveKit's own tooling can produce these via the server's generate-keys command). You'll find this key/secret pair in your deploy summary or inside livekit.yaml under the keys: section — treat the secret like a password, since anyone holding it can mint valid room tokens.

First connection

With the key and secret in hand, the fastest way to confirm the server works is generating a test token with the LiveKit CLI (lk) and opening it in the LiveKit Meet example app — a public reference frontend, not something installed by default, where you paste a token to join a test room and confirm video and audio come through. For anything beyond a manual test, tokens are normally minted by your own backend using a server SDK (Node.js, Python, Go, and others are available) rather than typed in by hand each time.

Deploy LiveKit in about 5 minutes

Choose a server — we do the rest: install, configure and send you the credentials.

Choose a serverAll apps