Meetings that stay inside your bandwidth
It does not try to send everybody to everybody
Each person’s browser subscribes only to whoever is speaking and the faces actually on their screen, at the smallest quality that still looks right. Everybody else is dropped rather than hidden.
Why this is the whole design
A meeting of fifty where every browser receives all fifty streams needs roughly ten gigabits per second leaving the building. That is not a tuning problem; it is the reason large meetings on under-provisioned platforms degrade into a slideshow.
So it was never built that way. A browser asks for the active speaker plus the tiles on screen — twelve by default — and nothing else. Scroll a face out of view and its video is unsubscribed, not merely covered up.
What you notice
Mostly, nothing, which is the point. On a poor connection the effect is that the meeting keeps working and the faces you are not looking at are the ones that go first.
On a managed network it means a meeting of fifty costs roughly what a meeting of twelve costs, which is the difference between a platform an organisation can run at scale and one it cannot.
What this does not do
This is real engineering and it is invisible in a demo. It shows up as a number on a network graph, or as the absence of a complaint, and neither is something a sales call can show you.