01
Your own domain, real certificates
Point a CNAME at Wormhop, add a TXT record, and it issues and renews a Let's Encrypt certificate for you.
Run the agent on any machine at home and give your services a public HTTPS address, on a wormhop.dev subdomain or your own domain. It only connects out, so there's nothing to open on your router, and it works behind CGNAT where port forwarding can't.
$wormhop http 8123 --hostname home.example.com # Home Assistant$wormhop http 192.168.1.20:80 --subdomain my-nas # another box on your LAN$wormhop tcp 22 --remote-port 20022 # SSH into the lab01
Point a CNAME at Wormhop, add a TXT record, and it issues and renews a Let's Encrypt certificate for you.
02
The agent can forward to other machines on your LAN, so one Raspberry Pi can publish the whole lab.
03
Put basic auth in front of anything that doesn't have its own login, with one flag.
04
Keep every tunnel in one config file and start them together with wormhop start --all.
Questions
Yes. The agent makes an outbound connection, so it works where your ISP doesn't give you a public IP and port forwarding is impossible.
For yourself and a few people, yes. Watch the plan's monthly data transfer: video uses it quickly, and tunnels pause when it runs out.
Free works for trying it. Hobbyist adds a custom domain, reserved subdomains and UDP; Pro is for a bigger lab with more services running at once.