What are the primary use cases for developers using Mux and what types of customers benefit the most from the product?

Adam: We have two products today. We have our data product and our video product.

The data product was the first thing that we built, and it is an analytics collection tool set for collecting video end-user experience metrics. We build SDKs that integrate with video players that then let us analyze and present metrics on how well their full video stack is performing. As developers, the use case here is you're trying to make a choice between video player A and B or video delivery stack B and C, and you can see how all of these things are performing compared to each other. That's in the developer workflow set. Then once you have it up and running, it becomes your monitoring for that as well. For larger livestreams and things like that, these kinds of monitoring use cases can be really important. You can actually make real-time decisions based on some of this stuff.

The video product is the full end-to-end solution. You give us a video source file -- whether it be live or a video on demand, like a recording -- and we handle all of the hard bits in between: the transcoding, the storage, and the delivery, including that last-mile delivery -- that CDN to ISP delivery -- as well. At the simplest, you give us a file and we give you a URL to drop into the video player, and it's going to work everywhere.