Mediasoup has a more low level API. It's more of a library/framework to make your own SFU (although there's an example SFU). Jitsi is more of a ready to use SFU. Mediasoup is newer, but has seen very fast development. Last performance comparison I know of had mediasoup as a clear winner over jitsi. But that's a fast moving target and the usual limitations of a benchmark apply here as well: https://webrtchacks.com/sfu-load-testing/

Mediasoup has a c++ core with node api. Jitsi is java.

If you're experienced with webRTC, you will probably like mediasoup better. Otherwise I'd stick with jitsi.

mediasoup co-author here.

Comparing Jitsi with mediasoup is like comparing Netflix (backend + apps) with Express.js + libcurl.

Jitsi developers may replace their RTC core internals (including the SFU) with mediasoup + mediasoup-client and you wouldn't even realize of it. Hope this helps.

Thanks for this. Do you plan to go higher in the stack and release components to get-started-quickly ?

Not at all.