Education & Training
Recorded lessons become a video-on-demand library, a lecture becomes a live channel, and a student's access is a line with an expiry date — all on servers the institution runs, with a free Professional licence for qualifying institutions.
The challenges
Recordings on personal drives, public video sites and chat threads: nothing is organised by course, and nothing expires when the course ends.
Students join and leave by term; access has to open on enrolment, close at the end of the access period, and not be shared beyond the student.
Lectures and student data must stay on the institution's own systems, and a campus network should serve its own viewers without going out to the internet.
How Xtream UI Pro helps
Each course is a bouquet of recorded lessons (series with seasons and episodes); a programme is a package that grants the bouquets a student needs.
Enrolment creates a line with the course access period as its expiry and a concurrent-session limit; the API or a connector does it from your student system.
The management server and a streaming node sit on the campus network; the licence key activates on site and the service keeps running without internet access.
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.
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
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
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
Two-factor sign-in, sealed secrets at rest, signed playback links bound to the viewer, IP and country rules, connection limits and brute-force protection.
TOTP · AES-sealed keys · HMAC-signed URLs · GeoIP and ISP rules
In the panel
Screenshots of the dashboard of a fresh installation with the sample catalogue. Nothing is mocked up.
Infrastructure architecture
A management server in the IT room, a streaming node in the second building, lecturers publishing recordings, and students watching on their own devices.
Pick a part of the diagram to see what it does.
In an education deployment the sources are lecture captures and uploaded recordings; the panel holds the course library and the student lines; a node in each building serves its halls; the student information system or LMS talks to the API.
The Ubuntu installer puts the panel, the API, the worker and the origin on one server of the campus network.
Upload or ingest the recordings; each course becomes a series, each lesson an episode, each programme a bouquet and a package.
Lines come from the student system through the Reseller API or from activation codes handed out at enrolment, with the term's end as the expiry.
Enrol a node over SSH from the panel; viewers of that building are routed to it, and the origin serves everyone else.
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, course organisation, student access, live classes, LMS integration and troubleshooting, step by step.
Read the setup guide| In your industry | On the platform |
|---|---|
| Training centre or distribution partner | Partner account (reseller): a delegated dashboard with credits, permissions and its own lines |
| Course collection | Bouquet: a named set of channels, films or series that a package grants |
| Recorded lessons | VOD catalogue: movies and series with seasons and episodes, categories and metadata |
| Live class | Live channel: a stream with its sources, EPG and output formats |
| Student access | Line: one access with its package, bouquets, expiry, connection limit and outputs |
| Course access period | Expiry date of the line, renewed by a package, a credit or the API |
| Concurrent session limit | Max connections of the line: how many devices may watch at once |
| LMS or commerce integration | Reseller API and webhooks: the operations of the panel from your own system |
Student information systems and learning management systems do not plug in natively: they create and renew student lines through the Reseller API (one request id per operation) or through a connector of your commerce platform, and receive webhooks when access is created, expiring or expired. The platform has no built-in single sign-on for students: a student signs in to the player with the line's credentials.
Lines carry a connection limit and may be bound to the viewer's address; playback links are signed and expire. Keep student personal data in your student system and put only what the line needs in the panel. Two-factor sign-in and permission groups protect the staff accounts of the panel.
The institution must hold the rights to the recordings and channels it distributes; the platform supplies none. A free Professional licence key is issued to qualifying educational institutions for internal use (see the programme).
Content Rights & Acceptable UseProgramme
Qualifying educational institutions 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 centreNot today: the platform has no single sign-on for viewers. Each student gets a line (user name and password, or an activation code); your student system can create and renew those lines through the API.
No. The licence key activates on site and the panel, the origin and the nodes serve the campus network on their own; internet is needed only for sources that come from outside.
No. It is video infrastructure: it stores, organises and streams the video and controls who may watch. Quizzes, grades and course pages stay in your LMS, which can link to the player or drive access through the API.
