RemoteDeck
A watchlist of hosts that stays quiet until something actually changes state.
Free right now — no account, no card
Preview
1 interface design, then a screenshot of it running. Drag, scroll or use the arrows.
Free while we’re in preview
Get RemoteDeck
A watchlist of hosts that stays quiet until something actually changes state.
The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.
One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.
Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.
- One file — no installer
- Reaches only what you point it at
- Source code published below
Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. At launch, RemoteDeck is included in every plan along with the rest of the range.
Silence is the feature
Point it at a text file of name host:port lines. RemoteDeck polls each target over TCP on your --interval, holds every target’s up/down state in memory, and prints nothing while nothing changes. You hear from it on a transition: unknown to up, up to down, down to up. The first pass counts as everything leaving “unknown”, so you get one status line for free at startup.
--log events.log appends every transition as a JSON line carrying the time, target name, address, old and new state, and either the failure reason or the connect latency. That file is something a real monitoring pipeline can tail.
--once runs a single pass, prints the full status table, and exits non-zero if any target is down. That’s the form to wire into cron or a CI health check.
What this prototype isn’t
No SSH, no SFTP, no RDP, no tunnels, no session tabs, no credential vault. A correct SSH client needs a crypto library beyond Go’s standard library, and this suite has no dependencies deliberately.
NetLens is the one-shot scan you read and forget. RemoteDeck is the one you leave running underneath everything else.
Reading on the job itself
- How to watch a handful of servers without setting up a monitoring stack A list of host and port, checked on an interval, that stays silent until something changes state. Almost al...
Advanced & technical details Command-line builds, source code, checksums and a recorded session — for developers and IT teams
A working CLI prototype of the "is everything up" layer: a persistent multi-host TCP watchlist with up/down transition detection and a JSON-lines event log, distinct from the sibling NetLens one-shot scanner. Real SSH/SFTP/RDP, tunnels, and a credential vault need a crypto library and GUI session management and are on the roadmap.
Naming status
Working name only — brand verdict **AVOID** (Very High). Collision: RemoteDeck. Rename completely.
What it draws on
Existing paid software whose best ideas shaped this program: MobaXterm Professional, SecureCRT, WinSCP Microsoft Store Edition, Remote Desktop Manager.
Command line
There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.
RemoteDeck - persistent multi-host TCP health/uptime watchlist
Usage:
remotedeck watch --targets <file> [--interval 5s] [--timeout 2s] [--once] [--log events.log] [--json]
remotedeck help
Watchlist file format (one target per line):
# comment lines and blank lines are ignored
name host:port
Watch flags:
--targets path to the watchlist file (required)
--interval time between poll passes in continuous mode (default 5s)
--timeout per-target TCP connect timeout (default 2s)
--once do a single poll pass, print a full status table, and exit
(non-zero exit if any target is DOWN; useful for cron/CI)
--log append every state-transition event as a JSON line to this file
--json print console events as JSON instead of human-readable text
(the --log file is always JSON-lines regardless of this flag)
Examples:
remotedeck watch --targets targets.txt --once
remotedeck watch --targets targets.txt --interval 10s --log events.logRecorded from the shipped binary, not written by hand.
Source
Every file the program is built from:
console.go · console_test.go · guided.go · main.go
SHA-256 checksums · build instructions & scope notes · full build plan