Open Source FAST Channel Software — What Actually Works

The open source community has built several capable tools for FAST channel playout. If you want to build your own channel infrastructure from source, this guide covers what's available and what's involved.

The honest framing first

Running open source FAST infrastructure means you're operating a media platform, not just running a channel. You're responsible for:

• Server uptime (your channel goes offline if your server crashes)
• CDN configuration and costs
• FFmpeg pipeline maintenance
• Storage management
• Security patches
• Scaling under load

This is a perfectly valid choice for developers and technically inclined operators who enjoy the infrastructure work. It's a poor choice for content creators who want to focus on programming.

The cost comparison also isn't as favorable as it appears: open source software is free, but server + CDN + storage infrastructure is not.

ErsatzTV

What it is: ErsatzTV is the most capable open source FAST channel playout software available. It generates live HLS channels from a local or remote media library with a full scheduling interface.

Key features:

• Web-based UI for schedule management
• Multiple channel support
• EPG generation (XMLTV output)
• Hardware transcoding support (NVIDIA, AMD, Intel QSV)
• HDHR (HDHomeRun) network tuner support
• Library management with metadata from TheMovieDB, TheTVDB

What it doesn't do:

• SSAI (no server-side ad insertion)
• Programmatic monetization
• Multi-CDN distribution
• TV platform distribution (you'd need to integrate separately)

ErsatzTV outputs an HLS stream that you can then push through a CDN. Ad insertion would require a separate SSAI layer (like AWS Elemental MediaTailor or Mux SSAI).

Best use case: Running a personal media server as a FAST channel for home or small group use, or as a foundation for a developer building a custom FAST platform.

GitHub: ErsatzTV on GitHub

Restreamer

What it is: Restreamer is an open source live streaming tool that supports streaming from RTMP, SRT, HTTP, and other sources to multiple outputs simultaneously.

Key features:

• Docker-based deployment
• Multiple output destinations (HLS, RTMP, SRT, etc.)
• Embedded server for HLS output
• Process-based transcoding

What it doesn't do:

• Scheduling/playout from a media library (it's a relay/encoder, not a playout system)
• EPG generation
• SSAI

Restreamer is useful for taking a live feed and distributing it, not for building a scheduled FAST channel from VOD content.

GitHub: Restreamer on GitHub

FFmpeg-based custom solutions

FFmpeg is the foundational tool underlying most video processing — including playout. A custom FAST channel built on FFmpeg looks something like:

1. A scheduler (database or text file) that determines what should play at each time
2. An FFmpeg process that reads the current content item and outputs HLS segments
3. A file server or CDN serving the HLS output
4. A script that transitions between content items and ensures continuous output

This is entirely buildable but involves significant engineering:

# Example: basic FFmpeg HLS output
ffmpeg -re -i input.mp4 \
  -c:v libx264 -preset veryfast -b:v 2500k \
  -c:a aac -b:a 128k \
  -f hls \
  -hls_time 4 \
  -hls_playlist_type event \
  -hls_segment_filename 'segments/seg%03d.ts' \
  output.m3u8

Running this continuously with automatic content transitions, proper SCTE-35 insertion, ABR ladder generation, and failover is a non-trivial engineering project.

Castr and Dacast (low-cost managed, not open source)

These aren't open source but are worth mentioning in this context because they're low-cost alternatives to building your own:

Castr (~$10-$100/month): Live streaming relay with some scheduling features. More affordable than enterprise FAST platforms, less capable than dedicated FAST tools.

Dacast (~$39-$500+/month): Streaming platform with OTT/FAST capabilities. More accessible than Amagi/Wurl.

Infrastructure costs for a self-hosted solution

Running your own FAST channel infrastructure for a public-facing channel:

Server (for transcoding/playout):

• Low-quality, minimal audience: $20-$50/month (basic VPS)
• 1080p, small audience (under 100 concurrent): $80-$200/month
• 1080p, moderate audience (100-1000 concurrent): $200-$1,000+/month

CDN (for HLS delivery):

• Bandwidth: $0.01-$0.08/GB
• 100 concurrent viewers × 3 Mbps = ~300 Mbps = ~110 GB/hour = $1.10-$8.80/hour
• That's $800-$6,300/month at 100 concurrent viewers 24/7

Storage: $20-$50+/month for a reasonable content library.

Total for 100 average concurrent viewers: $1,000-$7,000+/month

Compare this to Vidiyo (free) — the open source infrastructure path costs significantly more unless you're operating at a scale where the per-channel cost amortizes across many channels.

When open source makes sense

You're building a platform, not a channel. If you're building a FAST platform that will host many channels (10+), the economics of running your own infrastructure improve dramatically. The infrastructure cost is amortized across many channels, and you have the control needed to add features specific to your use case.

You're a developer who enjoys the infrastructure work. If running servers, optimizing FFmpeg pipelines, and debugging CDN configurations is interesting to you, open source is a valid choice. The learning is valuable even if a managed platform would be more efficient.

You have specific technical requirements that managed platforms don't support. Custom SCTE-35 injection logic, proprietary ad server integrations, specific codec requirements, or unusual distribution patterns that managed platforms can't accommodate.

You have existing infrastructure. If your organization already operates servers, CDN contracts, and has a DevOps team, the marginal cost of adding FAST playout is lower.

The recommendation

For channel operators (content and audience focus): Use a managed platform. Vidiyo is free; the operational cost of self-hosting infrastructure outweighs the savings.

For platform builders (building a system to host many channels): Evaluate open source tooling seriously. ErsatzTV is worth exploring as a playout component; pair it with a commercial SSAI solution and your own CDN.