Central Configuration
Review and maintain service settings and environment configuration from one interface.
Self-Hosted Operations
One Control Plane.
One Control Plane.
Every MiroTalk Service.
Centralize configuration, updates, credentials, process monitoring, and lifecycle operations for MiroTalk services running on your infrastructure.
Multi-instance control
Centralized updates
Self-hosted access
1
Control Plane
3
Management Modes
24/7
Service Visibility
100%
Self-Hosted
Operations in One Place
Manage the MiroTalk Stack
Give operators a focused dashboard for routine service administration without turning the control plane into a meeting or media server.
Application Updates
Coordinate updates across the MiroTalk services connected to your deployment.
Process Monitoring
Inspect operational status and keep track of managed application processes.
Multiple Instances
Operate several deployed MiroTalk instances from a centralized dashboard.
Access Administration
Manage dashboard users and credentials for your operations team.
Lifecycle Control
Start, stop, restart, and maintain services through the configured management mode.
Flexible Deployment
Choose How Admin Connects
Use the least-privileged mode that supports where and how your MiroTalk services run.
SSH
Manage services on remote hosts with pinned host keys and tightly scoped credentials.
Docker
Control sibling MiroTalk containers through the Docker daemon on the host.
PM2
Operate local Node.js application processes and their configuration through PM2.
Privileged by Design
Protect the Control Plane
Admin can affect every managed service. Isolate the dashboard, restrict operator access, and protect every credential it uses.
Read the Deployment Guide- Serve the dashboard over HTTPS
- Replace default credentials before exposure
- Use strong JWT secrets and restricted accounts
- Protect SSH keys and Docker socket access
- Limit network access to trusted operators
- Back up configuration before updates
Common Questions
MiroTalk Admin FAQ
Does Admin host video meetings?
No. Admin is an operational control plane for deployed MiroTalk services. It does not provide meeting rooms or process media.
Can it manage services on another server?
Yes. SSH mode is designed for remote hosts. Pin the host fingerprint and use credentials with only the permissions required for management.
Can I use Admin with Docker?
Yes. Docker mode can manage sibling containers when the deployment grants access to the Docker daemon. Treat that access as highly privileged.
Where should I start?
Use the quick-start guide to evaluate Admin locally, then follow the self-hosting guide to configure HTTPS, credentials, and production access controls.
Ready to Operate
Centralize Your MiroTalk Services
Deploy the dashboard, choose a management mode, and secure access before connecting production services.
Open the Quick Start