Sports Clubs & Academies
A match goes out live from the ground, a training session or an analysis clip joins a library by team and age group, and a member's or parent's access follows the membership the club sells — on servers the club runs.
The challenges
Parents, relatives and absent players want the match and the training session, and the club would rather give them that on its own service than on a public platform.
Coaches share session recordings and tactical clips that should reach the squad concerned, not the whole membership and not the public.
Registrations open in August, lapse in June and change with the age group, and nobody at the club wants to create each account by hand.
How Xtream UI Pro helps
The stadium or training-ground encoder pushes over RTMP to a channel; the channels of a team form a bouquet, and a package grants the bouquets a member pays for.
Recorded matches, sessions and clips are movies and series in categories by team, age group and season; a bouquet limits each collection to the squad that needs it.
A connector for the club's commerce platform or the Reseller API creates a line on registration, with the season as its period, and renews it on the next payment.
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
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 at the academy, a camera feed from the stadium, a video-analysis library kept by the coaches, and memberships sold through the club's shop.
Pick a part of the diagram to see what it does.
In a sports deployment the sources are the stadium and training-ground encoders and the coaches' recorded files; the panel holds the library and the members' lines; the origin serves the audience, with a node added when many families watch matches at once; the club's shop connects through a connector or the API.
One server runs the panel, the API, the worker and the origin; the coaching staff get a partner account with permissions for the library only.
One live channel per pitch camera, pushed over RTMP; categories per age group and season; bouquets for match days, for each squad's analysis material and for the whole academy.
The connector creates a line for each registered player or parent with the season as expiry, renews it on payment and disables it on cancellation.
Members use a player app on a phone or TV, or the web player; a connection limit per line keeps a family membership within the family.
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, installation at the club, match feeds, the analysis library, member and family access, memberships from the shop and troubleshooting, step by step.
Read the setup guide| In your industry | On the platform |
|---|---|
| Match or training feed | Live channel: a stream with its sources, EPG and output formats |
| Analysis and replay library | VOD catalogue: movies and series with seasons and episodes, categories and metadata |
| Squad or competition package | Bouquet: a named set of channels, films or series that a package grants |
| Member or family access | Line: one access with its package, bouquets, expiry, connection limit and outputs |
| Season or membership period | Expiry date of the line, renewed by a package, a credit or the API |
| Team or academy staff account | Partner account (reseller): a delegated dashboard with credits, permissions and its own lines |
| Shop or club-management integration | Reseller API and webhooks: the operations of the panel from your own system |
Commerce platforms with a ready connector (WooCommerce, Shopify, PrestaShop, Odoo and others) create and renew members' lines on registration; any other system, such as a club-management or ticketing tool, uses the Reseller API and webhooks. Encoders connect over RTMP. There is no native integration with a specific club-management product.
Analysis material sits in bouquets that only the right package grants; playback links are signed and expire; a connection limit per line stops a login from being passed around; staff accounts use two-factor sign-in, permission groups and the audit log.
The club needs the rights to what it streams, including broadcast rights for the competition, music and the images of players, minors included; the platform supplies no content and no rights. Standard plans apply.
Content Rights & Acceptable UseHelp centre
The questions operators ask before a deployment. The help centre has the general ones.
Help centreYes. Put the match channel in a bouquet that only the members' package grants; a line sees only the bouquets of its package.
Yes. Keep the squad's sessions in their own bouquet and grant it through a package given to that squad's lines.
Through the API: that system, or your shop, creates, renews and disables lines and receives webhooks. There is no native connector for a specific club-management product.
