Localhost tunneling

HELIX

Punch a hole from your laptop to the internet. Persistent paths. No middleman theater.

npm install -g helix01
Sign in →

Localhost in. Path out.

Your CLI holds the wire. The relay routes the signal.

Localhost

:3000

Helix relay

self-hosted

Public path

/tunnel/myapp/

In the terminal

Two commands.
One public path.

Authenticate once. Expose any port. Share /tunnel/myapp/ instead of a disposable subdomain.

✔ Logged in via email
✔ Tunnel registered
ℹ Public: /tunnel/myapp/

Why Helix

Built like infrastructure. Feels like a tool.

  • Paths, not subdomains

    Every tunnel lives at /tunnel/{name}/ — claim it, keep it, share it.

  • CLI is the product

    helix login. helix myapp 3000. The dashboard only watches the wire.

  • Email codes, done

    Passwordless sign-in. Same account on web and CLI.

  • Your relay, your rules

    Self-host the relay. Traffic stays on metal you control.

Three beats.

  1. 01

    Login

    Email code. Session saved.

    helix login
  2. 02

    Expose

    Claim a name. Open a port.

    helix myapp 3000
  3. 03

    Share

    Send the path. Stay live.

    /tunnel/myapp/

Pricing

Free. Pro when the demo matters.

Free

₦0

  • Live tunnels1
  • Idle timeout2 min
  • Request historyLast 50
  • Password lockNo

Pro

₦2,500/mo

  • Live tunnelsUnlimited
  • Idle timeout24 hours
  • Request historyLast 500
  • Password lockYes
Upgrade

Open a port.
Own the path.

npm install -g helix01
Open dashboard