Bring the stream closer to its audience
A practical base for licensed live video, on-demand media and transcoding.
Content revised · English
- Architecture to evaluate
- RTMP / SRT → transcode → HLS / DASH
- Prepared starting points
- 5 plans
- Responsibilities
- Application, rights and recovery
A fit shortlist, not installed software or live inventory.
Keep these in view.
- RTMP / SRT → transcode → HLS / DASH.
- Calculate concurrent output and the period total.
- Protect both the rights and the playback path.
RTMP / SRT → transcode → HLS / DASH
Separate ingest, transcoding, delivery and storage. RTMP or SRT can feed a worker; FFmpeg-style processing prepares renditions, and HLS/DASH segments are delivered to viewers. A cache or CDN can be evaluated separately; none is connected by this local product page.
Calculate concurrent output and the period total
250 viewers at 4 Mbps consume a theoretical 1 Gbps before protocol overhead and safety margin. A 25 TB monthly transfer allowance is another constraint, even on a faster port. Size for the bitrate ladder, concurrent viewers and watch hours rather than a single attractive bandwidth figure.
Protect both the rights and the playback path
Confirm rights for each region and audience, use appropriate access tokens and protect administration. Track buffering, segment errors and origin load. Keep a takedown-response process and a recovery copy for assets you have permission to distribute.
Estimate the output
Concurrency multiplied by bitrate gives an initial bandwidth estimate. Add room for protocol overhead, several renditions and bursts, then compare the result with the plan's port and transfer allowance.
Separate the jobs
Ingestion, transcoding, origin delivery and viewer distribution are distinct tasks. A GPU can help supported encoding workloads, while storage and network capacity determine how content is retained and delivered.
Make delivery observable
Monitor dropped frames, buffering, segment creation and playback errors. Hold distribution rights, secure management interfaces and keep a recovery copy of content you cannot recreate.
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 HLS or DASH outputs configured automatically?
No media software is installed by the order. Ingest, transcode, packaging and delivery must be configured on a compatible production stack.
Can a CDN reduce origin load?
It can when cacheability, tokens and the provider’s policy fit the workload. It is a separate contract and configuration; no CDN is connected here.
Are IPTV and adult streams automatically permitted?
Each needs its own rights, audience and applicable-law review. The proposed AUP excludes unlawful material; a streaming plan does not provide licences or consent records.
How should I read the streaming transfer limit?
Check port speed and monthly volume separately. A fast output can exhaust a quota quickly; the plan’s exact specification controls the prepared capacity.
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.