Cloud DR playout next to your on-prem playout

Article ·

Many broadcasters run their main playout on-prem, on systems that work well and still have years of life left. The weak point is the site itself: it can lose power, the network can fail, or the building can become unusable. The traditional answer is a second hardware site, which means buying, housing and maintaining a duplicate system that mostly sits idle.

Veset Nimbus gives you a separate DR playout in the cloud instead. Your main playout stays exactly as it is, and the DR channel runs next to it. This article shows how the two fit together. The cloud disaster recovery page has the full overview.

Your schedule comes across as it is

Nimbus imports playlists in BXF, XML, XLSX, CSV and JSON. You can send them through the web console, the REST API or the Nimbus MCP server, or drop them into an S3 or SFTP watch folder that Nimbus imports from automatically. If your automation exports a format of its own, we write a parser for it during onboarding.

Your live feeds go to both

Nimbus takes live inputs natively over SRT, HLS, ABR HLS, RTMP, RTP-FEC 2D, CDI and JPEG XS. On AWS, Nimbus sets up AWS MediaConnect automatically for Zixi, RIST and other protocols. If a live input drops, the DR playout falls back to a backup input or to the emergency playlist or slate, returns to live when the signal comes back, and sends an alert.

Library cleanup never moves DR content to cold storage, so the media is ready at failover.

It costs nothing to run until you need it

The DR playout doesn’t run until it’s needed. When it is, an operator starts it from the console, the REST API or MCP, and it’s on air within minutes. Your headend or MCR then switches to the DR feed. Nimbus doesn’t switch between feeds, so the switchover stays under your control.

You can test the DR channel whenever you want. Tell us before a test, and the test time doesn’t count against your included playback hours.

You choose where it runs

Nimbus runs in your own cloud account or on cloud resources Veset provides, on AWS or Hetzner. Hetzner runs data centres in the EU, so a Hetzner deployment keeps processing and storage in the EU. Nimbus offers the same features on Hetzner as on AWS, except AWS-specific services such as AWS MediaConnect, AWS MediaLive and AWS CDI.

Broadcasters already doing this

TV Azteca runs a cloud backup channel for its adn40 news network on Veset Nimbus on AWS. If the primary broadcast infrastructure has an outage, the channel is ready to go on air in the cloud, without duplicate on-prem systems. Read the TV Azteca case study.

Latvian Television (LTV) launched a DR channel on Veset Nimbus with no new hardware. The team ingests media and live feeds, changes playlists and delivers to several platforms, all remotely. Read the LTV case study.

What it costs

Cloud DR starts from $499 per channel per month. That includes cloud infrastructure for a standard configuration and 24 hours of active playback a month, which is the time the DR playout is running. Playback beyond 24 hours is charged per hour, at a rate agreed with Veset. See all plans on the pricing page.

Get started

Tell us which playout and automation you run today and which playlist format it exports. We’ll show you how a DR channel would run next to it.

Broadcast disaster recovery in the cloud, from $499 a month

Cloud disaster recovery for broadcasters with on-prem playout. Nimbus feeds your headends from the cloud. From $499 a month, 24 hours of playback included.