Home
XtreamUIPro

Media & Content Creators

Your own channel, sold to your own audience

The studio runs a channel around the clock and a library of its shows, supporters subscribe through the studio's shop, and affiliates sell access from partner accounts — with the audience and the revenue staying yours.

A film crew setting up a professional camera in a studio.
Photo: Mico Medel · Pexels License

The challenges

What a creator has to solve

  • An audience held by someone else

    On a public platform the audience, the terms and the revenue belong to the platform, and the studio cannot take its viewers with it.

  • Supporters who pay monthly

    A subscription must open the library on payment, hold it while paid and close it when the supporter stops, without anyone handling accounts.

  • A catalogue that keeps growing

    New episodes arrive every week, old seasons go to back catalogue, and a channel should keep running between releases.

How Xtream UI Pro helps

How the platform fits

  • A channel and a library

    The studio's playout feeds a live channel that runs all day; shows are series with seasons and episodes in categories, grouped into bouquets that a package grants.

  • The shop creates the supporters

    A connector for the studio's shop (WooCommerce, Shopify and others) or the Reseller API creates a line when a supporter subscribes and renews it on each payment.

  • Affiliates as partner accounts

    An affiliate or a distributor is a partner account (reseller) with credits and its own lines, so it can sell access without touching the catalogue.

Platform capabilities

What this industry uses

The capabilities below are the ones this deployment relies on. Each is in the product today; nothing here is planned or on request.

  • Live streaming

    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

  • Video on demand

    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

  • Subscriber management

    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

  • Partner management

    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

  • API & integrations

    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

  • Security & access control

    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

The pages this deployment lives in

Screenshots of the dashboard of a fresh installation with the sample catalogue. Nothing is mocked up.

The Streams page of the dashboard: the live channels with their status, category, source and output formats.
Live streaming · Origin hub with one upstream per channel · RTMP in and out · ffmpeg transcoding
The Movies page of the dashboard: the films of the catalogue with their category, year and status.
Video on demand · Signed, time-limited playback links · per-node VOD cache

Infrastructure architecture

Example deployment: a production studio

A management server, a 24/7 channel from the studio's playout, a library of shows, supporters subscribing through a WooCommerce shop, and affiliates with partner accounts.

Pick a part of the diagram to see what it does.

In a creator deployment the sources are the studio's playout encoder and the finished episodes; the panel holds the library, the packages and the supporters' lines; the origin serves the audience, with nodes added in the regions where it grows; the shop connects through a connector, and affiliates through partner accounts.

  1. Install the platform

    One server runs the panel, the API, the worker and the origin; the studio's staff get partner accounts with their own permissions.

  2. Publish the channel and the shows

    The playout pushes over RTMP to a live channel; each show is a series with seasons and episodes; bouquets group the channel and the shows by tier.

  3. Connect the shop

    The WooCommerce connector creates a line when a supporter subscribes, with the billing period as expiry, renews it on each payment and disables it on cancellation.

  4. Bring in the affiliates

    Each affiliate gets a partner account with credits and a package at its own price; its sales appear as lines under that account.

Configuration mapping

Your concepts, the platform's objects

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.

Step-by-step setup guide

Prerequisites, installation, the channel and the shows, supporters from the shop, affiliates, expiry and troubleshooting, step by step.

Read the setup guide
In your industryOn the platform
The studio's channelLive channel: a stream with its sources, EPG and output formats
Show libraryVOD catalogue: movies and series with seasons and episodes, categories and metadata
Subscription tierBouquet: a named set of channels, films or series that a package grants
Supporter accessLine: one access with its package, bouquets, expiry, connection limit and outputs
Billing periodExpiry date of the line, renewed by a package, a credit or the API
Affiliate or distributor accountPartner account (reseller): a delegated dashboard with credits, permissions and its own lines
Shop or membership integrationReseller API and webhooks: the operations of the panel from your own system

Integration considerations

Commerce platforms with a ready connector (WooCommerce, Shopify, PrestaShop, Odoo and others) create and renew supporters' lines on payment; any other system uses the Reseller API and webhooks. Encoders connect over RTMP. There is no native integration with a specific creator-membership product.

Security considerations

A connection limit per line keeps a subscription from being shared; playback links are signed and expire; an affiliate's partner account sees only its own lines; the studio's accounts use two-factor sign-in, permission groups and the audit log.

Content rights and licensing

The studio needs the rights to everything it publishes, including music, guests and archive material; the platform supplies no content and no rights. Standard plans apply.

Content Rights & Acceptable Use

Help centre

Questions from this industry

The questions operators ask before a deployment. The help centre has the general ones.

Help centre
Can supporters pay through our own shop?

Yes. The shop's connector or the Reseller API creates the supporter's line on payment and renews it each period; the platform does not take payments itself.

Can we run a channel around the clock?

Yes. A live channel from your playout runs continuously; shows of the library can also be offered on demand next to it.

Can affiliates sell access without seeing our catalogue settings?

Yes. A partner account holds credits and its own lines, and its permission group limits it to selling; it is a delegated account, not an isolated tenant.