Also, aside from the obvious AV chat systems (eg: Jitsi. Zoom, etc.) 'cloud-gaming' platforms such as Google Stadia and Shadow use it.
I've been monitoring and experimenting with webRTC for a few years now and one of the most exciting recent developments has been more or less full support in desktop and mobile browsers (even Safari, which dragged its heels for years)
Fwiw, WebRTC doesn't imply p2p/serverless.
WebRTC is fundamentally peer-to-peer. But scaling up to larger calls, and doing things like recording, generally requires routing the audio/video through media servers that selectively forward, process, or transcode the media streams.
<shameless-plug> I cofounded a company that makes it easy to get started with and scale WebRTC-based applications and features. [0] </shameless-plug> In addition to basic video calls, we're seeing rapid growth of online classes, games, fitness applications, live collaboration in productivity apps, e-commerce and customer support, and IoT and robotics streaming video.
Zoom doesn't use webrtc (unless you count the browser fallback version which nobody uses), they use their own video codec - which notably uses a lot of cpu but requires little bandwidth. From my experience, zoom is the only solution where I don't experience bandwidth problems all the times.
Yes and it works well
For example, Jitsi delegates authentication of users to Prosody. Prosody already has a bunch of authentication backends ( https://modules.prosody.im/type_auth ) and Jitsi benefits from these without needing to reinvent the wheel.
I've seen the Jitsi+Prosody combo integrated into many kinds of platforms. People also implement things like custom access control, logging, notifications and provisioning at this layer. These things would generally be harder to customize in a monolithic off-the-shelf system.
Meanwhile a simple self-hosted setup is still easy enough to pull off in a spare afternoon ( https://jitsi.github.io/handbook/docs/devops-guide/devops-gu... ).
(I'm currently looking in to using Mediasoup for some WebRTC to RTMP ideas I've been mulling.)
But we are indeed integrating Jitsi into a game experience here and its open-source stack is really nice to deal with (after many days needed to really understand it).