512 MB RAMamd64 / arm64 / armv7JavaScriptVery easyMITVersion 2.5.7
Instead of a subscription
Self-hosted alternatives to Better Uptime
Better Uptime checks whether your sites answer, escalates alerts through on-call rotations and publishes a status page. The monitor here runs the same checks and the same status page from a server you place yourself — including, if you choose, outside the network it watches.
Ten monitors come free with every plan, and ten is what a personal setup asks for, so there is no price here to set against a server.
Requirements
Side by side
| Application | Minimum RAM | Disk estimate | Database | Installation difficulty | Backup | Recipe verification | License |
|---|---|---|---|---|---|---|---|
| Uptime Kuma | 512 MB RAM | 2 GB | SQLite | Very easy | Yes · Restore tested | Fully verifiedRecheck overdue · 0 dCheck is current | MIT |
| Gatus | 128 MB RAM | 1 GB | SQLite | Easy | Yes · Restore tested | Fully verifiedRecheck overdue · 0 dCheck is current | Apache-2.0 |
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.
- What a Raspberry Pi can actually runA shortlist for 32-bit ARM systems, plus the newer options a 64-bit Pi can consider. Check the actual architecture test result before choosing a recipe.
- 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.