Beszel
A lightweight server monitoring hub with historical data, docker stats, and alerts.
Platform availability
Available on 5 of 10 platforms
- Unraid
- TrueNAS
- Umbrel (not listed)
- ZimaOS
- Proxmox
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
90/100 Excellent
- Maintained
- 100last commit 2 days ago
- Popular
- 8927,483 GitHub stars
- Easy to install
- 654 install platforms, install notes, Docker image
- Light to run
- 95512 MB minimum RAM, runs on ARM
Availability: platform listings confirmed today, links checked 8 days ago
- GitHub stars
- 27,483
- Open issues
- 391
- Last commit
- 2026-11-19
- Latest release
- v0.21.2
- License
- MIT
- Activity
- declining
Checked 2 days ago - source: GitHub (henrygd/beszel)
Resources & Compatibility
Minimum requirements: 512 MB RAM, 1 CPU core(s), 5 GB disk. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install the Hub first and open port 8090 Run the Hub installer so it sets up and starts the Beszel dashboard service; the dashboard is the central place that stores data and shows graphs. It normally listens on port 8090 (the number your browser connects to), so if you can't reach that port, the site won't load. source
- Install the agent on every machine you monitor Install and start the Beszel agent on each machine you want to monitor; the agent is the little program that collects stats like CPU, memory, and disks. Without it, the Hub has no data from that machine and it won't show up in the dashboard. source
- Give the agent its Hub URL, key, and token Before starting the agent, enter the Hub URL, the machine's public key (a code that says this agent is allowed to join), and its token (a secret access code). These let the agent connect securely; if they're wrong or missing, the machine can't register and will appear offline or unknown. source
Fetched 54 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which port does the Beszel dashboard need to be reachable on?
The Hub dashboard normally listens on port 8090, so that port must be open for the browser to load the dashboard. If the port is not reachable, the site will not load.
What does an agent need before it can connect to the Beszel Hub?
Install the agent on each machine you monitor and set its Hub URL, public key, and token before starting it. If those values are wrong or missing, the machine cannot register and will show as offline or unknown.
Why might agents fail after an update when using self-signed HTTPS certificates?
Beszel 0.19.0 made agents verify HTTPS certificates as a breaking change. Self-signed certificates may require setting CA_CERT_FILE so the agent can trust them.
Does Beszel require a separate database to be provisioned?
No, Beszel does not require a separate database to provision. It provides history and threshold alerts without a separate database setup.
Answers sourced from beszel.dev, beszel.dev, forum.cloudron.io, selfhostatlas.com
Community
- Topics tagged beszel - forum.ansible.com (forum)
- Anyone got Beszel working? - forum.opnsense.org (forum)
- Beszel | Cloudron Forum (forum)
- Reddit (reddit)
- Reddit - Please wait for verification (reddit)
Collected 48 days ago - public community threads