SVOD
SVOD (subscription video on demand) gives subscribers access to a whole video catalogue for a recurring fee, and removes access when the subscription ends. For the video stack, that means every play checks an active subscription before a playback token is issued, licensed titles carry DRM whose licenses expire with the subscription, the same catalogue plays on phones, browsers and TVs, and playback quality is measured per subscriber so problems surface before viewers cancel.
How does SVOD playback work?
An SVOD play starts with identity. The viewer signs in, and the app asks your subscription service whether the account is active and which tier it is on. If it is, your backend issues a short-lived playback token for the chosen title. The player uses the token to fetch the manifest and segments from the CDN.
For titles under studio or league licenses, the player then asks a DRM license server for a decryption key. The license can carry rules taken from the subscription: how long it lasts before renewal, the maximum resolution for the device's security level, and whether the title can be downloaded for offline viewing. Offline downloads use persistent licenses that expire after a set number of days and must be renewed online, which is how a downloaded episode stops playing after a subscriber cancels.
What does an SVOD platform need from its video stack?
An SVOD catalogue is watched on many screens for months, so the video stack is judged on consistency rather than on any single play. A title that plays well on phones but fails on one TV model still costs subscribers. These are the parts every SVOD service ends up building or buying.
- Per-title encoding, so each series gets a bitrate ladder that suits its content.
- Players for web, iOS, Android and TV platforms, ideally sharing one playback ID.
- Entitlement tokens checked on every play, tied to the subscription tier.
- Multi-DRM for licensed titles, with license rules that follow the subscription.
- Captions and audio tracks in the languages the catalogue is sold in.
- Per-view analytics tied to the subscriber ID.
SVOD vs. AVOD vs. TVOD: how the video stack differs
The three models share encoding, packaging and delivery. They differ in what the stack must check at playback and what it must insert.
SVOD checks one thing per play: is this subscription active, and does its tier include this title. DRM licenses can renew for as long as billing continues. AVOD, ad-supported video on demand, usually needs no entitlement at all, but it needs ad breaks marked in the stream and an ad system that fills them, either in the player or stitched in on the server. TVOD, transactional video on demand, sells single titles as rentals or purchases, so tokens and licenses must name one title and expire on the rental's clock, often a window to start watching plus a shorter one that begins at first play.
Hybrid services run all three at once. The same title can be in a subscription tier, an ad-supported tier and a rental store, with each request routed to a different rule.
How do SVOD services keep playback reliable at peak?
SVOD demand is predictable but sharp. A new season dropping at a set hour, or the evening peak in one time zone, sends a large share of subscribers to the same titles at once. Popular segments stay hot in CDN caches, so the pressure falls on manifest requests, token issuance and DRM license servers, which all sit on the startup path. Multi-CDN routing with per-region failover keeps one degraded network from turning into a regional outage.
Reliability also has to be measured per subscriber, not just in aggregate. A dashboard average can look healthy while one device model or one ISP is failing. Passing the subscriber ID into playback analytics links startup time, rebuffering and errors to the account, so a support team can see that a cancelling subscriber hit errors on a TV for weeks.
How does FastPix handle SVOD?
FastPix covers the video layer of an SVOD service; subscriptions and billing stay in your stack. Each upload gets a per-title ladder in H.264 and HEVC (H.265) as standard, with AV1 available on request, with Standard, Pro and Premium quality tiers up to 4K with HDR10, Dolby Vision and HLG, packaged just in time as CMAF for HLS and DASH. Captions and subtitles are generated on every asset, with transcription in 50+ languages.
One playback ID plays across the FastPix Player's native SDKs for web, Android (built on Media3, including Android TV), iOS (built on AVPlayer, including tvOS) and Flutter, with DRM playback, Chromecast, AirPlay and offline downloads. Your backend checks the subscription and signs a JWT with FastPix signing keys, and signed playback IDs refuse requests without a valid token. Licensed titles can add Widevine, FairPlay and PlayReady DRM through the DRM API. Delivery runs across a multi-CDN mesh of 300+ points of presence with per-region failover.
Pass your subscriber ID as the viewer ID and Video Data scores every session on stability, render quality and startup across 56 dimensions. Event-level export to Snowflake, BigQuery, Redshift, Databricks or ClickHouse lets you join playback quality with your billing data.
Standard encoding is free at every resolution up to 4K and billed once per source minute, not per rendition. Storage is billed per rendition-minute each month and streaming per minute watched, and capping maximum resolution at 720p, 1080p or 2K shapes the bill for a mobile-heavy audience. DRM is a monthly platform fee plus a small fee per license. A free account with no card covers 10 videos and 100,000 streaming minutes a month.
By the numbers
- Netflix launched its streaming service, offering video on demand over the internet, on January 16, 2007. (Netflix (Wikipedia))
