Build a business with MiroTalk
Use a focused MiroTalk application or combine the suite to create a branded video service, add real-time communication to an existing product, or operate a private deployment.
Choose a business path
| Business goal | Relevant MiroTalk path | Start here |
|---|---|---|
| Launch a video SaaS | Accounts, scheduling, meetings, APIs, and subscription billing | MiroTalk WEB and Stripe billing |
| Deliver classes or consultations | Group rooms, private calls, screen sharing, and collaboration tools where supported | Choose a product |
| Add customer support video | Click-to-call, agent availability, or direct one-to-one calls | MiroTalk CME or MiroTalk C2C |
| Run webinars or events | Moderated group meetings or one-to-many broadcasting | MiroTalk SFU or MiroTalk BRO |
| Deliver client projects | Embedding, direct links, REST APIs, webhooks, and white-label options | Build with MiroTalk |
| Operate a private platform | Self-hosted applications, deployment guidance, and infrastructure administration | Self-host MiroTalk |
| Deploy the complete suite | Seven independently deployable applications in one commercial bundle | MiroTalk Ultimate |
Capabilities vary by application. Confirm the required workflow in the product comparison before choosing an architecture.
Common solution patterns
Video SaaS and marketplaces
Build accounts, room creation, scheduling, invitations, and eligible paid access around MiroTalk WEB, then connect the media application that matches the meeting model. Use the published APIs and webhooks where supported instead of assuming every application exposes the same integration surface.
Education and professional consultations
Use SFU for server-routed group sessions, P2P for smaller mesh meetings, or C2C for focused one-to-one calls. Organizations in regulated sectors remain responsible for evaluating privacy, security, data handling, retention, consent, and compliance requirements for their deployment.
Customer support and sales
Use CME when a visitor should see agent availability and start a call, or C2C when the workflow needs a direct one-to-one room. Embed the experience in an existing site or create links from the host application.
Agencies and integrators
Deliver a branded client experience using documented integration and rebranding paths. Confirm licensing for each end product and define who owns infrastructure, updates, monitoring, third-party services, and ongoing support before delivery.
Webinars and live events
Use SFU when participants need an interactive server-routed room, or BRO for a broadcaster-and-viewer model. Capacity depends on topology, media settings, recording, streaming, network conditions, and infrastructure; validate representative load before launch.
Hosted or self-hosted?
| Choose | When it fits | Your responsibility |
|---|---|---|
| MiroTalk Cloud | You want to use MiroTalk without operating its infrastructure | Configure and use the available managed service |
| Self-hosted MiroTalk | You need infrastructure control, source-level adaptation, or a private operating model | Deployment, security, capacity, backups, monitoring, updates, and third-party services |
Self-hosting provides control, not automatic compliance or unlimited scale. Your organization decides whether the selected architecture and operating controls meet its requirements.
Plan the commercial path
- Choose the product that matches the communication workflow.
- Compare architectures and identify integration requirements.
- Decide between the managed service and self-hosting.
- Validate the workflow, security controls, and representative load.
- Review the licensing options before building a closed-source or paid end product.
- Discuss non-standard architecture, customization, or delivery requirements through enterprise services.