MiroTalk SFU is an open-source video conferencing platform, licensed under AGPLv3, that runs in the browser on WebRTC and installs on your own server, so meetings, recordings and data stay under the control of whoever runs it. It uses an SFU (selective forwarding unit) architecture based on mediasoup, and its author presents it as an alternative to Zoom, Google Meet, Jitsi Meet and Microsoft Teams.
MiroTalk SFU key facts in 20 seconds
- Free, self-hosted video conferencing on WebRTC and mediasoup.
- No time or room limits, according to the project.
- Installs with Node.js 24 or Docker Compose.
- One-time paid licences cover closed-source or rebranded use.
The project is maintained by developer Miroslav Pejic, who also publishes other MiroTalk variants, and had passed 3,100 GitHub stars in early November 2026. An SFU receives each participant’s stream and forwards it to the others without mixing it, which eases the load on browsers compared with peer-to-peer connections as rooms grow. A public demo at sfu.mirotalk.com lets you try it before installing anything.

Features and security
According to its documentation, it supports video up to 8K at 60 frames per second, screen sharing, recording and picture-in-picture. Video effects are processed in the browser: blurred or replaced backgrounds, filters and 3D face accessories. It includes Markdown chat, a collaborative whiteboard, a rich-text editor and file sharing, and is translated into 133 languages. It also integrates ChatGPT and DeepSeek, AI avatars and speech recognition, all optional.
For live streaming it offers built-in RTMP and WHIP ingest, the WebRTC ingestion protocol defined in RFC 9725, so OBS can connect to it. On the security side it has OIDC authentication, a host protection mode, JWT credentials, room passwords and a lobby. To integrate it with other apps there is a REST API, webhooks, Slack, Discord and Mattermost connectors and embedding through an iframe or widget.
Installing it with Node.js or Docker
The project is tested with Node.js 24 and needs mediasoup’s build requirements. On Ubuntu 24.04 LTS the documentation suggests installing build-essential, Python with pip and FFmpeg first:
git clone https://github.com/miroslavpejic85/mirotalksfu.git
cd mirotalksfu
cp app/src/config.template.js app/src/config.js
cp .env.template .env
npm install
npm start # or: SERVER_LISTEN_PORT=3011 npm startCode language: PHP (php)
With Docker Engine and Docker Compose the process is similar, using the official mirotalk/sfu image from Docker Hub:
git clone https://github.com/miroslavpejic85/mirotalksfu.git
cd mirotalksfu
cp app/src/config.template.js app/src/config.js
cp .env.template .env
cp docker-compose.template.yml docker-compose.yml
docker compose pull
docker compose up -dCode language: PHP (php)
Either way the service is available at https://localhost:3010. The real configuration lives in app/src/config.js, .env and docker-compose.yml. For an internet-facing server, the official self-hosting guide is the place to check the reverse proxy, certificates and network settings before going live. For several servers there is a k3s cluster mode described in the repository’s kubernetes directory, and it can also be installed in one click from the Cloudron App Store.
AGPL and commercial licences
AGPLv3 lets you use and modify MiroTalk SFU freely, but requires you to publish your modifications when the service is offered over a network, as the README itself points out. To build it into a closed-source or rebranded product, the author sells one-time licences: Regular, for an end product whose users are not charged, and Extended, for one where access is paid. Prices are in the official documentation.
Frequently asked questions
Is MiroTalk SFU free?
Yes, it is open source under AGPLv3. You only need to pay for a licence to use it in a closed-source or rebranded product.
Which Node.js version does it need?
The project is tested with Node.js 24, plus mediasoup’s build requirements.
Can I stream from OBS?
Yes. It includes RTMP and WHIP ingest, both compatible with OBS.
Which port does it use?
Port 3010 with HTTPS by default. It can be changed with the SERVER_LISTEN_PORT variable.
Sources:
