Public Sector
A council session goes out live and stays in the archive, staff training is a library by department, and the public receives a line with a long expiry from the institution's website. The video stays on infrastructure the institution runs.
The challenges
Meetings are broadcast and then have to stay available for residents, in an archive the institution holds, not only on an outside platform.
Residents watch open sessions and information, while staff use training and internal briefings that must not be public.
Procurement and data-protection rules often ask where the service runs and who administers it, and a hosted service raises the question every time.
How Xtream UI Pro helps
A session is a live channel fed by the chamber's encoder; with catch-up enabled late viewers can rewind, and the recording is filed as an episode of the sessions series.
Residents get a line with a long expiry from the institution's website; staff get lines by department with their own packages and bouquets, so training and internal briefings stay out of the public line-up.
The panel, the origin and the nodes run on servers the institution chooses, with two-factor sign-in, permission groups, an audit log and encrypted backups for its own operators.
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
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
Connection and traffic views, audit logs, Prometheus metrics, alerts by mail, Telegram or webhook, maintenance mode and a built-in update check.
/metrics endpoints · job queue with leases · encrypted database backups
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 in the council's data centre, the chamber's feed as a live channel with a kept archive, a staff training library by department, public lines with a long expiry, and the council's own systems on the Reseller API.
Pick a part of the diagram to see what it does.
In a public-sector deployment the sources are the chamber's live feed, the recordings of past sessions and the training videos; the panel holds the public and the staff bouquets and the lines of both audiences; the origin serves them, with nodes where a site needs one; the council's systems connect through the Reseller API.
The panel, the API, the worker and the origin run on a council server behind its reverse proxy; the playback base is the public address residents reach.
The chamber's encoder pushes a live channel in the public bouquet; the recording becomes an episode in a series per body, such as the full council and committees.
Residents receive a line with a long expiry handed out on the council's website, bound to the public bouquet only.
Staff get lines per department with packages that add the training library and internal briefings; the council's own systems create and disable them through the Reseller API.
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 on the institution's servers, live sessions and archive, public and staff access, security and troubleshooting, step by step.
Read the setup guide| In your industry | On the platform |
|---|---|
| Council session or public channel | Live channel: a stream with its sources, EPG and output formats |
| Session archive and training library | VOD catalogue: movies and series with seasons and episodes, categories and metadata |
| Public programme or department collection | Bouquet: a named set of channels, films or series that a package grants |
| Resident or staff access | Line: one access with its package, bouquets, expiry, connection limit and outputs |
| Validity of a public or staff access | Expiry date of the line, renewed by a package, a credit or the API |
| Council system integration | Reseller API and webhooks: the operations of the panel from your own system |
The institution's own systems, such as its website, its staff directory or its case system, connect through the Reseller API (create, renew, disable a line) and webhooks; the panel has no native integration with a specific public-sector product and no single sign-on for viewers.
Keep the platform on the institution's own infrastructure behind its reverse proxy with TLS; keep public and internal material in separate bouquets; lines carry a connection limit; playback links are signed and expire; panel accounts use two-factor sign-in, permission groups and Admin API keys with an IP allow-list; the audit log records every change.
The institution needs the right to publish the sessions and any third-party material in its training library; 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 centreViewers always use a line. The council can hand out a line with a long expiry from its website, bound to the public bouquet, so residents receive credentials and need no further account.
Yes. Put it in bouquets that only the staff packages grant; a line sees only the bouquets of its package, so the public line never receives the training library.
The recording is added to the catalogue as an episode and stays until the institution removes it; it is the institution's file on its own server, and the retention is the institution's decision.
