APIs become procurement criteria as broadcasters abandon single-vendor stacks

The shift in how broadcasters evaluate technology vendors is no longer subtle. Where the conversation once centered on what a product could do, it now turns on whether the product can be replaced without rebuilding the workflow around it.

That change in evaluation criteria is the practical consequence of a broader move away from monolithic, end-to-end vendor stacks. Broadcasters that committed to single-vendor architectures during earlier infrastructure cycles are now describing the cost of those decisions in terms of agility, not capability.

“The era of the single-vendor end-to-end solution is functionally over — the pace of innovation across ingest, MAM, editing, AI tooling, and distribution means the best answer for any given workflow stage rarely comes from the same company, and organizations that locked into monolithic stacks are now paying the price in agility,” said Rich Zabel, VP of media supply chain at Diversified, in the Industry Insights roundtable on workflows and integration.

The position is not unique to systems integrators.

“We are seeing a rising trend of organizations prioritizing pluggable ecosystems where open standards and robust APIs allow for a seamless exchange, while shifting away from vendors who treat data as a black box,” said Clara Aler, head of marketing at Knox Media Hub. “The industry is moving away from single-vendor solutions, as the resulting lack of flexibility and vendor lock-in is proving too costly.”

From feature to requirement

The most visible consequence of the shift is in how broadcasters write their requirements documents.

API quality has moved from a technical detail evaluated alongside other features to a procurement criterion that can disqualify a vendor before product capability is considered.

“Rich, well-maintained APIs are no longer a feature to evaluate — they are a procurement requirement, because a best-of-breed architecture only delivers its promise when every component can be orchestrated, monitored, and replaced without rebuilding the surrounding pipeline from scratch,” said Zabel.

Advertisement

The framing matters because it inverts the traditional evaluation order. A vendor with a strong product but limited APIs is now read as a long-term risk regardless of feature depth. A vendor with open, documented integration surfaces becomes viable even when individual capabilities are less complete than competitors.

That inversion is reshaping vendor strategy.

“Customers are pushing for open, software-driven architecture that combines best in class tools without risking reliability,” said Guillaume Aubuchon, VP of product management at Avid. “That’s why we’re investing in lightweight connectors, open APIs across Avid. The intent is to give customers broader choices, while ensuring tools work together seamlessly.”

The vendor argument has shifted accordingly.

Where vendors previously sold the convenience of a single accountable supplier, the same vendors are now selling the depth and quality of their integration with third-party systems.

The technical debt of getting it wrong

The cost of building workflows around proprietary integrations is rarely visible at the moment of construction. It surfaces later, when a component needs to be replaced.

“Organizations often underestimate the cost of proprietary integrations until they have to replace a vendor, at which point that technical debt becomes very visible,” said Geoff Stedman, CMO at SDVI.

Zabel described the same pattern in more detail.

“One-off custom integrations are a technical debt trap: they work at the moment of build, but they become the most expensive and fragile points in the system the moment either vendor ships a breaking change, which makes API quality and vendor commitment to maintaining them a long-term operational risk calculation, not just a technical one,” said Zabel.

The framing reaches beyond engineering teams. A procurement decision that requires custom integration work creates an ongoing maintenance liability rarely captured in initial cost models. Each vendor update on either side of the integration becomes a potential point of failure that engineering must manage indefinitely.

Several respondents in the roundtable described the same lesson learned in different terms. Aler called it the cost of vendor lock-in. Stedman described it as the friction of swapping components.

Derek Barrilleaux, CEO of Projective, pointed to the absence of well-documented APIs as a sign that a vendor had not internalized the change.

Advertisement

“Well-documented and open APIs are key; many legacy vendors seem to offer APIs as an afterthought,” said Barrilleaux. “But if you have smart, modern tooling with open APIs, the interoperability becomes easier and — just as important — can evolve as things change.”

Platform pitches meet pluggable demand

The procurement shift is arriving at the same moment vendors are repositioning their portfolios as platforms rather than products, a transition examined in the companion piece on the broadcast industry’s move from products to platforms.

That creates a tension the next several years of vendor competition will need to resolve.

A platform sells well to customers who want a single accountable supplier and a consistent operational interface across functions. The same platform pitch sells less well to customers who have built workflows around multiple vendors and want those workflows to keep working without renegotiation.

The resolution, in most vendor responses, is the same word: interoperability.

“There is much less tolerance now for closed operational islands,” said Yaya Selva, CMO at Net Insight. “As workflows become more distributed and more software-defined, customers are putting real weight behind open standards, open APIs and architectures that let them combine specialized solutions without creating new long-term lock-in.”

What the vendor and customer positions share is a starting premise: no single vendor will cover the full workflow.

“The reality of a modern media supply chain is that no single vendor covers the full workflow, and most organizations have stopped trying to force that model,” said Stedman.

Where they differ is on the consequence.

Vendors offering platforms argue that a strong orchestration layer can govern an ecosystem of best-of-breed tools while preserving the operational consistency that single-vendor stacks once provided. Customers, in the procurement criteria they now apply, are reserving judgment on whether that promise survives contact with deployment.

Advertisement

What stays and what goes

The procurement shift does not erase the role of the established vendor.

Broadcasters with significant legacy infrastructure are not replacing it on a vendor’s preferred timeline, and several respondents described modular modernization rather than wholesale replacement.

“Many are operating a mix of legacy hardware, newer software platforms, cloud services and remote collaboration tools,” said Bob Caniglia, director of sales operations, Americas at Blackmagic Design. “A modular approach makes it easier to preserve previous investments while still modernizing the overall workflow.”

The common transport layer that allows that modular approach to function is increasingly standards-based.

“ST 2110, in particular, has become the common transport layer that everything builds on,” said John Mailhot, SVP of product management at Imagine Communications. “That gives broadcasters the freedom to evolve their infrastructure over time without having to replace everything at once or lock themselves into one approach.”

The vendors that built workflows on closed standards are the ones now facing the procurement shift most directly. The vendors that participated in standards bodies and built open integration surfaces have a structural advantage in a market that has stopped rewarding lock-in.

What this means for buyers is not that the single-vendor relationship disappears. It is that the question being asked of vendors has changed.

The capability question, what does your product do, still matters. The question that now sits above it, what happens to our workflow when we replace your product, is the one that decides procurement.

The overall shift is a maturing of decision-making in broadcast technology. The terms in use, including supply chain, governance and technical debt, are drawn from disciplines that have managed similar transitions in other industries.

Broadcasters have changed how they buy. Vendors are still adjusting to how they sell.