Uptime Kuma: hardware requirements
Lightweight uptime monitoring and alerts for every service.
Hardware tiers
| Tier | CPU | RAM | Storage | GPU | VRAM | Network |
|---|---|---|---|---|---|---|
| Minimum sensible | 1 cores | 1 GB | 0.2 TB (ssd) | None | — | 1 GbE |
| Recommended | 1 cores | 2 GB | 0.5 TB (ssd) | None | — | 1 GbE |
| Comfortable | 2 cores | 4 GB | 1 TB (ssd) | None | — | 1 GbE |
| Overkill | 4 cores | 7 GB | 2 TB (ssd) | None | — | 1 GbE |
- Minimum sensible: The smallest build that genuinely works — tight, focused, no fluff.
- Recommended: The sweet spot: handles the service plus the usual side-services.
- Comfortable: Real headroom — this service will never be the bottleneck.
- Overkill: More than you will ever use for this service alone — spend the money elsewhere.
Beyond Comfortable — 2 cores, 4 GB RAM, 1 TB: headroom you will never use for this service alone.
Runs well with
Homelab ops, Docker, Reverse proxy
Frequently asked questions
How much RAM does Uptime Kuma need?
1 GB is the sensible minimum, 2 GB covers most real setups, and 4 GB gives comfortable headroom.
How many CPU cores does Uptime Kuma need?
1 cores are the minimum, 1 cores the sweet spot, and 2 cores comfortable when shared with other services.
Can I run several services on one machine?
Yes — most services share resources. Use the planner and select several services; the engine sums and overlaps the requirements instead of stacking them.
What if I already have hardware?
Register it in My hardware and the analysis shows exactly which services your current system can comfortably run — including an honest “do nothing”.