Go Router
Running a lot of containers I had to keep track of an unreasonable amount of ports. After around 10 of them, I could barely remember how to navigate to my services. To make things worse, hard coding ports for inter-service communication became a nightmare. Ideally I would have solved this problem using a DNS server, but this would have been complicated with my network stack at the time.
I set up a pi-hole instance to solve the intra-service communication, but other devices on the network could not leverage it in a convinent way. At a previous employer we had the notion of "go-links", which were essentially short links to urls. I decided to implement a similar system for my home network, such that any device on the network could resolve containers by visiting go/<short path>.