"What server do I need for my IPTV business?" is the most common question we get. The honest answer: it depends on workload — but there are real numbers behind the right answer. This article gives you the framework and concrete recommendations.

The four resources that matter

Every IPTV server is bottlenecked by one of four things:

  1. Bandwidth: Total throughput your network can sustain
  2. CPU: Especially if you're transcoding
  3. RAM: Holds active streams, EPG data, connection state
  4. Disk I/O: Critical if you're recording HLS chunks for catch-up

For pure restream (passthrough, no transcoding), bandwidth is almost always the bottleneck. CPU only matters when you transcode. RAM and disk become limits only at large scale.

Bandwidth math

The single most important calculation: peak concurrent viewers × average bitrate.

Typical IPTV stream bitrates:

  • SD (480p): 1.5–2.5 Mbps
  • HD (720p): 2.5–4 Mbps
  • Full HD (1080p): 4–6 Mbps
  • 4K: 15–25 Mbps

If you have 100 concurrent viewers averaging 4 Mbps each, you need 400 Mbps of sustained outbound bandwidth.

Critical word: sustained. A "1 Gbps" advertised port that throttles to 200 Mbps after 1 TB/day is not actually 1 Gbps. Read the fine print.

Use our bandwidth calculator for exact numbers given your stream mix and viewer count.

CPU requirements

If you're NOT transcoding (passthrough only)

CPU is mostly idle. A 4-core VPS can handle 1000+ concurrent passthrough connections. The work is just receiving TCP packets, segmenting HLS chunks, and serving them to clients.

If you ARE transcoding

CPU is your bottleneck. Rough estimates for software (libx264) transcoding:

  • 1080p single-rate transcode: ~2 dedicated cores per stream
  • 1080p ABR ladder (3 renditions): ~4 dedicated cores per source
  • 4K transcoding: ~8 cores per stream (use hardware acceleration)

Hardware acceleration changes the math dramatically:

  • Intel QuickSync (modern Xeon): 20–40 simultaneous 1080p transcodes
  • NVIDIA NVENC (T4/A2 GPU): 30–50 simultaneous 1080p transcodes

RAM requirements

For passthrough restream, RAM scales with active stream count, not viewer count:

  • 50 active channels: 4 GB minimum
  • 200 active channels: 8 GB
  • 1000 active channels: 16 GB
  • 5000+ active channels: 32 GB+ (and consider sharding across servers)

Add RAM for: panel database (XUI/Xtream uses 2–4 GB at scale), Memcached/Redis (1 GB), system overhead (1 GB).

Disk requirements

Without DVR/catch-up

50–100 GB SSD is enough. You're storing the OS, panel software, logs, and rolling HLS chunks (a few hundred MB).

With DVR/catch-up

Disk requirements explode. 1 day of 1080p stream archive ≈ 30 GB per channel.

  • 30 channels × 7 days × 30 GB = 6.3 TB
  • 100 channels × 7 days × 30 GB = 21 TB

This is why serious operators use separate slow-disk volumes for archives (HDD or spinning storage) and fast NVMe for the live stream cache and database.

Network considerations

Symmetric vs asymmetric

You need upload bandwidth, since streaming is inherently outbound. Some VPS providers oversell upload while advertising a high "port speed." Test with speedtest-cli at peak hours before signing a 12-month contract.

Network quality matters

Bandwidth alone isn't enough. Your customers' streams cross multiple networks:

  • Latency: Below 60 ms ideal, under 150 ms acceptable
  • Packet loss: Under 0.1% — anything more causes visible buffering
  • Jitter: Stable inter-packet timing matters more than raw speed

This is why CDN distribution (multiple edge locations) trumps a single fat server in one location for global audiences.

DDoS protection

IPTV servers get DDoSed constantly — competitors, disgruntled customers, even random script kiddies. Budget for this:

  • Up to 10 Gbps attacks: Most reputable VPS providers absorb these
  • 10–100 Gbps attacks: Need a provider with active mitigation (OVH "Game" or "Anti-DDoS Game", Path.net, Voxility)
  • Above 100 Gbps: Cloudflare Spectrum or Magic Transit, dedicated mitigation services

Concrete configurations by scale

Tier 1: 50 concurrent viewers, no transcoding

  • 4 vCPU, 8 GB RAM, 100 GB SSD
  • 1 Gbps unmetered uplink
  • ~$60–100/month (Vultr, Hetzner, OVH)

Tier 2: 250 concurrent viewers, no transcoding

  • 8 vCPU, 16 GB RAM, 200 GB SSD
  • 1–2 Gbps unmetered or 10 Gbps port
  • ~$150–250/month

Tier 3: 1000 concurrent viewers, no transcoding

  • Dedicated server: 16 cores, 32 GB RAM, 500 GB NVMe
  • 10 Gbps unmetered uplink
  • ~$400–700/month
  • Consider 2 servers + load balancer instead

Tier 4: With transcoding (any scale)

Add either:

  • Intel Xeon with QuickSync (e.g. Xeon E-2288G, ~$200/mo extra)
  • NVIDIA T4 GPU (~$300/mo extra; supports 50+ concurrent transcodes)

Tier 5: With catch-up TV / DVR

Add:

  • Multi-TB storage volume (HDD is fine; NVMe wasted on archive)
  • Separate I/O path so archive writes don't choke live serving

Provider recommendations

None of these are sponsored. Just real-world observations from running infrastructure for years:

  • Hetzner: Best price-performance for dedicated servers, mostly EU locations. Watch out for strict ToS.
  • OVH: Wide global presence, "Game" line has solid DDoS protection. Performance varies by datacenter.
  • Vultr: Reliable VPS for smaller deployments, good worldwide coverage.
  • DigitalOcean / Linode: Premium-priced but high quality. Good for panel servers, less ideal for high-bandwidth streaming.
  • QuadraNet / Path.net: Specialty IPTV/streaming hosts; expensive but won't kick you off for high traffic.

Avoid: $5/mo VPS deals (oversold), AWS/GCP for streaming (egress fees will bankrupt you), unlimited-bandwidth offers (always have a hidden cap).

Don't forget the panel server

Your panel (XUI.ONE, Xtream Codes) often runs on a separate server from your stream server, especially at scale. The panel handles:

  • Customer authentication
  • EPG data
  • API requests
  • Admin interface

Panel servers need less bandwidth (most traffic is API JSON, not video) but benefit from low latency to your customer base. Many operators put the panel on a small US-East server even if their stream servers are in EU/Asia, because their customer base is US-heavy.

Quick decision tree

  • < 50 viewers, just starting → 1 mid-size VPS, no transcoding, ~$80/mo
  • 50–500 viewers, growing → Beefier VPS or entry dedicated, ~$200/mo
  • 500–2000 viewers → Dedicated server with 10 Gbps, ~$500/mo
  • 2000+ viewers → Multiple servers + load balancer + CDN, ~$1500+/mo
  • Don't want to manage any of this? → Managed restream from $149/mo

The honest pitch

Self-hosting starts cheaper but real total cost — including DDoS protection, monitoring, replacement parts when something breaks at 3 AM — usually crosses managed service pricing around the 200-customer mark. Past that, managed almost always wins on TCO. Run the math for your specific situation.