Thanks — I’m responding to your request about moving or connecting LiveKit servers so a single room can use multiple nodes. Short answer: • Self-hosted LiveKit cannot split a single room across multiple nodes — each room runs entirely on one node. • To have a single room span multiple servers, use LiveKit Cloud, which natively distributes a room across multiple SFU nodes. How I can help next (pick one or tell me which fits): • If you’re self-hosting and want migration steps to move a room from one node to another, tell me your deployment (Kubernetes or bare VM) and I’ll outline steps and options (graceful handoff, ICE restart approach). • If you want to run many rooms across multiple nodes (not a single-room split), tell me your current Redis/load‑balancer setup and I’ll give a recommended multi-node deployment pattern. • If you want to explore LiveKit Cloud for multi-node rooms, I can summarize the benefits and next steps to migrate. Which option do you want to proceed with? Sources: Distributed Setup | LiveKit docs | Benchmarking | LiveKit docs | LiveKit Cloud Architecture | LiveKit docs | Announcing LiveKit Cloud | Announcing LiveKit Cloud