Fitness & Wellness
A class goes out live from the studio, the recording joins a library by instructor and programme, and a member's access follows the membership your shop sells — on servers the studio runs, with the audience staying yours.
The challenges
Members want the live schedule and the recordings at home, and the studio wants that audience on its own service, not a public platform's.
A membership bought, paused or cancelled in the studio's shop should open, hold and close the video access without manual work.
A chain needs each studio to stream its own classes while sharing one library and one membership system.
How Xtream UI Pro helps
Each studio pushes its live class over RTMP to a channel; a schedule of channels is a bouquet, and a programme is a package of bouquets.
A connector for your commerce platform (WooCommerce, Shopify and others) or the Reseller API creates the member's line on purchase and renews it on each payment.
Recorded sessions are VOD entries in categories by instructor and by programme; each studio is a partner account that manages its own schedule.
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
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
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 management server at the head office, each studio pushing its classes, the chain's shop driving memberships, and members watching on phones and TVs.
Pick a part of the diagram to see what it does.
In a fitness deployment the sources are each studio's live encoder and the recorded sessions; the panel holds the library and the members' lines; the origin serves the audience, with a node added for a large chain; the commerce platform connects through a connector or the API.
One server runs the panel, the API, the worker and the origin; each studio gets a partner account with its own permissions.
One live channel per studio room, pushed over RTMP; bouquets per schedule and per programme; recordings uploaded into the library.
The commerce connector creates a line on purchase with the membership as expiry, renews it on payment and disables it on cancellation.
Members use a player app on their phone or TV, or the web player; a connection limit per line keeps a membership personal.
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 class | Live channel: a stream with its sources, EPG and output formats |
| Recorded sessions | VOD catalogue: movies and series with seasons and episodes, categories and metadata |
| Schedule or 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 |
| Membership period | Expiry date of the line, renewed by a package, a credit or the API |
| Commerce or membership 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 purchase; any other system uses the Reseller API and webhooks. Encoders connect over RTMP. There is no native integration with a specific gym-management product.
A connection limit per line keeps a membership from being shared; playback links are signed and expire; studios' partner accounts see only their own members and schedule; head-office accounts use two-factor sign-in and the audit log.
The studio needs the rights to the music and the material in its classes and recordings; 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 centreYour shop's connector or the Reseller API creates the member's line on purchase and renews it on each payment; the member signs in to the player with the credentials the shop sends.
Yes. Each studio is a partner account with its own permissions and dashboard; the head office keeps the library and the memberships.
A player app on their phone or TV that speaks the Xtream Codes API or M3U, or the web player in a browser. No custom app is required.
