Telecom & ISPs
Your subscribers get a channel line-up and a VOD library delivered from nodes in your points of presence. Their lines are created and renewed from your billing, and dealers sell with credits in their own dashboards.
The challenges
A television offer has to be sold, billed and cancelled with the internet plan, not run as a separate system with its own accounts.
A line-up served from a distant data centre loads the upstream link and shows in quality; delivery should start close to the subscriber.
Regional dealers sell and support the service, and each plan limits how many screens a household may use at once.
How Xtream UI Pro helps
A package per subscription tier grants its bouquets and carries a duration; your billing creates, renews and disables the subscriber's line through a connector or the Reseller API.
Nodes are enrolled from the panel and installed over SSH; each takes a live channel once from the origin, caches the VOD library and serves the subscribers routed to it.
A dealer is a partner account (reseller) with credits, a permission group and its own lines; sub-resellers can mirror a dealer network, and the connection limit is set per subscription.
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
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
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 operator's core site, a node in each point of presence, a channel line-up and a VOD library, subscriber lines driven by the ISP's billing, and dealers as partner accounts with credits.
Pick a part of the diagram to see what it does.
In an operator deployment the sources are the licensed channel feeds and the VOD library; the panel holds the packages, the bouquets, the subscribers' lines and the dealers' credits; the origin and a node per point of presence serve the subscribers; billing connects through a connector or the Reseller API.
The panel, the API, the worker and the origin run on the operator's servers; the playback base is the address subscribers reach, and a node is enrolled for each point of presence from Servers.
Bouquets for the basic line-up, premium channels and the VOD library; one package per subscription tier with its duration and its price in credits.
WHMCS, Odoo or another connector, or the billing's own calls to the Reseller API, create a line when a subscription starts, renew it each period and disable it when it is cancelled.
Each regional dealer gets a partner account with credits and a group that limits it to lines; the dealer's sales spend the credits of the package.
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 in the core site and the points of presence, plans, billing integration, dealers, security and troubleshooting, step by step.
Read the setup guide| In your industry | On the platform |
|---|---|
| Dealer or regional partner account | Partner account (reseller): a delegated dashboard with credits, permissions and its own lines |
| Channel tier or add-on pack | Bouquet: a named set of channels, films or series that a package grants |
| Television channel | Live channel: a stream with its sources, EPG and output formats |
| VOD library | VOD catalogue: movies and series with seasons and episodes, categories and metadata |
| Subscriber's television access | Line: one access with its package, bouquets, expiry, connection limit and outputs |
| End of the billing period | Expiry date of the line, renewed by a package, a credit or the API |
| Screens per subscription | Max connections of the line: how many devices may watch at once |
| Billing and provisioning integration | Reseller API and webhooks: the operations of the panel from your own system |
| Point-of-presence node | Streaming nodes: edge servers enrolled from the panel, one per site or building |
Billing connects through the open-source connectors that install on the operator's side (WHMCS, Blesta, WISECP, HostBill, ClientExec, FOSSBilling, Paymenter, Odoo and others) or through the Reseller API and webhooks; there is no native integration with a specific OSS or BSS product beyond those connectors, and no single sign-on for viewers.
Subscribers' lines carry a connection limit and can be bound to an address, a country or an ISP; playback links are signed and expire; behind a reverse proxy, TRUSTED_PROXIES keeps the real address in the logs and IP rules; panel accounts use two-factor sign-in, permission groups and Admin API keys with an IP allow-list; the audit log and encrypted backups complete it.
The operator needs the rights to every channel and title it carries to its subscribers; the platform supplies no content and no rights. Standard plans apply; an Enterprise engagement adds integration work and an SLA.
Content Rights & Acceptable UseHelp centre
The questions operators ask before a deployment. The help centre has the general ones.
Help centreYes. A package per tier and a connector or API calls from your billing create the line when the subscription starts and disable it when it ends.
Seventeen open-source connectors cover systems such as WHMCS, Blesta, HostBill, FOSSBilling, Odoo and others; any other system uses the Reseller API and webhooks. There is no connector for proprietary BSS products.
A dealer is a partner account with credits and its own lines, optionally with sub-resellers below it. It is a delegated account, not an isolated installation.
