Our take
Activeregular commits- Activity
- 53
- Community
- 33
- Issues
- 68
- Pull requests
- 44
+20 stars in the last 10 days
MiroTalk P2P is a feature-rich self-hosted meeting option with active development, but adoption means accepting AGPL-3.0 terms and a strong dependence on one maintainer.
Good fit if
- You want to run a WebRTC meeting service on your own server and can operate a Node.js or Docker deployment.
- Your meetings benefit from built-in tools such as screen sharing, chat, recording, and whiteboards.
- You can work within AGPL-3.0 obligations, or arrange different licensing terms with the project.
Look elsewhere if
- Your team requires a project whose development is spread broadly across contributors, since most measured contribution activity comes from one person.
- You require a recent tagged release, as the project has had no release in over a year.
- AGPL-3.0 does not suit your distribution or modification plans.
All health signals
| Last commit | 2026-10-13 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 0 |
| Contributors | 27 (top contributor: 98% of commits) |
| Issues closed, last 90 days | 4 (typically closed in 1 day) |
| Pull requests merged, last 90 days | 1 |
| Project age | 5 years |
Checked on 2026-10-14 with the GitHub API.
Overview
MiroTalk P2P is a browser-based video-conferencing app that uses peer-to-peer WebRTC connections. It gives organizations and communities a way to host meeting rooms on their own server rather than relying solely on a hosted conferencing service.
Alongside video calls, it includes collaboration features such as screen sharing, chat, whiteboards, and recording. The project is actively maintained, but its measured contribution activity is highly concentrated in one person, and it has had no release in over a year.
Key Features
- Browser-based peer-to-peer video meetings, with no client downloads required.
- Screen sharing and picture-in-picture.
- Meeting chat, file sharing, and a collaborative whiteboard.
- Recording and camera background effects.
- Room passwords, OIDC authentication, JWT credentials, and host protection options.
- REST API, plus Slack and Mattermost integrations.
- Docker and Node.js deployment options.
Use Cases
- A small organization that wants to host video meetings on infrastructure it controls.
- A distributed team that needs screen sharing, chat, and a shared whiteboard during browser-based meetings.
- A community or event organizer who wants rooms without meeting time limits imposed by a hosted service.
- A product team looking to embed meeting functionality using the project's iframe or widget integrations.
What you need
Detected in the repository
- Node.js (from package.json)
- A Dockerfile, so it can run in a container
- A test suite and automated checks on GitHub Actions
License in plain words
AGPL-3.0network copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service)
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
The README documents a Node.js setup:
git clone https://github.com/miroslavpejic85/mirotalk.git
cd mirotalk
cp .env.template .env
cp app/src/config.template.js app/src/config.js
npm install
npm start
Then open http://localhost:3000. See the README and self-hosting documentation for configuration and deployment details.
Alternatives
- jitsi-meet: Jitsi Meet offers a full conferencing platform with mobile apps and SDKs, while MiroTalk P2P focuses on browser-based peer-to-peer meetings.
- mirotalksfu: MiroTalk SFU routes media through a mediasoup server, while MiroTalk P2P connects participants peer to peer.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| mirotalk | JavaScript | AGPL-3.0 | 4.8k | Active |
| jitsi-meet | TypeScript | Apache-2.0 | 30.1k | Active |
| mirotalksfu | JavaScript | AGPL-3.0 | 3.1k | Active |
Considerations
- The project is marked active and has frequent recent commits, while measured issue handling is prompt. However, contribution activity is concentrated in one person, which creates maintainer-dependence risk.
- The measured health data shows no release in the past year. Teams that depend on versioned releases should consider how they will track and validate updates.
- Self-hosting requires operating the application with Node.js or Docker. The README also describes externally loaded resources for camera background effects, which require access to their listed hosts and compatible browser capabilities.
- The repository is licensed under AGPL-3.0. Review its obligations before distributing modified versions or incorporating it into a larger product.
Found this useful?
Share it with someone who would like mirotalk.