Enterprise and startup video infrastructure
Lenny Bogdonoff, co-founder and CTO of Milk Video, on the past, present and future of Javascript
This points to a basic rule of infrastructure markets, the vendor builds first for the customer segment that pays the biggest bills, then adapts that product downward for startups. Mux built strong enterprise muscles through video analytics sold to large media customers, while its video API was aimed at developers adding video inside apps. Milk sits in between, where the product is useful, but the economics are watched much more closely.
-
Mux itself describes a split market. Its data product found early success with enterprise customers like large media companies, while the video product started more developer first and worked toward enterprise requirements like captions, DRM, and heavier compliance needs.
-
That creates a practical pricing tension. For a startup using video as an app feature, video spend lands in COGS and gets scrutinized line by line. Milk separately noted that running FFmpeg on AWS Lambda could be cents versus paying Mux premium rates, which is why the product can feel great but still look expensive.
-
The contrast with Wistia makes the segmentation clearer. Wistia says most of its revenue comes from marketing teams buying a revenue tool, not developers buying infrastructure. In that world, higher pricing is easier to support because the buyer is paying for lead capture, embeds, analytics, and workflow, not just encoding and delivery.
Over time, video infrastructure keeps moving toward a Stripe like shape, where developer APIs win the startup and mid market layer, and richer workflow products capture higher value higher up the stack. The companies that win will be the ones that can serve both without forcing low margin infrastructure buyers to subsidize enterprise feature roadmaps.