What it does
Beszel pairs a web-based hub with lightweight agents installed on the systems being monitored. The hub keeps historical measurements and configurable alerts, while agents report host statistics and optional Docker or Podman container details. Its project documentation also covers SMART disk data, network response monitoring, backups, OAuth/OIDC, and a REST API. It suits people who want a small self-hosted fleet view rather than a managed observability platform.
Beszel's setup is a hub-and-agent workflow. The official getting-started guide says to run the hub as a binary or in Docker or Podman, open its web address, create an administrator account, then use Add System to define a machine. Start the agent on that host and finish adding it in the dialog; the system then appears in the dashboard. The steps are drawn from the documentation, not performed for this listing.
Once agents are connected, the hub can show host CPU, memory, disk, network, temperatures, and other supported metrics. For Docker or Podman hosts, it also keeps per-container CPU, memory, and network history. Alerts can watch configured metrics and notify through supported services; REST endpoints make it possible to use or update Beszel data from another script. A practical home-lab example is to group a few small servers in one hub and set an alert for a disk or service metric that should not be ignored.
The upstream project is MIT-licensed and designed to be self-hosted. That keeps the core tool independent of a vendor account, but it means the operator is responsible for running the hub, deploying agents, preserving its data, and maintaining connectivity. Container metrics require Docker or Podman on the monitored host. The project advertises that agents need no public Internet exposure, but the hub and agent still need a working path to exchange measurements.
Strengths
- One hub can collect host measurements and historical container statistics from multiple systems.
- Configurable metric alerts, SMART disk information, and agent-reported network monitoring cover more than basic CPU graphs.
- OAuth/OIDC, multi-user access, automatic backups, and a REST API are documented in the project materials.
Watch out for
- The deployment has separate hub and agent components, so each monitored host needs agent installation and a route to the hub.
- Per-container statistics depend on Docker or Podman being present on the host.
Best for
- Homelabs and small fleets that need a self-hosted server overview
- Administrators checking Docker or Podman resource use alongside host health
- Operators who want configurable alerts and SMART disk monitoring without a hosted monitoring account
Sources
- Beszel | Simple, lightweight server monitoring (Oct 26, 2026)
- Getting Started | Beszel (Oct 26, 2026)
- GitHub - henrygd/beszel: Lightweight server monitoring with historical data, docker stats, and alerts. · GitHub (Oct 26, 2026)
- beszel/LICENSE at main · henrygd/beszel · GitHub (Oct 26, 2026)