Own the process
- Detect and adopt a live native server
- Install public or selected SteamCMD branches
- Start, graceful stop and safe restart
- Bounded watchdog and desired-state recovery
- Multi-server controller fleet on one host
FREE · OPTIONAL · WINDOWS + LINUX
The control room
The control room
your 7DTD host was missing.
RefugeBot Monitor adopts the native server you already run—or installs a new one—then gives you private lifecycle, console, settings, ports, verified backups, protected mods and recovery. It works standalone. Linking RefugeBot is optional.
Native full control when you choose Managed
Docker watch-only, never mutation
Private loopback dashboard by default
Run. Protect. Extend. Connect.
One private utility covers the jobs a raw dedicated-server install leaves scattered across scripts, terminals and memory.
Prove every change
- Private bounded console and health evidence
- Blood-moon-aware maintenance guard
- Verified save/world/config/admin backups
- Safety snapshot before verified restore
- Complete present-property settings and port plan
Operate without a shell
- Installed-mod inventory and exact compatibility
- Protected install, update, remove and rollback
- Health-proved self-update with binary rollback
- Versioned scoped API and Linux CLI
- Native Windows tray and Update Center
Stay local—or link
- Standalone owner account; no RefugeBot required
- Optional one-server, one-tenant pairing
- Typed hosted lifecycle and backup operations
- Compatible remote Blueprint recipes
- Revocable scopes; no dashboard or shell tunnel
Three modes. No hidden takeover.
Monitor changes a server only when its lifecycle mode and authority explicitly permit it.
Private local manager
Observe first, or choose Managed so Monitor becomes the one lifecycle owner for a native Windows or Linux server.
Full lifecycle · backups · restore · settings · ports · console · mods · updates · API/CLI/trayRefugeBot-connected host
Keep the private dashboard and add typed operations in the correct tenant/server with only the scopes you approve.
Everything standalone has · hosted controls · Blueprint compatibility · artifact publication pathVisibility, not ownership
Read container status, private Telnet console evidence and ports while Docker or Compose remains authoritative.
No start/stop · no XML writes · no backups/restore · no mod changes · no docker.sock mountAlready use AMP, Pterodactyl or a host panel? Keep it as lifecycle authority. Two watchdogs should never race to restart one server.
Everything important stays in one view.
Explore the populated dashboard used for validation. Tabs support arrow keys, Home and End.
OverviewHealth, lifecycle, horde guard, ports and bounded console.
01 / 06
Protected modsInventory, source identity, exact version, safety backup, health proof and rollback.
02 / 06
Backups + restoreVerified archives, retention policy and pre-restore safety snapshot.
03 / 06
Game updatesBranch-aware SteamCMD maintenance with lifecycle guardrails.
04 / 06
WatchdogDesired state, bounded recovery and blood-moon-aware maintenance.
05 / 06
API + self-updateNamed scoped tokens, versioned typed operations and health-proved upgrade.
06 / 06
STANDALONE
Provider-direct, locally protected
Monitor reads the physical Mods folder, matches approved catalog metadata and immutable pins, then downloads the original provider artifact into its bounded work area. It rechecks the exact game version/build, creates a Mods-inclusive safety backup, stages atomically and requires local health—or rolls back.
LINKED NATIVE SERVER
Blueprint compatibility, same safety lane
Active remote Blueprint recipes and compatible published artifacts can use the same protected transaction. The hosted catalog is not a player CDN; the native Monitor remains the executor and Docker remains read-only.
Choose the machine running 7DTD.
Install Monitor on the same Windows or Linux host as the dedicated server. Both installers verify the current AMD64 release before replacing files.
⊞
WINDOWS · ADMIN POWERSHELL
Windows 10/11 or Server 2019+
Runs as a windowless Windows service; the signed-in desktop can use the native tray companion.
$i="$env:TEMP\refugebot-monitor-install.ps1"; irm https://refugebot.com/downloads/refugebot-monitor/install.ps1 -OutFile $i; & $i$
LINUX · TERMINAL
systemd with apt or dnf
Creates a non-root service account. First run stays private by default, with either the printed SSH tunnel or an explicit one-time-token LAN HTTPS setup URL.
curl -fsSL https://refugebot.com/downloads/refugebot-monitor/install.sh | sudo -E bashCURRENT RELEASE · latest · SHA-256 VERIFIED · AMD64
FIRST RUN
- Choose a source. Adopt a detected server, select an existing install, or install a new branch.
- Confirm paths. Select the game tree and
serverconfig.xml; Monitor discovers Telnet and ports. - Create the owner. Set a local username and 12+ character password, then choose Observe or Managed.
- Choose dashboard access. Keep loopback/SSH, or explicitly enable trusted-LAN HTTPS with a generated or existing certificate.
Powerful locally. Narrow remotely.
Monitor is a typed server manager, not a generic remote-administration agent.
Private by default
Dashboard access defaults to loopback. Trusted-LAN/VPN access is an explicit HTTPS-only choice with exact origins and a persistent warning; public port forwarding is strongly discouraged.
One process owner
Local, RefugeBot or External restart authority is explicit. Pairing does not silently grant lifecycle control.
Typed remote scope
No shell, raw Telnet, arbitrary file, XML upload, dashboard iframe or Docker-control tunnel.
Secrets stay home
Telnet passwords, host paths, raw XML and provider credentials do not enter hosted responses or history.
1Create a ten-minute pairing code for the exact tenant and server.
2Paste it into the private dashboard and approve the scopes you want. Monitor software updates are a separate opt-in; old credentials never inherit it.
3Choose RefugeBot authority only if hosted schedules should become the source of truth.
Choose a server →
Start with the boundary that applies.
Do I need Monitor to use RefugeBot?
No. RefugeBot setup needs only its small Agent mod. Monitor is a free optional host utility for machines that need lifecycle, backup, recovery, settings, ports or protected mod tooling.
Can Monitor control a Docker server?
No. Docker support is deliberately watch-only: status, private console evidence and ports. Docker or Compose keeps lifecycle ownership; there are no XML, backup, restore or mod mutations.
Why is Start or Restart disabled?
Check Observe versus Managed and the selected restart authority. External belongs to your existing panel; hosted control additionally needs a live native capability and approved scope.
How do I reach the Linux dashboard?
Loopback remains the default: run ssh -L 8787:127.0.0.1:8787 user@host and browse to http://127.0.0.1:8787/. If SSH is unavailable, start the explicit temporary network setup path; Monitor generates a one-time token and HTTPS URL, and setup can configure the permanent dashboard for trusted-LAN/VPN HTTPS. Never expose plain HTTP or forward the dashboard publicly.
Can my scripts use Monitor?
Yes. Setup creates an owner-only local CLI token, and the same guarded management API powers update check and update apply. Named read/operator/full tokens remain available. Remote listening requires TLS; there is no shell or offline update bypass.
Can RefugeBot update Monitor for me?
Yes, after a fresh pairing explicitly grants monitor:update and the Monitor advertises monitor.update.v1. RefugeBot accepts only the exact checked stable version, never an arbitrary URL or command. An unknown handoff waits for reconnect/version/health evidence and is not retried blindly. Controller-created child instances remain host-maintenance only.
Can one host manage several servers?
Each Monitor process owns one game server. The optional Windows/Linux controller inventories isolated services and provides typed fleet Start, Stop and Restart without merging accounts, configs or game trees.
Your host. Your rules. One calm control room.
Start standalone on native Windows or Linux. Link RefugeBot only when its hosted controls are useful to you.