Advertise Launch My TV Channel

Self-Host Your Live Streams on a Budget

Skip managed CDN costs. Use a cheap dedicated server with generous bandwidth to serve HLS streams directly to your viewers. Here is what to rent, how much bandwidth you really need, a working nginx configuration, and when a managed 24/7 channel is the better deal.

Updated 29 October 2026 · My TV Channel

Why self-hosting HLS is cheap

HLS (HTTP Live Streaming) is a playlist file plus a stream of small video segments, each a few seconds long. A player downloads the playlist, then the segments, one after another. To the server, a live stream is just static files that change every few seconds. That means you do not need a media server, a transcoding cluster or a per-minute streaming plan. You need a web server and enough bandwidth.

Managed platforms charge for the convenience of the encoding, the delivery and the per-gigabyte egress. If you do the encoding yourself, on your own computer, the only cost left is the delivery. A flat-rate server with unmetered bandwidth turns that cost into a fixed monthly bill, with no overage surprise when a stream goes well.

What you need

The app pushes HLS segments to your server with HTTPS PUT. nginx serves them to viewers. That's it.

Server providers compared

We compared the most cost-effective providers for streaming workloads. Bandwidth is the biggest cost factor. Prices are entry prices from our research in 2026 and change often, so check the provider's site before you order.

Truly unmetered bandwidth

ProviderFromBandwidthPort speedLocationsNotes
Scaleway Dedibox€4.99/moUnmetered100–500 MbpsParis, AmsterdamCheapest entry point. Pro range from €34.99
OVHcloud Kimsufi$20/moUnmetered300–500 MbpsFrance, Canada, Germany, UK, US, Australia, SingaporeBest value. Anti-DDoS included
OVHcloud SoYouStart$30/moUnmetered500 Mbps–2 GbpsSame as KimsufiMid-tier with more RAM and CPU
OneProvider~$15/moUnmetered (fair use)1 Gbps40+ locations worldwideReseller, widest geographic coverage
Psychz Networks~$49/moUnmetered1 GbpsUS, Europe, Asia, Africa, AustraliaGood for non-European audiences

Metered but affordable

ProviderFromIncluded trafficOverageLocationsNotes
Hetzner Dedicated~€37/mo“Unlimited” on 1G (fair use)Warnings, then throttleGermany, FinlandGreat hardware, but not truly unmetered. Cloud plans: 20 TB, then €1.20/TB
Hetzner Auction~€25/moSame fair-use policySameGermany, FinlandRefurbished servers, good deals if you can get one

A note about Hetzner: their dedicated servers are marketed with "unlimited" traffic, but a fair-use policy applies. If you saturate the connection for long periods they will contact you and may throttle. Their cloud servers have a 20 TB monthly allowance with overage at €1.20/TB. Great hardware and pricing, as long as you know the limits.

How to choose

Bandwidth: the only number that matters

The maths is short. Concurrent viewers multiplied by the bitrate they watch gives the port speed you need. Hours multiplied by that gives the monthly traffic. For a 4 Mbps stream (720p or 1080p):

Average concurrent viewers, 24/7Port loadTraffic per month
14 Mbps~1.3 TB
520 Mbps~6.5 TB
1040 Mbps~13 TB
25100 Mbps~32 TB

Events work the other way round. A two-hour match with 200 viewers needs 800 Mbps at its peak but only about 720 GB in total. For occasional events, port speed is the limit. For an always-on stream, the monthly traffic is. An unmetered server covers both.

Rule of thumb: a 100 Mbps unmetered server handles up to about 25 concurrent viewers at 4 Mbps. A 1 Gbps port serves about 250. For most community broadcasters, a €5–20 per month server is more than enough. Because the app encodes several renditions, viewers on phones often pick a lower one, which stretches these numbers a little.

Setup, step by step

  1. Rent a server from one of the providers above and point a subdomain, for example stream.example.com, at it.
  2. Install nginx and a certificate: apt install nginx apache2-utils certbot python3-certbot-nginx, then run certbot --nginx -d stream.example.com.
  3. Create the upload folder and a password: mkdir -p /var/www/hls && chown www-data:www-data /var/www/hls, then htpasswd -c /etc/nginx/.htpasswd yourname.
  4. Add the site configuration below to /etc/nginx/sites-available/hls-upload, link it into sites-enabled, and run nginx -t && systemctl reload nginx.
  5. In My Live TV Channel, add a destination of type HTTP PUT Server. Set the base upload URL to https://stream.example.com/upload/, turn on Basic Authentication with your user name and password, and set the public playback URL to https://stream.example.com/live/. Use the connection test before you save: it uploads a small file and measures your upload speed.
  6. Go live. The app pushes segments as it encodes, and nginx serves them to anyone with the playback link, in Safari, in an HLS player on your website, or on a smart TV.

This is the minimal configuration that the app's own setup guide uses: one password-protected path that accepts uploads, and one public path that serves them.

server {
    listen 443 ssl;
    server_name stream.example.com;

    ssl_certificate     /etc/letsencrypt/live/stream.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/stream.example.com/privkey.pem;

    # Upload endpoint (PUT with basic auth)
    location /upload/ {
        auth_basic           "Stream Upload";
        auth_basic_user_file /etc/nginx/.htpasswd;
        dav_methods PUT DELETE;
        create_full_put_path on;
        dav_access user:rw group:r all:r;
        client_max_body_size 20m;
        root /var/www/hls;
    }

    # Public playback (no auth)
    location /live/ {
        alias /var/www/hls/upload/;
        types {
            application/vnd.apple.mpegurl m3u8;
            video/mp4                     mp4;
            video/iso.segment             m4s;
        }
        add_header Cache-Control "no-cache, no-store";
        add_header Access-Control-Allow-Origin *;
    }
}

Five things to get right

  1. Keep uploads behind a password. Anyone who can PUT to your server can replace your stream. Use a long password and never share the upload URL.
  2. Send CORS headers on playback. A web player on another domain needs Access-Control-Allow-Origin, or the browser blocks the stream.
  3. Watch the disk. Segments add up quickly. A daily cron job that deletes old segment files is a cheap safety net.
  4. Add rate limiting. nginx's limit_req on the public path stops one scraper from eating the port that your real viewers share.
  5. Scale out, not up. When one server is not enough, add a second in another region and use DNS-based load balancing. Start with one server and grow with your audience.

Where a 24/7 channel fits

Self-hosting is ideal for live moments: a match, a service, a talk, a launch. It does nothing for the other 23 hours of the day, when the server sits idle and the link shows an empty player. A linear channel fills those hours.

Fill the hours between your live streams

Turn your videos into a channel that plays all day, then go live on it from your Mac whenever you have something to show.

FAQ

Do I need a streaming server such as Wowza or an RTMP server?

No. HLS is a playlist plus small video files delivered over plain HTTP. If the encoder writes those files to your server, any web server can deliver them. My Live TV Channel encodes and packages on the Mac and uploads the files with HTTPS PUT, so nginx only has to accept the upload and serve static files.

How many viewers can a cheap server handle?

Divide the port speed by the stream bitrate and keep a margin. A 100 Mbps port serves about 20 to 25 concurrent viewers of a 4 Mbps stream. A 1 Gbps port serves about 200 to 250. Viewers on a phone often pick a lower rendition, which stretches the number a little.

How much bandwidth does a 24/7 stream use?

One viewer watching a 4 Mbps stream around the clock uses about 1.3 TB per month. Multiply by the average number of concurrent viewers. Ten viewers on average is about 13 TB per month, which is why unmetered servers are the safe choice for always-on streams.

Can the videos of my 24/7 channel be served from my own hosting?

Yes, through the free WordPress plugin. My TV Channel builds the schedule and the playlist, and your host stores and serves the video files, so it costs less. The free tier covers one channel and up to five concurrent viewers. Without WordPress, the videos are stored and served by My TV Channel.

Can I send a self-hosted live stream into my 24/7 channel?

My Live TV Channel can publish to your own server and to your My TV Channel channel. When you go live on the channel, the broadcast replaces regular programming, and the schedule resumes when you stop.