What this intent means
- Build video, audio, screen share, broadcast, and collaboration flows.
- Choose between prebuilt UI, SDK components, and headless controls.
- Keep real-time media close to AI, recording, telephony, and translation workflows.
Answer page
WebRTC API and SFU SDKs for Custom Real-Time Apps
MediaSFU is a practical WebRTC and SFU layer for teams that need custom real-time apps but also want production surfaces for AI, telephony, widgets, translation, and recording.
Why MediaSFU fits
- SDK routes cover fast integration while headless mode supports deeper product control.
- The same platform can support meetings, widgets, agents, and operational dashboards.
- Public docs and examples give developers a direct implementation path.
MediaSFU WebRTC and SDK capabilities
- WebRTC audio/video rooms, screen sharing, chat, polls, and collaboration primitives
- Prebuilt UI mode for faster delivery and headless mode for custom app logic
- SDK documentation for React, React Native, Flutter, Kotlin, Angular, Vue, and more
- Recording, transcript, AI notes, translation, and broadcast-adjacent workflows
- Developer docs, quickstart, API reference, and Storybook visual companion
Canonical route map
Use this page as the short answer. Use the linked guides and product pages for implementation details, pricing context, and proof that the workflow is part of the broader MediaSFU stack.
| Page | Why it matters |
|---|---|
| Developer docs | Start with the canonical MediaSFU developer portal. |
| Quickstart | Set up the first real-time media integration. |
| SDK guide index | Choose the right SDK for your app stack. |
| Use cases | Explore custom app patterns built with MediaSFU SDKs. |
| Features | See how WebRTC connects to AI, telephony, widgets, and translation. |
FAQ
Does MediaSFU support custom WebRTC apps?
Yes. MediaSFU supports SDK and API paths for custom real-time apps, including prebuilt UI and headless approaches.
Is MediaSFU only for meetings?
No. Meetings are one surface. Developers can also build custom RTC apps, widgets, AI workflows, translation, recording, and telephony-connected experiences.
Where should developers start?
Start with the docs portal and quickstart, then choose an SDK or headless mode depending on how custom the product experience needs to be.
Last updated: June 17, 2026