MiroTalk SFU

Simple, secure, scalable real-time video conferences up to 4k, compatible with all browsers and platforms.

Healthy · 70
70/100
Healthy

Actively maintained with regular releases.

Maintenance 30/40
Releases 13/25
Community 12/20
Momentum 15/15

Commit activity more than 75% of tracked projects; popularity more than 58%. How this is calculated.

Commits, last 11 months

2025-12: 85 commits 2026-01: 19 commits 2026-02: 37 commits 2026-03: 68 commits 2026-04: 133 commits 2026-05: 84 commits 2026-06: 16 commits 2026-07: 28 commits 2026-08: 112 commits 2026-09: 126 commits 2026-10: 211 commits
2025-12 919 total 2026-10
Stars3.2k
Latest release—
Repo updated19 Nov 2026
LicenceAGPL-3.0
Built withNodejs, Docker

Is MiroTalk SFU actively maintained?

MiroTalk SFU is under active development: 919 commits landed over the last 11 months, averaging roughly 150 commits a month in the most recent quarter.

Activity is accelerating: the last quarter carried 251% more commits than the one before it.

No tagged releases are published, so there is no stable version to pin to — you would deploy from the default branch or a container image built from it.

Of the 10 projects we track in Communication - Video Conferencing, MiroTalk SFU ranks #3 by health score — in the top quarter of its category.

What MiroTalk SFU actually does

MiroTalk SFU is a self-hosted web application designed to facilitate real-time video conferences across multiple browsers and platforms. It utilises selective forwarding units to handle media streams, aiming to support high-resolution video outputs up to 4k. The project is distributed under an open-source licence and containerised for deployment.

Best fit: It suits teams or individuals looking for a dedicated, self-hosted video conferencing node that they can run entirely on their own infrastructure.

Worth knowing: The AGPL-3.0 licence carries strict copyleft implications if you modify and distribute the code or offer it as a hosted service. Additionally, managing real-time media routing can impose significant bandwidth and CPU demands on your server.

Deployment notes

As a Node.js application packaged with Docker, you will typically need to configure a reverse proxy to handle TLS termination and manage persistent storage or environment variables according to your setup.


MiroTalk SFU as a replacement for


Alternatives to MiroTalk SFU

Projects in the same categories, ordered by health score.