RouterOS operations
Manage everyday access-control work from one place: bindings, active PPP sessions, time-based schedules, router status, and authenticated remote access. Actions remain tied to the selected tenant-owned router.
Centralized MikroTik management
Bring routers, user and IP bindings, PPPoE sessions, schedules, and worker infrastructure into one secure control plane—without losing the boundaries between tenants.
User Manager is more than a device list. It connects identity, ownership, RouterOS state, secure connectivity, and VPS capacity so each action has the right context—and each tenant sees only what belongs to them.
Manage everyday access-control work from one place: bindings, active PPP sessions, time-based schedules, router status, and authenticated remote access. Actions remain tied to the selected tenant-owned router.
Google Sign-In and Firebase email accounts open isolated workspaces. Every normal user receives a separate persistent WireGuard subnet, while router APIs, live updates, adoption, relays, and deletion enforce ownership on the server.
Prepare worker VPS capacity, move a tenant’s adopted routers together, and follow recovery when a worker stops responding. The movement record follows the actual router through preparation, registration, and handshake proof.
Stay signed in across ordinary browser restarts without weakening administrative controls. Optional authenticator-based two-step verification, recovery codes, suspension, revocation, and all-device logout remain distinct from Firebase email verification.
Deleting an online router is designed to remove User Manager configuration from RouterOS before removing its panel record. A scheduled script alone is not completion: the cleanup callback must confirm that no managed artifacts remain.
Validate capacity and private transport, then prepare the required WireGuard peer and routing state without changing the tenant’s persistent subnet.
Move all adopted siblings in the same tenant group together, preserving their tunnel addresses and security material.
The movement remains pending until that router registers through the target worker. A queued reinstall command is not presented as a completed move.
Only target-side registration and fresh connectivity evidence complete the router’s recovery record. Other routers in the tenant group complete independently.
Your infrastructure
The public panel sits behind your domain and Cloudflare. Router Web access follows the existing authenticated path through the master and private master-to-worker WireGuard transport, keeping worker relays out of the public panel architecture.
Create your own isolated workspace, or sign in to continue operating your network.
Create Account