MiroTalk C2C
Self-hosted cam-to-cam video calling designed for iframe embedding. Two-participant only, end-to-end encrypted, with screen sharing. Built to drop into any website as a lightweight video widget
Quick Start
docker run -d -p 8080:8080 mirotalk/c2c:latest Overview
MiroTalk C2C is the smallest and most focused of the MiroTalk tools. It handles exactly one use case: a private, end-to-end encrypted video call between two people, designed to be embedded in any website as an iframe widget. There is no room for a third participant, no group call feature, and no complex configuration — just a clean 1-to-1 video connection you can drop into an existing product.
The target use case is a live video widget embedded into a website or application. A customer support chat that escalates to video, a client portal where the user can call their account manager directly, or a SaaS product that needs 1-to-1 video without paying a per-minute API fee. Because it runs on your own server, no media passes through a third-party service.
Screen sharing is included. Chat, whiteboard, and recording are not — the tool is intentionally minimal. Recent commits show active security maintenance: XSS mitigations in the chat layer and a new ALLOWED_EMBED_ORIGINS environment variable to restrict which domains can embed the iframe via CSP frame-ancestor headers.
For groups larger than two, or for standalone meetings without embedding, MiroTalk P2P or MiroTalk SFU are the better fit.
MiroTalk C2C: Pros & Cons
| Pros (The Wins) | Cons (The Friction) |
|---|---|
| Built for embedding: iframe-first design; drop into any page with minimal config. | Two participants only: Hard limit; no group calls of any size supported. |
| End-to-end encrypted: WebRTC direct connection; no media touches a cloud server. | Minimal feature set: No chat, whiteboard, or recording by design. |
| Self-hosted: No per-minute API fees; runs on your own server. | Small community: 508 stars; less documentation and fewer third-party resources. |
| Actively maintained: Recent security patches and CSP embed controls. | AGPL-3.0: Commercial SaaS use requires source disclosure. |
Use Cases
Specific ways to use MiroTalk C2C for your workflow.
Deployment Strategy
Recommended ways to host MiroTalk C2C in your own environment.