Self-Hosted Monitoring Comparison: Beszel vs. Alternatives on a $3 VPS
Description and use
Beszel was selected as the best tool for small-scale self-hosted monitoring due to its extremely low memory footprint (12 MB hub + 8 MB agent), zero-config setup, and unified dashboard for multiple servers. It replaced expensive SaaS tools and complex self-hosted stacks, reducing monthly costs to $3 while providing comprehensive metrics and alerting.
Problem
High cost and complexity of SaaS monitoring tools (UptimeRobot, Datadog) for low-traffic side projects, combined with the high resource overhead and configuration complexity of traditional self-hosted solutions like Netdata and Grafana/Prometheus on small VPS instances.
Outcome
Beszel was selected as the best tool for small-scale self-hosted monitoring due to its extremely low memory footprint (12 MB hub + 8 MB agent), zero-config setup, and unified dashboard for multiple servers. It replaced expensive SaaS tools and complex self-hosted stacks, reducing monthly costs to $3 while providing comprehensive metrics and alerting.
Workflow
- Spin up a cheap VPS (e.g., $3/mo, 1 vCPU, 2 GB RAM) running Ubuntu 24.04.
- Download and extract the Beszel hub binary on the VPS.
- Run the Beszel hub server.
- Download and extract the Beszel agent binary on the target server(s) to be monitored.
- Run the Beszel agent, passing the SSH public key for authentication.
- Access the Beszel web UI on the hub server.
- Add the agent to the hub by pasting the public key.
- Configure alerts (e.g., CPU > 90% for 5 minutes) and notification channels (Email, Discord, Telegram, etc.).
Evidence
Beszel's 12 MB is a rounding error. Netdata's 320 MB is 16% of your RAM gone before you've shipped any user code.
Setup, end to end... That's 4 minutes if you've made a single typo, 3 minutes if you haven't.
The whole thing costs less than one month of UptimeRobot Pro and tells you more.
- Record date: 2026-09-09T02:45:15.417Z