Beszel

Beszel is a lightweight server monitoring platform that includes Docker statistics, historical data, and alert functions.

It has a friendly web interface, simple configuration, and is ready to use out of the box. It supports automatic backup, multi-user, OAuth authentication, and API access.

Features

• Lightweight: Smaller and less resource-intensive than leading solutions.
• Simple: Easy setup with little manual configuration required.
• Docker stats: Tracks CPU, memory, and network usage history for each container.
• Alerts: Configurable alerts for CPU, memory, disk, bandwidth, temperature, load average, and status.
• Multi-user: Users manage their own systems. Admins can share systems across users.
• OAuth / OIDC: Supports many OAuth2 providers. Password auth can be disabled.
• Automatic backups: Save to and restore from disk or S3-compatible storage.

Architecture

Beszel consists of two main components: the hub and the agent.

• Hub: A web application built on PocketBase that provides a dashboard for viewing and managing connected systems.
• Agent: Runs on each system you want to monitor and communicates system metrics to the hub.

Local deployment notes

This repository includes local operational customizations that are not part of upstream Beszel defaults.

Latest local changes (2026-03-08)

• Added SSH collection timeout safeguards to avoid the hub getting stuck while polling SSH-based systems.
• Recovered a corrupted SQLite data.db and made the hub SQLite journal mode configurable for local deployments.
• Set the local deployment to BESZEL_HUB_SQLITE_JOURNAL_MODE=DELETE and BESZEL_HUB_SQLITE_SYNCHRONOUS=FULL to avoid WAL-related corruption in the current macOS + OrbStack bind-mount environment.
• Preserved custom systems.info fields such as z193, z193_jitter, z193_status, and zt_probe_ts when the hub updates system records.
• Restored the ZT 193 Latency home-table column by preventing hub writes from overwriting script-injected latency metadata.
• Linked the UI alert bell Status toggle to zT 193 DingTalk notifications so disabling Status silences zT offline/recovery/jitter messages for that system.
• Updated the home systems table to fully expand smaller deployments instead of showing only a short scroll window.
• Switched the MacBook agent to WebSocket mode to reduce transient SSH/ZT down-state flicker on the dashboard.
• Added a Synology DS224+ node using a Dockerized agent connected via WebSocket instead of SSH polling.
• Documented DS224+ onboarding, current service footprint, and a first-pass security review in the private notes and local project docs.

For local operational details, see the project notes under 文档/ and planning/.

Getting started

The quick start guide and other documentation is available on our website, beszel.dev. You'll be up and running in a few minutes.

Screenshots

Supported metrics

• CPU usage - Host system and Docker / Podman containers.
• Memory usage - Host system and containers. Includes swap and ZFS ARC.
• Disk usage - Host system. Supports multiple partitions and devices.
• Disk I/O - Host system. Supports multiple partitions and devices.
• Network usage - Host system and containers.
• Load average - Host system.
• Temperature - Host system sensors.
• GPU usage / power draw - Nvidia, AMD, and Intel.
• Battery - Host system battery charge.
• Containers - Status and metrics of all running Docker / Podman containers.
• S.M.A.R.T. - Host system disk health.

Help and discussion

Please search existing issues and discussions before opening a new one. I try my best to respond, but may not always have time to do so.

Bug reports and feature requests

Bug reports and feature requests can be posted on GitHub issues.

Support and general discussion

Support requests and general discussion can be posted on GitHub discussions or the community-run Matrix room: #beszel:matrix.org.

License

Beszel is licensed under the MIT License. See the LICENSE file for more details.