WisePC
Menu
Workload guide · Development Always-on 24/7

Uptime monitor: hardware requirements guide

Lightweight monitoring (Uptime Kuma) for service health checks and alerts.

Hardware requirements by tier

Three tiers for every workload: the minimum that works, the recommended sweet spot, and the comfortable headroom level. These are the same tiers the WisePC decision engine uses when it plans a build around your goal.

TierCPU coresRAMStorageGPUVRAMNetwork
Minimum1 cores1 GB0.2 TB (ssd)None1 GbE
Recommended1 cores2 GB0.5 TB (ssd)None1 GbE
Comfortable2 cores4 GB1 TB (ssd)None1 GbE
Overkill4 cores7 GB2 TB (ssd)None1 GbE

Beyond Comfortable — 4 cores, 7 GB RAM, 2 TB (SSD): headroom you will never use for this workload alone. Put the difference into storage, backup or silence.

Recommended system shape

Derived by the decision engine from the recommended tier — the same logic that plans full builds.

Form factor
sff
Build style
prebuilt
Drive plan
2× 2TB NVMe

Light requirements (1 threads, 2GB RAM) fit a sff prebuilt system — simpler and more efficient than building from parts.

One box or a separate machine?

Whether this workload deserves its own system or should live on the main server.

Keep on the main server

Lightweight always-on service — a separate system would add cost, energy and maintenance for no benefit.

Storage arrays, priced

Five physical strategies for the recommended capacity — the same planner, drive model and reference prices as the storage planner tool.

StrategyDrivesUsableCostIdle
Cheapest1× 4TB hdd4 TB · none≈ €1005 W
Balanced1× 16TB hdd16 TB · none≈ €2406 W
Redundant3× 8TB hdd8 TB · parity2≈ €45015 W
Expansion-friendly1× 20TB hdd20 TB · none≈ €3007 W
PerformanceRecommended2× 4TB nvme4 TB · parity1≈ €4802 W

For a fast working tier, go all-flash — the performance strategy protects speed without the HDD rebuild pain.

Backup is not storage

The extra copy that survives drive failure, deletion and ransomware — the same engine as the backup planner.

Protect 0.5TB with at least two copies on separate hardware, ideally one offsite. The recommended start is a dedicated NAS.

Recommended: Separate NAS A dedicated box that only stores backups · ≈ €259

What will it cost?

Market-neutral EUR bands from the reference drive model (≈ = estimated street price). Live component prices resolve on the build page for your region.

Storage array
≈ €100 – €480
Array energy / year
≈ €37/yr (∼17 W idle)

Compute (CPU, board, RAM, GPU) is not included — see the recommended build for live prices.

Growth outlook

What happens when the data keeps growing — the same engine as the growth simulator.

This architecture becomes inadequate in year 2 — 2 bays needed. Plan the next step (bigger array, NAS or DAS, or a stronger platform) before then.

Exceeds max 2TB by 1TB — need larger array/DAS/NAS. Fresh Performance array for 3TB: 2 bays, ~480€.

Which tier do you need?

Frequently asked questions

How much RAM does uptime monitor need?

1 GB is the sensible minimum, 2 GB covers most real setups, and 4 GB gives comfortable headroom for growth and extra services.

How many CPU cores does uptime monitor need?

A 1-core CPU is the minimum, 1 cores is the recommended sweet spot, and 2 cores is comfortable when it shares the machine with other workloads.

Does uptime monitor need a dedicated GPU?

No — integrated graphics or a headless setup is enough.

What storage and network does uptime monitor expect?

Storage: 0.5 TB of SSD is the recommended baseline (0.2 TB minimum, 1 TB comfortable). Network: 1 GbE is the recommended baseline.

What runs well alongside uptime monitor?

It pairs naturally with: Homelab ops, Docker, Reverse proxy.

How much power does uptime monitor use?

The storage array idles around 17 W (≈ 37 €/year at 0.25 €/kWh). The full system adds CPU, board and fans on top — see the cost section for the honest bands.

See the recommended buildPlan your own

Related workload guides