04 / CASE STUDY
AiServer homelab
Practice self-hosting, monitoring and scoped administration.
Private operational lab. No public management link or live demo.
AI-assisted administration and documentation of a private operational lab; not a claim that AI built the entire environment or performed a security audit.
Private access → Ubuntu host → Docker services
Health reporting · Service visibility · Self-hosted AI
No addresses, endpoints or management links shown.
Challenge
Practice repeatable self-hosting and operational visibility without publishing private management surfaces.
Environment
Private Ubuntu server with Docker. Service availability is verified operational context, not a security audit.
Built
Self-hosted services and monitoring: Discord health reporting; Uptime Kuma, Dozzle, Glance and WUD for visibility; Ollama and Open WebUI for local AI. A homelab wiki container runs, but its content was not verified.
Tested
Prior verified operational context includes working Discord health monitoring, running containers, private Tailscale access and scoped SSH through a dedicated non-root account. Narrow diagnostic permissions were tested for allowed and blocked operations. No live network inspection or security audit was performed for this portfolio.
Concepts
Least-privilege administration, container operations, health visibility and separation of public documentation from private infrastructure.
Outcomes
A working private environment supports learning and self-hosted tooling. Operational status is not evidence of hardened configuration, incident detection or production-grade reliability.
Takeaways
A sanitized overview can explain operational work without revealing topology, management links, scripts or credentials. Running services and verified security controls are different claims.
Limitations
No public homelab screenshot or raw configuration is included. No uptime statistics, security audit or public deployment claim. Protected monitoring scripts and webhook configuration were not inspected.