OFFSHORE STREAMING SERVERS
Choose dedicated streaming hardware for live, VOD and IPTV workloads. Compare package-specific Port options and Unmetered Traffic, then plan an origin that delivers directly or feeds an optional CDN/edge layer.
Load model; offered capacity up to 100 Gbps.
01 / THE SHORT ANSWER
An offshore streaming server is a dedicated server used as a media origin and delivery node for live, IPTV, VOD or audio workloads. It combines dedicated hardware, package-specific network Port capacity and plan-specific traffic allowances. Your application can serve viewers directly or feed an optional distribution layer.
02 / STREAMING DELIVERY
Live feeds and prepared media arrive at the origin. Your chosen application receives, prepares or serves that content; the workflow depends on the media format and delivery protocol.
The origin can serve streams or media segments directly to viewers, or feed an optional CDN/edge layer. Port capacity supports the outgoing delivery path; a CDN service is not specified in the published server packages.
03 / AVAILABLE STREAMING SERVERS
Compare CPU, memory, storage, port capacity and traffic allowance across 18 streaming configurations. Deployment depends on stock; confirm your installation image and application requirements.
* Stock dependent.
Need a bandwidth pool across several servers? Discuss a custom configuration ↗ Pool scope and pricing require an individual enquiry.
04 / CAPACITY PLANNING
Bitrate × concurrent sessions. Delivery demand grows with the number of simultaneous viewers and the bitrate each session receives. Plan for the peak audience, not only the typical session count. For example, 1,000 concurrent sessions at 5 Mbps require 5,000 Mbps (5 Gbps) of media egress before overhead. This is a demand estimate, not a supported-viewer promise.
Leave room for the real workflow. Codec, adaptive bitrate, protocol overhead and application behavior influence actual demand. Direct delivery and CDN-assisted delivery place different loads on the origin. Validate your ingest, processing and playback together before launch.
Measure a 1 Gbps or 10 Gbps requirement ↗05 / ORIGIN & DISTRIBUTION
Direct origin delivery. Each viewer receives media from the origin. This keeps the delivery path straightforward, while simultaneous sessions share the origin’s processing, media reads and outbound Port.
An optional edge layer. A CDN can serve repeated media requests downstream. Live feeds, cache misses and non-cacheable content still require origin capacity. Select the architecture around your audience and application; confirm any additional CDN service separately.
06 / LIVE, IPTV & VOD WORKLOADS
Plan sustained concurrent sessions and ongoing egress around each channel’s bitrate and active audience. Content rights and compatible software remain part of the deployment.
Short events can concentrate demand into sudden audience peaks. Test ingest, processing and playback against the concurrency you expect before the broadcast.
Library size, read patterns and repeated media requests influence both storage and delivery. Coordinate retained capacity with the direct or edge delivery path.
Use the actual audio bitrate and session duration. Lower bitrate per listener can still produce sustained egress when many sessions stay connected.
Maintain the primary media source and its serving application. Size incoming feeds, optional processing, storage and outgoing delivery together.
Feed downstream distribution while accounting for live content, cache misses and refreshes. Viewer delivery may move to the edge; the origin still supplies the media.
Read the first second: four streams at 2.35 Gbit/s add to a 9.40 Gbit/s SUM. The four interval rates average 9.55 Gbit/s over four seconds. Compare the final sender and receiver rows, then check longer runs and the actual application; a short multi-stream test does not establish single-stream or video playback performance.
Worked values, not a WebCare360 measurement. Set IPERF_HOST to the server address supplied for an authorized test; -P 4 opens four streams and -t 4 sets four seconds.
$ iperf3 -c "$IPERF_HOST" -P 4 -t 407 / PROCESSING, TRANSCODING & STORAGE
Serve prepared media. Pass-through delivery emphasizes the network path and access to media. Assess sustained parallel transfers separately from encoding performance. A VOD library also needs sufficient retained capacity and appropriate read behavior.
Create new outputs. Transcoding adds processing work. Codec, resolution, output profiles and software influence CPU demand; compatible GPU acceleration is conditional. Neither a GPU nor a transcoding service is specified in these package lists.
Handle live ingest. Simultaneous input, processing and viewer delivery can stress different resources. Plan the complete media workflow, including software and licences, before choosing the configuration.
08 / OPERATING SYSTEMS & CONTROL
Choose an operating environment for your media application, customer-installed streaming software, monitoring and remote administration. Confirm the installation image, licence and hardware compatibility for your configuration; a listed OS does not mean a media platform is bundled.
26.04 LTS · 24.04 LTS · 22.04 LTS
Confirm installation image
13.x · 12.x
Confirm installation image
10.x · 9.x · 8.x
Confirm installation image
10.x · 9.x · 8.x
Confirm installation image
10 · 9
Confirm installation image
2025 · 2022 · 2019
Confirm licence and image
The public options also mention Fedora and custom ISO installation. Confirm the current image and installation requirements before deployment. Dedicated services are unmanaged unless otherwise agreed.
09 / OFFSHORE SERVICE CONTEXT
Plan the rights to transmit and retain your media alongside the infrastructure. You remain responsible for hosted content, application administration and lawful use. Offshore service does not remove applicable legal obligations or complaint handling under the Service Agreement.
10 / FAQ
A physical server allocated to your media workload. It can host or serve live video, IPTV channels, on-demand content or audio through software you select and administer.
The server holding or serving the primary media before delivery directly to viewers or through a downstream CDN/edge layer. Some workflows also process media at the origin.
It depends on your audience and application. Direct delivery uses the origin for viewer requests; an edge layer can distribute repeated delivery. Live feeds, cache misses and non-cacheable content still require origin capacity.
A CDN service is not specified in the published server packages. The diagrams show an optional architecture; confirm any additional delivery service separately.
More simultaneous sessions at higher bitrates require more delivery capacity. Codec, adaptive bitrate, protocol overhead and application behavior also matter. Plan for peaks and test the complete delivery path.
There is no universal viewer count. Capacity depends on bitrate, codec, protocol, concurrency, Port, processing and application overhead, and whether viewers are served directly or through a CDN.
Port describes the connection capacity. Traffic describes the transfer allowance or model. An Unmetered Traffic model does not make the Port infinitely fast.
The current catalogue includes Unmetered Traffic plans and 200TB, 300TB or 500TB allowances. Check the selected plan’s Traffic field; Port capacity and governing service terms still apply.
These are advertised workload categories. Match the hardware and software to your workflow, ensure you have the required content rights and comply with the service terms.
The package lists do not establish an included transcoder, encoder or managed media platform. Dedicated service is unmanaged unless otherwise agreed; confirm software, licences and any assistance separately.
Creating new encoded outputs adds compute work compared with serving prepared media. Requirements vary with codec, resolution, output profiles and software. A compatible GPU may help a particular workflow, but is not specified as included in these packages.
The current catalogue publishes 24–48 Hours deployment, depending on stock, and a one-month minimum term. Confirm availability and installation requirements for the selected configuration.
YOUR NEXT CONFIGURATION
Compare the configuration with your audience, media workload and delivery architecture in mind.
Talk to Our Team ↗