Instead of a subscription
Self-hosted alternatives to Netdata Cloud
Netdata Cloud connects infrastructure metrics to a hosted monitoring workspace. A self-hosted hub can keep server-resource history locally while you operate agents, retention, access and alert delivery; its integrations and monitoring scope differ.
Requirements
Side by side
| Application | Minimum RAM | Disk estimate | Database | Installation difficulty | Backup | Recipe verification | License |
|---|---|---|---|---|---|---|---|
| Netdata | 512 MB RAM | 5 GB | Embedded, other | Medium | Yes · Restore tested | Fully verifiedRecheck overdue · 0 dCheck is current | GPL-3.0-or-later AND LicenseRef-Netdata-Cloud-UI-1.0 |
| Beszel | 128 MB RAM | 2 GB | SQLite | Easy | Yes · Restore tested | Fully verifiedRecheck overdue · 0 dCheck is current | MIT |
Migration
What changes when you host it yourself
The data stops leaving your network, and so does the responsibility for it: backups, the restore you have actually tested, and the disk it all sits on.
Feature parity is never exact. Read what each recipe states about limitations and the smoke test before planning a migration.
The bill turns into work: updates, certificates and an eye on the release notes. The catalog shows how much of that each recipe asks for.
Categories
Guides with these applications
- A home server that earns its keepA modular home-server starter set: passwords, DNS, sync, monitoring, notifications, media and household recipes. Choose the services you need and add them gradually.
- Applications with a minimum of 1 GB RAM or lessSmall declared resource requirements for a VPS or thin client, with new metrics, notifications, notes and utility recipes. The limit applies to each application separately.
- Knowing when your server stopsAvailability checks, server-resource history, notification delivery and a shared dashboard serve different jobs. Build only the layers you need and monitor from outside the server.