127ohoh1
One line in, one URL out

Your localhost, now reachable, in one line.

Run one command and your local app is live on a stable HTTPS address before your coffee's done.

127ohoh1 expose http://127.0.0.1:3000
Get your tunnel — it's free Read the docs

No signup to try it. No calendar invite to talk pricing.

the internet firewall A firewall B 127ohoh1 client A client B

Everything your NAT was too embarrassed to admit it needed.

No agents to install on your router. No inbound port to open, no inbound firewall rule to justify in the next audit. Just one outbound connection, doing its one job well.

Outbound only

The CLI opens one outbound, authenticated TLS connection. Nothing listens on your machine, so nothing on your machine has to explain itself to security.

Your key is your identity

Endpoints belong to an Ed25519 key you hold — not a username, not a password you'll forget by Tuesday. An account is optional, and only manages paid names and notifications.

Pay in USDC, per name

Reserved names are paid over HTTP 402 with USDC. No credit card, no subscription you forgot to cancel, no small talk with a sales rep.

We don't peek

Request bodies passing through your tunnel are never stored, and URLs and query strings are never logged. What it carries is between you and whoever you handed the link to.

Three steps. Zero paperwork.

  1. Get the CLI

    One line picks the right build for your machine and checks it against our signed release:

    curl -fsSL https://127ohoh1.com/install.sh | sh

    Linux and macOS. Windows, or rather read it first? See the docs.

  2. Point it at your service

    Run one command. That's the entire setup ceremony.

  3. Get a stable HTTPS name

    Share it, embed it, forget your router exists.

$ 127ohoh1 expose http://127.0.0.1:3000
✓ tunnel established
→ https://sturdy-otter-4821.127ohoh1.com (example name)

Questions people ask before they expose localhost

How do I expose localhost to the internet?

Run 127ohoh1 expose http://127.0.0.1:3000. The CLI connects out to us and your local app is served on a stable HTTPS address. Nothing about your machine or router changes.

Do I need to open an inbound port?

No. The tunnel is a single outbound TLS connection, so there is no inbound firewall rule, no port forwarding and nothing listening on your machine.

What can I put behind a tunnel?

Any local HTTP service: a dev server, a webhook receiver, an API or a demo. It is HTTP only; there is no generic TCP, SSH or UDP forwarding.

Is it free?

Yes. You get a random HTTPS name without an account, with 100 kB/s and 500 MB a month. Reserved names are paid in USDC; see the exact plans.

Free to start. Cheap to stay.

One reserved name, straightforward limits, no discovery call with a sales team that wants to walk you through a slide deck. Exact numbers live on the pricing page — no asterisks hiding underneath.

See exact plans →

Stop opening ports.
Start opening tunnels.

One command. No inbound rule. No drama.

Get your tunnel — it's free Read the docs