At NAB in April, Sam Phillips, who runs architecture strategy and emerging technologies at AMC Global Media, spoke on an AWS panel about a system his team had built called PRISM. It sits on top of their media asset management systems, the databases a company uses to track where every piece of content lives, what version it is, and what has been done to it. Its purpose was to widen internal access to those assets and to find out what generative AI could do with them.
The reason he gave for it working is the part worth slowing down on. AMC had assets spread across locations, storage systems, and formats. Consolidating all of that into one environment before doing anything else was not a realistic starting point. So they went up instead. Phillips said they were inspired by the media lake concept, the idea of moving up in the architecture, and that this was why they got into production so fast, because they could move without needing to worry about what their current state was.
The constraint came first and the architecture answered it. Paul Dulac of AWS, on the same panel, described the mechanism from the vendor side, with S3 holding the assets as a single source of truth and PRISM handing references and pointers to the systems downstream, so editors could work immediately.
Nobody on that panel used the word reversibility, but that is what Phillips was describing. PRISM delivers access. What building it protected was something else, which is the ability to change things later without having to fix everything underneath first. The alternative was to consolidate first, agreeing on one storage system and one set of formats and one place where everything lives. At AMC’s scale that is not a step before the project. It is a larger project than the one it was supposed to enable, and nobody sees a benefit until it finishes.
What He Was Actually Protecting
The industry calls this lock-in, and the label misleads. Lock-in describes a condition imposed by a supplier, usually through a contract or a proprietary format, and it implies a villain. Most of what actually constrains a media operation has no villain in it.
AWS, of all parties, makes the cleaner argument. In its own guidance on the subject, and in an archived whitepaper written to address the concern directly, the company argues that lock-in is a misleading term and that what organizations really have are switching costs. Choose Java, migrate later to Node, and you pay something. The cost has existed throughout the history of the industry and it attaches to every commitment anyone has ever made.
That useful reframing is correct but it is also self-serving. It concedes that the property exists while implying it can be assessed. You know what you committed to, so you can reason about what leaving would cost.
Engineers have a name for the neighboring idea. Technical debt is the cost of a shortcut somebody took on purpose, and it comes with an author, a date, and usually a ticket. What we are describing has none of those, because nobody chose it and nobody deferred it.
Here is where the reframing breaks. A component diagram tells you what the pieces are and how the signal moves between them. It does not tell you what any of those pieces costs to replace. Those are different questions and only one of them can be drawn. An architect knows a single view never captures everything, and the discipline has whole practices built around that limitation. The problem is not that architects are naive. It is that the industry has started reading component diversity as evidence of reversibility, but it has never been a measure of that.
Everyone Is Hybrid Now
Which matters more this year than last, because the stacks have stopped looking like anyone’s category.
Avid arrived at IBC 2026 with Media Composer 2026.8, and the announcement leads with openness. Broadened collaboration choice. Third-party storage support. An OpenTimelineIO 2.0 adapter for round-trip fidelity with other tools. Expanded APIs. A Google Gemini panel and an agentic orchestration layer sitting across the workflow. Read the feature list and you can see a company distributing itself deliberately across other people’s components.
Read the same announcement for what moved between tiers and something else appears. Shared Projects is the capability that lets several editors work on the same material at the same time, which is how any facility of size actually runs. On Avid’s own Nexis storage, that capability comes down to the standard tier. The supported path for doing the same thing on qualified third-party storage sits in enterprise, at the top of the product line. Both changes are in the release that announced broadened choice, neither is hidden, and it is all on a price list. It drew enough criticism to make the trade headline.
Akta comes at it from the other direction. Its pitch is consolidation in its purest form, a unified AI-first platform meant to replace the collection of tools a media company uses to move, understand, repurpose and measure content, all inside one cloud. Then in June the platform went generally available on Oracle Cloud Infrastructure, and the reason given, as reported at the time, was lower-cost egress and native routing making full cloud production practical. Egress pricing is what a cloud provider charges to move data out, and it is one of the most commonly cited reasons that further cloud adoption stays difficult for media distributors. The company selling freedom from stitched-together tools changed the ground underneath itself over what it costs to leave.
Two companies, opposite strategies, and in both cases the fact that matters is on a pricing page rather than in an architecture description. Neither is doing anything underhanded. Both are behaving rationally. And an operator comparing them on capability would see none of it.
Below the line, a broadcaster replaces one component, spends the next ten months on everything attached to it, and shows you the cost that no architecture diagram will ever display.
