Do I need to have a separate billing plan (build s...
# ask-aib
blue-branch-38615
03/24/2026, 3:15 PMDo I need to have a separate billing plan (build scale ship etc.) for each LiveKit project?
✅ 1
t
tall-airline-16756
03/24/2026, 3:16 PMThanks for reaching out, Rohan. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
tall-airline-16756
03/24/2026, 3:16 PMThanks — good question. You're asking whether each LiveKit project needs its own billing plan. Here's the clear answer and what you can do next.
• Each LiveKit project must be assigned a pricing plan (Build, Ship, Scale, Enterprise), so every project has a plan associated with it.
• You do not need a different plan type for every project — multiple projects can use the same plan type.
• If you want a single plan shared across multiple projects (for unified billing), the Scale plan includes a “shared plan across projects” feature that lets you do that.
If you tell me how many projects you have and whether you want consolidated billing or different limits per project, I can recommend which plan might fit best and walk you through assigning or switching plans.
Sources: Towards a future-aligned pricing model | LiveKit | Pricing | LiveKit | Pricing | LiveKit, with interactive elements
b
blue-branch-38615
03/24/2026, 3:17 PMShould each env (staging prod local) be a different project?
t
tall-airline-16756
03/24/2026, 3:17 PMThanks — great question. You're asking whether staging, production, and local environments should be separate LiveKit projects. Short answer and recommended practice:
• Yes — it’s recommended to use separate LiveKit instances (projects in LiveKit Cloud) for staging, production, and development/local.
◦ Each LiveKit Cloud project has its own URL, API key, and secret, which prevents accidental use of production credentials in lower environments.
◦ Separate projects reduce the risk of test traffic affecting production users and make it easier to test configuration, scaling, or upgrades safely.
• If you self-host, use separate deployments for staging and production and a local server for development.
What I can help with next
• If you want guidance tailored to your team, tell me: how many projects/environments you plan to run, whether you want shared billing, and whether you use LiveKit Cloud or self-hosted.
• If you prefer consolidated billing across those projects, note that the Scale plan supports a “shared plan across projects” so billing can be unified while keeping environments separate.
Would you like a recommendation based on your current project count and team setup?
Sources: Self-hosted deployments | LiveKit Documentation, with interactive elements
3 Views