How eduMEET works
From link to lecture in seconds
Open your university's link
For example meet.youruniversity.edu.gh.
Sign in as usual
Your university account, through eduID.africa or BonafID.
Get connected nearby
eduMEET picks the closest server with spare capacity.
Meet
Share, chat and present. If a server fails, you stay connected.
Centrally managed, locally hosted
A federation model that combines local service identity with shared orchestration and distributed media resources, seeded across the WACREN backbone.
Domain, tenant and SSO
Users access the service through your domain and institutional identity (eduID.africa / BonafID).
Central orchestration
The federation coordinates service operation, routing and software management.
Backbone media nodes
Traffic uses available nodes across the WACREN backbone, by geography and load.
Local identity, shared infrastructure
The African eduMEET Federation separates infrastructure hosting from service orchestration. WACREN seeds the federation with media nodes across its 12-country backbone, and NRENs that join contribute additional server resources. The eduMEET team manages the software layer, installation, updates and federation-level operation.
Service subscribers can use the federated infrastructure without operating their own media nodes. When users join a meeting, media traffic is assigned to an appropriate node based on geography and current load. If a node becomes unavailable or reaches capacity, the federation routes participants through other available nodes.
What the federation provides
Distributed media nodes
Capacity hosted by WACREN PoPs and participating NRENs, used as a shared pool.
Central orchestration
The eduMEET team at PCSS coordinates routing, software and federation operation.
Geographic and load-aware routing
Traffic goes to the nearest node with spare capacity, keeping latency low.
Failover
Traffic is rerouted if a node is unavailable, without interrupting meetings.
Tenant and domain
Each NREN or institution runs a dedicated tenant under its own domain and brand.
SSO via eduID.africa
OpenID Connect, including eduGAIN-based, eduID.africa and BonafID identity providers.
Towards autonomous African infrastructure
The federation launches on shared management infrastructure operated by the eduMEET team at PCSS, the same infrastructure behind the European federation. WACREN holds full administrative control over African tenants, domains and user management from day one. The roadmap moves to an African-hosted management node, making the orchestration layer, management node and all tenant data African-hosted under WACREN's control.
Pilot
- PCSS manages orchestration
- WACREN manages African tenants and NRENs
- Media nodes on the WACREN backbone
Autonomous
- WACREN operates its own management node in Africa
- Full operational independence from the European federation
MOU provision: The WACREN–PCSS MOU will cover migration to self-managed orchestration: configuration handover, data portability and operational transition.