explaingit

henrygd/beszel

📈 Trending21,927GoAudience · ops devopsComplexity · 2/5ActiveLicenseSetup · moderate

TLDR

Lightweight self-hosted server monitoring dashboard. Install an agent on each server, view CPU, memory, disk, network, and Docker metrics in a web browser.

Mindmap

mindmap
  root((Beszel))
    What it does
      Server monitoring
      Docker tracking
      Alert system
      Data backup
    Key features
      Web dashboard
      Hub-agent design
      Multi-user support
      OAuth2 login
    Metrics tracked
      CPU usage
      Memory usage
      Disk space
      Network traffic
      System temperature
    Use cases
      Home lab monitoring
      Small production systems
      Personal server oversight

Things people build with this

USE CASE 1

Monitor CPU, memory, and disk usage across multiple home lab servers from a single dashboard.

USE CASE 2

Track individual Docker container performance and resource consumption in real time.

USE CASE 3

Set up alerts to notify you when disk space runs low or CPU usage spikes on production systems.

USE CASE 4

Back up monitoring data to S3-compatible cloud storage for long-term retention and compliance.

Tech stack

GoDockerS3OAuth2

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Docker for containerization and OAuth2 provider configuration for authentication.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

Beszel is a lightweight self-hosted tool for monitoring servers. If you run one or more servers, whether personal machines, home lab setups, or small production systems, Beszel gives you a web dashboard where you can see at a glance how each server is performing: CPU usage, memory, disk usage and read/write speed, network traffic, system temperature, and more. It also tracks Docker containers (packaged apps running in isolated environments) individually, showing their CPU, memory, and network usage over time. The system is built around two components. The hub is the central web application you visit in your browser to see all your server metrics. The agent is a small program you install on each server you want to monitor; it collects the metrics locally and sends them back to the hub. This hub-and-agent design means you only need a web browser to view data, and the agents running on your servers stay small and unobtrusive. Beyond basic monitoring, Beszel supports configurable alerts so you can be notified when something goes wrong, such as CPU usage spiking or a disk filling up. It can back up its own data to a local folder or to S3-compatible cloud storage (a common standard for object storage). It supports multiple users, with each user managing their own systems, and administrators able to share systems across users. Login can be handled by username and password or via OAuth2, a standard sign-in method that lets you use an existing account from another provider. You would use Beszel when you want a simple, low-resource way to keep an eye on one or more servers without complex setup. It is written in Go and licensed under the MIT license.

Copy-paste prompts

Prompt 1
How do I install the Beszel agent on my Linux server and connect it to the hub?
Prompt 2
Show me how to set up email alerts in Beszel when CPU usage exceeds 80%.
Prompt 3
How do I configure Beszel to back up its data to S3-compatible storage like MinIO?
Prompt 4
Can I use Beszel to monitor Docker containers, and how do I view per-container metrics?
Prompt 5
How do I set up OAuth2 authentication in Beszel so users can log in with GitHub?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.