These are legitimate deployment scenarios, not customer endorsements. No logos, quotes, usage counts, or testimonials are being presented as fact.
Internet service providers
Separate customer operations from platform operations.
Give each operator or customer an isolated workspace while the Master Command Center retains the global view needed for capacity, recovery, and audit work. Manage bindings, PPPoE state, schedules, and router access without merging tenant data.
Tenant isolation
Hotspot & managed access
Keep access-control work close to the router.
Centralize user and IP bindings, host visibility, schedules, and device state across managed locations. Authenticated remote access provides a route back to the device when an operator needs its native interface.
RouterOS operations
Distributed branches
Operate sites without public inbound router access.
Routers establish outbound WireGuard connectivity to the data plane. Add worker capacity where it is operationally useful, and preserve each tenant’s persistent subnet when a router moves to another worker.
Connectivity model
Internal network teams
Make fleet changes reviewable.
Track manual worker moves and automatic recovery through actual router identity, source and target workers, operational state, and proof timestamps. Keep a one-month movement record for short-term operational investigation.
Fleet movement
Self-hosted administrators
Keep the control plane in your hands.
Use your domain, master VPS, worker providers, Firebase project, and RouterOS environment. Apply updates without intentionally discarding configuration, named volumes, certificates, backups, or tenant state.
Deployment guidance
Security-conscious teams
Add assurance without confusing the layers.
Use Firebase for identity, verification, and password reset. Add optional authenticator TOTP for a second sign-in step, retain recovery codes offline, and use revocation when access must end across devices.
Account security