Expose localhost to the world.
Your local server, live on a public subdomain — through one secure outbound
tunnel. No port forwarding, no firewall changes, no config.
Type otunl expose 3000 and share yourapp.otunl.com.
This is the real otunl CLI — the banner, the live status panel, the request log. Exactly what your terminal will look like.
Everything a tunnel should do, nothing you have to configure.
No dashboard detours, no YAML. The tunnel starts the moment you ask for it — and the live request log streams right there in your terminal.
Pick a name and keep it. Demos, webhooks, and clients always find you at the same address.
Wi-Fi dropped? Laptop slept? The tunnel heals itself with exponential backoff and picks up where it left off.
Every tunnel ships behind a wildcard certificate on *.otunl.com — your localhost speaks TLS to the world without owning a single cert.
Your machine dials out — so nothing ever has to dial in. The relay routes the world back to you over that same connection.
Anything on localhost:3000 — an API, a site, a webhook target.
One persistent, secure, outbound tunnel — multiplexing every request over a single connection.
Anyone opens myapp.otunl.com — and reaches your machine, instantly.

SOFTWARE ENGINEER · BUILDING OTUNL
Software engineer at the Palestinian Ministry of Finance, where his Spring Boot services connect government systems to banks and the national e-payment platform. Computer Systems Engineering graduate (PTUK) and a national top-10 finisher at the PCPC programming competition. otunl is his from-scratch take on developer tunneling — its protocol, relay, and CLI all built by hand.
Tulkarm, Palestine