System overview
The Vindral Live ecosystem consists of a variety of modular components and services, each designed to meet specific needs. Together, they form Vindral LiveEngine — a high-performance, low-latency platform optimized for large-scale deployments. With Vindral LiveEngine, you can build a fully self-managed live CDN service that supports a wide range of protocols including MoQ, LLHLS, RTMP, SRT, and more. The system is highly customizable, offering white-labeling options, OEM licensing, and deployment flexibility on your own infrastructure.
For those seeking a fully managed solution, Vindral LiveCloud provides a global, cloud-based live CDN service. Built on top of Vindral LiveEngine, LiveCloud offers all the features of Vindral LiveEngine, with the added convenience of managed services, robust SLAs, and a redundant, multi-provider infrastructure to ensure maximum uptime and reliability.
Keep reading to learn more about how Vindral Live works and how easy it is to get started.
Concepts
Some concepts need to be clarified within the live streaming area. Here, we explain some terms and the components related to them.
Ingress
When broadcasting, the video/audio feed usually goes through a certain path from the source into the delivery network.
This process is called Ingress.
The graph above exemplifies how it may work, as different setups use different protocols.
Our ingress servers can handle different types of content over various transport protocols.
The most common ways to ingress streams are:
- RTMP(s) - de facto standard for video ingress over the internet
- SRT - Secure Reliable Transport
- WebRTC - easy to use and embeddable on websites
- MPEG-TS - useful for on-prem installations
- HD-SDI - useful for on-prem installations
Visit the protocol page to read more about supported ways of ingesting streams into Vindral Live.
Transcoding
Most streams sent over the internet use multiple qualities to cater to different viewer conditions. Often, a single stream is sent to our service and turned into multiple qualities, a.k.a. an ABR Ladder.
This process is called Transcoding.
Our transcoding components are built for robust 24/7 streaming and support many different codecs and settings. They are built for dense and environmentally friendly operations through hardware offloading. These are used internally within Vindral Live and can be used on-prem as well. Let us know if you are interested in learning more.
Egress
After the stream has reached the Vindral Live ingress server, it will be transcoded and transmuxed as needed. After the transcoding step, the stream will find its path to the viewers.
This process is called Egress.
The internal process of spreading data from the origin to edge servers closest to viewers is called fanout.
Our edge egress servers are highly optimized and can handle loads of viewers globally. We have tuned internal communication specifically to achieve low latency while maintaining stability.
The egress nodes have built-in support for serving live thumbnails, allowing you to create live lobbies, channel previews, monitoring boards, and more.
The last step, where the streams are sent from our closest edge servers to the viewers, is called last-mile.
Players and SDKs
There are plenty of ways to consume Vindral Live streams:
- The Vindral Web SDK - an extensive javascript (with Typescript typings) library, which includes a ready-to-use Player GUI, standalone Google Cast Sender, standalone API client, and more
- Google Cast receiver - one of a few live streaming services with full support for Google Cast receivers (Chromecast, Android TV). Frame-synced metadata events can be sent to companion app/website
- CDN-hosted player - can be used standalone for fullscreen monitoring or embedded on a website using iframe
- Native - the easiest way to consume Vindral in a native app is to wrap the CDN-hosted player within a WebView, which will get you up and running in a few lines of code
- Live thumbnails - great for monitoring and for serving a lobby of different channels
- Any (LL-)HLS (Low latency HLS or regular) compatible player
Formats and protocols
- MoQ – the default protocol of Vindral Live - a modern low-latency transport protocol, used for all internal communication as well as for egress to viewers. Has a clever fallback mechanism to WebSockets for browsers that do not support WebTransport, with the same features and in most cases the same performance
- HLS – used for playback of recordings and live HLS (LL-HLS) in cases where it’s needed, such as Apple Airplay
- JPEG – live thumbnails are served as JPEG images
Customer Portal
The entry point for Vindral is called Vindral Portal. Channels, channel groups, auth secrets and settings are managed from here. You'll find analytics for all your channels to view in the browser or to download as CSV files.
API
Vindral is actively maintained, and improving our APIs is always a top priority for the team. Use the Management API for integrating Vindral into your own services.
Channel vs. Stream
The relation between a channel and a stream is not obvious. Let us use water as a reference for explaining:
A stream is any body of running water that occupies a channel.
Streams may be permanent or intermittent — occurring only part of the time.
The channel is always there even if no water runs in it.
A channel can be part of a Channel Group, a logical grouping of channels. Channel groups allow for sharing authorization across channels and enable fast channel switching between them.
On-prem
Encoding and packaging
Vindral LivePackager is a high-performant on-prem encoder that can be used for ingesting streams into Vindral Live and other services. It is a software-based solution that can run on basically any hardware, supports GPU/ASIC offload and is designed to be used in a 24/7 environment. It support muxing, transcoding, and ABR ladder generation. It is a great solution for customers who want to run their own encoder on-prem.
Video Compositing
For customers requiring a high-end on-prem encoder with support for real-time video compositing, camera switching, chroma key, color correction, live graphics etc, we recommend Vindral Composer. For verticals such as iGaming and other event-driven use cases, Composer is a turn-key solution that provides more features, higher density, lower complexity, and a more cost-efficient solution.
Composer is licensed separately from Vindral Live.
For more information, please visit vindral.com/composer and the Composer Documentation.
Third-party solutions
Most on-prem solutions are compatible with Vindral Live. A few examples are:
- LiveU - hardware encoder
- Blackmagic - hardware encoder
- Intinor - hardware encoder
- Elemental - hardware encoder
Technical Deep-Dive
Read the Technical Deep-Dive section for more information about the protocols, components, and the internal flow within Vindral Live.