Community Organisations
An assembly, a service or a performance goes out as a live channel; the recording joins a library; members watch with an access the organisation grants and ends — without handing the audience to a public platform.
The challenges
Older members, distant members and overflow rooms need the event live, with little equipment and no streaming expertise on site.
Many events are for members only; a public video platform cannot restrict the audience or keep the recording private.
Past events should remain available to members in an organised way, not disappear into a feed.
How Xtream UI Pro helps
A camera or an encoder pushes to the platform over RTMP; the event is a live channel in the members' bouquet, watched on phones, TVs and the web player.
Each member gets a line with the membership period as its expiry; activation codes are handed out at registration, and a volunteer renews them from the panel.
Recordings become VOD entries in categories by year and by kind; a package decides which members see which library.
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
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 small server at the hall or in a data centre, one encoder in the hall, a volunteer running the panel, and members watching live or later.
Pick a part of the diagram to see what it does.
In a community deployment the sources are the hall's encoder and the recordings; the panel holds the members' lines and the library; the origin alone serves a small audience, and a node is added when the audience grows; registration happens in the panel or through a connector of the association's membership tool.
One host runs the panel and the origin; the Free plan covers a small organisation, the Professional plan a larger one.
The hall's encoder or camera pushes the event over RTMP to a live channel; the recording is uploaded afterwards.
Activation codes or lines created from the panel, with the membership year as expiry; a membership tool can do it through a connector or the API.
A node is enrolled from the panel when the audience outgrows the origin; nothing else changes for the members.
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.
| In your industry | On the platform |
|---|---|
| Live event | Live channel: a stream with its sources, EPG and output formats |
| Past events library | VOD catalogue: movies and series with seasons and episodes, categories and metadata |
| Members' programme | Bouquet: a named set of channels, films or series that a package grants |
| Member access | Line: one access with its package, bouquets, expiry, connection limit and outputs |
| Branch or section of the organisation | Partner account (reseller): a delegated dashboard with credits, permissions and its own lines |
| Membership period | Expiry date of the line, renewed by a package, a credit or the API |
Membership and donation tools are connected through a commerce connector or the Reseller API, which creates and renews member lines; webhooks tell your tool when access is created or expires. Encoders and cameras connect over RTMP. There is no native integration with a specific membership product.
Members' lines carry a connection limit; playback links are signed and expire; the recording library is visible only to lines whose package grants it. The volunteers' panel accounts use two-factor sign-in and limited permissions.
The organisation needs the rights to what it streams, including music performed at its events; the platform supplies no content and no rights. Non-profits teaching media skills may qualify for the education programme.
Content Rights & Acceptable UseHelp centre
The questions operators ask before a deployment. The help centre has the general ones.
Help centreA camera or an encoder that pushes RTMP, and a network connection to the server. The platform takes the RTMP feed as a live channel.
Yes. It is a live channel in a bouquet that only members' packages grant; viewers without a line see nothing.
The Free plan runs on your own server with a small catalogue and a limited number of lines; the Professional plan raises the limits. Both are self-hosted.
