My setup is a pile of kludges built on top of each other over the last two decades.
I started with ULAs distributed through DHCP, connected to named, which allows hosts do declare their own name and let me access local services as though I had a real domain.
My ISP eventually started supporting IPV6, but only assigned /128, so the ULAs got NAT-6ed out to the real world.
I eventually learned how to request prefix delegation from the ISP and set up SLAAC.
So now, my PIv6 clients have a) their link-local address, b) the ULA, c) a “privacy” SLAAC, and d) a unique SLAAC. All my internal services still refer to the ULAs.
I don’t think I’d recommend this system for someone setting up from scratch. The easiest thing would be to go with SLAAC, if you can get prefix delegation, and set your DNS/pihole to send the unique-SLAAC address of any servers you run.




Keep power in mind. For most home-use services, you don’t really need much computing power, and you might be able to do all you want with a single box. Even 30W, 24/7 is $25 (@10¢/kWh)-125(@50¢)/year of electricity. That said, it’s a small price to learn how to do clustering or swarms.
I’d guess that your biggest load would be transcoding in Jellyfin, for which Intel Gen 6 added h265 to quicksync. The Gen 3/4 CPUs in M73 would be extra slow with most modern codecs.