Veset Nimbus handles 8 simultaneous live feeds at 4-8 second latency

Veset Nimbus positions itself as a cost-competitive cloud playout option for broadcasters managing live events, with the Linux-on-AWS approach lowering operating costs relative to Windows-based alternatives. The 4-8 second latency penalty versus SDI is broadly consistent with what other cloud playout vendors report — Amagi's CLOUDPORT, for instance, cites approximately one second of internal playout latency before encoder and transport overhead. The broader cloud playout market, valued at roughly $2.8 billion in 2025 per market research, is growing at roughly 15% annually as FAST and OTT channels scale. Watch whether Veset's November 2025 self-service subscription launch drives adoption among smaller content owners who need fast channel spin-up.

Veset has been steadily expanding Nimbus's live ingest and transport capabilities to compete with larger cloud playout providers. In April 2025, Veset integrated JPEG XS and Multicast networking into Nimbus on AWS infrastructure, making it one of the first cloud playout providers to offer both features. JPEG XS enables low-latency, visually lossless video transport within the cloud, while Multicast networking allows broadcasters to distribute live feeds to Nimbus and third-party products simultaneously without complex unicast workarounds. CEO Gatis Gailis framed the addition as bringing traditional broadcast reliability to cloud playout operations.

The company, a wholly owned subsidiary of Japan's PLAY, Inc., operates from Latvia and serves customers in more than 20 countries. Veset positions Nimbus as a true cloud SaaS playout platform that supports SCTE-35 signaling for ad insertion, Content Advisory (V-Chip) data, and automatic recording of incoming live feeds to AWS S3 or compatible storage. The platform's Linux-on-AWS architecture avoids Windows licensing costs, a differentiator Veset emphasizes against competitors that run on Windows-based instances.

The platform also integrates with AWS MediaLive and AWS DirectConnect for lower-latency paths when sources originate within AWS. Veset's FAQ notes that the one scenario where Nimbus is not ideal is traditional live news with zero-latency anchor switching between multiple ad hoc feeds, acknowledging the inherent latency trade-off of cloud playout versus SDI.