If the watcher and the watched die in the same accident, you get the worst monitoring result of all: silence that looks exactly like health.
Every monitoring system has a blind spot shaped exactly like itself. Install Uptime Kuma on the file server, and the day the file server dies, Kuma dies too — no alert, no record, just a quiet dashboard nobody can open. The video installs Kuma on a Synology NAS, a separate always-on box, and that instinct is correct. This guide turns it into a rule and grades the realistic options: NAS, a small dedicated PC, and a cloud server — including the failure each one still cannot see.
👆 There is no universally best row — there is only the row whose blind spot you have honestly accepted.
Kuma must not share the failure it exists to report. Run the checklist against any proposed home: does it share the machine with a target? The hypervisor or storage? The power strip without a UPS? The single internet connection it needs to send alerts? Every shared item is a scenario where everything breaks and nothing reports. You will not reach perfect independence on a small budget — the goal is to know exactly which scenarios still silence you, and to close the cheap ones.
A NAS is a natural Kuma home: it is already on 24×7, Docker is built in, and it sits inside the LAN with a clear view of every office device. For watching LAN servers, printers and the gateway, it is hard to beat for the price of zero. Its remaining blind spots are honest ones: total office power failure takes the NAS down too, and if the office internet dies, a LAN-bound Kuma can detect everything and tell nobody — the alerts need a path out. Put the NAS, router and switch on a small UPS and both blind spots shrink dramatically.
An old mini PC or a Raspberry Pi running nothing but Kuma is the connoisseur's budget answer: cheap, silent, wired by Ethernet, and — the important part — plugged into the same UPS as the router and switch. During a power cut it keeps watching the LAN and, while the router still has battery, keeps sending Telegram alerts about what else has died. It cannot survive the building's internet dying, and it adds one more small machine to maintain. For most small offices this and the NAS are the two right answers; pick whichever hardware you already trust.
A small VPS flips the geometry: power and internet are now rock solid, and it is the perfect watcher for websites, public IPs and anything the world can reach — including the most valuable check of all, “is our office visible from outside at all?”. But it is blind to LAN-only devices: the printer and the file server do not exist from its viewpoint unless a VPN tunnel connects it, and when that tunnel drops, everything shows down simultaneously — which is, once you recognise it, itself a useful signal about the tunnel. Many good setups run both: Kuma in the office for the LAN, the VPS copy (or a free external checker) for the public face.
Whatever you choose, arrange one tripwire for Kuma itself. The simplest: point a free external uptime service at your status page address — if Kuma's machine dies, the status page dies, and the external service's alert about that is your watcher alarm. In offices with two sites, each site's Kuma can hold one ping monitor for the other site's Kuma. The principle matters more than the tool: silence must always have a witness.
Watch the video to see the Synology install from this guide done step by step, then place your own Kuma where it can survive the failures it reports.
▶️ Watch Full VideoIt will run happily — until that server fails, which is precisely the event monitoring exists for. Resource-wise it is tiny; risk-wise it is the worst seat in the house. If you truly have no second machine, run it there anyway as a start, but write “move Kuma to its own box” at the top of the hardware list.
No — Telegram, email and webhooks all need a working path out of the building. A LAN Kuma will record the outage faithfully for later review, but the live alert cannot leave. If instant alerting during internet failures matters, add an outside watcher for the public side, or give the Kuma host a backup path such as a 4G failover on the router.
For the typical office load — dozens of ping and website checks at 60-second intervals — yes, comfortably. Use a decent power supply and a good memory card (or better, an SSD), keep it wired to the network, and it will out-wait most servers it watches.