Plain-language project guide

Which MiroTalk should you choose?

Start with what you want to do, how many people you need to connect, and what you want to spend on infrastructure. You do not need to understand WebRTC to make the right choice.

Open source, self-hosted, and browser based
MiroTalk video meetings on desktop and laptop
Focused building blocksDifferent jobs, audiences, and budgets, not seven versions of one app.
The key distinction

Three layers, not seven competing apps

First choose the communication experience. Add a portal or admin dashboard only when you need those extra layers.

Communication products

Where people actually meet, call, or broadcast.

SFUP2PC2CCMEBRO

User portal

WEB schedules and organizes meetings for users.

Infrastructure

ADMIN manages services running on your servers.

Quick chooser

What do you need?

Pick the outcome closest to yours. We will point you to the best starting place.

SFU
Best match

A complete meeting platform

The safest default for scalable group meetings, webinars, and a Zoom-like experience.

Explore SFU
Communication products

Where calls and meetings happen

These products deliver the live experience. Their differences are workflow, audience size, and where media traffic goes.

MiroTalk P2P small group meeting
P2PSmall meetings
Lowest cost

Minimal infrastructure

Participants send media directly to each other. Your server mainly helps them connect, keeping routine hosting costs low.

Best forSmall groups
Server costLow ●○○
Trade-off: More people put more load on every user's device. TURN relay traffic can add cost.
MiroTalk C2C one-to-one call
C2CCam to cam
Simplest

Just a one-to-one call

A focused two-person experience and a practical base for embedding or customizing video without a full meeting platform.

Room sizeExactly 2
Server costLow ●○○
Trade-off: Fewer features; not intended for group meetings or broadcasts.
MiroTalk CME click-to-call interface
CMEClick to call
Call workflow

Call a specific person

Let a user accept an incoming call. Push notifications suit support, consultations, and telehealth-style workflows.

Best forDirect calling
Server costLow ●○○
Trade-off: Specialized around calling people, not conventional large meetings.
MiroTalk BRO broadcast interface
BROBroadcast
One to many

Broadcast to viewers

Optimized for one presenter and an audience. Use P2P mode for small audiences or SFU mode when you need better scale.

Best forLive audiences
Server costVariable ●●○
Trade-off: P2P is cheaper; SFU mode costs more but supports larger audiences.
Supporting products

Add organization and control

WEB and ADMIN do not replace a communication product. They sit around it and solve different problems.

MiroTalk WEB scheduling dashboard
For end users

WEB organizes meetings

A portal for accounts, rooms, schedules, and invitations that connects users to your communication products.

Explore WEB
MiroTalk ADMIN dashboard
For administrators

ADMIN runs infrastructure

Monitor, configure, update, start, and stop MiroTalk services across your servers.

Explore ADMIN
At a glance

Cost and trade-off comparison

Relative guidance, not hosting quotes. Actual cost depends on concurrent users, quality, traffic, region, and media relaying.

Project What it does Typical scale Media path Server cost Main trade-off
SFU Meetings and webinars Small to large Media server Higher More infrastructure
P2P Small meetings Small Between users Low Harder on user devices
C2C Camera calls 2 people Between users Low Only two participants
CME Direct calling 1-to-1 focused Between users Low Specialized workflow
BRO Broadcast Small to large P2P or SFU Low to higher Audience changes cost
WEB Meeting portal Any Not a media engine Additional Needs communication app
ADMIN Infrastructure control Multiple instances Not a media engine Additional Not needed for simple setups

TURN note: Restrictive networks may force P2P media through a TURN relay. Relayed traffic consumes server bandwidth and can increase cost.

No jargon required

Where does the video travel?

This explains most of the difference in scalability and running cost.

P2P: between people

Every participant sends video directly to the others.

Cheaper server, limited room size

SFU: through your server

Each person sends once; the server forwards the right streams.

SFU
Higher cost, much better scale

BRO: from one to many

One broadcaster sends to viewers directly or through an SFU.

For audiences, not equal participants
Why separate projects?

Focused codebases are a feature

No architecture is cheapest, simplest, and most scalable in every situation.

01

Different workloads need different architecture

P2P minimizes server cost. SFU spends more resources to make larger rooms practical. BRO centers an audience.

02

Self-hosting makes cost a real decision

A two-person call and a conference with hundreds of viewers should not force the same infrastructure footprint.

03

Open source is a starting point

A focused C2C or CME codebase is easier to adapt than stripping most features from a huge platform.

04

The products can work together

Use WEB to schedule an SFU meeting, then ADMIN to maintain the SFU deployment.

Still unsure? Start with SFU.

For most people seeking a modern, self-hosted video platform, SFU gives the most complete experience and clearest path to growth.

Explore MiroTalk SFU
MiroTalk SFU on laptop and mobile