Thinking about moving from the hosted to a self-hosted version of LiveKit? It means setting up your own infrastructure and getting the server configured, but don’t worry—I’m here to guide you through the main steps: • Choose Hosting Method: You’ve got options! You can self-host using a Virtual Machine (VM) with Docker Compose and Caddy, or go with a Kubernetes cluster using Helm. • Set Up Configuration: You’ll generate configuration files tailored for your domain and then deploy them using Docker Compose or Helm, depending on which method you picked. • DNS and SSL: Make sure your domain’s DNS records point to your server, and that SSL certificates are set up—luckily, Caddy can handle this part automatically for you. • Firewall: Don’t forget to configure your firewall so it allows traffic through the ports you need. • Update Clients: Once you’ve made the switch, update your client apps to connect to your new self-hosted server URL. If you hit any bumps along the way or want to chat about any step in more detail, just let me know—I’m happy to help! Sources: Deploy to a VM | LiveKit Docs | Deploy to Kubernetes | LiveKit Docs