Use JustTunnel in your local dev workflow

Mobile testing, OAuth callbacks, team demos, and PR previews — all from a localhost tunnel.

You want to make your local dev server reachable from anywhere — a phone on the same Wi-Fi, an OAuth provider, a teammate in another city — without deploying or fiddling with router config. A JustTunnel URL points at your laptop and keeps working until you stop the tunnel.

Mobile testing

DevTools device emulation only goes so far. To test on a real phone, you need a URL the phone can reach.

justtunnel 3000

Open the printed URL on your phone. Done. No LAN IPs, no port forwarding, no separate hotspot.

Team demos

Show a feature to a PM without deploying:

justtunnel 3000 --subdomain demo-feature-x

Share https://demo-feature-x.justtunnel.dev in chat. They see your local build immediately. No CI wait, no staging conflicts.

OAuth and third-party callbacks

Most OAuth providers (Google, GitHub, etc.) require a publicly reachable redirect URL. During development:

justtunnel 3000
# → https://abc123.justtunnel.dev

Set your OAuth redirect to https://abc123.justtunnel.dev/api/auth/callback and run the full flow locally. With a reserved subdomain, the URL stays the same across sessions so you don't keep editing the provider's settings — see Reserve a subdomain.

PR previews without staging

Before pushing a branch, share a live preview:

Run the branch locally.
Expose it with justtunnel 3000.
Drop the URL in the PR description.

Reviewers click into the actual running build instead of reading a diff.

Tips

Reserved subdomains pay for themselves. If you're testing webhooks or OAuth, locking the URL down means provider config never goes stale.
HTTPS is built in. No certificate setup; no mixed-content errors when you embed the URL elsewhere.
Any framework, any port. justtunnel <port> works the same for Next.js, Rails, Django, Go services, or a static file server.