Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/IsaiasCarrion/Homelab/llms.txt

Use this file to discover all available pages before exploring further.

The homelab is built in deliberate phases, each one producing a stable, usable state before the next layer of complexity is introduced. Phase 1 establishes the networking and virtualisation primitives everything else depends on. Phase 2 turns the Docker platform into a proper development environment. Phase 3 adds the observability stack that makes the lab self-monitoring. Phase 4 extends into experimental territory — Kubernetes, AI workloads, and GitOps — once the foundation is solid enough to support them reliably.

Phase 1 — Core Infrastructure

The foundation layer covers bare-metal virtualisation, local networking, remote access, and the container platform. Every item in this phase is complete.
ComponentDescriptionStatus
Proxmox VEHypervisor at 192.168.1.20, managing all VMs and LXC containers
Technitium DNSLocal DNS, split DNS, ad-blocking via big.oisd.nl at 192.168.1.21
Nginx Proxy ManagerSSL termination and reverse proxy for all home.arpa hostnames at 192.168.1.22
Docker VMDebian 13 VM at 192.168.1.30 running Docker Engine and Docker Compose
TailscaleSubnet router and exit node for secure remote access at 192.168.1.23

Phase 2 — Dev Platform

The dev platform phase adds container management, dashboards, and the services needed for self-hosted development workflows. Core monitoring and management tooling is already live; database and source control services are in progress.
ComponentDescriptionStatus
PortainerWeb UI for Docker container and stack management at portainer.home.arpa
DashyMain homelab dashboard at dashy.home.arpa
Speedtest TrackerISP speed monitoring at speed.home.arpa
GiteaSelf-hosted Git service at git.home.arpa🚧
PostgreSQLRelational database for application workloads🚧
RedisIn-memory cache and message broker🚧
n8nSelf-hosted workflow automation and API integration🚧
CI/CD pipelines and GitOps tooling are planned as a follow-on to the Gitea deployment. Once Gitea, PostgreSQL, and Redis are stable, the dev platform phase will close with a self-hosted CI/CD runner and GitOps-driven configuration management.

Phase 3 — Observability

The observability phase builds a full metrics and alerting stack on top of the running services. All items are pending and will begin once the dev platform is complete.
ComponentDescriptionStatus
Uptime KumaHealthcheck and uptime monitoring for all services🚧
GrafanaMetrics dashboards at grafana.home.arpa🚧
PrometheusMetrics collection and storage at prometheus.home.arpa🚧
AlertingAlert rules and notification routing for the observability stack🚧

Phase 4 — Labs

The labs phase is the experimental frontier: Kubernetes for orchestration practice, Ollama for local AI inference, and GitOps for infrastructure-as-code at scale. These will run in the 192.168.1.50–69 range reserved for labs and AI workloads.
ComponentDescriptionStatus
KubernetesSingle-node or multi-node K8s cluster for orchestration learning🚧
OllamaLocal large language model inference server🚧
AI WorkloadsExperimentation with local AI pipelines and tooling🚧
GitOpsInfrastructure-as-code with git as the source of truth🚧

Future Lab Projects

Beyond the four main phases, additional projects are planned to extend the homelab into security, identity management, and advanced automation.
ProjectDescriptionStatus
Kubernetes LabFull K8s environment with persistent storage and ingress🚧
AI / OllamaSelf-hosted LLM inference and AI tooling🚧
Full ObservabilityEnd-to-end metrics, logs, traces, and alerting🚧
GitOpsInfrastructure-as-code with git as the source of truth🚧
CI/CD Self-HostedSelf-hosted CI/CD runner for automated pipelines🚧
AuthentikSelf-hosted identity provider and SSO for all services🚧

Build docs developers (and LLMs) love