Running in production · Edition No. 5 · 30 Aug 2026

henrygd/beszel

Very light server monitoring with per-container Docker stats, history and alerts — the answer to 'can the box take one more container?'

← Running in productionRead the whole edition →

25.2k stars · MIT · v0.19.0 (2026-09-03)

Very light server monitoring with per-container Docker stats, history and alerts — the answer to 'can the box take one more container?'

Repo detailsthe review · specs · pros & cons · install

What it is

A very light server monitor: a hub with a web dashboard plus a small agent on each machine, recording CPU, memory, disk, network and per-container Docker statistics with history and configurable alerts. The whole thing is two Go binaries and uses a handful of megabytes.

Why it matters

Count what this radar has now put on one Hetzner box: Grasppy, ScalpingMate, PostgreSQL, and candidates including Umami, Listmonk, Mixpost, RSSHub, Tolgee, LibreTranslate, Coolify, plus today's comments and support desk. Every single edition has said "check your RAM headroom" and you have had no way to check it. Beszel gives you the number per container, over time, which converts an anxious guess into a decision — and its alerts mean the first time you learn that Postgres is being starved is not when a user emails you. This is deliberately the wildcard rather than a marketing entry, because the marketing plan fails just as completely when the site is down as when nobody visits it.

Stars25.2k
LicenceMIT
Latestv0.19.0 (2026-09-03)checked 7 Sep 2026
Written inGo
NeedsDocker and a GPU
Setup effort
2 / 5
Payoff
4 / 5
Good
  • Genuinely tiny — a monitoring tool that does not itself need the RAM you are trying to measure, unlike a Prometheus and Grafana stack
  • Per-Docker-container CPU and memory history, which is exactly the granularity your install decisions need
  • MIT, actively released, and alerting works out of the box rather than after a day of configuration
Watch for
  • Resource monitoring only. It will not tell you a page is slow or an API call is failing — that is a different tool
  • Still 0.x. It is stable in practice but the configuration format can move between versions
  • It monitors; it does not fix. Knowing you are at 92% memory is progress, but the next step is still yours
Works well with

Hub as a Docker container on the VPS behind your reverse proxy, agent alongside it on the same machine.

How to get it

Hub as a Docker container on the VPS behind your reverse proxy, agent alongside it on the same machine.

Get the next edition in your inbox

A dozen repositories, opened and checked. The licence read, the last release dated, and the ones that did not make it named with the reason. It is the half most lists leave out.

No tracking pixels. One click to leave. The archive stays free either way.

We use your address to send the edition and nothing else. Confirm by email, leave in one click. How we handle it.