Comparisons
Three pages for the part of the decision that happens before you write code: which kind of SFU to use, what self-hosting actually costs against a per-minute vendor, and which licence you are agreeing to. Each one names the cases where the answer is not this kit.
LiveKit vs a single-binary Pion SFU: an honest comparison
LiveKit is the right default for most SFU work. This page is about the narrow case where a small, readable, single-binary application beats a platform - and the cases where it does not.
Read the LiveKit comparison ->Managed video APIs vs self-hosting: the break-even, computed
Managed APIs are priced per participant-minute and self-hosting is priced in server time. Here is the two-multiplication calculation that turns those into the same unit.
Read the break-even page ->WebRTC SFU landscape: LiveKit, Janus, mediasoup, Jitsi, Kurento, Pion
LiveKit, Janus, mediasoup, Jitsi, Kurento and Pion are four different kinds of thing. Sorting them into libraries, platforms, products and starting applications decides your timeline before any benchmark does.
Read the landscape page ->What these pages are not
They are not benchmarks. There is no throughput chart here, because a synthetic comparison on one machine would not survive contact with your network. The claims that are checkable - licences, dependencies, what a project includes - are stated with the date they were checked so you can re-check them.
If you are still choosing, the guides are the faster read: they start from a symptom and narrow the cause, which is what the first week of a WebRTC project actually looks like.