Low Latency
Real-time WebRTC delivery without a buffered HLS workflow.
Low-Latency Live BroadcastingBroadcast Live.
Broadcast Live.
Control the Platform.
Launch branded WebRTC broadcasts from your own server with flexible P2P and SFU delivery modes for different audience needs.
Full source code P2P + SFU modes Self-hosted
2
Delivery Modes
WebRTC
Real-Time Media
$0/mo
Platform Subscription
API
Developer Ready
Own the Broadcast
Built for Live Audiences
A browser-based platform for webinars, events, announcements, education, and embedded live experiences.
Flexible Broadcasts
Choose peer delivery or server-assisted forwarding by audience needs.
Browser Based
Broadcast and watch without a dedicated desktop application.
Cross-Platform
Responsive experiences across desktop, tablet, and mobile.
White-Label Ready
Adapt the full source code to your own brand and workflow.
REST API
Create broadcasts programmatically from another application.
Dual Architecture
Choose the Right Delivery Mode
Start lightweight with P2P, then use SFU forwarding when audience size or broadcaster bandwidth calls for it.
P2P Broadcasting
The broadcaster sends a stream to each viewer. Best for smaller audiences; broadcaster upload grows with each viewer, and TURN relays when direct connectivity is unavailable.
SFU Broadcasting
The broadcaster sends one upstream feed to the SFU, which forwards media to viewers. Capacity depends on server resources, throughput, quality, and deployment design.
Embed and Automate
Broadcast Inside Your Product
Use an iframe for the complete experience or the API for programmatic broadcast creation.
Server Requirements
- Ubuntu 22.04 LTS
- 2 vCPU and 2 GB RAM starting point
- Node.js v22+ or Docker
- Domain, DNS, and SSL
- STUN/TURN recommended
Common Questions
MiroTalk BRO FAQ
Which broadcast mode should I use?
Use P2P for smaller audiences and lightweight deployments. Use SFU when one broadcaster upload needs server-assisted distribution to a larger audience.
How many viewers can it support?
There is no universal number. P2P depends mainly on broadcaster upload; SFU depends on server resources, throughput, stream quality, and deployment design.
Can I white-label it?
Yes. Full source code is included for branding and custom development.
Is it subscription-based?
No. It is a one-time CodeCanyon purchase. Hosting, bandwidth, TURN, and SFU infrastructure remain your responsibility.
Go Live
Launch Your WebRTC Broadcast Platform
One-time purchase. Full source code. P2P and SFU broadcasting modes.
Buy MiroTalk BRO