Cloudflare Realtime is infrastructure for real-time audio/video/data applications. It allows you to build real-time apps without worrying about scaling or regions. It can act as a selective forwarding unit (WebRTC SFU), as a fanout delivery system for broadcasting (WebRTC CDN) or anything in between.
Are we still quite a ways off from having an input stream and output stream of differing formats? Specifically, I have a use case where I need to stream in with SRT and output to WHEP. Stream seems like the perfect product for this, rather than running a conversion gateway locally to produce a WHIP stream.
Do you have existing accurate analytics to support your view numbers, or just basing off rough numbers? Your math is correct, but its very rare that a viewer will be watching long form content for the entire time. I do many regular 3 hour streams, with hundreds of total views, and average 5-25K minutes viewed per stream. Which means each viewer is only watching a small portion of the total runtime on average
I've asked this before, but with the Browser Rendering API and OTFE platform slowly maturing over time, is there possibility for being able to inject a HTML5 browser instance over the top of a live stream? That and input switching would be the only things I need to entirely transition from AWS
Yeah, this is all theoretical; on behalf of a client I'm doing consulting for. I too, think the numbers are ambitious, but I have to give them a cost based on their figures
From pure math, the cost is legit. But in my experience (2000 videos per year), CF Stream is the cheapest around without having huge bandwidth/view numbers (many millions)
I was able to transition 12 streams on the fly within 5 minutes to Cloudflare due to an outage with our old streaming provider and haven't looked back. Very easy to use