diddy
The Problem
I run a small fleet of Linux boxes around the house — a few Debian machines, a couple of Raspberry Pis, the odd mini-PC picked up secondhand. Nothing exotic, just a home network's worth of "always meant to tidy that up" computers.
For years I kept waiting for Zorin OS to ship Zorin Grid, their long-promised fleet management tool. It never arrived. Around the same time I kept running into Google's Chrome Enterprise / Admin Console — the tool schools use to manage a whole classroom of Chromebooks from one dashboard: enroll a device, push policy, done. It got me thinking: that model — one admin, a fleet of simple machines, zero-touch onboarding — doesn't really exist for home Linux users. Ansible exists, but it's a sledgehammer for a home fleet of five to twenty boxes; you'll spend more time writing playbooks than you would just clicking a button.
So I built the tool I wanted: Remote Linux Manager.
Demo
What It Is
A cross-platform (Linux/Mac/Windows) desktop GUI for administrating a fleet of Ubuntu/Debian-derived boxes over SSH. No agents, no daemons to install on the managed machines — if it runs SSH, you can manage it. Point it at your home network, add your PCs, and get one dashboard for status, updates, commands, and file transfers across all of them.
The design philosophy is simple: cover the 80% of actions a home admin actually does day to day — check what's out of date, push a command, deploy some packages, bring a new box up to speed — without dragging in the infrastructure-as-code machinery that real config management tools assume you want.
Getting Your Fleet Onto the Dashboard
Adding a PC used to mean typing in its hostname or IP by hand. Now the tool scans your local subnet in the background the moment you open the "Add PC" dialog, and offers matching devices as you type — pick one and you're done. Free-text entry still works for anything the scan misses, so nothing's locked down.
As a nice side effect of the scan, the PC's MAC address gets captured automatically too — which sets up the next feature.
Wake-on-LAN: Making Sleeping PCs a Non-Issue
Half the point of running a home fleet is that some of those machines sleep to save power. That used to just look like "offline" to the tool — which isn't wrong, but it isn't the whole story either.
Now the tool tells the difference. Before it tries to talk to a PC over SSH, it does a quick check — if the machine doesn't answer but has a MAC address on file, it sends a Wake-on-LAN magic packet and gives it a window to boot before giving up. Practically, that means:
- Click an action on a sleeping PC and it just works — no more "turn it on first, then try again."
- A full fleet status sweep won't get stuck waiting on one sleepy machine; it wakes it and moves on, checking again next pass.
- A background watchdog polls connectivity every 30 seconds and nudges sleeping PCs on its own, so a machine can go from asleep to fully checked-in with zero input from you.
It's not aggressive about it either — wake attempts are throttled to about once a minute per PC, so a machine that's genuinely off (not just asleep) doesn't get spammed forever, it just gets a gentle, harmless nudge periodically in case that ever changes.
(Needs Wake-on-LAN enabled in BIOS/UEFI and at the OS/NIC level, and a wired connection — WoL over Wi-Fi is a coin flip on most hardware.)
What Else It Does
- Live fleet status — online/offline, uptime, disk space, and pending update counts for every PC, refreshed automatically.
- Mass actions — run updates, deploy packages, or execute an arbitrary command across as many selected PCs as you like, in one go.
- Reboot/shutdown monitoring — sends the command, then watches the PC actually drop offline and come back before reporting success (not just "command sent, hope it worked").
- Snapshots and drift detection — snapshot a PC's installed package list, get notified if it drifts from that baseline later, and revert back to it if needed.
- Clone...
Yann Guidon / YGDES
Kevin Andersson
lion mclionhead
Dmitry