What it is

MiroTalk SFU is a self-hosted, open-source WebRTC video conferencing platform written in JavaScript and built on the Mediasoup selective forwarding unit architecture. It provides real-time communication and collaboration features for rooms, screen sharing, chat, file sharing, live streaming, and recording, while allowing organizations to run the service on their own server. The project positions itself as an alternative to Zoom, Google Meet, Jitsi Meet, and Microsoft Teams.

The concrete problem it solves is dependence on hosted conferencing products for meetings, collaboration, and streaming. By running MiroTalk SFU, an operator can keep data on its own infrastructure, avoid vendor lock-in, and use unlimited concurrent rooms without the time limits described for paid tiers. It lives in the open-source WebRTC and Node.js ecosystem, with Docker deployment support and integrations for Slack, Discord, Mattermost, and embeddable interfaces.

Key capabilities

• Video conferencing supports up to 8K at 60fps, screen sharing, recording, and picture-in-picture.
• Collaboration tools include Markdown chat, emoji, collaborative whiteboard, rich text editor, and file sharing.
• AI features include ChatGPT and DeepSeek integration, VideoAI avatars, and speech recognition.
• Access controls include OIDC authentication, JWT credentials, room passwords, host protection, lobby, and spam mitigation.
• Integration options include a REST API, embeddable iframe and widget support, Slack, Discord, and Mattermost connections.
• RTMP and OBS live streaming are built in, and the interface supports 133 languages.
• Deployment can use Docker, Node.js, or one-click install methods.

Who uses it and how

• Teams use it for self-hosted meetings where they need unlimited concurrent rooms and control over data privacy.
• Educators and presenters use screen sharing, whiteboard, chat, file sharing, and recording during collaborative sessions.
• Developers use the REST API, iframe, widget, and messaging integrations to place conferencing inside existing products or workflows.
• Streamers use built-in RTMP and OBS support to broadcast meetings through live-streaming infrastructure.
• Organizations use OIDC, JWT, room passwords, lobby, and host protection to manage access for internal or external participants.

Getting started

The README shows a quick start with git clone, copying config and environment templates, npm install, npm start, and opening https://localhost:3010. It also mentions Docker, Node.js, and one-click install, with Node.js 22.X and Mediasoup requirements noted for full setup.

When to use it — and when not to

Use MiroTalk SFU when an organization wants a self-hosted WebRTC alternative to Zoom, Google Meet, Jitsi Meet, or Microsoft Teams and can operate the required server, Node.js, Mediasoup, and Docker infrastructure. Avoid it if an organization needs a managed service with no self-hosting burden, because the project expects the operator to handle deployment, access controls, and infrastructure. AGPL-3.0 licensing and available one-time fee licenses mean teams should review licensing obligations before choosing this platform.

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

apt-get update
apt-get install -y build-essential
DEBIAN_FRONTEND=noninteractive apt-get install -y tzdata
apt install -y software-properties-common
add-apt-repository -y ppa:deadsnakes/ppa
apt update
apt install -y python3.8 python3-pip
apt install -y ffmpeg

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 start

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    # optional: pull official image
docker-compose up      # add -d to run in background