Amagi cuts playlist publishing 70%

Broadcast playout is the part of TV infrastructure that decides what goes on air, in what order, and what happens when something breaks. It sounds back-office, but it is the thing standing between a clean channel and dead air. Amagi’s news on May 12 is that it has pushed a much bigger version of CLOUDPORT into market — not just a tune-up, but a broader rebuild aimed at cloud-native broadcast operations. The pitch is simple: make cloud playout fast enough, redundant enough, and predictable enough that broadcasters trust it for always-on channels. ### What exactly did Amagi launch? Amagi said this is the largest CLOUDPORT upgrade it has shipped so far, with more than 250 features delivered across FY25-26. The platform is meant for linear TV, FAST channels, and live-event broadcasters, and the company is framing the release as part of a shift from selling isolated tools to offering a broader cloud broadcast platform. (amagi.com) ### Why does playlist publishing matter? A playlist is the running order for a channel — shows, ads, promos, graphics, all of it. If publishing that schedule is slow, operators lose time when they need to make last-minute changes, fix a bad asset, or spin up a special feed. Amagi’s claim of roughly 70% faster playlist publishing matters because speed here is really a proxy for operational slack — the difference between calmly fixing a schedule and scrambling before airtime. (amagi.com) ### What are the biggest hard numbers? The release hangs on three numbers. CLOUDPORT now supports 100+ concurrent feeds in a single tenant, with 200-player multi-availability-zone redundancy, and Amagi says the platform is engineered for 99.999% availability. For a broadcaster, that translates into bigger channel groups running in one environment and more backup paths if part of the stack fails. (amagi.com) ### How is it trying to cut on-air mistakes? The new piece here is Amagi Monitoring, which watches for missing assets, schedule gaps, ingest failures, audio setup errors, and delivery anomalies before they hit the channel. Amagi says the monitoring layer has helped avert more than 80% of potential disruption scenarios since late 2025. That does not mean failures disappear — but it does mean the company is pushing more of the “catch the problem early” work into software instead of manual checks. (amagi.com) ### Why all the talk about resiliency? Because cloud broadcast only works if the backup plan is boring. Amagi says CLOUDPORT supports SMPTE ST 2022-7 for hitless protection switching in RTP workflows, plus active-active multi-region and multi-AZ designs. It also keeps an on-premises disaster recovery box for up to 72 hours of survivability during extended cloud or network outages. Basically, the company is trying to answer the broadcaster’s oldest objection to cloud playout — what happens when the network does something ugly? (amagi.com) ### Where does AWS fit in? AWS is not the headline of this release, but it is part of the underlying story. Amagi already positions CLOUDPORT as built on AWS and sells it through AWS channels, while AWS has previously highlighted Amagi’s multi-AZ and multi-region resilience patterns for broadcast continuity. So when Amagi talks about larger distributed deployments, the subtext is that this is meant to scale on infrastructure broadcasters already use. (amagi.com) ### What’s the real significance? The real move is less about one codec or one dashboard and more about trust. Broadcasters have spent years hearing that cloud playout is flexible and cheaper, but the catch has always been operational risk. Amagi is trying to narrow that gap with speed, monitoring, and redundancy in one package. If those claims hold up in production, cloud playout starts looking less like a migration project and more like default infrastructure. (amagi.com) ### Bottom line? Amagi’s upgrade is a bet that broadcast buyers are done asking whether playout can move to the cloud and are now asking which platform can survive real-world pressure. CLOUDPORT’s new numbers are meant to answer that. (amagi.com)