NIDAL SIDDIQUE ORITRO
Nidal Siddique Oritro

Software Engineer / Manager

Software Engineer turned into Engineering Manager, helping teams to build better software and solve complex problems. I am passionate about building high-performing teams and creating a culture of continuous improvement.

Who Am i?

I started writing code as a profession early 2013 and i never stopped. My 13+ years of industry experience is helping me bring structure and value to my team. My 2025 goal is to build digital automation that helps team work more effortlessly.

This is my personal blog, portfolio, whatever floats your boat. I write about software engineering, homelab, self hosting, my journey into becoming a manager, my experience in helping teams build a better software and my experience in building high-performing teams.

I am a novice 3d model desiger, love 3d printing, creating complex homelab server ( that i probably don't need), working with LLM and AI models.

Back to home

Building a Homelab - Part 1 - Decade long journey

April 1, 2025
Oritro Ahmed

Topic Summary

This post is a part of 3 posts sharing my experience in building my own homelab ecosystem.

Building a Decade of Homelab Infrastructure: Part 1 - The Service Ecosystem

Homelab has exploded in popularity since the pandemic hit, with people becoming increasingly interested in cutting the cord and keeping everything within their own network as much as possible. The current homelab ecosystem ranges from simply running a few basic services to almost industrial-looking setups, with everything imaginable in between.

I’ve been tinkering with homelab infrastructure since 2015. What started as a simple Plex server has, over the past decade, morphed into something of a digital beast in its own right. After this 10-year journey through countless configurations, upgrades, and late-night troubleshooting sessions, I thought it was time to share some of my experiences, the common pitfalls I’ve stumbled into, and everything I’ve learned along the way.

My current setup runs on dedicated hardware that’s evolved significantly from those early days:

Hardware Configuration

[ Main Server ]

  • CPU: AMD Ryzen 3500x
  • RAM: DDR4 32 GB (4x 8 GB)
  • GPU: Nvidia 1660 Super OC Edition
  • Motherboard: MSI B450 Tomahawk Max
  • Storage: 1x 10TB HDD, 3x 8TB HDD, 512GB NVMe SSD

[ Octoprint Server ]

  • Intel 10th gen Core i5 laptop (Huawei MateBook Pro repurposed)

[ AdGuard Server ]

  • Orange Pi Zero (because sometimes the smallest devices handle the biggest responsibilities)

What’s Actually Running

After a decade of experimentation, my homelab has settled into running a diverse ecosystem of services. Here’s the complete breakdown of what’s currently deployed:

CategoryServicePurposeWhy It Matters
Core InfrastructureHomepageDashboard & Service DirectorySingle pane of glass for everything
NginxReverse Proxy & SSL TerminationClean URLs instead of port chaos
AutheliaSingle Sign-On AuthenticationOne login for everything
LLDAPUser DirectoryCentralized user management
PortainerContainer ManagementVisual Docker interface
DozzleReal-time Log ViewerDebug containers without SSH
Media StreamingPlexMedia Server (Primary)Polished streaming experience
JellyfinMedia Server (Secondary)Open-source alternative
NavidromeMusic StreamingPersonal Spotify replacement
Photo ManagementImmichPhoto & Video LibraryGoogle Photos alternative
Entertainment ToolsOverseerrMedia Request ManagementFamily-friendly request system
JellyseerrAlternative Request ManagerJellyfin-focused requests
Home AutomationHome AssistantIoT Hub & AutomationSmart home brain
N8NWorkflow AutomationPersonal automation engine
FrigateAI Security CamerasSmart surveillance with object detection
NTFYPush NotificationsCustom alerts and updates
Document ManagementPaperless-NGXDocument DigitizationPaperless office solution
DocmostTeam DocumentationInternal wiki and knowledge base
NocoDBDatabase InterfaceAirtable alternative
Personal ProductivityVaultwardenPassword ManagerBitwarden server
LinkwardenBookmark ManagerCentralized link collection
MemosQuick NotesPersonal note-taking
Actual BudgetFinancial ManagementPrivacy-focused budgeting
WallosSubscription TrackerKnow what you’re paying for
UtilitiesStirling PDFPDF ToolsDocument processing
CyberChefData AnalysisSwiss army knife for data
Change DetectionWebsite MonitoringTrack changes across the web
FileFlowsMedia ProcessingAutomated file workflows
DevelopmentOpen WebUIAI Chat InterfaceLocal ChatGPT alternative
AtuinShell History SyncCommand history across devices
GamingPufferPanelGame Server ManagementMinecraft and friends
Media Management*arr StackAutomated Media CollectionManaging thousands of movies and TV shows

The beauty of this setup isn’t just in the individual services, but in how they work together. Overseerr talks to the media services, Home Assistant triggers N8N workflows, and everything shares the same authentication system. It’s become less of a collection of tools and more of an integrated digital ecosystem.

In this first part, we’ll explore how these services complement each other and why each one earned its place in my infrastructure. The foundational architecture – the networking, security, and orchestration that makes it all possible – will be the focus of part two, where we’ll dig into the technical decisions that keep everything running smoothly.

What’s Coming Next

This series will unfold across three detailed posts:

  1. Part 1: The Service Ecosystem ( This Post ) - Understanding what runs and why
  2. Part 2: Foundation Architecture - Networking, security, and service discovery
  3. Part 3: Advanced Operations - Scaling, monitoring, and maintenance

Let’s dive into the world of self-hosted services and see what a decade of iteration has taught me about building resilient home infrastructure.