Beszel
Lightweight self-hosted server monitoring with history, Docker stats, and alerts.
- Stars
- 26.8k
- Forks
- 1.1k
- Licence
- MIT
- Language
- Go
- Last update
- 5 days ago
- Type
- App
What it is
Beszel is a server monitoring tool you run yourself. A hub with a web dashboard collects metrics from small agents installed on each machine you want to watch. It keeps historical data, tracks Docker container stats, and can send alerts when metrics cross limits you set.
- See CPU, memory, disk, and network history for several servers on one dashboard
- Track CPU, memory, and network use for each Docker container over time
- Get alerted when a metric crosses a threshold you configure
- Check disk health with S.M.A.R.T. data and get notified of drive failures
- Back up Beszel data to disk or S3-compatible storage
Great for
- People running a homelab or a few personal servers
- Anyone who wants a web dashboard for several machines without a heavy setup
- Users who want to monitor Docker or Podman containers alongside the host
- People who want alerts sent to notification services when something goes wrong
Not ideal for
- Teams needing large-scale, enterprise monitoring; the README describes a lightweight tool and does not mention large-scale deployments
- People who do not want to host any software themselves, since it is self-hosted
- Users who need a REST API today, since the README shows that feature as commented out
How to get it
- 1
Run with Docker
You'll need: Docker (for the Docker-based install shown in the project's docs)
Clone the repository
git clone https://github.com/henrygd/beszel - 2
Run it
- Follow the quick start guide at beszel.dev/guide/getting-started
- Install the hub and then install the agent on each system you want to monitor
- Open the web dashboard and add your systems
- Configure alerts and notification services in settings
- 3
Get the most out of it
- Enable OAuth / OIDC login and disable password auth if you want stronger access control
- Set up automatic backups to disk or S3-compatible storage
- Use network monitoring to check response time and interruptions from agents
- Enable S.M.A.R.T. monitoring to get early warnings about disk failure
- Set up alerts across the metrics you care about and link them to your notification services
Downloads
Strengths
- Lightweight, according to the README, with a simple setup and little manual configuration
- Covers host metrics, containers, and hardware sensors such as temperature, fans, GPU, and S.M.A.R.T.
- Released under the MIT license, which allows free use and modification
Trade-offs
- Some features, such as the REST API, are not fully documented in the README and are marked as commented out
- Hardware metrics like fan speed are Linux-specific according to the README
- Full setup details are on the external website rather than in the README
How it compares
| Project | Stars | Type | Level | Updated | Best for |
|---|---|---|---|---|---|
| beszel (this) | 26.8k | App | intermediate | 5 days ago | People running a homelab or a few personal servers |
| uptime-kuma | 93.2k | App | beginner | 4 days ago | People who want to monitor their own websites or services without paying a hosted monitoring service |
| dashy | 26.9k | App | beginner | 5 days ago | People running a homelab or home server who want one page for all their services |
| Proxmox | 15.1k | Dev tool | intermediate | 2.0 years ago | Homelab users who run Proxmox VE and want a guided way to create containers or VMs |
| memos | 64.2k | App | intermediate | 4 days ago | People who want a private, self-hosted journal or quick-notes timeline |
| huginn | 50.3k | App | intermediate | 4 days ago | People who want IFTTT-style automations without sending their data to a third-party service |
Stats synced from GitHub. The assessment above was drafted with AI from the project's README on 2026-10-29 and may miss recent changes — check the README before relying on a command. MIT licence: free to use, modify and distribute, including commercially, as long as you keep the copyright notice.