DISCLAIMER: This page is for information only. It is not legal, financial or procurement advice and does not replace your own due diligence. Licenses, ownership, features and certifications can change: confirm what your decision rests on with the official sources.
🩺 Vitals
- 🟢 Last active: 2026-10-26
- 📦 Latest release: No stable release on the forge
- 🐞 Open issues: 0
- 🌟 Stars: 4.8k
What do these metrics mean?
- Last active: when code was last pushed, as of our last check. The dot is green when that was recent, grey otherwise. A long gap can mean a tool is finished and stable, not only unmaintained.
- Latest release: the most recent stable version the maintainers published as a release on the forge. Some healthy projects publish only tags, or publish their versions elsewhere.
- Open issues: unresolved reports and requests. A high number is normal for a popular project and is not a warning on its own.
- Stars: how many people bookmarked the project on its forge. A rough popularity signal, not a measure of quality.
🏗️ Profile
- Official: docs.mirotalk.com
- Source: github.com/miroslavpejic85/mirotalk
- License: AGPL-3.0-only
- Deployment: Docker Container | Language Runtime (Pip/NPM) | Kubernetes (K8s)
- Jurisdiction: Italy 🇮🇹 / EU 🇪🇺 (Individual Maintainer)
- Compliance (SaaS): p2p.mirotalk.com: none published
- Compliance (Self-Hosted): Self-Hosted (User Managed)
- Complexity: Low (2/5) - One Node.js service with no database; a TURN relay for restrictive networks is recommended, not required
- Maintenance: Low (2/5) - Pulls of a rolling image with no versioned releases and nothing to back up; each participant sends media to every other, so room size rests on their upload bandwidth
- User Management: Moderate (3/5) - OIDC sign-in, host logins with per-login room lists, a presenter role and TLS in its own server in the free build; no audit log
What the scores mean: Reading the Scores
1. The Executive Summary
What is it? MiroTalk P2P is a browser-based video conferencing tool for private calls and small groups, where audio and video flow directly between participants over WebRTC. It covers screen sharing, recording to the user's own device, chat, a whiteboard, a shared editor, polls, breakout rooms and file sharing, and embeds in other sites and apps.
The Strategic Verdict:
- 🔴 For organisations that need an audit trail or large meetings: Caution. The free build keeps no log of who did what, and each participant sends media to every other, so rooms stay small (User Management, Maintenance).
- 🟢 For teams that want private calls on a server they control: Conditional Buy. Media flows directly between participants and the server keeps no meeting content; the operator must replace the public relay and Google's server and stop the maintainer's analytics (What is it?, Cost of Ownership, The Compliance Shift, Jurisdiction).
2. Cost of Ownership
| Cost Component | MiroTalk P2P (Self-Hosted) |
|---|---|
| Pricing Model | No license fee under AGPL-3.0-only; paid license for other terms |
| Operations | Single small VM, grows with TURN relay traffic; plus your team's time to run it (Maintenance, in the Profile) |
| Support | From the maintainer: p2p.mirotalk.com, a managed service, and paid support for self-hosted installs (enterprise support); elsewhere, a paid service provider |
| Exit | No stored data (.env config) |
What each row covers: Total Cost of Ownership
3. Risk Assessment
- Jurisdiction: The project is controlled by one person (Individual Maintainer), based in Italy, under EU law and the GDPR. The maintainer runs p2p.mirotalk.com, a hosted service where your data can live, hosted only by parties domiciled in the EU. A self-hosted install sends usage data to the maintainer unless the operator switches it off.
- The Compliance Shift: By default, calls that cannot connect directly relay encrypted media through a free public TURN service, and Google's STUN server sees each participant's address, until the operator replaces both. Self-hosting moves the security and compliance duties of running the software to the operator (the operator's compliance checklist).
- License Risk: MiroTalk P2P is under AGPL-3.0-only, an OSI-approved network copyleft license (what it allows and requires). The project moved to these terms from ISC in 2021. Contributors keep the rights to their code and no agreement transfers them, so moving future versions to terms without copyleft would need every holder's consent. The maintainer says rebranding needs one of the paid licences, a condition the AGPL-3.0 licence file itself does not carry.
4. Market Landscape
🏢 Proprietary Incumbents
- Zoom Workplace: Zoom Workplace is a hosted service for video meetings, team chat and docs.
Data held by: Zoom Communications, Inc., United States 🇺🇸, subject to the US CLOUD Act for the data it holds, wherever it is stored.
Why teams leave: Its privacy notice lets advertising and analytics partners analyze users' interactions with its app.
Exit: Cloud recordings with transcripts and meeting chat through the Cloud Recording API (MP4, M4A, VTT, TXT); Team Chat messages through its API, partial export (participant data for older meetings) - Microsoft Teams: Microsoft Teams is a cloud service for chat, calls and online meetings at work.
Data held by: Microsoft Corporation, United States 🇺🇸, subject to the US CLOUD Act for the data it holds, wherever it is stored.
Why teams leave: Encryption with its customers' own keys needs a top Microsoft plan or a paid add-on.
Exit: Teams Export APIs (Microsoft Graph)
🤝 Open-Source Alternatives
- Jitsi Meet: Apache-2.0 self-hosted video conferencing for web and mobile, with optional end-to-end encryption: no per-seat fees, no cloud dependency, full data residency.