Skip to content

Expose localhost to the internet without port forwarding

Let teammates and clients access apps running on your computer. No VPN, public IP, router port forwarding, or deployment required.

You need Node.js 26.7 or later and a Tubu API key on the publisher machine. Follow the Quick start to get your key. Replace YOUR_API_KEY and choose an available Tubu domain in the examples. The publisher must reach the target service and connect outward to Tubu. Keep it running while access is needed.

Your app only works on your computer

A localhost URL does not work on a teammate’s computer. Deploying each change slows down demos, reviews, and testing on other devices. Your home or office router may also sit behind NAT with no public IP.

Give your local app a public HTTPS URL

Start your app on port 3000, then run Tubu on the same computer:

npx tubu-cli http 3000 --domain my-app.tubu.dev --authtoken YOUR_API_KEY

Wait for Tunnel ready:. Tubu connects outward from your computer and forwards incoming HTTPS requests to your app. Keep both processes running.

Open the app from another device

curl --fail https://my-app.tubu.dev

Expect your app’s response. Share that HTTPS URL with your reviewer or open it on your phone. Visitors do not need the Tubu CLI. Keep application authentication enabled for content that requires a login.

If you receive a 502, check that the app responds locally on port 3000. If your development server rejects the hostname, check its allowed hosts. Stop Tubu with Ctrl+C when the review ends.

Get started with Tubu