Cost and Power Tracking
A short, honest look at tracking what your homelab actually costs to run - a genuinely common rabbit hole, worth doing lightly rather than obsessively.
This page is deliberately short, because the topic itself deserves a warning label: tracking homelab cost and power draw is one of the most common rabbit holes in the hobby. It's easy to spend more hours building a Grafana dashboard to track your electricity cost than you'll ever save by optimizing it.
The lightweight version, which is enough for most people
You already have the raw numbers from Power, Noise, and Thermals - a plug-in power meter or smart plug reading, and your electricity rate from a recent bill. Multiply it out for your actual setup:
watts ÷ 1000 × 24 hours × 30 days × price per kWh = monthly cost
For a typical Beginner-tier mini PC (10-20W idle), that's usually $3-8/month - genuinely cheap, and worth knowing once rather than tracking continuously. Write the number down, revisit it if you significantly change hardware, and move on.
Where tracking becomes worth doing properly
A couple of real situations justify going further than a one-time calculation:
- You're deciding between hardware options and want to compare actual running cost, not just purchase price - the mini-PC-vs-used- server trade-off from Choosing Hardware is a good example of a decision real numbers improve.
- You're running enough hardware that it shows up on your bill - once you're past one small machine (particularly once you reach Intermediate and start running always-on virtualization hosts), the aggregate draw is worth periodic checking rather than a single estimate.
If you want a running number without a dashboard project, a Shelly Plug or similar smart plug reporting to its own app is enough - it doesn't need Grafana, Prometheus, or a database. Save the full observability stack for Monitoring and Alerting in Intermediate, where it's actually solving a broader problem than "one number."
What "done" looks like for Beginner
If you've followed this tier in order, you now have: one machine running Debian/Ubuntu, Docker and Compose managing a handful of real services, basic network hygiene, backups you've actually tested, and a rough sense of what it costs to keep running. That's a complete, legitimate homelab - not a "starter" one you're obligated to outgrow.
When you're ready for virtualization, network segmentation, and dedicated storage, move on to Intermediate.