Likely so. More precisely, it would need to be managed with whatever manages DNS for whoever you want to be able to access this stuff.
So, if (as is usually the case) your router serves DNS to your LAN, and everyone you want to access this stuff is on your LAN, then your router is where you’d set it up. If instead you use something like Pi-Hole or AdGuard Pro for local DNS, you’d set it up there. In these cases, you can freely make up domain names, but do not put them in existing top-level domains (so you could, e.g., use myhome.lan, but not myhome.com). You can do HTTPS in these cases, but only with a self-signed certificate, so you will get certificate errors (though you can bypass them).
If you want remote users to be able to access your stuff by way of a domain name, though, you have a bit of a problem. In that case, you’ll need a public domain name so that you can update public DNS records, so that your remote users will be able to resolve those names.
Consider that domain names are cheap, starting around US$10-15 per year (and in some cases even less, though those cases usually have strings attached). If you want it to have some connection to your name or purpose, it may take some searching to find a suitable one available, but if you just want something short, you can search for it here:
The last domain I ordered, I didn’t really care what it was, I just wanted something short. 2v6.in was available, so I picked it up and went with it. It’s six meaningless characters as far as I’m concerned, but if ever I share it with someone, it’s going to be in writing anyway, so it doesn’t much matter to me that it be meaningful. You can, of course, search there, maybe finding something incorporating your name or initials so as to be somewhat meaningful. Or if you don’t care that the domain name be short, that isn’t so much of an issue anyway.
Another option would be to use Tailscale with its Magic DNS feature, which gives you your own private subdomain. Some relevant information on that option:
