Notfi Tunnels

Secure tunnels, on demand

Your local services, reachable in one command.

Notfi Tunnels gives a web app on your laptop, an SSH port on a field device, or a service inside your app a public address.

alice@macbook
$ notfi-tunnel login
Token for tunnels.notfi.io:4443 (from the Account page): ••••••••
Logged in to tunnels.notfi.io:4443 as 'alice'.

$ notfi-tunnel http 3000
Forwarding: https://k3j9x0ab.tunnels.notfi.io → localhost:3000
12:04:31  GET   /api/orders   200  18 ms
12:04:33  POST  /api/orders   201  42 ms

01 · Features

Everything a tunnel should do

HTTP and TCP tunnels

Web apps get an HTTPS subdomain with WebSockets, streaming and large uploads. SSH, databases and anything else get a TCP port.

Devices on demand

Agents on devices hold one quiet connection and open SSH or a web UI only when someone asks, for as long as they ask. Nothing is exposed in between.

Web dashboard

Live tunnels with traffic graphs, history, devices, your token and fixed subdomains, users and an activity log of every sign-in and change.

Request inspector

See every request and response on your machine, replay it, or copy it as curl. Only you can open it.

Built for code

Client libraries open tunnels inside your app, starting with .NET, and --json makes the CLI easy to drive from any language.

Secure by default

TLS everywhere, one token per account that you can replace instantly, data encrypted at rest, and limits that keep one client from hogging the server.

02 · Dashboard

See and control every tunnel

Everything the clients do shows up live in the web dashboard. Watch traffic as it happens, open a device's SSH for an hour, or sign a lost laptop out, all from the browser.

Tunnels page: open tunnels with live requests and traffic per client
Tunnels. Live tunnels per computer and device, with requests, traffic and a one-click disconnect.
Devices page: agents with services that can be opened for a set time
Devices. The services each device offers. Open one for a set time; it closes again on its own.
Account page: your token and fixed subdomains
Account. Your one token, which you can show again or replace, and the subdomains that are yours.

03 · How it works

How it works

  1. The client connects out. It opens a connection to the tunnel server, so it works from behind NAT, firewalls and cellular networks. Nothing connects into your machine or device.
  2. The server gives it an address. https://name.tunnels.notfi.io for web apps, tunnels.notfi.io:20022 for TCP.
  3. Traffic is relayed. Each visitor's connection is carried to the client, then on to your local service.

04 · Get started

Get started

1

Install the client

One file for Windows, macOS or Linux. Nothing else to install. Pick your download.

2

Log in

Paste the token from your Account page in the dashboard. The same token works on every machine and device you use.

notfi-tunnel login
3

Expose a port

notfi-tunnel http 3000
notfi-tunnel tcp 22

Addresses are random. To use a name of your own, assign it to your account in the dashboard, then --subdomain myapp.

05 · Download

Download

Each download is a single executable with everything it needs built in. Extract it and run it. All releases and checksums

Windows

Windows 10, Windows 11 and Windows Server.

x64
Expand-Archive notfi-tunnel-win-x64.zip
.\notfi-tunnel-win-x64\notfi-tunnel.exe login

macOS

Apple silicon Macs. Downloaded in a browser? Clear the quarantine flag first.

tar -xzf notfi-tunnel-osx-arm64.tar.gz
cd notfi-tunnel-osx-arm64
xattr -d com.apple.quarantine notfi-tunnel
./notfi-tunnel login

Linux

Ubuntu, Debian, Fedora, RHEL, Raspberry Pi OS and other glibc distributions.

tar -xzf notfi-tunnel-linux-x64.tar.gz
sudo sh notfi-tunnel-linux-x64/install.sh

On Linux the installer asks whether to set up the client or a device agent, then asks for your token (and, for an agent, which services it may open) and does the rest.

06 · Devices

Reach devices only when you need to

Run the client as an agent on a device. It holds one outbound connection and sends a 4-byte keepalive every minute, nothing more. Open a service from the dashboard, pick how long, and the device opens that tunnel right away. It closes again on its own.

  • The device decides which services can ever be opened.
  • Only the device's owner and admins can open them.
  • Devices use your account's token; replace it and every device is out at once.
  • Runs as a background service on x64 and ARM Linux.
notfi-tunnel agent \
  --service tcp:22 \
  --service http:8080 \
  --name gateway-01

Device 'gateway-01' registered as 'alice', offering
  tcp-22 (tcp localhost:22),
  http-8080 (http localhost:8080).
Keepalive every 60s.
Opening 'tcp-22' for alice, closes at 14:30

07 · Languages

Tunnels inside your app

Client libraries run the same engine as the CLI inside your process. There's no process to spawn and no output to parse: you get the URL back and an event for every request.

Available dotnet add package Notfi.Tunnels.Client

await using var tunnel = await NotfiTunnel.StartHttpAsync(5000,
    new NotfiTunnelOptions { Token = token });

Console.WriteLine(tunnel.PublicUrl);

tunnel.RequestCompleted += (_, r) =>
    Console.WriteLine($"{r.Method} {r.Path} → {r.Status}");