A short YouTube presentation by Tsahi Levent-Levi explaining the "origin story" concept for video API vendors: where vendors started (video API, voice/CPaaS, SaaS conferencing, or IaaS/cloud) and how those origins shape their capabilities, business models, and market positioning. The speaker notes that some vendors span multiple origins (e.g., acquisitions) and refers listeners to a longer report for details.
One of the things that I try to explain in my video API report is the notion of origin story. The origin story of the video API vendors. Where do they come from once they get into this market of video APIs? So the most apparent one is the ones that are in the video API market. This is how they started, this is what they began life as. There are several vendors there and it's like this is what they do. Then you started seeing other types of vendors. These are voice API vendors, CPaaS, communication platform as a service vendors that offer voice and SMS that decided one day that they want to also introduce video and support video APIs within their platform. Then there are SaaS, software as a service vendors. These are vendors that do video conferencing solutions, web meeting solutions and other types of SaaS services. They have video capabilities and they have the video know how infrastructure. But they decided to look for a slightly different market, either by pivoting to that market and leaving the original market, or doing both at the same time. So they come from a video infrastructure experience and go into the video API market. Another type of vendors are the IaaS vendors. Infrastructure as a service, cloud compute vendors that provide compute, network, CPUs, memory, machine storage, whatever. And they decide one day that doing video is also interesting enough to offer that as a service to their customers and not only the infrastructure for building such services. Okay, now all of these vendors today go and try to offer video API vendors. Whoever you go and choose out of these types of vendors with their own origin stories will also indicate what kind of capabilities you're going to get. What is the business business model going to be in, what their focus is? Deciding which to choose is rather important. Now, interestingly, the numbers that I've placed here are the number of vendors of each type that are covered within the report itself. Some of them come from two different origin stories. For example, a voice API vendor or a SAS vendor that decided to acquire another video API vendor. Okay, so what is their origin story? Is that the one that they acquired or the one that they were before that acquisition? An interesting question. Okay, if you want to learn more about video APIs, the vendors and the market, check out my report. It's a good read.
Meta rebuilt AV1 for mobile scale. Should smaller teams follow? | Chats with Arin
