Media-node capacity
Provide server capacity to the shared media-node pool and become part of the federation's infrastructure.
Participation
eduMEET Federation is built by the institutions that join it. Contribute media-node capacity, become part of the shared infrastructure pool, and run your own trusted video service under your own domain.
How to participate
The federation grows when institutions contribute media-node capacity. Contributors donate CPU cores, join the shared infrastructure pool, and receive service entitlement in return.
Provide server capacity to the shared media-node pool and become part of the federation's infrastructure.
Receive slot entitlement and run your own branded eduMEET service under your own domain.
Cannot host infrastructure? Organisations can also use the federation on a paid basis — see subscription options.
How capacity is counted
eduMEET Federation does not require separate room types to be configured in advance. Every active room is classified automatically by its current participant count.
Classification is measured during the session. A room can move between categories as participants join or leave.
| Current participants | Classified as | Typical use |
|---|---|---|
| 1-100 | Meeting | Tutorials, team meetings, small classes |
| 101-300 | Lecture | Lectures, seminars, workshops |
| 301-1,000 | Webinar | Conferences, large events, town halls |
Infrastructure credits
Infrastructure contributors receive slot entitlements in return for donated CPU cores. The donated infrastructure can be allocated across Meeting, Lecture and Webinar categories.
Allocation can be adjusted for the next billing period, so organisations can adapt their mix as usage patterns change.
| Category | Core-to-slot conversion | 48-core server example |
|---|---|---|
| Meeting | 1 core = 1 Meeting slot | 48 Meeting slots |
| Lecture | 2 cores = 1 Lecture slot | 24 Lecture slots |
| Webinar | 8 cores = 1 Webinar slot | 6 Webinar slots |
If peak usage exceeds your entitlement, the extra usage is simply billed as overage in the relevant category — meetings are never blocked. See the overage rule for details.
What contributing involves
Contributors provide a server with a public IPv4 address and a configured firewall. The eduMEET team installs and maintains the eduMEET software, manages updates and operates the federation layer.
Server sizing, firewall rules, DNS and optional SSO/OpenID Connect integration are described in detail in the technical onboarding guide.
View technical requirementsAt a glance
Ready to join?
Tell us about your organisation, the infrastructure you can contribute and your expected use case.