There's still a lot of room in the space of WebRTC troubleshooting tooling, precisely due to the complexity inherent of "doing it right". I know well about the

There's still a lot of room in the space of WebRTC troubleshooting tooling, precisely due to the complexity inherent of "doing it right". I know well about the mess of difficult to debug technologies that form WebRTC... and on top of that you'll want monitoring, recording, reconnection logic when things go wrong. Of course, add the ability to seamlessly scale when there are lots of users joining a call. The list goes on and on even for a seemingly simple service that "just works"!! I've been maintaining and improving the oss Kurento server for several years now (https://www.kurento.org/ https://www.kurento.org/), and the kind of issues that users find is crazy. A slight misconfig in an intermediate proxy can cause random issues very hard to track down. Shameless plug: We're now building OpenVidu (https://openvidu.io/ https://openvidu.io/) on top of Kurento, to provide some of these features. This is a tool that in turn (pun intended) eases writing videoconference services. Most people looking into starting their own WebRTC app from scratch with Kurento, would be better served by OpenVidu!