IIUC, LikveKit has 3 modes of deployment: 1. self-hosting (not touching any part of LK infra itself) 2. hybrid (uses LK's infra for RTC, routing, etc) but agent code runs on the customer's env 3. cloud (uses LK's infra for everything including running agent code) Did i get that right or am I missing something? Would really appreciate if someone can help me get a better mental model. Thanks.

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

specific application logic

LiveKit offers two main ways to get started, and I’m here to help you find the best fit for your needs: • Cloud Deployment: This option is fully managed by LiveKit, taking care of RTC, routing, and application logic for you. It comes with great features like automatic scaling, multi-region support, and built-in analytics to make your experience smooth and reliable. • Self-Hosted Deployment: If you prefer more control, you can deploy the open-source LiveKit server on your own infrastructure. This way, you have full flexibility to customize and manage everything exactly how you want. Although there isn’t an official “hybrid” deployment mode documented, LiveKit’s architecture is quite flexible. For instance, you could run self-hosted agents alongside LiveKit’s cloud infrastructure for media transport—opening the door to some creative hybrid setups tailored to your unique needs. If you’re thinking about hybrid options or have any specific questions, please feel free to reach out. I’m happy to guide you through the possibilities and help you find the perfect solution. Sources: Intro to LiveKit | LiveKit Docs | How We Built a Globally Distributed WebRTC Mesh Network | How We Built a Globally Distributed WebRTC Mesh Network | LiveKit Cloud | LiveKit Docs | README.md

For instance, you could run self-hosted agents alongside LiveKit’s cloud infrastructure for media transport

What you call this method of deployment?

I’m glad you asked about this! While LiveKit doesn’t have an official name for this method of deployment, you can think of it as a custom hybrid deployment. Essentially, it means running self-hosted agents to handle specific parts of your application’s logic, while still taking advantage of LiveKit’s cloud infrastructure for media transport and other services. Since this isn’t a formally documented deployment mode, it does mean you’ll need to set up some custom configurations for things like routing, token management, and coordinating your infrastructure. But don’t worry—I’m here to help! Just let me know if you’d like some guidance on how to get started with this setup.