This topic is about evaluating all tools about audio/video conferencing for creating virtual events or meetings.
This topic is a wiki feel free to edit it.
|Name||E2E Encryption||Audio||Video||Screen sharing||Chat||Web client||License||Notes|
|Jitsi Meet||-||+||+||+||+||+||Apache 2.0||Works quite well with few participants. Often disconnects and audio loss were participants need to reconnect. List of public Jitsi servers: 1, 2|
|BigBlueButton||?||+||+||+||+||+||LGPL||Not tested / Made specifically for education.|
|Tox||?||+||+||+||+||-||GPL 3.0||Not tested / Distributed, no central server is required.|
|OpenVidu||?||+||+||+||+||+||Apache 2.0||Not tested / Multiple WebRTC video conference modes: One-to-One, One-to-Many, Many-to-Many.|
|Zoom||-||+||+||+||+||-||proprietary||Battle tested. Works quite well. Resource heavy (requires lots of CPU and RAM).|
|mediasoup||?||+||+||+||+||+||ISC||Not tested / Testing server: Uninett multiparty meeting|
|Mumble||?||+||-||-||+||-||BSD-3||Low latency high quality voice chat. Works very well with many participants. 3rd party HTML5 client mumble-web.|
|Kopano Meet||?||+||+||+||+||+||GNU AGLv3||Not tested / Testing server: Meet|
|Pion||?||+||+||+||+||+||MIT||Not tested / Distributed RTC System by pure Go and Flutter|
Tests the network latency and throughput (as well as other information) of multiple Jitsi servers to help choose the best server according to your location. At the time of this writing there are 208 Jitsi servers being tested.