Wistia In House Encoding Advantage
Ben Ruedlinger, CINO at Wistia, on the video hosting infrastructure stack
Wistia’s cost edge comes from having turned video encoding from a vendor bill into a scaled internal utility. Every uploaded file has to be transcoded into multiple playback versions, stored, and delivered, so owning encoding at Wistia’s volume protects gross margin and lets the company price as a marketing software product, not like raw infrastructure sold into COGS. That is why Wistia keeps encoding and customer analytics in house, while buying more commoditized layers like CDN delivery.
-
Wistia built its encoder before vendors like Mux, Zencoder, and Encoding.com existed, then kept scaling it for more than a decade. Ben Ruedlinger said the system now processes roughly 1 percent of YouTube’s video minutes, which is enough scale for in house economics to beat outside pricing by a wide margin.
-
The comparison point is companies like Mux, which package transcoding, storage, delivery, and monitoring into an API so a developer can upload a file and get back a working stream URL. That model is ideal for startups that need speed and simplicity, but it bakes vendor margin into a workload that becomes very expensive at large volume.
-
Smaller video companies often make the opposite trade. Milk Video used Mux for coding, then looked to replace parts of it with AWS Lambda and FFmpeg because running a short function could cost cents instead of paying a premium every time. That shows how quickly video infrastructure gets repriced once a workflow becomes common and repeatable.
Going forward, more of the video stack will be easy to buy through APIs, browser tools, and AI features, which raises the premium on the parts a company can uniquely own. For Wistia, that means infrastructure advantage matters most when it feeds higher level products for marketers, like analytics, lead capture, and publishing, where savings on encoding can be turned into better margins and faster product development.