MiroTalk P2P is a free, open-source, self-hosted video conferencing platform that connects participants through direct peer-to-peer WebRTC links, aimed at teams and organisations that want browser-based meeting rooms running on their own infrastructure.

What it is

MiroTalk P2P is a JavaScript application that turns a server you control into a WebRTC meeting service. Rooms are created and joined from a browser, with no downloads and no time limits, and media travels peer-to-peer between participants rather than through a central conferencing cloud. It is distributed under the AGPL-3.0 licence and is published on the public web at https://p2p.mirotalk.com as a live demonstration of the same codebase that ships in the repository.

The concrete problem it solves is dependence on hosted conferencing SaaS. The project's own comparison table positions it against cloud-only alternatives on cost, self-hosting, privacy, time limits, concurrent rooms, resolution, language coverage, API access, AI features, rebranding and deployment method. Where those services meter meeting length on free tiers, cap room counts, restrict branding, or process data on third-party infrastructure, MiroTalk P2P replaces that arrangement with software the operator runs, holds and can modify. It lives in the WebRTC and peer-to-peer ecosystem, alongside the Docker and Node.js tooling used to deploy it.

Key capabilities

• Video calls support resolutions up to 8K at 60fps, alongside screen sharing, recording and picture-in-picture.
• In-meeting collaboration covers chat with Markdown and emoji, a collaborative whiteboard and file sharing.
• A full REST API is included rather than sold as an add-on, with JWT credentials, OIDC authentication, room passwords, host protection and peer-to-peer encryption for access control.
• ChatGPT (OpenAI) integration and speech recognition are built in, while the comparison table lists AI features as paid add-ons elsewhere.
• The interface is translated into 133 languages.
• Rooms can be embedded through an iframe or widget, and Slack and Mattermost integrations are provided.
• Deployment paths include a Docker image published as mirotalk/p2p and a straight Node.js install.

Who uses it and how

• Operators who need unlimited concurrent rooms can run the Compose stack from docker-compose.template.yml and scale meeting count without per-room licensing.
• Teams running the mirotalk/p2p image from Docker Hub, or a plain Node.js install, keep meeting traffic and configuration on their own server.
• Organisations with an existing identity provider can gate access through OIDC authentication and per-room passwords instead of issuing separate accounts.
• Product teams can embed rooms into their own applications via iframe or widget, or rebuild the front end for white-label use since the full source is provided.
• Chat-centric teams already working in Slack or Mattermost can surface meeting links through the provided integrations.

Getting started

The README gives two routes: clone the repository, copy .env.template to .env and app/src/config.template.js to app/src/config.js, then run npm install and npm start; or copy docker-compose.template.yml to docker-compose.yml and run docker-compose up, optionally pulling the official mirotalk/p2p image first. Both serve the application at http://localhost:3000, and the README directs operators to edit app/src/config.js, .env and docker-compose.yml to customise the setup.

How it compares

The registry facts name no direct open-source competitors, so MiroTalk P2P stands alone here rather than sitting beside a set of peer tools. Its README contrasts the project with unnamed cloud-only solutions: those typically carry paid plans, third-party data processing, 40-60 minute limits on free tiers, limited concurrent rooms and resolution capped around 1080p, while MiroTalk P2P is AGPL-3.0, self-hosted, unlimited in room count and duration, and reaches 8K at 60fps. An alternative one-time fee licence is offered commercially for buyers who cannot work within AGPL-3.0 terms.

When to use it — and when not to

Adopting it means operating the server yourself: a Node.js runtime or Docker Engine with Docker Compose, plus the configuration files named above, so a team with no appetite for running infrastructure will find a hosted service simpler. Shops that require a vendor support contract, or that cannot accept AGPL-3.0 copyleft obligations, should look elsewhere or buy the commercial licence. The registry entry also reflects an unusually quiet maintenance signal, with zero open issues and a README excerpt that is cut off mid-sentence, so evaluate the current repository state directly before committing.

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

git clone https://github.com/miroslavpejic85/mirotalk.git
cd mirotalk
cp .env.template .env
cp app/src/config.template.js app/src/config.js
cp docker-compose.template.yml docker-compose.yml
docker-compose pull    # optional: pull official image
docker-compose up      # add -d to run in background