Skip to main content

LiveKit

LiveKit is available in the NetActuate Marketplace as a one-click, open-source appliance you can deploy into any NetActuate PoP. Open-source LiveKit WebRTC SFU: real-time audio, video and data rooms. It is grouped under the Media & Streaming category.

What It Does​

LiveKit is an open source, end to end WebRTC stack for building real time audio, video and data applications. This appliance packages the open source LiveKit server (Apache 2.0) as a turnkey single node instance on Ubuntu 24.04 LTS, with an embedded Redis for state, so you can stand up a self hosted Selective Forwarding Unit (SFU) in the NetActuate PoP nearest your participants.

What you get

  • The open source LiveKit server: rooms, participants, tracks, and the server APIs and SDKs (JavaScript, React, Swift, Android, Flutter, Go, Rust, Python and more)
  • Selective Forwarding Unit (SFU) media routing for scalable multi party audio and video
  • WebRTC over UDP with a single port mux, plus a TCP fallback for restrictive networks
  • An API key and secret, generated at deploy, that your application server uses to mint access tokens
  • Embedded Redis on the instance, so the single node is ready to grow into a multi node cluster later with no image change
  • systemd managed services that start on boot and restart on failure

Only single node, open source capabilities This is the open source LiveKit server running as one node. It does not include the distributed, multi region mesh, autoscaling or managed features of LiveKit Cloud. For a fully managed, globally distributed service, see LiveKit Cloud at livekit.io. You can build your own multi node cluster from several of these appliances sharing a Redis, which is a later phase story, not a launch claim.

Use cases

  • Video conferencing and virtual events
  • Live audio rooms and interactive streaming
  • Real time voice and video for AI agents and assistants
  • Telehealth, education and collaboration apps that need low latency media

Getting started After deploy, retrieve the generated API key and secret from your deployment, point your LiveKit application or SDK at wss://YOUR_HOST:7880 with a token signed by that key and secret, and start joining rooms. See the instructions tab for the exact steps and ports.

Upstream project: https://github.com/livekit/livekit (Apache 2.0). LiveKit is an independent open source community project; NetActuate packages the unmodified upstream server binary and is not affiliated with or endorsed by the LiveKit project.

Vendor and Project​

LiveKit is an open-source project, offered here under the Open Source listing with best-effort community support.

NetActuate supports the underlying infrastructure. Application-level support follows the listing SLA class (open-source, best effort).

Sizing​

vCPURAMDisk
Minimum24 GB20 GB
Recommended816 GB40 GB

No VPU (hardware acceleration) is required for this appliance. Choose a size at deploy based on your expected load.

Configuration Fields​

When you deploy, you provide these fields. They are written into the appliance at first boot.

FieldRequiredDefaultNotes
API KeyNogeneratedLiveKit API key your application server uses to mint access tokens. Generated automatically at deploy. Stored write-only in your account secret list
API SecretNogeneratedLiveKit API secret paired with the API key; keep it private. Generated automatically at deploy. Stored write-only in your account secret list
Public HostnameNononeOptional public DNS name clients use to reach this server for your own TLS or reverse proxy. Leave blank to use the node public IP.
Signal PortNo7880HTTP and WebSocket signalling port that clients connect to (ws).
WebRTC TCP PortNo7881Fallback TCP port for WebRTC media on restrictive networks (ICE over TCP).
WebRTC UDP Mux PortNo7882Primary UDP port for WebRTC media, using a single port mux for easy firewalling.

Using the Appliance​

Connect to your LiveKit server

  1. Get your API key and secret. Both are generated at deploy and delivered to your account secret store as mkt-<deploymentId>-api_key and mkt-<deploymentId>-api_secret. They are never shown in plain text in the portal. Your application server uses them to mint access tokens.
  2. Reach the server. SSH to the host as ubuntu@YOUR_VM_IP with the key or password you set at deploy. LiveKit listens for client signalling on ws://YOUR_VM_IP:7880 (put your own TLS terminator or reverse proxy in front for wss:// in production).
  3. Open the media ports. WebRTC media uses UDP 7882 (single port mux) with a TCP fallback on 7881. These are opened on the instance by the appliance; allow them at your network edge.
  4. Mint a token and join. With the LiveKit server SDK (or the lk CLI), create an access token signed with your API key and secret, then connect a client: lk token create --api-key <API_KEY> --api-secret <API_SECRET> --join --room demo --identity you --valid-for 24h then open the LiveKit Meet example (https://meet.livekit.io/custom) pointed at ws://YOUR_VM_IP:7880 with that token.
  5. Verify. curl http://YOUR_VM_IP:7880/ returns OK when the server is healthy, and journalctl -u livekit-server on the host shows room and participant activity.

Docs: https://docs.livekit.io/ Source: https://github.com/livekit/livekit (Apache 2.0).

FAQ​

Is there a software license fee? No. LiveKit is open source and free to run. You pay only for the NetActuate infrastructure and bandwidth.

Which port does the appliance serve on? The primary service is published on port 7880 by default; see the configuration fields for any adjustable ports.

Who supports it? NetActuate operates the underlying infrastructure. The application itself is community-supported open source (best-effort SLA class).

Version and Changelog​

VersionStatusReleased
1.13.3Current (default)2026-07-10

Deploy​

Need Help?​

Contact support@netactuate.com or open a support ticket from the portal.