The university as a tenant: white-label platforms explained

In software, a tenant is a self-contained unit: a university, a department with its own continuing education, or a company. Each tenant has its own users, courses, examinations and settings — and above all its own data, which no other tenant sees. The software is the same for all; the data are not.

The advantage is obvious: development, security, updates and operations are done once for everyone. A small university gets the same platform as a large one without building its own development team. The precondition is that tenant separation is technically and organisationally reliable.

White-label means the platform appears under the university's brand. Students see their university's logo, colours and address, not the software provider's. Certificates and degree certificates name the university as issuer; courses carry its design.

This is more than cosmetics. For students it is their university, which they trust. For employers checking a credential, what matters is that the issuing university is clearly identifiable. And for the university itself, its own brand is part of its profile in the competition for students.

Legally, the university is the controller for its students' and staff's data, the platform operator a processor. This requires a contract under Article 28 GDPR. Technically, it must be ensured that every query returns only the tenant's own data — ideally through rules directly in the database that even a programming error cannot bypass.

For universities with special requirements — for instance from state law or because of sensitive research data — a dedicated instance can make sense: the same software, but with its own database and separate deployment. The price is higher operating effort; the gain is maximum separation. The university should decide which option fits together with its data protection officer and IT security, and document the outcome.

Not every university needs everything. A campus-based university might use only examinations and verifiable degree certificates, a distance-learning university the full chain from application to graduation, a continuing education academy courses and participation certificates. A modular platform lets each tenant book building blocks and switch individual features on or off. What is not booked does not appear.

It matters that modules fit together but do not have to depend on each other. A university that keeps its existing learning system should still be able to use examinations or certificates from the new platform — connected through standards such as LTI 1.3.

Choosing a white-label platform is a decision for years. Besides features, reliability, transparency and the possibility of leaving again count.

The path to your own platform starts with a few decisions: at which address should it be reachable? Which modules does the university need at launch? Who manages users and rights? Then come brand and content — logo, colours, texts, first courses — and connecting existing systems, such as sign-in with the university account.

Before students use the platform, the data processing agreement, privacy notice, legal notice and, where required, accessibility statement should be in place. A short pilot with a group of lecturers and students shows whether processes and texts are understandable.