Universities & Campuses
The campus channels, the recorded lectures and the halls of residence share one platform. Faculties get their own partner accounts, and each student's access is a line your student-information system creates for the semester.
The challenges
Recordings sit on faculty drives or on outside video sites, with no common catalogue, no retention you control and no way to restrict them to enrolled students.
Lecture halls, libraries and halls of residence spread over several campuses, and the evening load from residences should not fall on the central link.
Thousands of students enrol and leave each term; access must open at enrolment and close at the end, without staff touching accounts one by one.
How Xtream UI Pro helps
A faculty's lectures are series with seasons and episodes in their own categories; a bouquet per faculty and a partner account (reseller) let each faculty manage its own collection.
The student-information system creates a line per student through the Reseller API with a package whose duration is the semester, and renews it at re-enrolment.
Each campus and each hall of residence has a node that takes the live channels once from the origin and caches the lectures, so evening viewing stays on the local network.
Platform capabilities
The capabilities below are the ones this deployment relies on. Each is in the product today; nothing here is planned or on request.
Live channels from your own sources, with EPG, catch-up and timeshift where the source allows, delivered as HLS or MPEG-TS to the apps and boxes your viewers use.
Origin hub with one upstream per channel · RTMP in and out · ffmpeg transcoding
Movies, series with seasons and episodes, and radio, organised in categories and bouquets, with TMDB metadata and an ingest job that downloads and encodes your sources.
Signed, time-limited playback links · per-node VOD cache
Enrol edge servers from the panel; viewers are routed to a node by load and by country, and the origin serves everybody while no node exists.
Installed over SSH from the panel · GeoIP routing · heartbeats and traffic stats
A line is one viewer's access: package, bouquets, expiry, connection limit and output formats, with activation codes, trials and renewals following the same rules everywhere.
Xtream Codes API, M3U/XMLTV, MAG and Enigma2 portals, web player
Delegated accounts with credits, permissions and their own dashboard, up to five levels deep, for the distributors, operators and resellers you work with.
Groups and permissions · credit ledger · sub-partners
Create, renew and suspend access from your own systems through the Reseller API, receive signed webhooks, and connect billing or commerce platforms with a ready connector.
Reseller API with idempotent request ids · Admin API keys · 17 connectors
In the panel
Screenshots of the dashboard of a fresh installation with the sample catalogue. Nothing is mocked up.
Infrastructure architecture
A management server on the main campus, a node per campus and per hall of residence, a campus channel line-up, lecture recordings by faculty, faculties as partner accounts, and student lines created from the SIS.
Pick a part of the diagram to see what it does.
In a university deployment the sources are the campus channel feeds, the lecture-capture recordings and live events from halls; the panel holds the faculty libraries, the packages and the student lines; the origin and a node per campus or hall serve them; the student-information system connects through the Reseller API.
The panel, the API, the worker and the origin run on a university server; a node is enrolled for each other campus and each hall of residence from Servers.
Each faculty gets a partner account with permissions for its own lines and bouquets; its lectures are filed as series under its categories.
The SIS calls the Reseller API to create a line per enrolled student with the semester package and renews it at the next enrolment.
The campus line-up and live events from the lecture halls are live channels in the campus bouquet; the nodes in halls of residence fan them out.
Configuration mapping
The platform has no industry-specific objects: a bouquet, a line, a package or a partner account is used as the concept your industry needs. These are conceptual mappings, not native features of that industry.
Prerequisites, deployment on the campus network, faculty archives, student access from the SIS, campus channels, security and troubleshooting, step by step.
Read the setup guide| In your industry | On the platform |
|---|---|
| Faculty or department account | Partner account (reseller): a delegated dashboard with credits, permissions and its own lines |
| Faculty collection or campus line-up | Bouquet: a named set of channels, films or series that a package grants |
| Campus channel or live event | Live channel: a stream with its sources, EPG and output formats |
| Lecture archive | VOD catalogue: movies and series with seasons and episodes, categories and metadata |
| Student or staff access | Line: one access with its package, bouquets, expiry, connection limit and outputs |
| End of the semester or the enrolment | Expiry date of the line, renewed by a package, a credit or the API |
| Campus or hall of residence node | Streaming nodes: edge servers enrolled from the panel, one per site or building |
| Student-information system integration | Reseller API and webhooks: the operations of the panel from your own system |
The student-information system connects through the Reseller API (create, renew, disable a line) and webhooks; the panel has no native SIS, LMS or campus-card integration and no single sign-on for students, so a student signs in to the player with the credentials of the line your system issued.
Keep the platform on the campus network or behind your reverse proxy; lines carry a connection limit and can be bound to an address or a country; playback links are signed and expire; panel accounts use two-factor sign-in and permission groups so a faculty sees only its own lines; the audit log and the encrypted backups complete it.
The university needs the rights to the channels it carries and to the recordings it publishes, including lectures with third-party material; the platform supplies no content and no rights. Standard plans apply, and the education programme applies to qualifying institutions.
Content Rights & Acceptable UseProgramme
Qualifying universities run the Professional plan at no cost: one licence key per institution, valid two years, requested by e-mail from the institution's academic domain.
Education · free
For a growing service with its own resellers.
instead of $49 / month · 2 years per key
Help centre
The questions operators ask before a deployment. The help centre has the general ones.
Help centreYes. A faculty is a partner account with its own lines and a permission group, and its lectures sit in its own bouquets. It is a delegated account, not an isolated installation.
Not today: a student uses the credentials of the line your student-information system created. Single sign-on for viewers is not a feature of the platform.
The package's duration is the access period, so a line expires at the end of the semester unless it is renewed. The system can also disable a line through the Reseller API when a student leaves.
