In brief
Cloudflare Stream’s WebRTC broadcasting is generally available, with usage-based billing. Event teams should test the whole audience experience.
What is available
Cloudflare announced general availability of low-latency WebRTC live delivery in Stream on 15 October 2026. Its announcement describes browser-based broadcasting, updated WHIP and WHEP protocol support, and delivery information in Stream analytics.
Usage-based billing for WebRTC began on the same date. Cloudflare positions Stream as a managed one-to-many broadcast service, while Realtime provides building blocks for many-to-many experiences. Check the current pricing and documentation before estimating a project.
Where it may fit
Our editorial view is that this is relevant when a business wants live video inside its own event or member experience, rather than only linking to an external broadcast page. A product demonstration with a coordinated on-site audience is one example to evaluate, not a claim of an existing Miracode deployment.
Low latency can be useful when timing matters, but it does not solve registration, access control, moderation or audience support. Those remain separate parts of the product brief.
Test the experience outside the office
Rehearse from the actual venue and representative audience devices. Include a viewer on a weaker connection and someone joining after the session has begun. An attractive player on a fast office network is not enough evidence for launch.
- Verify camera and microphone permissions before the event.
- Check access rules for members, guests and expired links.
- Estimate viewing minutes across the expected audience and duration.
- Decide how the team communicates if the live feed fails.
- Specify recording and replay requirements independently.
Choose the simplest suitable broadcast
For a straightforward public announcement, an existing hosted video platform may already meet the requirement. A custom experience is more compelling when registration, branding, membership or interaction needs justify the extra work.
Before committing, describe the viewer journey from invitation to playback and support. Then evaluate the video service as one component of that journey, with an explicit budget and a tested fallback.
