Jitsi is very, very impressive. But their whole platform is also bound up with a lot of other tech in the stack. (jitsi-meet, jitsi-videobridge, jicofo and 'Prosody' (XMPP).
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).