ion-sfu VS peer-calls

There's nothing particularly difficult on the server side — a quality SFU should be capable to handle on the order of 400 video flows per core, and there are quite a few high-quality free software SFUs available (Janus, Jitsi, ion-sfu, livekit, Galene). To give some perspective: we're using Galene for lectures, and our single-CPU server uses around 40% CPU usage in a room with 120 students (who keep their cameras switched off during the lecture, of course, and only occasionally switch them on to ask questions).

As the grandparent mentioned, the problem is the client side. Since there is no standard videoconferencing protocol, every free software project needs to develop their own clients. And it's difficult for a free software project to have the manpower and expertise to develop quality clients for the web, Android and iOS, so in effect what we currently have are mostly half-baked web clients.

There is some hope, though. The IETF have been working on standard protocols for ingress (https://datatracker.ietf.org/wg/wish/), and if their protocols get deployed, you'll be able to use the same streaming software (think OBS) or IP camera with multiple distinct videoconferencing servers. An interoperable interactive videoconferencing protocol is nowhere near, but as more people understand videoconferencing technology, there is some hope that people will get together and start working on multi-protocol clients (remember Pidgin?).

Full disclosure: I'm the author of Galene (https://galene.org), and I've been actively participating in the Pion community (https://github.com/pion/webrtc) and collaborating with the authors of ion-sfu (https://github.com/pion/ion-sfu) and LiveKit (https://github.com/livekit).

go get: module github.com/pion/ion-sfu@upgrade found (v1.10.8), but does not contain package github.com/pion/ion-sfu/cmd/server/grpc/proto

Really appreciate that they have a Protocol project, really helps quickly get a sense of what's under the hood. It's just a bunch of protobuf messages, but that's a super helpful reference, and nice to not have it embedded in one of the various other projects: https://github.com/livekit/protocol

Notably using the well known extremely well reputed super battle hardened Pion sfu, ion: https://github.com/pion/ion-sfu

I just found this yesterday, haven't used it but looks nice: https://peercalls.com

I don't know much about peercalls's tech stack, but based on eyeballing it, it seems like E2E is an option. https://github.com/peer-calls/peer-calls/pull/142

As a last resort, you can self host https://github.com/peer-calls/peer-calls and just slap everything in the webview on both platforms. Kinda works, trust me!

If you are doing something more custom it could be great. If you are doing something generic you will want to use a SFU (or media server). There are a few that use Pion ion, Galene and peer-calls