Live video at broadcast quality,
under a second behind live
Vidilix is a streaming protocol and player built for one job: put a live TV channel on any screen between a third of a second and a second and a half behind live, at the scale of an ordinary CDN, with ads spliced into the picture for every viewer.
Live streaming forces a trade-off
Today you pick two: low delay, huge scale on a cheap CDN, or rich features like DVR and server-side ads. HLS and DASH scale but run 6 to 30 seconds behind. WebRTC is near-instant but needs a fleet of media servers. Vidilix was designed to stop choosing.
Typical delay behind live
Typical production ranges from public deployments; the hatched part of each bar is the spread. Vidilix's bar is our own measurement, from the frame entering the origin to the viewer's screen: 0.6 s median in the low-latency modes, 1.5 s in stable mode. Lower is better. The scale is linear up to 30 s.
One system, from camera to revenue
Vidilix is not a player bolted onto someone else's server. Every part, from ingest to the ad that plays in the middle of the evening news, is built to work with the others. Select a part to see what it does.
A protocol built for the live edge
Vidilix is a new delivery protocol designed from the first line for live television. It keeps viewers within a second of live while riding on the ordinary HTTP CDNs that already serve the internet, so a channel scales like a website instead of like a video call.
Made for CDNs
Everything a player fetches is a normal, cacheable web request. Thousands of viewers behind the same CDN edge cost the origin almost nothing extra, and stream addresses cannot be guessed or harvested.
One continuous timeline
Encoder restarts, source failover and server restarts never break the stream's clock, so players and the recording never jump, freeze or lose their place.
DVR from the same media
The recording is the live stream itself. Catch-up, start-over and seeking by programme are exact to the frame, with no second copy to package.
Adaptive by design
Every quality level is in step with every other, so the player can change quality on the fly without a gap or a flash.
Signals in the stream
Ad breaks and on-screen information travel inside the stream, in sync with the picture, to every viewer at the same moment.
Measured end to end
Every frame knows when it entered the system, so each player knows its exact delay behind live, and so do we.
A TV experience in any browser
The Vidilix player decodes and presents every frame itself, in the browser, so it decides exactly how far behind live it sits. Around it is everything viewers expect from television: a programme guide, catch-up, start-over and ads that feel like part of the channel.
Catchup · programme guide
The recording is the real Vidilix player on a demo channel: our own footage, the real programme guide and a real server-inserted ad break with our house ads. The buttons switch to an interactive illustration; its channel and programmes are fictional.
What viewers get
- Programme guide and catch-up. A visual guide with thumbnails from the recording. Jump to any programme of the last days, start the current one over, return to live with one tap.
- Now playing. The current programme and its progress, from the channel's guide (XMLTV or entered by hand), in sync with what is on screen.
- Seamless adaptive quality. Quality follows the network without gaps, and without the up-and-down flicker common in adaptive streaming.
- Fast start. Playback starts in about a second, at the right quality for the device.
- Phones, PiP and keyboards. Fullscreen with our own controls, rotation, picture-in-picture, background audio, keyboard shortcuts and screen-reader labels.
- Your brand. Accent colour, logo, Hebrew or English interface, and branded error screens per customer.
- Anywhere on the web. One iframe or a small JavaScript SDK, with per-site keys, allowed domains and country rules.
Three latency modes
Choose per channel how close to live to play. The player absorbs network hiccups on its own and quietly returns to its target.
Every frame is encrypted
Vidilix encrypts the stream itself, frame by frame, not just the connection. A copied address, a scraped CDN cache or a recorded download is noise without keys, and keys go only to players that pass the channel's rules.
Frame-level encryption
Industry-standard AES encryption applied inside the stream. Seeking, quality switches and catch-up stay instant.
Rotating, scoped keys
Keys change automatically and are scoped per channel and per quality, so a single leaked key opens very little, for very little time.
Keys behind the rules
Keys go only to players that pass the channel's rules: authorised site, session and country, and where a preroll is set, only after it has played. Skipping the ad means no picture.
The same stream, two very different copies
Studio DRM (Widevine, FairPlay, PlayReady) is planned for the optional HLS and DASH outputs, for screens that require it.
Every way to earn from a live channel
Vidilix replaces the broadcaster's commercials with a different ad pod for each viewer, cut exactly on a frame boundary, inside the stream itself. Around that sit prerolls, midrolls, catch-up ads, direct campaigns, programmatic demand and house ads, with measurement that ad partners trust.
Four ways to deliver an ad break
Chosen per channel.
One break, end to end
What happens in the seconds around a break. Select a step, or let it play.
Formats, demand and control
Preroll that cannot be skipped
The picture unlocks only after the preroll has played. Length and how often a viewer sees one are set per channel.
Broadcast break replacement
The channel's own commercials are replaced on the fly, per audience or per viewer, frame-accurate, ended early when the programme comes back.
Midrolls by watch time
Extra breaks of your own, counted on real viewing time (not paused or hidden), never right after joining, reset by any broadcast break.
Fresh ads in catch-up
Viewers of the recording get today's ads in yesterday's breaks, measured like live, and cannot jump over a break they have not seen.
Direct campaigns
Sell inventory yourself: flights, priorities, budgets paced evenly across the flight, and per-viewer frequency caps.
Programmatic demand
Any ad server or SSP that speaks the IAB standards, with wrapper chains, ad pods and the full set of IAB macros.
House ads and fallbacks
Promos of your own fill whatever paid demand leaves empty, so a break is never a black screen. Closers reserve the last slot.
Measurement partners trust
Impressions and quartiles tracked server-side for stitched ads, with the viewer's IP and user agent forwarded per IAB guidance, plus client pixels from the player.
Viewer comfort
A cap on ad seconds per viewer per hour across every source, and a creative library to preview every ad before it airs.
Built to stay on air
A live channel is judged by its worst minute. The origin watches itself and its players, fails over between sources on its own, and tells the operator exactly what happened.
Source failover
- Primary and backups in priority order
- Switch on silence, errors or timestamp jumps
- Return to primary only after it proves stable
- A flapping primary is held back longer each time
Live dashboard
- Viewers, CDN bandwidth, latency, rebuffering, startup
- Per-channel source chain and break control
- System events timeline
Diagnostics
- Player errors grouped by cause
- Rebuffering by country, browser, device, rendition
- Any viewer's session replayed from their code
Measured delivery
- CDN traffic counted from what players received
- Load generator with synthetic viewers that never touch real ad partners
- Origin health: event-loop lag, CPU, memory
How Vidilix compares
Every protocol here is good at something. This is where each one usually sits in production, and what Vidilix does differently.
| Protocol | Typical delay | Scales on a standard HTTP CDN | Plays in the browser | DVR / catch-up | Server-side ads | Main use today |
|---|---|---|---|---|---|---|
| VidilixVidilix protocol | 0.3–1.5 s 0.6 s median low-latency · 1.5 s stable, measured | Yes, standard HTTP CDNs | Yes, modern browsers | Yes, frame-exact | Frame-accurate, per viewer | Live TV and events with ads |
| HLSsegments + playlists | 6–30 s | Yes | Native in Safari, others via a JS library | Yes | Yes, via manifest manipulation | Default for VOD and live at scale |
| LL-HLSpartial segments | 2–5 s | Needs CDN support for blocking reloads and preload hints | Native in Safari, others via a JS library | Yes | Yes, harder to keep tight | Low-latency sports and live |
| MPEG-DASHsegments + MPD | 6–30 s | Yes | Via a JS library (MSE) | Yes | Yes | Android, smart TVs, DRM workflows |
| LL-DASHCMAF chunks | 2–5 s | Needs chunked transfer end to end | Via a JS library (MSE) | Yes | Yes, harder to keep tight | Low-latency live |
| WebRTCRTP over UDP | 0.2–0.5 s | No, needs media servers (SFUs) per audience | Yes | Not built in | Rarely | Calls, auctions, interactive video |
| SRTreliable UDP | < 1 s | No | No | — | — | Contribution: studio to origin (Vidilix ingests it) |
| RTMPTCP, Flash-era | 2–5 s | No | No | — | — | Ingest from encoders and OBS (Vidilix ingests it) |
| MoQMedia over QUIC, IETF draft | Sub-second goal | Needs new QUIC relays | WebTransport, support still uneven | Being specified | Being specified | Standards work in progress |
Why not just WebRTC or MoQ?
WebRTC is the lowest delay there is, but every viewer needs a stateful media server, so a national audience means a server fleet and a large bill. MoQ is the standards community's answer and is still being written. Vidilix reaches comparable delay today, over the HTTP CDNs that already exist.
The honest trade-offs
Vidilix needs its own player (web player, SDK, or wrapped apps) and a modern browser. For older smart TVs and set-top boxes that cannot run it, and for workflows that require studio DRM, the platform adds HLS and DASH outputs packaged from the same media, as an option per channel.
What was hard, and how we solved it
The protocol is simple. Keeping a real channel on air through real networks, real encoders and real ad servers is not. A few of the problems we hit on the pilot.
01The live edge on a CDN built for files
delivery
Problem. CDNs are made to cache files that already exist. Live video is a file that does not exist yet.
Result. Viewers stay within a second of live through a standard CDN, and the origin's load stays flat as the audience grows.
02Quality that ping-pongs
player
Problem. At the live edge a player cannot easily tell how much spare bandwidth it has, so adaptive streaming tends to climb, stutter and drop.
Result. Steady quality that reaches full resolution within seconds of starting.
03A timeline that survives everything
origin
Problem. Encoders restart, sources fail over, servers reboot, and each one normally resets the stream's clock.
Result. Players and the recording never see a jump, through any of it.
04Failover that does not flap
reliability
Problem. Switching to a backup is easy; knowing when to come back is not. An unstable primary can bounce a channel back and forth.
Result. Automatic failover and failback that hold steady under a flapping source, covered by automated failure tests.
05Ads nobody can skip
ads
Problem. Client-side ads can be blocked or skipped by tampering with the player.
Result. Ads are part of the stream, and the picture unlocks only after the preroll.
06Breaks on channels that send no signal
computer vision
Problem. Many channels carry no SCTE-35, so nothing tells the system a break started.
Result. Breaks recognised from the picture to within a second on a real channel, and a new channel taught in minutes.
07Phones
player
Problem. Mobile browsers restrict fullscreen, background audio and picture-in-picture for anything that is not a plain video element.
Result. Fullscreen with our own controls, rotation, picture-in-picture and background audio on phones.
08Finding the cause of a stall
observability
Problem. "It stutters" can mean the viewer's Wi-Fi, a VPN, the CDN or the origin.
Result. Every player reports what it saw; any viewer's session can be replayed from a short code, and problems are traced to their cause in minutes.
From protocol to product
Vidilix ships as a complete media platform around the protocol: ingest, transcoding, recording, ads, analytics and a console for every role. Next, it opens up to any broadcaster, event producer or creator.
Ingest & encode
- SRT, RTMP, WHIP, HLS, RTSP, UDP
- Adaptive ladder or passthrough
- Primary and backup sources
Record & replay
- Days of DVR in the same format
- Programme guide from XMLTV
- Catch-up with fresh ads
Monetise
- SSAI per cohort or per viewer
- VAST/VMAP, campaigns, house ads
- SCTE-35, Break API, visual detection
Distribute
- Embeds and SDK with site keys
- Geo and domain rules
- Any HTTP CDN
Roadmap
Broadcast pilot
24/7 channel live with SSAI, automatic break detection, failover, DVR, diagnostics.
Teams & brands
Organisations with roles for engineers, ad ops and editors; a brand editor that themes player, site and apps.
Self-serve
Sign up and go live in minutes with a free trial channel; plans, usage metering and billing.
OTT & events
Branded OTT sites and wrapped mobile and TV apps; live events with tickets and simulcast; HLS/DASH and DRM outputs.
See it on your own channel
Tell us about your channel or event. We'll set up a live demo on your own feed, with your branding and your ads, and show you the numbers.