MiroTalk P2P
Self-hosted WebRTC video conferencing with direct peer-to-peer connections. Minimal server load, no time limits, and up to 8K at 60fps. Best suited for small groups and 1-to-1 calls
Quick Start
docker run -d -p 3000:3000 mirotalk/p2p:latest Overview
MiroTalk P2P is a self-hosted video conferencing tool built on direct WebRTC peer-to-peer connections. Participants connect to each other through their browsers — the server establishes the connection through signalling but does not touch the media streams. This keeps server load low, making it practical to run on modest hardware where an SFU-based tool would demand more resources.
The feature set covers the standard video call workflow: screen sharing, in-meeting chat with Markdown support, a collaborative whiteboard, file sharing, and local browser recording. Video supports up to 8K at 60fps where hardware and network allow. Rooms are created on demand with no time limits, and there are no restrictions on concurrent rooms.
The architecture is the main constraint. In a P2P call, every browser connects directly to every other browser. With two or three participants this works well and feels fast. With six or more, each browser is sending separate video streams to every other participant simultaneously, and call quality degrades under the combined upload load. For larger groups, MiroTalk SFU routes all media through a server and scales further.
Deployment is a single Docker container. The iframe embed and REST API make integration into an existing web product straightforward. AGPL-3.0 covers personal and internal self-hosted use without restriction.
MiroTalk P2P: Pros & Cons
| Pros (The Wins) | Cons (The Friction) |
|---|---|
| Low server load: Signalling only; media travels directly between browsers. | Small group limit: P2P degrades past 4-5 people; use SFU for larger groups. |
| No restrictions: Unlimited rooms, participants, and call duration. | AGPL-3.0: Commercial SaaS use requires source code disclosure. |
| Full feature set: Screen share, whiteboard, chat, files, and recording. | TURN server needed: Corporate firewalls and NAT require a TURN relay to connect. |
| Easy to embed: iframe and REST API cover most integration needs. | Local recording only: No server-side recording; recordings stay in the browser. |
Use Cases
Specific ways to use MiroTalk P2P for your workflow.
Deployment Strategy
Recommended ways to host MiroTalk P2P in your own environment.