Discover how to build a local dashboard with just one config file for managing your self-hosted services. Solve the problem of thirty services and zero visibility by creating an efficient ops strategy
TL;DR: The moment you cross about a dozen self-hosted services, browser bookmarks stop working as an ops strategy. You end up with a mental map that looks something like this: Ollama is on :11434, n8n is on :5678, Grafana on :3000, Portainer on :9000, your WordPress instance so
What's in this article
The Problem: Thirty Services, Zero Visibility
What Homepage Actually Is (and What It Isn't)
Getting It Running: Docker Compose and Directory Layout
I built and operate a 13-service self-hosted platform on a single Linux VPS: a personal AI chat...
The standard observability stack: Grafana + Loki + Tempo + Prometheus. Four services to deploy, four...
A tour of my self-hosted infrastructure - from reverse proxy to local AI, CI/CD pipelines, document management, and home…
Setting up the three pillars of observability should not take a weekend. Here is how I made it take 30 seconds.
How we went from 8 drifting Helm charts to one unified chart that 70+ .NET microservices depend on in production — and what we…
Originally published on kuryzhev.cloud We thought setting up a self-hosted Ollama homelab for...
