Mercury, Quicksilver Stream and a streaming platform you can change without rebuilding itSome months ago Tom Richardson of Mercury called me. He had read two of my articles, and one sentence in the second had caught the room's attention: "the stack is the product". We ended up doing strategy work together, so read what follows as coming from someone with a stake in the outcome.My guest on A Guy With A Scarf is Stephen Tallent, who founded Mercury in 1996 and carries the CEO and CTO roles together. He is an authentic product and technology person, and you can feel it in the interview: he attaches conditions to his own claims, names the tensions in Mercury's model openly, and makes no promise he cannot explain.Swapping a vendor without touching the appsA sports app on match night runs on Roku, Apple TV, connected TV, mobile and web, with authentication, video and analytics providers behind every client. Stephen puts the business logic in one set of APIs and lets the apps "focus on the pixels".His example is authentication. A provider will offer an SDK to drop into each app, which saves time at the start and ties you to that vendor. If it gets acquired, the change lands in every app at once. "The path of least resistance can very often be the worst decision for those client apps," he said.I pushed on whether this survives a real project. "In most cases, absolutely. Now it takes planning from the beginning."Where Quicksilver Stream came fromFor years big brands picked a video platform, hit its walls, and called Mercury to write the custom middleware around it. "That integration layer is basically everything," Stephen said. "That is the duct tape that's holding up these apps." Mercury waited until the same pain showed up at several customers, then built the common part into Quicksilver Stream. "We're developers and we're just trying to make our own life easier because we know the right way to do it."What intrigued me is that it is not yet-another-streaming-platform. It sits between the client apps and the vendors a customer chooses, so JW Player, Mux or an authentication provider can change underneath it.Lock-in, including to MercuryStephen prefers the word control to ownership. His claim of no lock-in, Mercury included, sounded bold from a vendor, so I challenged it. "If you provide a good product and you provide good service, they're gonna stay with you whether they have to or not." He then named the tension himself: "A customer needs control, but the platform vendor needs to be able to make money."When a client hires its own developers, Stephen says Mercury has supported that for a dozen customers and encourages it.A producer builds a page by typing a requestAt IBC in Amsterdam I built a database of what vendors said about AI. Mercury is my client, so I report only what I saw on screen. I described a feature I wanted, a producer trying a new page layout in plain language, and the team did it in front of me on the working platform. I had thought my idea was clever, and the feature already existed, so I felt a mix of embarrassment and surprise.Stephen's example is a scary movies page for October, built by an editor with no developer involved. The limit comes from him: "it may work when one person hits it." I have not load-tested anything, so his claim for game-time traffic stays his until a customer proves it at tip-off.Three questions for your own architectureWhich vendor swap would stall your roadmap today? What would your editors build if they could try five versions of a page, one per audience segment, without waiting for a developer? Who holds the keys to your endpoints on the day your current supplier is acquired?To see Quicksilver Stream, visit mercury.io and schedule a demo. If you want an introduction, write to me and tell me what you want to see.https://mercury.io/quicksilver