Multiple Servers Online/Offline Status No Domain Required

Fleet Dashboard

Manage multiple servers from one dashboard — register remote agents, see which ones are online, and ping them instantly.

One pane of glass for all your machines

If you have more than one server — a Raspberry Pi at home, a VPS in the cloud, a Mac mini in the office — you'd normally have to open each one separately. DevMonk's Fleet Dashboard lets you register all your agents in one primary dashboard and see their status at a glance. Online, offline, last seen time — all in one place. Click a machine to open its dashboard directly.

Primary DevMonk Agent Fleet Dashboard GET /api/fleet POST /api/fleet/:id/ping Your VPS (main) 🍓 Raspberry Pi ● online 10.100.0.2:7474 linux/arm64 · v1.12 ☁ VPS Europe ● online vps2.example.com linux/amd64 · v1.12 🍎 MacBook ● offline 10.100.0.4:7474 last seen 2h ago 🏠 Home Server ● online home.duckdns.org linux/amd64 · v1.11
Why use the Fleet Dashboard?
🍓
Monitor multiple Raspberry Pis
Running a Pi cluster or several Pis around the house? See all of them in one view.
☁️
Manage VPS across providers
Hetzner, DigitalOcean, AWS — register agents from anywhere and see them all here.
👁️
See all servers at a glance
Quick health check: is everything up? Which machines went offline overnight?
🔗
Quick jump to any machine
Click an agent in the fleet to open its DevMonk dashboard directly in a new tab.
Requirements checklist
DevMonk agent installed on the primary machine (where you'll manage the fleet)
DevMonk agent installed on each remote machine you want to add
The primary machine must be able to reach each remote agent's URL (domain, IP, or VPN IP)
How to set up the Fleet Dashboard
1
Install the DevMonk agent on each machine
On every machine you want to add to the fleet, run the installer. Each agent starts listening on its own port.
$ curl -sSL https://devops-monk.com/install.sh | bash
2
Open the Fleet page on your primary machine
Go to your main DevMonk instance → click "Fleet" in the sidebar.
┌──────────────────────────────────────────┐ │ FLEET [ + Register ] │ │ ──────────────────────────────────── │ │ No agents registered yet. │ │ │ │ Add a remote agent to get started. │ └──────────────────────────────────────────┘
3
Click "Register Agent"
Enter a name for the machine and its DevMonk URL. This can be an IP address, a domain, or a VPN IP (like 10.100.0.x).
┌──────────────────────────────────────┐ │ Register Agent │ │ Name: [ raspberry-pi ] │ │ URL: [ http://192.168.1.100:7474] │ │ [ Register ] │ └──────────────────────────────────────┘
4
Ping to verify the connection
Click "Ping" next to the new agent. If it responds, the status turns green. If not, check the URL and network connectivity.
1
Install DevMonk on all your VPS machines
SSH into each VPS and run the installer once. The agent starts automatically on port 7474 (or behind your configured domain).
2
Register each VPS in your primary Fleet page
On your primary DevMonk instance → Fleet → Register Agent → enter the VPS domain or public IP.
┌──────────────────────────────────────────┐ │ FLEET │ │ ● vps-germany https://de.example.com │ │ ● vps-usa https://us.example.com │ │ ✗ vps-asia offline (last: 3m ago) │ └──────────────────────────────────────────┘
3
Ping agents to check connectivity
Use the Ping button for a quick latency check and to confirm the agent is alive. The status updates in real time.
Try it now
Register your first remote agent
Install DevMonk on a second machine (even another device on your home network), then register it in your primary Fleet page. Ping it to confirm the connection — you'll see the latency in milliseconds.
# On the remote machine — install the agent:
curl -sSL https://devops-monk.com/install.sh | bash

# Then in your primary DevMonk:
Fleet → Register Agent → enter http://REMOTE_IP:7474 → Ping
FAQ
The agent's status shows as "offline" with a "last seen" timestamp indicating the last time it responded. Nothing is removed — when the machine comes back online and the agent starts again, the status automatically updates to online.
No. You can register an agent using its local IP (192.168.x.x), a VPN IP (10.100.0.x if you've set up WireGuard), or a domain name. As long as your primary machine can reach the URL, it works.
The Fleet Dashboard currently supports ping and status checks only. To manage a remote agent's containers or files, click the agent's URL link to open its full DevMonk dashboard in a new tab — then you have access to all features for that machine.
There's no hard limit. Register as many machines as you need. The fleet page scales to show all of them in a list. Performance depends on how many pings the primary agent does periodically to check statuses.
Explore related features
← Audit Log All Features →