Self-hosted services
Internal tools, bots, and web services on cluster compute I control.
▲ Self-hosted · k3s · Resilient infrastructure
A private lab running Kubernetes, self-hosted services, telemetry, and automation — built to be observable and honest about its own state.
What is this?
A cluster of small computers running self-hosted services, monitoring, and automation — maintained by one person, from home.
Physical machines in a redundant cluster — self-hosted, not rented.
Metrics, logs, and service health gathered continuously. Problems surface before they're noticed.
TLS everywhere, Cloudflare Tunnel, no open ports. Data stays on hardware I own.
Capabilities
Connected infrastructure — understood at a glance, repaired with intention.
Internal tools, bots, and web services on cluster compute I control.
Uptime, power draw, logs, and service health — gathered continuously.
Layered access control, TLS everywhere, firewall rules, and log review. Recovery paths are documented and exercised, not assumed to work.
Scheduled, verified, and periodically tested restores — not just set and forgotten.
Repeated repairs become repeatable tools — scripts, playbooks, and CronJobs.
Raw system noise translated into language that helps decide what to do next. Dashboards should reduce anxiety, not manufacture it.
Current stack
Hardware and software as of the last update. The stack evolves.
The lab
Compute, networking, storage, and monitoring as connected systems — understood, not just kept running.
Design principles
Signal Board
Tunnel latency, power draw, backup health, and service readiness — live data, updated every 15 minutes.
Cloudflare Tunnel · edge path · 7-sample window
7-sample window
restic snapshots · weekly view · higher is better
Core services · from /data/service-health.json
Cloudflare WAF · managed rules · last 24 hours
Status
Live data from the cluster — updated every 15 minutes.
—
——
——
——
——
——
—Visitors
Top countries by request volume — last 30 days via Cloudflare analytics.
Connect
Personal project. Questions about homelab infrastructure or anything here — reach out directly.