LiveKit subscription needs to be contracted for ea...
# ask-ai
b
LiveKit subscription needs to be contracted for each project, or is it possible to share one subscription for multiple projects in the organization?
t
Thanks for reaching out, toshi. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I’m happy to clarify this for you. You can share a single LiveKit subscription (plan) across multiple projects within the same organization. On the Enterprise plan, multiple projects can be linked to the same agreement so you get shared billing and centralized plan controls while keeping each project isolated. To attach projects to the same subscription, provide LiveKit Support with the
project_id
of each project you want included and they will add those projects to the same subscription. This gives you centralized billing and resource management without needing separate contracts per project. Would you like help gathering the `project_id`s or confirming which projects in your organization are already linked to the subscription? Sources: Structuring development and test environments | LiveKit
b
Sharing the plan across multiple projects is only possible for the Enterprise plan? How about Ship plan?
t
Thanks for the follow-up — good question. Sharing a single LiveKit subscription across multiple projects is only available on the Enterprise plan. Enterprise customers can attach multiple projects to the same agreement for shared billing and centralized plan controls while keeping each project isolated (credentials, logs, usage remain separate). The Ship plan (and lower-tier plans) do not support sharing a subscription across projects—each project on those plans requires its own standalone subscription and plan allotments. Would you like help checking which of your projects could be rolled into a single Enterprise agreement or gathering the `project_id`s to initiate that setup? Sources: Structuring development and test environments | LiveKit