I'm a systems administrator in Germany. At work it's Linux, Windows, Active Directory and keeping things running. After hours I build software I'd want to use myself: careful, offline-first where possible, and documented well enough that I'll still understand it in a year.
$ systemctl status nerve
● nerve.service - Self-hosted network management platform
Loaded: loaded (private repository; enabled)
Active: active (running) in the background
Tasks: device discovery, infrastructure inventory, network visualization
Status: "Building it slowly and properly. Public when it's ready."
NERVE is the project I keep coming back to. It's a self-hosted platform that discovers what's on your network and maps how devices, VMs, containers and services connect, so the network itself becomes the way you navigate. It runs on Go, PostgreSQL and Docker Compose. It isn't public yet, but it's why the map above has something in the middle.
sysadmin-scripts: Windows support scripts for
Active Directory, Outlook, Teams, OneDrive and Appx cleanup. Each one previews first and only
changes the machine when you pass /apply.
The homelab is where things break before they reach anything that matters: Proxmox, Docker Compose, WireGuard, reverse proxies, monitoring and backups. Most of what ends up in NERVE started as a question about my own network.
Toolbox: Linux, Windows Server, Active Directory, Proxmox, Docker, PowerShell, Bash, Go, TypeScript and React. Next on the list: Ansible and infrastructure as code.
Found a bug or have an idea for one of the projects? Open an issue in that repository. I'm always happy to talk about Linux, self-hosting and small tools that save a sysadmin ten minutes a day.
More about me and notes from the homelab: luis-0508.github.io (English and German).


