Lambda Replaces Mux Utility Jobs
Lenny Bogdonoff, co-founder and CTO of Milk Video, on the video infrastructure value chain
Lambda turns basic video processing into cheap compute work, which squeezes the standalone value of infrastructure vendors like Mux at the low end. For Milk, jobs like transcoding, resizing, and packaging a file for playback can be broken into small FFmpeg based steps, run for seconds inside AWS, and written back to S3. That makes the expensive part less the code itself, and more the higher level workflow, analytics, and reliability layers around it.
-
Milk is not talking about replacing all of Mux at once. The replaceable pieces are the utility jobs that happen after upload, like converting formats, resizing, and clipping. Milk already described running FFmpeg in Lambda for cents, versus paying Mux several dollars per hour of video.
-
Mux’s defensible layer is the part that is hard to rebuild with a few serverless functions. Mux bundles ingest, storage, delivery, playback reliability, and especially video performance analytics. Mux itself describes the product as giving developers a source file in and a playable URL out, plus monitoring for how video performs in the field.
-
This build versus buy split shows up elsewhere in the stack. Wistia built its own encoding because third party video infrastructure would have crushed gross margins at scale, but still uses Mux for performance data. Wistia also frames infrastructure as a COGS category where customers keep pushing price down unless the vendor offers something hard to replicate.
The direction of travel is that more of the raw mechanics of video become default features of clouds, browsers, and bundled platforms. That pushes specialist vendors upward, toward analytics, interactivity, developer workflow, and full end to end products. The companies that win will be the ones owning the hard to commoditize layer, not the ones charging a premium for routine processing.