When we look at what people actually use their localnode.app subdomains for, a handful of patterns come up again and again. Here are the most common ones.
1. Reach your home server from anywhere
The big one. Point a subdomain at your home IP, enable DDNS so it follows your dynamic IP when your ISP changes it, and you have a permanent address for whatever's running at home. No more texting yourself your current IP or getting locked out when it changes overnight.
2. Give each service its own name
Running a few things on the same box? Give them each a subdomain. jellyfin.localnode.app, homeassistant.localnode.app, nextcloud.localnode.app - cleaner than memorising which port does what, and your browser's actually happy to bookmark them.
3. Show someone what you're tinkering with
Pair your subdomain with a tunnel tool like Cloudflare Tunnel or ngrok and whatever's running on your local machine gets a real public address. Send the link to a friend or family member. No deployment, no server, just your laptop doing the work.
4. Make a Raspberry Pi feel like a real server
A Pi sitting on your desk is basically a VPS you already paid for. Add a subdomain and a bit of port forwarding and it's reachable from anywhere in the world. Feels a lot more satisfying than 192.168.1.42:8080.
5. Try something without committing to a domain
Got an idea you want to poke at? Spin up a subdomain, run the project for a few weeks, see if it goes anywhere. If it doesn't, delete the record. Zero cost, zero cleanup, no annual renewal sitting in your inbox six months later.