Demo localhost without a tunnel account

The build runs on your laptop, port 3000, behind hotel wifi. The client wants to see it before their board call in twenty minutes.

hoody-tunnel: your laptop opens one WebSocket out to your container, and an EXPOSE binding publishes local port 3000 at the container's public URL. The hostname and its certificate already exist, so there is no DNS step, no certificate wait, no account with a tunnel vendor, no rate-limit tier. Your laptop never accepts an inbound connection: it is the WebSocket client: so this works behind NAT, a corporate firewall, a captive portal.

You paste the URL. The client clicks. When you close the session, the URL stops answering.

The public URL already existed; the tunnel just points your laptop at it.