MediaKind Streamlines Playout To Delivery On-Prem And In The Cloud

MediaKind has outlined a unified playout-to-delivery workflow that consolidates ingest, playout, graphics, audio/video processing and distribution into a single operational chain, deployable either on-premises via XOS or in the cloud with VOS360.

Traditionally, getting a TV channel to air involved a string of siloed systems and teams for each step—from content ingest and branding to processing and broadcast or streaming delivery. MediaKind's approach is to merge those functions so a live or file source goes in and a broadcast- and streaming-ready channel comes out, with the same workflow whether it runs on-prem or in the cloud.

The company highlights three practical gains: a single operations layer across the full channel workflow; up to 25 HD playout channels running on one XOS appliance; and roughly half the infrastructure needed for an end-to-end on-premises chain from playout through delivery.

Building channels the old way meant stitching together multiple boxes—one for ingest, another for playout and graphics, others for encoding, processing and delivery—driving up infrastructure, management overhead and complexity. With rising server and memory costs, MediaKind argues the economics now demand higher feature density and simpler operations.

Stephane Cloirec, VP Product Management, Appliances and Software, said: "We have to do better. We have to do more in terms of features, in terms of applications, with less in terms of infrastructure."

Under the consolidated model, a source flows through ingest, playout and graphics, transcoding and encoding, packaging, encryption, origin and delivery—without separate systems at each hop. XOS Playout works with existing plant (SDI, ASI, TS over IP, SRT, SMPTE-2110) and outputs for satellite, cable, terrestrial and IPTV, plus streaming formats such as HLS, DASH and CMAF. Playout is managed through web-based automation.

MediaKind describes this as a "feature collapse": XOS extends beyond encoding/transcoding to include streaming packaging and origin, plus playout, advanced graphics, convergence, SDR/HDR and audio for production. Everything runs as Kubernetes-orchestrated microservices—the same software stack it operates in the cloud—which also ties XOS to VOS360.

Cloirec added: "We can divide by two the amount of infrastructure, which is required from an end-to-end workflow, playout to delivery."

Fewer moving parts translate to simpler operations and savings on rack space, cooling and power. Density adds to that equation: a single XOS appliance can host up to 25 HD playout channels, reducing the number of systems to procure and manage.

MediaKind positions cloud and on-prem as complementary. Elastic, event-driven workloads are well suited to the cloud, while always-on 24/7 channels can retain a total-cost advantage on-prem. The company says customers increasingly model TCO to place each workload where it best fits.

"It makes sense to have the right workflow running in the right deployment environment," said Cloirec.

In practice, organisations can tier channels—running primary services on-prem while hosting secondary and disaster-recovery instances in VOS360, mirroring on-prem operations. A single automation layer oversees both environments through one interface.

Cloirec concluded: "From an operator perspective, there is absolutely no difference whether the channel sits on-prem or the channel sits in the cloud."

For operators, the promise is operational consistency regardless of location, with MediaKind providing the on-prem XOS and cloud-based VOS360 building blocks to run channels the same way in either environment.

www.mediakind.com/