Show HN: Kula – Lightweight, self-contained Linux server monitoring tool

One-file server watcher sparks ‘clone wars,’ name drama, and benchmark demands

TLDR: Kula is a one-file server monitor with a built-in dashboard and fixed-size storage, aiming for easy setup. The crowd split fast: some yelled “Netdata clone,” others demanded real benchmarks, while a few pushed alternatives like Zabbix and dashdot — making this a showdown of simplicity versus proven heavyweights.

Kula burst onto Hacker News promising a single-file, no-fuss way to watch your Linux server’s health — think CPU, memory, network, and disk stats in a tidy dashboard. It reads your system every second and saves history in a fixed-size “ring,” so it won’t gobble disk space. Sounds neat… until the comments showed up. The top vibe? “Is this just Netdata in a trench coat?” One skeptic fired the first shot: “Vibe coded netdata clone?” and the “clone wars” were on.

Meanwhile, builders wanted receipts. A popular ask was simple: prove it’s light. “Benchmarks or it didn’t happen” energy flooded in, with one commenter begging for a tiny-server test showing memory, CPU, and disk use. Others dropped alternatives like dashdot with a live demo at dash.mauz.dev, and a hardliner declared, “Zabbix does it better.”

There was even name drama when a long-time user named “Kulahan” asked where the name came from. Plus a spicy nitpick over adding a copyright symbol next to “Linux.” Of course. Still, fans loved the just-run-it simplicity, built-in web/terminal views, and optional password protection. The verdict: a clean, compact tool with home-lab charm — if it can survive the clone jabs and bring the benchmarks.

Key Points

  • Kula is a single-binary Linux server monitoring tool with no external dependencies or databases.
  • It collects metrics every second from /proc and /sys and exposes them via a real-time Web UI and a terminal TUI.
  • A built-in tiered ring-buffer storage engine (1s, 1m, 5m tiers) provides bounded, maintenance-free disk usage.
  • An embedded REST API and WebSocket endpoint deliver current, historical, and live-streamed data.
  • Authentication is optional; when enabled, Argon2id password hashing is used, with tunable parameters recommended.

Hottest takes

“Vibe coded netdata clone?” — smashed
“one small benchmark table in the README/HN post for a tiny VPS (say 1 vCPU / 1 GB RAM): idle RSS, CPU%, disk write rate” — thebuilderjr
“Zabbix still looks like a better solution by any metric.” — savalione
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.