Ownership before interface
Tenant boundaries belong in server-side authorization, not in hidden buttons. Every router-targeting workflow needs the same ownership decision across page loads, live updates, relays, and destructive actions.
About User Manager
User Manager is a self-hosted MikroTik control plane built around a simple idea: centralized management becomes useful only when ownership, connectivity, and operational evidence stay clear.
The purpose
Router fleets involve more than reachability. An operator needs to know who owns a device, which tenant subnet it belongs to, which worker carries its traffic, whether a move actually completed, and whether deletion really cleaned RouterOS.
User Manager connects those concerns deliberately. The Master Command Center provides global operational visibility; normal users receive isolated workspaces. Public pages describe the product without exposing tenant, worker, session, or router data.
Tenant boundaries belong in server-side authorization, not in hidden buttons. Every router-targeting workflow needs the same ownership decision across page loads, live updates, relays, and destructive actions.
A queued command is not a moved router. A scheduled cleanup is not a deleted configuration. Operational states should show what has actually been proven and what still needs attention.
The control plane runs on infrastructure you choose. Configuration and tenant data remain on your deployment, and safe updates are designed to preserve the operational state around the application.
Architecture in plain language
A user reaches the panel through your domain and Cloudflare. Firebase establishes identity, and the application creates an authorized panel session. MikroTik routers connect outbound to worker data planes using WireGuard, so the routers do not need public inbound access.
The master coordinates ownership, worker capacity, recovery, and authenticated remote access. Worker movement preserves the tenant network allocation while replacing the underlying worker. Provider firewalls and external Security Groups remain visible operator responsibilities rather than being described as magically automated.
Read the architecture guideProduct scope
The product centers on RouterOS adoption, user and IP bindings, PPPoE state, schedules, secure remote access, worker health, tenant-aware movement, and account lifecycle controls. It does not try to be a generic hosting dashboard or an invented customer-success portal.
The public site follows the same rule: real product guidance, real navigation, no stock testimonials, no fabricated customer logos, and no public operational metrics.
Explore practical deployment scenarios or create an isolated workspace on this installation.
Explore use cases