An infrastructure plan for licensed channels
Streaming resources for authorised IPTV applications and distribution rights.
Content revised · English
- Architecture to evaluate
- Licensed live / VOD / distribution
- Prepared starting points
- 5 plans
- Responsibilities
- Application, rights and recovery
A fit shortlist, not installed software or live inventory.
Keep these in view.
- Licensed live / VOD / distribution.
- Compute the actual delivery budget.
- Keep tokens and control endpoints narrow.
Licensed live / VOD / distribution
Confirm rights for each channel, programme, audience and region before configuring delivery. An infrastructure product does not supply content licences or a merchant payment integration. Define complaint handling and authorised access as part of the platform.
Compute the actual delivery budget
A theoretical 250 simultaneous streams at 4 Mbps consume 1 Gbps before margin. Live ingest, transcode and HLS output are separate stages, while VOD adds storage and cache design. A hot library and a colder storage tier need a tested connection between them.
Keep tokens and control endpoints narrow
Use expiring playback authorisation where appropriate, restrict the panel and avoid public administrative credentials. Track origin load and playback errors, then test recovery with the licensed content subset. A faster port cannot correct a rights or authentication problem.
Rights determine the service
Only distribute channels and recordings for which you have permission. A server location or a hosting label does not remove licensing, territorial or content obligations.
Estimate delivery carefully
Concurrent viewers, target bitrate and transcoding variants drive network demand. Separate the media origin, authentication and playlist delivery so access control remains manageable.
Protect continuity
Monitor ingestion and viewer failures, retain essential configuration and document a recovery path. Validate permitted use and bandwidth conditions before choosing a streaming plan.
Capacity to consider.
Match these starting points to the representative application. Software installation and live inventory are not connected; the exact specification and period total come from the catalogue.
Horizon 10
Deliver an authorised live channel or video service with four EPYC virtual CPUs, 8 GB of ECC memory and 200 GB of NVMe storage. The configuration includes 10 TB of monthly transfer, NGINX-RTMP and FFmpeg stack options, an OBS relay workflow and SRS or Wowza setup assistance.
- Compute
- 4 vCPU (EPYC)
- Memory
- 8 GB DDR4 ECC
- Storage
- 200 GB NVMe SSD
- Transfer
- 10 TB / month
billed monthly
Horizon 25
Increase video storage and delivery capacity to eight EPYC virtual CPUs, 16 GB of ECC memory, 500 GB of NVMe storage and 25 TB of monthly transfer. NGINX-RTMP, FFmpeg and a Wowza trial are the listed stack choices, with an 80 Gbps network mitigation tier.
- Compute
- 8 vCPU (EPYC)
- Memory
- 16 GB DDR4 ECC
- Storage
- 500 GB NVMe SSD
- Transfer
- 25 TB / month
billed monthly
Eclipse Ryzen
Use a dedicated Ryzen 9 5950X with 16 physical cores, 32 threads and 64 GB of ECC memory for compute-intensive services. Two 1 TB NVMe drives in RAID-1 provide mirrored storage, with IPMI access, a 1 Gbps port and 50 TB of monthly transfer.
- Compute
- AMD Ryzen 9 5950X (16c / 32t @ 3.4 GHz)
- Memory
- 64 GB DDR4 ECC
- Storage
- 2× 1 TB NVMe (RAID-1)
- Transfer
- 50 TB / month
billed monthly
Eclipse EPYC
Consolidate larger workloads on a physical EPYC 7443P server with 24 cores, 48 threads and 128 GB of ECC memory. Two 2 TB NVMe drives in RAID-1 pair with a 10 Gbps uplink, 100 TB of monthly transfer and a 200 Gbps network mitigation tier.
- Compute
- AMD EPYC 7443P (24c / 48t @ 2.85 GHz)
- Memory
- 128 GB DDR4 ECC
- Storage
- 2× 2 TB NVMe (RAID-1)
- Transfer
- 100 TB / month
billed monthly
Eclipse Dual
Reserve two Xeon Gold 6338 processors for a total of 64 physical cores and 128 threads, supported by 256 GB of ECC memory. Four 4 TB NVMe drives form RAID-10, with a 10 Gbps port, unmetered transfer and a 400 Gbps network mitigation tier for large parallel workloads.
- Compute
- 2× Intel Xeon Gold 6338 (32c / 64t each)
- Memory
- 256 GB DDR4 ECC
- Storage
- 4× 4 TB NVMe (RAID-10)
- Transfer
- Unmetered
billed monthly
Before this workload goes live.
- Check the exact plan’s CPU, memory, disk, transfer and port.
- Choose a listed region and verify the workload’s permitted use.
- Test the representative application and an independent restore.
Questions, answered.
Are particular IPTV panels included or approved?
No panel is installed. Any application must be maintained, licensed where required and operated with the appropriate content and audience rights.
How much bandwidth do concurrent viewers use?
Multiply concurrent viewers by their chosen bitrate, then add overhead and margin. Around 250 viewers at 4 Mbps reaches 1 Gbps before margin; watch time determines the period volume.
Can merchant payments be bundled?
No merchant processor is connected. Hosting payment options are separate from a platform’s payments to its viewers.
Can live and VOD share the same plan?
They can be designed together only after budgeting ingest, transcode, storage, cache and output. A larger cold library may need a separate storage tier and tested data path.
What is kept in my account workspace?
Your configuration, selected plan, image, location and billing term are kept with the order and payment request references. Quotes, payment-state reads and support conversations remain linked to your account. Read fulfilment details separately from payment status.