👋 Hello, team! Hi LiveKit Team, I am on the Build Plan for my project "MarkazAlBukhari". I want to confirm: Does the 50GB free data transfer limit reset every month? And on which day does the reset happen? Thanks!

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

Hello LiveKit Team, I’d like to explain my app idea and ask if LiveKit is the right platform for it. 📱 My App Concept: 1. One-to-One Calls: - One or more teachers are online, waiting for student calls. - A student opens the app, sees the list of available teachers, selects one, and starts a call. - At the same moment, another student opens the app, sees the same available teachers, and chooses a different teacher to connect with. - Teachers are fixed; students change throughout the day. 2. Group Calls: - A teacher has a fixed group of students (members may increase, decrease, or switch between teachers — e.g., student A moves from teacher X to teacher Y). - They hold group calls lasting about one hour or more, at least twice a week. 3. Live Streaming: - A teacher starts a live broadcast. - Students join as listeners/viewers only. - Audience size may go up or down dynamically during the stream. 📌 Summary: This is the core idea of my application. My question: Can I fully rely on LiveKit to build this? Are there any limitations I should be aware of for these use cases? Thank you.

Thanks — this is a clear and useful description of your app. I’ll address whether LiveKit can support each of your three use cases, point out potential limitations to consider, and ask a couple of targeted questions so I can give more specific guidance for your expected scale and costs. Short answer • Yes — LiveKit can support one-to-one calls, dynamic group calls, and teacher-led live broadcasts (viewer-only audience). These are common realtime-communication patterns LiveKit is designed for. How LiveKit maps to each part of your app • One-to-one calls ◦ LiveKit supports many simultaneous peer connections and lobby-style flows where teachers are “available” and students join. You can present a list of available teachers in your app and have the student create/join a room with the selected teacher. ◦ Teachers can host multiple sequential or concurrent 1:1 sessions depending on your app logic and server capacity. • Group calls with dynamic membership ◦ LiveKit rooms support adding/removing participants and role/state changes (e.g., who can publish audio/video). You can maintain a fixed teacher role and update the student roster as members move between teachers. ◦ Rooms can handle hour-long calls; you will want to plan for server resources and bandwidth based on group size and media quality. • Live streaming (teacher publishes, students are listeners) ◦ LiveKit supports publisher-only streams and large numbers of viewers who subscribe as listeners. You can restrict viewers to subscribe-only (no publish) to reduce upstream usage. ◦ For very large audiences, you can use LiveKit’s server-side features (SFU) and optionally integrate with CDN or RTMP distribution if you need broadcast-level scale or very high concurrent viewers. Potential limitations and things to plan for • Scale & bandwidth costs ◦ Large numbers of concurrent participants or high-resolution streams increase CPU, memory, and bandwidth usage. Downstream data transfer is billed per GB, so estimate costs for group calls and especially for large live audiences. • Maximum practical room sizes ◦ While LiveKit’s SFU architecture supports many participants, optimal limits depend on the mix of publishers vs. subscribers and your server sizing. Large group calls with many active webcams are heavier than many listeners-only viewers. • Role/permission management ◦ You’ll need to implement app-layer logic to manage teacher vs. student roles, permissions to publish, and membership changes. LiveKit provides the primitives (room/participant/events), but your app handles grouping/authorization. • Recording, playback, and archiving ◦ If you need recorded sessions or VOD of live streams, plan how you’ll capture and store media (LiveKit offers recording options or you can route to an external storage/CDN). • Latency expectations ◦ LiveKit provides low-latency realtime audio/video; if you require sub-100ms glass-to-glass latency for certain live interactions, plan your infrastructure (region placement, server sizing). For broadcast+CDN workflows, final latency may be higher. • Device & network variability ◦ Mobile and lower-bandwidth networks will affect perceived quality. Implement adaptive bitrate, simulcast, or publish-quality controls to handle this. Questions that will help me give targeted guidance 1. Expected concurrency: roughly how many simultaneous teachers, students, and peak concurrent viewers do you expect? 2. Typical group call size: how many students per group session on average and max? 3. Media quality targets: do you need HD video, or is SD/voice-first acceptable? 4. Recording needs: do you want to record sessions/streams for later playback? 5. Geographic distribution: will participants be concentrated in a region or global? If you share answers to those, I’ll: • Recommend an architecture (single-room per session vs. persistent rooms, when to use simulcast, whether to offload viewers to CDN/RTMP) and suggest sizing and cost considerations. • Outline a simple flow for teacher availability, student matching, and role/permission changes you can implement with LiveKit. Would you like me to proceed with an architecture recommendation based on estimated concurrency, or show example flows (1:1, group, broadcast) you can implement?