What This Does

Syncthing Multi Server Monitor is a lightweight dashboard that watches over multiple Syncthing instances—the open-source file-syncing software that works like a private Dropbox across your devices. Instead of logging into each Syncthing server separately to check if your files are syncing properly, this tool gives you one central view showing the status of all your devices and folders at a glance.

How It Works

You tell the monitor about each of your Syncthing servers by providing their network address and an API key—either by writing them into a JSON file or setting environment variables. The monitor then regularly checks in with each server to pull basic status information: which devices are online or offline, whether any files have local changes waiting to sync, and whether there are any errors. It displays all of this in a simple web interface you can open on your phone or computer. The tool also exposes an API endpoint so other monitoring systems (like changedetection.io) can automatically check if everything is running smoothly.

Who Would Use This

This is built for people who run Syncthing across multiple machines or servers—say, syncing files between a home server, a laptop, and a phone—and want a quick way to verify everything is working without digging through individual interfaces. It's especially useful if you're running these servers in Docker containers or remotely on your network. The creator prioritized keeping it lightweight: the entire application is only about 65MB and uses roughly 34MB of RAM, so it won't bog down your system even if you're already resource-constrained.

What Makes It Notable

The project is stripped down by design. Rather than use existing libraries or frameworks, the creator built it from scratch using only basic calls to Syncthing's API, which keeps the image size and memory footprint minimal. There's no fancy dashboard—just the essential information. It also handles devices going offline and coming back (like when you close your laptop), and can be configured flexibly depending on whether you prefer environment variables or configuration files. The README notes this was written "with very little sleep," so the creator is actively looking for feedback on bugs or rough edges.