Last updated: July 7, 2026 · Reviewed by the StreamingVPS.com Engineering Team
A FAST channel is a free, ad-supported, always-on linear video channel — the same viewing experience as classic broadcast TV, just delivered over the internet to devices like Roku, Samsung TV Plus, and Pluto TV instead of over the air. There’s no subscription: revenue comes entirely from ads inserted into scheduled breaks. Technically, a FAST channel is built the same way any 24/7 streaming TV channel is built — a playout engine assembles a fixed schedule and outputs a continuous encoded feed — but getting that feed onto a real FAST platform almost always means routing it through a certified aggregator rather than uploading it yourself.
\nKey Takeaways
- FAST stands for Free Ad-Supported Streaming Television — a live, scheduled, linear channel funded by ads, distinct from AVOD (on-demand titles with ads) and SVOD (subscription, no ads).
- Nearly every major FAST platform (Roku Channel, Samsung TV Plus, Pluto TV, Vizio WatchFree+) requires distribution through a Linear Certified Partner — an aggregator like Amagi, Wurl, or Frequency — rather than accepting a direct feed from an independent operator.
- The origin channel itself is built with ordinary playout software: Flussonic’s
playlist://source or Wowza’s StreamPublisher module assembles VOD and live segments into a 24/7 schedule, which a VPS can run and encode. - SCTE-35 marks the exact in/out points of ad breaks inside the video stream; SCTE-224 (ESNI) carries the separate metadata about which ads and rules apply to each break — 2026’s SCTE-301 framework unifies both across FAST, OTT, and CTV delivery.
- Amazon’s Freevee brand shut down in September 2025 and was folded into Prime Video’s free ad-supported tier, a reminder that FAST platform lineups change and a channel should be built for multi-platform delivery, not locked to one partner.
What Exactly Is a FAST Channel, Technically?
A FAST channel is not a different streaming protocol or file format — it’s a business model layered on top of the same live-streaming infrastructure covered elsewhere on this site: a continuous H.264/HEVC encode, packaged as HLS or MPEG-TS, delivered to a viewer’s screen. What makes it "FAST" specifically is three things working together: the content runs on a fixed schedule like a broadcast network (not on-demand), the viewer pays nothing, and the entire cost is recovered through inserted advertising rather than a subscription or one-time purchase.
This puts FAST in the middle of a three-way monetization spectrum worth knowing precisely, since the terms get used loosely:
| Model | Viewer cost | Content structure | Example |
|---|---|---|---|
| SVOD | Subscription fee | On-demand library | A paid streaming service’s ad-free tier |
| AVOD | Free | On-demand library, ads between titles | A free on-demand app with pre-roll/mid-roll |
| FAST | Free | Live, scheduled, linear channel, ads at breaks | A 24/7 channel on Roku Channel or Pluto TV |
If you’ve already built a 24/7 loop or a scheduled playout channel on a VPS — the kind of setup covered in our TV-channel playout automation guide — you’ve already built the origin side of a FAST channel. What’s left is ad signaling and platform distribution.
\nHow Do You Actually Get a Channel Onto Roku, Samsung TV Plus, or Pluto TV?
You almost never submit a feed directly to the platform. Samsung TV Plus content partnerships, for example, aren’t an open self-service form — a distributor either has an existing relationship or works through an established channel operator that already holds the playout relationship, and full technical specs are typically shared under NDA during onboarding. Roku and Pluto TV follow a similar pattern: their public documentation covers app development and VOD ingest, but linear channel slots are allocated through a small set of Linear Certified Partners — companies like Amagi, Wurl, and Frequency — who already speak each platform’s proprietary ingest and EPG format.
In practice this means your VPS doesn’t feed Roku or Samsung directly. It feeds the aggregator, and the aggregator feeds the platform. That’s a normal, expected part of the FAST supply chain — not a workaround — and it’s the same model traditional broadcasters use to get a channel onto a cable headend.
What the aggregator actually needs from you
Aggregators like Amagi accept live ingest over SRT, RTP, RTP-FEC, NDI, or RTMP, plus higher-end formats like ST 2110 with JPEG XS for broadcast-grade origination — you don’t need that last one for a typical online-only FAST channel. Realistic encode targets an aggregator will ask for:
- Video: H.264 High Profile (encoder choice matters here — see our Wowza Transcoder and Flussonic transcoder guides for how to configure this on a VPS)
- Audio: AC-3, with region-appropriate frame rates — 1080p50 is standard for EU delivery, 1080p at 29.97/59.94 fps for US delivery
- Container: MPEG-TS for the linear feed (not fragmented MP4, which is reserved for VOD ingest)
- SCTE-35 splice markers embedded at every ad break, at the exact frame the break should start and end
What Does the Ad-Insertion Signaling Actually Look Like?
This is where FAST channels differ meaningfully from a plain 24/7 loop: every ad break has to be signaled, not just left as a gap in the content.
SCTE-35 is the in-band marker — a short binary cue embedded directly in the MPEG-TS or HLS manifest (#EXT-X-CUE-OUT / #EXT-X-CUE-IN at the HLS layer) that tells every downstream system "an ad break starts here, and it’s this many seconds long." If you’ve read our SSAI guide, this is the same marker technology — Wowza’s ModuleAdMarkers and Ant Media’s SCTE35Plugin both produce it.
SCTE-224, also called ESNI (Event Schedule Notification Interface), is the layer above that: an out-of-band metadata protocol describing what should happen at each marked break — which ad decisioning system to call, what content rights and blackout rules apply, and how the break maps to the channel’s published schedule. Where SCTE-35 says "break here," SCTE-224 says "here’s what’s allowed to fill it."
The industry pushed these two standards further together in 2026: SCTE-301 is a newer recommended practice that coordinates SCTE-35, SCTE-224, SCTE-250, and SCTE-277 into a single framework specifically aimed at assembling and distributing linear channels across broadcast, IPTV, CTV, OTT, and FAST — worth knowing if you’re evaluating aggregator platforms, since support for SCTE-301 is becoming a differentiator among them.
For ad-break enforcement to actually pay out, the SCTE-35 markers have to fire at the exact scheduled position — a marker that drifts by even a second or two against the published EPG schedule means the ad decisioning system either serves the wrong break or drops it, both of which cost you revenue. This is one more reason to run playout on the same VPS that controls your master schedule rather than trying to splice markers in downstream.
\nWhat Does a VPS-Based FAST Channel Pipeline Actually Look Like?
A realistic single-channel setup:
- Content library and schedule live on the VPS — VOD assets plus any live windows, assembled by Flussonic’s
playlist://directive or Wowza’s StreamPublisher (ServerListenerStreamPublisherfor a static schedule,ModuleStreamPublisherif you need to reload the schedule without restarting the application). - Encoding happens on the same VPS — H.264 High Profile output, sized for the aggregator’s target bitrate (typically 4–8 Mbps for 1080p linear delivery).
- SCTE-35 insertion happens at the playout/encode stage, tied to the same schedule data so break timing never drifts from the published EPG.
- Delivery to the aggregator goes out over SRT or RTMP push — SRT is generally preferred for its packet-loss recovery over the public internet, which matters more here than for a single-viewer HLS stream since a dropped frame in a linear feed can’t be re-buffered by the viewer.
- A backup feed runs in parallel. Aggregators and platforms typically expect a redundant primary/backup pair for any 24/7 linear channel — a second VPS (or a second process on the same box pushing to a different SRT port) covering for encoder crashes or network blips.
For a single 1080p channel plus a backup feed, a 4 vCPU / 8 GB VPS has comfortable headroom in our testing — playout and SCTE-35 insertion is a light, predictable CPU load compared to serving concurrent viewer connections, since the aggregator (not your VPS) handles fan-out to millions of screens.
How Much Does It Cost to Run a FAST Channel?
| Cost component | Typical range | Notes |
|---|---|---|
| Origin VPS (playout + encode + backup feed) | $20–$80/month | Scales with resolution/bitrate, not viewer count |
| Aggregator/distribution deal | Usually revenue share, not a flat fee | Terms vary by platform and are typically NDA’d |
| Content licensing (if not owner-produced) | Highly variable | Zero if you own or have distribution rights to your library |
| EPG/metadata management | Included with most aggregator packages | Some require XMLTV-formatted schedule feeds |
The VPS side is the cheap, predictable part. The economics of a FAST channel live almost entirely in the aggregator’s revenue-share terms and how much ad inventory you can actually fill — infrastructure cost is rarely the bottleneck.
Should You Use SSAI or Rely on the Aggregator’s Ad Insertion?
Most FAST platform deals have the aggregator handle server-side ad insertion (SSAI) centrally, since they own the ad decisioning relationships and the platform-side compliance. You typically don’t need to run your own SSAI stack on the origin VPS for a standard FAST distribution deal — your job is producing a clean, correctly-marked feed; theirs is filling the breaks. If you’re also running a direct-to-web version of the same channel (bypassing the aggregator entirely for your own site or app), that’s when running your own SSAI setup — covered in our dedicated SSAI guide — becomes relevant, since there’s no aggregator in that path to do it for you.
\nFAQ
What is a FAST channel?
A FAST (Free Ad-Supported Streaming Television) channel is a live, linear, always-on video channel delivered over the internet at no cost to the viewer, funded entirely by inserted advertising rather than a subscription fee.
Can I submit a channel directly to Roku or Samsung TV Plus myself?
Generally no. Most major FAST platforms require distribution through a Linear Certified Partner or aggregator such as Amagi, Wurl, or Frequency, who handle feed ingest, EPG delivery, and platform-specific compliance on your behalf.
What is the difference between SCTE-35 and SCTE-224?
SCTE-35 embeds in-band splice markers directly in the video stream to signal exactly when an ad break starts and ends. SCTE-224 (ESNI) is a separate out-of-band metadata protocol that describes which ads, rights, and rules apply to those breaks, enabling addressable and targeted ad decisioning.
What VPS specs do I need to run a FAST channel origin?
A 4 vCPU / 8 GB VPS running Flussonic or Wowza can comfortably assemble and encode a single 1080p H.264 FAST channel plus a redundant backup feed, since playout is a scheduling and light-transcoding workload rather than a high-concurrency delivery workload.
Is Amazon Freevee still a FAST platform?
No. Amazon shut down the standalone Freevee brand in September 2025 and folded its ad-supported content directly into Prime Video’s free tier, so channel operators should no longer plan a distribution deal with Freevee specifically.
Get Your FAST Channel Origin Running Today
Whether you’re assembling your first 24/7 schedule or adding SCTE-35 signaling to an existing loop, you need a VPS that already has the playout engine installed and configured — not a blank server you have to build from scratch. Get a pre-installed Wowza or Flussonic streaming VPS from StreamingVPS.com — go live in 60 seconds. Check pricing or see the Wowza Streaming VPS plan built for exactly this kind of always-on channel workload.
