
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 MCP, or drop them into an S3 or SFTP watch folder. 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 MediaConnect automatically for Zixi, RIST and other protocols. If a live input drops, the playout falls back to a backup input or to the emergency playlist or slate. It returns to live when the signal comes back and sends an alert.
The DR channel 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 API or MCP, and it’s on air within minutes. Your headend or MCR then switches to the DR feed, so the switchover stays under your control.
You choose where it runs. Nimbus can run in your own cloud account or on cloud resources Veset provides, on AWS or Hetzner. A Hetzner deployment keeps processing and storage in the EU. Nimbus offers the same features there as on AWS, apart from AWS-specific services such as MediaConnect.
TV Azteca uses Veset Nimbus on AWS as DR playout for its adn40 network. If the primary broadcast infrastructure has an outage, the broadcaster can switch to a ready-to-air channel in the cloud without maintaining duplicate on-premise systems. Read the TV Azteca case study
Latvian Television (LTV) launched a disaster recovery channel on Veset Nimbus with no new hardware, and manages the channel remotely. Read the LTV case study
Many broadcasters run their main playout on-prem, on systems that work well and still have years of life left. The weak point is what happens when that site goes down. The site might lose power, the network might fail, or the building itself might 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.
Cloud DR starts from $499 a month, including cloud infrastructure and 24 hours of active playback a month. See pricing
Tell us which playout and automation you run today and which playlist format it exports. We’ll show you how the DR channel would run alongside it. Book a demo