MiroTalk C2C is a self-hosted, open-source WebRTC application for one-to-one video calling that gives teams and operators private, browser-based cam-to-cam conversations for consultations, coaching, support, and telehealth without handing media to a third-party service.

What it is

MiroTalk C2C is a JavaScript application built on WebRTC for peer-to-peer, one-to-one video calls in the browser, with screen sharing and end-to-end encryption. It is authored by Miroslav Pejic, released under AGPL-3.0, and lives in the WebRTC and Node.js ecosystem; it ships as a git repository that runs through npm install and npm start, and also as a Docker image published on Docker Hub as mirotalk/c2c. The project sits in the Business Software / Collaboration & Communication category, carries 513 stars and 97 forks, and is documented at docs.mirotalk.com, with a live demo at c2c.mirotalk.com.

The concrete problem it solves is dependence on hosted third-party video-call services for private one-to-one conversations. Because the call is peer-to-peer, media travels between the two browsers rather than through a central media server, and because the operator runs the instance, the deployment stays under their own control. That matters for workflows where the conversation is sensitive and the infrastructure should not be rented from or visible to an outside vendor, such as telehealth appointments, coaching sessions, customer support calls, and client consultations. The same build can be embedded into an existing website, so an organisation does not need a separate meeting product to offer a call button.

Key capabilities

• Peer-to-peer cam-to-cam video calling between exactly two participants over WebRTC, with low-latency real-time communication.
• End-to-end encryption for the call, listed under both e2e-encryption and end-to-end-encryption in the repository topics.
• Screen sharing alongside the video call.
• Embeddable in any website through a simple iframe integration, so a call can live inside an existing product or page.
• REST API for programmatic control, plus a direct room join flow documented at docs.mirotalk.com.
• Configuration through a .env file created from .env.template, covering the instance's runtime settings.
• Container deployment using Docker Compose with docker-compose.template.yml, backed by the official mirotalk/c2c image.

Who uses it and how

• Clinics, coaches, and support teams running scheduled one-to-one sessions where the operator wants the call traffic on infrastructure they control.
• Small teams and solo operators deploying to a VPS, with Hetzner, Netcup, Hostinger, and Contabo listed as recommended hosting providers for a MiroTalk C2C instance.
• Developers embedding one-to-one calling inside an existing website via the iframe integration, rather than sending users to an external meeting tool.
• Operators automating deployment and maintenance with the automation scripts documented at docs.mirotalk.com/scripts/about/.
• Administrators exposing a local instance through Ngrok when a public address or certificate is not otherwise available, following the Ngrok guide in the documentation.

Getting started

Clone the repository, run cp .env.template .env, then npm install and npm start, and open http://localhost:8080. The Docker path copies docker-compose.template.yml to docker-compose.yml, runs docker-compose pull for the official image, then docker-compose up, and serves on the same port.

How it compares

The facts provided for this registry name no competing or paid products that MiroTalk C2C is positioned against, and no sibling one-to-one video-calling tools are listed either. On the evidence available, it stands alone in this registry.

When to use it — and when not

A self-hoster has to operate the Node.js service or the Docker Compose stack, edit .env and docker-compose.yml to match their setup, and arrange a public address, which the Ngrok guide exists to work around. It is also a strictly one-to-one product, so anyone who needs group calls or conference-style many-to-many meetings should look elsewhere, and the AGPL-3.0 licence is a copyleft licence that organisations embedding the code in a proprietary product must review before adopting it.

git clone https://github.com/miroslavpejic85/mirotalkc2c.git
cd mirotalkc2c
cp .env.template .env
npm install
npm start

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