lively-alarm-6252
03/15/2026, 7:06 AMtall-airline-16756
03/15/2026, 7:06 AMtall-airline-16756
03/15/2026, 7:07 AMlively-alarm-6252
03/15/2026, 7:08 AMinference module, you are also using LiveKit Inference (billed separately). Self‑hosting means you run your own agent/server infrastructure and manage model provider keys yourself unless you choose to route model calls through LiveKit Inference.
does that mean its billing both livekit inference and livekitcloud?
how do i change it to not use livekit cloud? does that require self-hosting?tall-airline-16756
03/15/2026, 7:08 AMinference module, you will be billed for both LiveKit Cloud (media/transport) and LiveKit Inference (model usage) separately.
• To avoid LiveKit Cloud for media, you must self‑host your LiveKit server (run your own LiveKit instance) so media transport no longer uses LiveKit Cloud.
• To avoid LiveKit Inference billing, do not route STT/LLM/TTS calls through the inference module — instead, have your self‑hosted agent call your chosen model provider(s) directly using your own provider keys.
What each billing line covers
• LiveKit Cloud: charges for real‑time media transport — WebRTC minutes, bandwidth/data transfer, and any plan fees.
• LiveKit Inference: charges for STT, LLM, and TTS model usage when you route those model calls through LiveKit’s inference service.
• Avatar/provider rendering: billed separately by the avatar provider (if used).
How to stop using LiveKit Cloud (high level)
1. Self‑host LiveKit server:
◦ Run your own LiveKit instance instead of using LiveKit Cloud. That moves media/agent hosting off LiveKit Cloud so you no longer incur LiveKit Cloud transport charges (you’ll keep infrastructure costs for the VM/container/network where you host LiveKit).
1. Manage inference calls yourself:
◦ Configure your agent to call STT/LLM/TTS providers directly using your provider API keys rather than using the inference module that routes through LiveKit Inference.
1. Update the Node starter repo configuration:
◦ Point the client and server to your self‑hosted LiveKit server URL and use the appropriate API/key settings.
◦ Replace or remove the inference integration so model calls go to your chosen providers.
Notes and tradeoffs
• Self‑hosting removes LiveKit Cloud transport billing but does not eliminate infrastructure costs (compute, egress, maintenance).
• If you self‑host but still use LiveKit Inference for STT/LLM/TTS, you will still be billed for inference.
• If you self‑host and also self‑host model calls (or use third‑party model providers directly), you will avoid LiveKit Inference charges but must manage provider keys, scaling, and reliability yourself.
If you want, I can help with next steps:
• Walk through specific config changes in the Node starter repo to point to a self‑hosted LiveKit server.
• Show how to remove/replace the inference module calls so your agent calls model providers directly.
• Help estimate costs comparing LiveKit Cloud + Inference vs self‑hosting (you’ll need to share expected session length, participant counts, and which model providers you plan to use).
Which of those would you like to do next?lively-alarm-6252
03/15/2026, 7:21 AMtall-airline-16756
03/15/2026, 7:22 AMlively-alarm-6252
03/15/2026, 7:25 AM