Streaming monetisation rarely stays as simple as it looks at launch. Whether a service starts with SVOD, AVOD, TVOD, FAST or a hybrid approach, the real decision is whether the platform can support the model today and adapt as commercial needs change.
The Leyra Team
The question of which monetisation model to choose sits near the top of almost every streaming launch conversation. SVOD, AVOD, TVOD, FAST, hybrid, the options are well-known, and most operators arrive at the table with a view already forming. What tends to get less attention is what each model actually requires to operate, and what happens when a service needs to run more than one model at the same time.
This guide covers each major model with that operational lens in mind. It looks beyond definitions to what each model demands in practice, and what the move toward hybrid monetisation means for the infrastructure underneath it.
The five models, and what each one actually requires
SVOD: Subscription Video on Demand
SVOD remains the dominant model for services with a defined content proposition and a paying audience willing to commit to it. Subscribers pay a recurring fee, monthly or annual, in exchange for access to a catalogue or content library.
The commercial logic is straightforward: predictable revenue, low transaction friction, and a direct relationship with the subscriber that generates usable data over time. The operational requirements are more demanding than the model's simplicity implies. Subscriber acquisition costs are high, particularly in competitive markets, and retention depends on the service consistently delivering enough value to justify renewal. Churn management, identifying at-risk subscribers and acting on those signals before cancellation, is one of the most operationally intensive parts of running an SVOD service at any meaningful scale.
SVOD also requires a billing infrastructure capable of handling free trials, offer localisation across currencies and territories, upgrade and downgrade paths, dunning management for failed payments, and promotional codes for acquisition and win-back campaigns. Services that underinvest in this layer often discover the gaps only when they try to run a promotion or respond to a churn spike.
Best suited to: Services with a strong, distinct content proposition; operators who can invest in subscriber acquisition and retention operations.
AVOD: Advertising Video on Demand
AVOD replaces the subscription fee with advertising revenue. Content is free to the viewer; revenue comes from ad impressions served against viewing time. The model has grown significantly in recent years, partly driven by subscriber fatigue with proliferating SVOD services and partly by the entry of major SVOD players, including Netflix, Disney+, Amazon, into ad-supported tiers.
The operational requirements are substantially different from SVOD. Meaningful AVOD revenue depends on audience scale: CPM rates vary widely by territory and content vertical, but a service needs significant viewing hours to generate revenue that funds content acquisition and operations. For most mid-market operators, AVOD alone is unlikely to be the primary revenue line. Where it performs well is as a lower-barrier entry point - a free tier that drives acquisition and, over time, converts a portion of that audience to subscription.
Running AVOD requires ad infrastructure: a server-side ad insertion (SSAI) integration to deliver ads with fewer client-side performance and blocking issues, ad marker support such as SCTE-35 for live and linear, and relationships with ad networks or a direct sales capability. Ad reporting, impression tracking, fill rates, revenue attribution, adds another data layer that purely subscription-based services do not need to manage.
Best suited to: Services with substantial audience reach or catalogue depth; operators using a free tier strategically as an acquisition channel.
TVOD: Transactional Video on Demand
TVOD charges per piece of content, either as a rental with time-limited access or as electronic sell-through, where users purchase long-term access to a title. It is the oldest model in digital video and remains the most appropriate structure for content that has clear standalone value: new film releases, major sporting events, live concerts and pay-per-view.
The revenue economics are different from subscription. There is no recurring revenue base, which makes forecasting harder, but there is also no obligation to maintain a broad catalogue to justify a monthly fee. Operators can launch TVOD-only services around specific content types and events without the subscriber management overhead that SVOD requires.
TVOD requires an offer structure that can handle rental windows, EST pricing, pass products such as access to a set of events for a fixed price and, for live events, real-time entitlement validation. Payment processing needs to support single-transaction flows with remembered payment details to reduce friction at the point of purchase.
Best suited to: Sports operators, film distributors, and live event specialists; services where premium content commands a per-view price that subscription pricing would undervalue.
FAST: Free Ad-Supported Streaming TV
FAST is the channel model of the streaming era. Services deliver linear programming schedules, typically built from catalogue content or curated thematic channels, and monetise through advertising, similar to traditional broadcast television does. Viewers tune in to a schedule rather than choosing individual titles.
The model's growth has been substantial. FAST platforms such as Pluto TV, Tubi, and Samsung TV Plus have demonstrated that audiences will engage with scheduled content in a streaming environment, and the model has become an important distribution channel for operators with archive libraries that generate limited revenue through VOD.
FAST requires linear broadcast infrastructure: electronic programme guides (EPG), live channel delivery, and in many cases, SSAI with accurate ad splicing and SCTE-35 ad marker support for reliable ad delivery against a linear schedule. The ad infrastructure requirements are more demanding than AVOD, because the scheduling and ad-break cadence is set in advance rather than served dynamically on demand. Distribution is also a distinct operational consideration: FAST channels are typically distributed through third-party platforms such as Roku, Samsung TV Plus, LG Channels and other connected TV environments, as well as an operator’s own apps.
Best suited to: Operators with substantial VOD libraries seeking incremental reach; broadcasters extending their linear presence into streaming environments.
Hybrid monetisation: combining models in one service
Most mature streaming services run a combination of models. The reasons vary, from a free AVOD tier to reduce acquisition friction, to a TVOD layer for premium content that sits above the subscription, or a FAST channel to reach audiences on third-party platforms, but the direction of travel is measurable. According to Ampere Analysis, ad-supported tiers accounted for 28% of global streaming subscription revenue in 2025, up from less than 5% in 2020. As ad-free subscriber growth stabilises in mature markets, hybrid subscription and advertising models are becoming an increasingly important driver of revenue growth.
The operational implication of hybrid is significant. Running SVOD and AVOD in the same service requires the platform to manage two distinct entitlement paths. Paying subscribers should not see advertising, while free-tier users need ad delivery against their viewing. Adding TVOD creates a third entitlement type: per-content access that sits outside both subscription and ad-supported tiers. Each combination adds complexity to the billing layer, the entitlement engine, and the user experience.
The common failure point for services attempting hybrid is not the strategy. It is the infrastructure. Services that bolt a second model onto a platform that was designed for one find that what looked like a product decision becomes an engineering project.
| Model | Revenue mechanism | Audience requirement | Ad infrastructure | Typical use case |
|---|---|---|---|---|
| SVOD | Recurring subscription fee | Paying subscribers willing to commit | None required | Defined content proposition; catalogue services |
| AVOD | Ad impressions against viewing hours | Scale — meaningful revenue requires large reach | SSAI, ad network, impression reporting | Free entry tier; acquisition channel to subscription |
| TVOD | Per-title rental or purchase | Audience willing to pay per event or title | None — but real-time entitlement needed | Sports PPV; new film releases; live events |
| FAST | Ad revenue from linear schedule | Platform distribution (Roku, Samsung, LG) | SSAI + SCTE35 frame-accurate ad splicing | Archive monetisation; broadcast extension |
| Hybrid | Multiple concurrent revenue streams | Varies by tier combination | Depends on models combined | Mature services; reducing acquisition friction |
Which model is right for you? Try our simple diagnostic tool:
What the move to hybrid actually requires from your platform
The model selection conversation and the platform capability conversation are more connected than they often appear in practice. An operator can decide on hybrid monetisation in a strategy session and then spend six months discovering that their billing infrastructure can only express it partially.
The questions worth asking before committing to a model, or before adding a second one, are operational rather than strategic:
Questions to ask
| 1 | Can the platform run SVOD and AVOD simultaneously, with entitlement logic that keeps the two audiences correctly separated? |
| 2 | Can TVOD offers, including rentals, EST and passes, be configured and published without a development cycle? |
| 3 | Does the ad infrastructure support SSAI with SCTE-35 marker handling, or only client-side ad insertion? |
| 4 | Can offer pricing be localised by currency, territory, and language without separate deployments per market? |
| 5 | How does the platform handle dunning management for web payments versus in-app purchase through Google Play, Apple, Roku, Amazon, where the failure and retry logic is different? |
| 6 | Can promotional codes, free trials, and win-back offers be configured independently for different offer types within the same service? |
| 7 | What does the billing reporting layer look like? Can conversion, churn, and revenue be segmented by offer type, territory, and acquisition channel? |
These are not advanced requirements. For any service operating more than one model, or planning to, they form the baseline for running the combined service without constant operational overhead.
Where FAST fits differently from the other models
FAST deserves a separate note because it sits differently from the other models in terms of platform requirements and commercial logic. Unlike SVOD, AVOD, and TVOD, which are primarily about how an operator monetises their own app audience, FAST is largely a distribution play.
Channels are typically made available on third-party platforms where the operator may have less direct control over the monetisation layer. Revenue comes from the platform partner, or through direct ad sales against the operator’s own FAST distribution.
The implication is that FAST rarely replaces another model. It extends reach and monetises archive content in a separate environment. Operators who evaluate FAST as a standalone revenue strategy can be disappointed; those who use it as a complementary distribution channel alongside their primary app-based service are more likely to find it valuable. The key infrastructure requirement is linear channel delivery with reliable ad splicing. Without that, a FAST channel is unlikely to meet the expectations of major distribution platforms.
How Leyra is built for combined monetisation
We built Leyra’s billing and monetisation engine to support combined models from day one, because the operators we work with are not choosing between SVOD and AVOD. They are running both, or planning to.
In practice, that means a single service can carry a free tier such as FVOD or AVOD, a subscription tier with monthly or annual plans and free trials, and transactional offers including rental, EST and pass products running concurrently, with entitlement logic that manages each audience correctly. Payment gateways cover Stripe, Adyen, and PayPal on web, and in-app purchase on Google Play, Apple, Roku, and Amazon Fire TV, with dunning configurations that reflect the different payment environments involved. Offer localisation handles currency, territory, and language without separate instances per market. Promotional codes, pre-authorised vouchers, and win-back codes on cancellation can be configured independently of the offer type they apply to.
For ad-supported models, Leyra’s OVP includes SSAI with SCTE-35 ad marker support for live and linear content, with Invidi and FreeWheel integrations alongside Google IMA and Google DAI. For operators whose billing or identity requirements are handled through a third-party system, Leyra’s Marketplace includes pre-integrated partners, including Cleeng, MPP Global (Aptitude), and InPlayer, that can be connected without custom development.
Billing reporting covers conversion, churn, country, and offer, with raw data export to AWS S3 for operators who need to work with the data in their own BI environment. The aim is that the model combination an operator decides on in a strategy conversation is one they can actually configure, launch, and report against without turning that decision into an engineering project.
The model a service launches with is rarely the model it runs at scale. Building toward that flexibility from the start tends to be considerably less expensive than retrofitting it later.
This article is part of a series on OTT monetisation strategy. The follow-up piece examines why the billing architecture decisions made at launch are often harder to reverse than the model decisions themselves, and how to avoid building constraints into your service before you understand your audience.
If you are evaluating OTT monetisation models or reviewing how well your current platform supports billing, entitlements, advertising and reporting, book a demo with Leyra or get in touch to talk through your requirements. You can also download the full Leyra feature specifications to review platform capabilities in detail.
Follow us on LinkedIn for more insights on building and running streaming services.
