Who runs it.

01

Institutions running their own cluster

A second BigBlueButton server is the usual trigger — past roughly 250 people at once, or when exams need to be kept away from ordinary lectures. From there the problem stops being capacity and starts being visibility.

Pools separate exams from teaching; support staff join a failing class without credentials or a shell.

02

Resellers selling conferencing

You already run the servers. What you do not have is a way to give each customer their own credentials, their own record and your branding, without standing up a separate cluster for every one of them.

Tenants with their own API secrets on the fleet you already run, and a branding tab so your customers never see our name.

03

Organisations keeping departments apart

Faculties, subsidiaries or business units that must not share credentials, but have no reason to buy the hardware twice.

Isolation at the credential layer, with pools when you want the separation to be physical too.