Little known trick–or perhaps everyone knows it and is quietly laughing behind my back–with Chromium browsers and Firefox (and maybe Safari, I’m not sure), you can add a slash to the end of an address and it will bypass the search.
So, for example, my router on the LAN goes by the hostname “pfsense”. I can then type pfsense.lan/ into my address bar and it will bring me to the web UI, no HTTP/s needed.
I didn’t care about any of this (my off the shelf Router used .local) and then I started selfhosting more and using pFsense as a router OS. It defaulted to using home.arpa, which was so objectionable that I spent time looking into RFC 6762 and promptly reverted to .lan forever.
The official choices were: .intranet, .internal, .home, .lan, .corp, and .private. LAN was the shortest and most applicable. Choice made.
.lan for everything.
I use Vaultwarden in Docker, which is a light-weight Rust implementation of the Bitwarden server. You can just point any of the apps or browser extensions to your server at login and it works seamlessly. The oficial Bitwarden Server is also available, but when last I used it, it was much more resource intensive and had a number of docker containers as dependencies instead of the single container for Vaultwarden.
For UniFi, I use a docker image–currently, I’m using this one.
I host the following off of the top of my head, in no particular order. Some are hosted at home on a combination of a Raspberry Pi 4 and a Synology DS1821+ NAS, some are hosted on a dedicated server:
I also run PFSense at home for my router, on a Protectli Vault, if that counts as self-hosting. Seems more like sysadmin, but there you go. I use Uptimerobot to monitor everything and create sleek public status pages.
https://www.youneedfeeds.com/starter-packs is a fairly solid resource for some good, category-based feed groups.