The story behind MiroTalk
MiroTalk began in 2020 with a simple question: could real-time communication be open, inspectable, and deployable on infrastructure chosen by its users?
1. It started with a pandemic
In 2020, the world stopped, but communication could not.
Overnight, video calls became classrooms, offices, and lifelines. Like millions of others, I found myself living through a screen to stay connected with friends, family, and collaborators.
As those platforms became part of everyday life, I kept returning to the same concern: users had little control over the systems carrying their conversations or the infrastructure behind them.
2. The problem hiding in plain sight
Most widely used video platforms were closed ecosystems. Their deployment, data handling, and product direction were controlled by their operators rather than by the people and organizations relying on them.
That raised practical questions:
- Can an organization choose where the application runs?
- Can developers inspect and adapt the implementation?
- Can teams avoid depending on a single hosted provider?
- Can operators define their own retention, access, and infrastructure policies?
Why should control over important conversations depend entirely on infrastructure and policies we cannot inspect or choose?
That question became the motivation to build an alternative.
3. A bold idea takes shape
I wanted to build an open-source WebRTC platform that people could deploy on their own servers and adapt to their own workflows.
Four principles guided the work:
Run the software on infrastructure you select and manage.
Define your own access, logging, retention, and network policies.
Review how signaling, media, authentication, and integrations are implemented.
Learn from, test, and contribute to the public codebases.
Self-hosting increases control, but privacy and security still depend on configuration, product architecture, infrastructure, integrations, and operating practices. The technical overview documents those boundaries.
4. How it got its name
Friends and colleagues have always called me Miro. The project was about helping people talk, so the name followed naturally:
Miro + Talk = MiroTalk
It is a simple name for communication software built with a personal connection to its purpose.
5. From side project to product family
What started as a solo experiment during lockdown developed into several products for different communication patterns. Developers, educators, teams, and communities began using the projects and bringing new requirements with them.
Today the suite covers:
- Group meetings through MiroTalk SFU
- Private and small-group calls through MiroTalk P2P
- Focused one-to-one calls through MiroTalk C2C
- One-to-many broadcasts through MiroTalk BRO
- Click-to-call workflows through MiroTalk CME
- Accounts, rooms, and scheduling through MiroTalk WEB
- Infrastructure administration through MiroTalk ADMIN
The product chooser explains where each product fits.
6. Shaped by the people who use it
Once people started using MiroTalk, they did more than run it. Feature requests, bug reports, deployment experiences, and conversations influenced how the projects evolved.
The best software is not built in isolation. It is shaped by the people who depend on it.
Building in public makes that feedback visible and gives users a direct way to inspect the work, report problems, and contribute improvements.
7. The work continues
MiroTalk continues to pursue a more open and operator-controlled approach to real-time communication. That work includes the applications themselves, deployment tooling, integration documentation, and the community around them.
You can take part by trying a project, reviewing its source, reporting an issue, improving the documentation, or sharing how you deploy it.
Choose a MiroTalk product Join the Discord community