Your media stack
Existing origins, streaming servers, CDN, applications, and payment gateway can stay in place.
Business Management
Operate your streaming service from source to subscriber.
Manage how live content is sourced, published, sold, and delivered, together with the subscribers, devices, payments, and analytics behind it. Use your own streaming infrastructure, CloudTV products, or both.
- One record
- Across business and product views
- Flexible stack
- Your infrastructure, ours, or both
Business workflowOne connected operating model
Configured
Starting point
Live content
Own sources · Connected media products
OPERATIONS
Customers Devices Usage Sales Revenue analytics
One platform, clear product boundaries
Keep what works. Connect what the service needs.
Business Management organizes the service. Media processing, live delivery, and native playback remain separate products that you enable only when a route needs them.
Business Management
- Content & offers
- Customers & subscriptions
- Devices & access
- Sales & analytics
CloudTV products
Live Media Core, Global Edge CDN, Live Subtitles, and Native SDK & Applications connect through the same content record.
CloudTV PlatformAccountEnabled productsConfigurationUsage & CloudTV billing
From source to viewer
Configure each live service in one place.
Add one or more source addresses, or create a push input. Keep the stream direct, or run it through Live Media Core when you need processing, subtitles, or additional outputs. Then decide how viewers receive it and who can watch.
Products enabled in this example
- RequestViewer
- AccessAuthorization
- EntryCloudTV entry
- DeliverySelected CDN edge
Active sourcePrimary pull sourceReceiving now · Backup 01 ready · Backup 02 ready
Media routeLive Media CoreTranscoding, subtitles, and compatible outputs are available.
Playback addressCloudTV entry URLThe stable viewer entry resolves the active delivery path.
Common playback outputsHLS · DASH · HTTP-TS · FLV · fMP4 · RTMP · SRT · WebRTC · RTSPCommon outputs shown. The complete protocol set and protected variants depend on the enabled products and route.
The original source remains the viewer destination.
The unified entry resolves the current source; media does not enter a CDN edge.
The live output is served from the edge receiving and processing that stream.
Viewer location, edge health, and load determine the delivery edge.
Content and commercial structure
Organize content first. Build plans around it.
Packages organize content. Plans define what customers buy.
Live content
Source · media path · publishing · access · playback
PublicAvailable without a subscription
Subscription routePackage → Plan
Group related content
Organize one or more live services for use in offers.
Define what customers buy
- One or more packages
- Price & subscription period
- Concurrent device limit
- Subscription rules
- Optional trial policy
Direct or reseller sales
Every paid or trial activation becomes a customer subscription.
- Package
- A group of related live content used by one or more Plans. Not a pricing plan or access credential.
- Plan
- The offer a customer buys, including Packages, price, subscription period, concurrent access, rules, and optional trial policy.
- Subscription
- A customer’s active, paid, granted, or trial Plan with start, expiry, and status.
- Customer
- The viewer account, including trial eligibility and subscription history.
- Viewer access
- The credential used by an SDK, App, API integration, or personalized M3U.
Follow the relationshipsOpen any record to see what stays connected.
Content record
- Packages containing this content
- Public content can be available without a subscription
- Protected content continues through Package, Plan, and Subscription
Package
- Included live services
- Referenced by Plans
- Not a pricing plan or access credential
Plan
- Packages included
- Price and subscription period
- Concurrent device or session limit
- Subscription and optional trial policy
- Direct and reseller sales
Sell and activate access
Sell plans wherever your audience already is.
Let resellers activate access, connect your own storefront through the API, use a hosted subscription page, or sell inside your SDK or branded application.
STARTPlanPackages · price · period · device limit · optional trial
Reseller activation
A reseller provisions the viewer’s subscription directly.
Your website or platform
Complete checkout in your storefront, then activate through the CloudTV API.
Hosted subscription page
Offer a ready subscription path connected to your selected plans.
SDK or branded application
Let viewers subscribe inside the application they already use.
Optional trial
Create a trial subscription when the Plan allows it and the customer is eligible.
All enabled routes create a Subscription
SUBSCRIPTIONCustomer entitlementStart · expiry · status · trial or paid
ACCESS POLICYConcurrent device & session limitsApplied from the selected Plan
VIEWER ACCESSSDK · App · API · Personalized M3UOne entitlement, multiple supported access paths
Coupons and promotions
Apply campaign rules to eligible Plans across your supported checkout paths.
Connect your payment gateway and manage subscriber transactions from the same workspace.
Customer and device operations
Manage the relationships behind every subscription.
Keep the customer, the Plan they can use, their active Subscription, registered devices, and the sales channel that created or renewed access connected in one operating record.
Customer profiles and subscription history
- Contact and account details
- Current, previous, trial, and expired Subscriptions
- Trial eligibility and access status
- Orders and customer gateway transactions
Approve, disable, transfer, and group devices
- Registration, activation, approval, and owner
- Last activity, client version, location, and device details
- Device transfer and operational history
- Plan device limits and concurrent access policy
CONNECTED OPERATING RECORD
CustomerViewer account
SubscriptionPlan · start · expiry · status
EntitlementContent · devices · access
Reseller accounts and sales performance
Let authorized resellers create or renew customer access while the service owner keeps Plans, customer relationships, and reporting visible.
- Reseller accounts and operating permissions
- Available Plans and customer activation
- Direct versus reseller orders and renewals
- Subscriber, sales, revenue, and Gross profit reporting
Configuration at the right level
Set defaults once. Change only the exceptions.
Apply common publishing, access, and playback settings across your service. When a live stream needs a different route or policy, its content-level settings take precedence.
Highest priorityContent settingGlobal defaultPlatform default
Campus lecturesInherits publishing and access defaults
InheritedPremium live eventOverrides CDN and authorization
2 overridesPartner feedOverrides media path and playback options
2 overridesConfiguration cannot bypass product subscriptions. Proxy still requires Live Media Core; CDN publishing still requires Global Edge CDN.
Connected product views
Create the content record once.
Configure media and publishing from the business workflow, then use each product view for its specialist controls and operating state. The record stays connected across the platform.
The same content record appears in every enabled product view. Product-specific controls remain in their specialist view; the record does not need to be created again.
Application operations
Operate the applications your viewers use.
Devices using a compatible Native SDK, Generated App, or connected Custom Application register to the same customer workspace. Business Management connects app configuration and communication with the customer, subscription, content, and device records that already run the service.
ONE CUSTOMER WORKSPACE
Every compatible client shares the business connection it needs.
Generated AppCommon connection plus full platform management
Native SDKCommon connection and selected APIs only
Custom ApplicationCommon connection plus an agreed management scope
Common platform connection
Identity, devices, subscriptions, content, and access.
This is the shared foundation. Native SDK and customer-managed applications can stop here and keep their existing interface, operations, and release system.
Platform-managed application operations
Enable only where the deployment allows platform control.
- Generated App Included
- Custom Application Optional
- Native SDK Customer-managed
Brand and client configuration
Set the app name, icon, splash and banner artwork, language, contact details, purchase link, layout, and visible features.
Branding · languages · layouts · feature visibilityContent and audience communication
Publish help, announcements, and promotions. Dynamic splash and campaign content can change without rebuilding the app; messages can target a device, group, or audience.
Help · announcements · promotions · messagingDevice and access operations
Manage registration, ownership, groups, access state, and the device or concurrent-session rules inherited from each customer’s Plan.
Registration · ownership · groups · access policyRelease and update control
Track customer-specific builds, versions, release notes, and automatic or required updates while preserving customer signing and release control.
Build status · versions · release policy · updatesApplication analytics
Follow downloads, new registered devices, client versions, acquisition source, and geographic distribution for each application.
Downloads · devices · versions · source · regionChoose the management boundary
Use the same platform without forcing every application into the same operating model.
Platform-managed lifecycle
Generate a branded application from the platform, typically in about five minutes after its build configuration is complete.
About five minutes covers the first generated build. Testing, signing, customer approval, app-store review, and publication are separate steps.
- Platform operates Client configuration, audience content, registered devices, and update policy
- Customer controls Brand choices, signing, approval, and release timing
- Best fit Launching without a separate application backend
Keep your existing app operations
Connect identity, devices, access, and the business APIs you need without moving the rest of your application operations.
- Platform provides Selected identity, device, entitlement, content, and subscription services
- Customer controls Interface, app content, operations, build, and release
- Best fit Adding CloudTV capabilities to an established application
Choose where operations live
Run the application through Business Management, or connect core access and device services while your own platform manages the experience.
- Platform provides The complete operating model or an agreed subset
- Customer controls The remaining operations and release responsibilities defined by the project
- Best fit Commissioned or in-house applications with specific workflows
- 01CloudTV client core updateCompatibility and core capabilities advance.
- 02Customer-specific buildYour branding and configuration are applied.
- 03Customer release or app-store processSigning, approval, and publication remain respected.
- 04Registered devices updateCompatible clients receive the released version.
Operations and built-in analytics
See the service and the business as they run.
Use the current operating state to handle today’s service, then use period-based analytics to understand viewing, customers, sales, offers, and application distribution over time.
What needs attention now.
Current state and operational records for the service your team is running.
Sources and delivery
Primary and backup source state, automatic failover, Direct or Proxy path, enabled outputs, CDN publishing, authorization, and Public status.
Sessions and devices
Current and concurrent viewing, authorization results, active devices, customer entitlement, and applied device limits.
Subscriptions and transactions
New and renewed access, reseller activations, customer payment-gateway transaction history, refunds, and current Subscription status.
Playback and client signals
Slow or broken playback feedback, source interruptions, fallback events, device activity, and the client version currently in use.
Built-in business analytics
Measure change over days, periods, products, sales channels, applications, and regions.
| Analytics view | What it answers | Measures and breakdowns |
|---|---|---|
| Content and playbackViewing analytics | Which live services people watch, where playback happens, and where the viewing experience needs attention. |
|
| Customers and devicesSubscriber and device analytics | How the viewer base changes over time and how subscribed and non-subscribed devices use the service. |
|
| Subscriptions and salesSales and subscription analytics | Which offers and sales channels generate orders, renewals, revenue, and Gross profit. |
|
| Offer performancePackage and Plan analytics | Which content combinations and commercial Plans attract, retain, or lose subscribers. |
|
| Applications and distributionApplication and distribution analytics | How each application reaches new viewers and which client versions remain active in the field. |
|
Compare byPeriodLive servicePackage or PlanSales channelApplication versionCountry or region
Your service, your stack
Bring your streaming service together.
Tell us what you already run and what you need to operate next.