Hello! I would like to ask a few questions related to my account. We purchased the "Scale" payment plan. We have a service that we would like to deploy to production, and we would like to have one project for production and another for development. Should I have two separate Scale projects? Or is "Scale" an account-level option? I've also noticed that there is a free quota that gets shared between projects.

Thanks for reaching out, Xurde. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

How much is the $$$ for the enterprise one

Thanks — I can clarify that for you. The Enterprise plan does not have a fixed public price. Enterprise pricing is customized based on your usage, required features (for example, SSO, support SLA, Slack support), and volume needs (including inference usage). Because it’s tailored, there isn’t a single dollar amount I can quote here. If you’d like a specific estimate, tell me a bit about your expected usage and requirements and I’ll prepare a tailored quote approach for you: • Expected monthly WebRTC minutes or concurrent users • Whether you need inference credits and an estimate of inference usage • Required features (SSO, dedicated SLAs, Slack support, custom integrations) • Whether you want multiple projects pooled under one agreement Share whichever of the above you have and I’ll outline likely cost factors and next steps to get an exact quote. Sources: Pricing | LiveKit

I onle know the pooled multiple of projects, maybe 10000 minutes.

Thanks — that helps. A few quick points and then a couple of targeted questions so I can give a more useful estimate. What I can confirm • Enterprise pricing is customized and there’s no single public dollar amount. • Pooled quotas and unified billing across multiple projects are available on Enterprise. • 10,000 minutes of pooled usage is a relatively modest volume to use as a starting point for a quote. To give a more accurate range or guidance on whether Enterprise is worth it versus keeping separate Scale projects, could you share any of the following details? You don’t need to have exact numbers — rough estimates are fine. • Expected monthly concurrent users (or peak concurrent sessions). • Whether the 10,000 minutes is WebRTC voice/video minutes, agent session minutes, or another metric. • Whether you expect any significant inference usage (AI features) and an estimate of inference minutes or calls. • Required Enterprise features: SSO, support SLA, Slack support, dedicated account management, custom integrations, or anything else. • Number of projects you want pooled under Enterprise. If you prefer, I can also outline two scenarios now: • A simple scenario recommending you keep separate Scale projects (when cost-savings matter and dev doesn’t need Scale features). • A pooled Enterprise scenario and the kinds of benefits and cost factors to expect (volume discounts, unified quotas, SLAs). Which would you like me to do next — give the two-scenario outline based on 10,000 minutes, or gather the details above to build a closer estimate?

10.000 minutes yeah use that

Thanks — that’s helpful. I’ll walk through what to expect for 10,000 pooled minutes and your practical options. Quick recap • The Scale plan is per project. Each project gets its own included quota unless you move to Enterprise. • Enterprise lets you pool quotas and unify billing across projects, but pricing is customized and not a fixed public rate. What 10,000 pooled minutes means (high level) • 10,000 minutes is a modest usage volume. On Enterprise, those minutes would be pooled across whatever projects you attach to the agreement (so dev + prod could draw from the same 10,000-minute allotment). • Enterprise pricing typically includes volume-based discounts and may bundle other features you need (SSO, SLAs, Slack support, dedicated account help). Those extras factor into the final price. How to choose between options • Keep separate Scale projects if: ◦ You want simple isolation and don’t need pooled quotas or unified billing. ◦ Dev can accept its own separate quota or a lower-cost plan. • Move to Enterprise if: ◦ You want pooled quotas (one 10,000-minute pool for multiple projects). ◦ You need centralized billing, SSO, SLAs, or dedicated support. ◦ You expect growth and want volume discounts and contract flexibility. Pricing guidance and next steps • I cannot give a fixed dollar amount because Enterprise pricing is customized per customer. • For a tailored estimate, the key cost drivers are: ◦ Whether 10,000 minutes are WebRTC voice/video minutes or another minute type. ◦ Number of projects to pool under Enterprise. ◦ Need for inference credits or high inference usage. ◦ Required enterprise features (SSO, SLA, dedicated support, integrations). If you want a rough ballpark estimate from me here, tell me: • Are the 10,000 minutes WebRTC voice/video minutes? • How many projects would you like pooled (e.g., 2: prod + dev)? • Do you need SSO, SLA, dedicated support, or inference credits included? Or, if you prefer, I can outline two scenarios now: 1. Keep separate Scale projects for prod and dev and save cost if dev doesn’t need Scale features. 2. Move to Enterprise to pool 10,000 minutes across projects and get centralized billing and SLAs — I’ll list which features typically add to cost so you know what to expect. Which would you like me to do next?

tell me the two scenarios

Thanks — I’ll lay out the two scenarios side-by-side and what to expect for ~10,000 pooled minutes so you can choose with confidence. Acknowledging your request • You asked for two scenarios: (A) keep separate Scale projects, and (B) move to Enterprise with pooled minutes. I’ll show costs, pros/cons, and which fits a 10,000‑minute use case. Scenario A — Separate Scale projects (one per environment) • What it looks like: ◦ Create distinct Scale projects for Prod and Dev (and any other environment). ◦ Each project is billed and quota'd separately. • Quotas & pricing (per project): ◦ Scale starts at $500/month per project. ◦ Each Scale project has its own included quotas (minutes, concurrency, inference limits). Those quotas do not pool across projects. • Pros: ◦ Strong isolation (credentials, logs, and usage are separate). ◦ Simple setup and predictable per-project limits. • Cons: ◦ No pooling — unused minutes in one project can’t be used by another. ◦ If you need Scale for both Prod and Dev, cost multiplies. Example: Prod + Dev = ~$1,000/month (starting). • When to pick this: ◦ Dev doesn’t need pooled minutes or Scale-level features, or you prefer strict separation and simpler billing per project. Scenario B — Enterprise plan with pooled quotas (recommended for your 10,000 pooled minutes) • What it looks like: ◦ Upgrade to Enterprise and attach multiple projects to one Enterprise agreement. ◦ Minutes and other entitlements are pooled across linked projects (so your 10,000 minutes can be shared by Prod and Dev). • Pricing & features: ◦ Enterprise pricing is custom (no fixed public price). It typically starts above the Scale base and uses volume-based pricing/discounts. ◦ Enterprise includes options such as pooled quotas, unified billing, SSO/SAML, SLAs, dedicated support, and compliance features (HIPAA/SOC2) if needed. • Pros: ◦ Efficient use of minutes (pooled 10,000 minutes across projects). ◦ Centralized billing, improved operational flexibility, and enterprise-grade support/security. • Cons: ◦ Custom contract and pricing; requires an agreement with sales. ◦ Often a higher minimum commitment than a single Scale project. • When to pick this: ◦ You want cost-efficiency across environments, quota pooling, centralized billing, or enterprise features like SSO and SLAs. Practical guidance for 10,000 minutes • If your only requirement is to pool ~10,000 minutes across Prod + Dev, Enterprise is the option that accomplishes that (Scale projects cannot share minutes). • If Dev can accept its own small separate quota or run on a lower plan, keeping Prod on Scale and Dev on a cheaper plan may be cheaper than Enterprise. • Enterprise becomes more attractive as you: ◦ Need pooled minutes across multiple projects, ◦ Expect growth or burst usage that benefits from pooled quotas and volume discounts, or ◦ Require enterprise features (SSO, SLA, compliance, dedicated support). Next steps I can help with • Compare cost scenarios: I can sketch two quick cost comparisons for you: 1) Prod on Scale + Dev on a lower plan (estimate monthly total). 2) Enterprise with pooled 10,000 minutes (explain which features drive price and what to ask sales). • Or, if you prefer, tell me whether Dev must use Scale features or could use a lower tier — I’ll build the comparison for you. Which next step would you like: a quick cost comparison (Prod+Dev vs Enterprise) or a list of the exact details to collect for a tailored Enterprise quote? Sources: Pricing | LiveKit | Structuring development and test environments | LiveKit | Build voice, video, and physical AI | LiveKit