Frequently asked questions
Short answers about nfltr on nfltr.xyz, each with a link to the page that explains it in full.
- What is nfltr?
- Who is it for, and when don't I need it?
- How is it different from SSH, Tailscale, ZeroTier or NetBird?
- Can I run the relay on my own network?
- Does my data go through nfltr.xyz? What can the relay see?
- What happens if the relay goes down?
- Which platforms are supported?
- Is nfltr open source?
- What does it cost?
- How is the download verified?
- How do I give feedback or report a problem?
- Where do I start?
What is nfltr?
nfltr connects services on machines that have no public address or open port. Every machine connects out to a relay (nfltr.xyz, or your own in beta), and the relay connects them inside one account. nfltr http and nfltr share give a link to a local app, file or command output; nfltr cat moves messages and files between your machines and carries TCP and SSH; nfltr up publishes services that clients reach on a local port; mailboxes take messages and webhooks over plain HTTP.
More: When to use NFLTR
Who is it for, and when don't I need it?
It is for reaching a service on another network without opening a port, running a certificate authority or adding a VPN route: a database at home, an API in staging, a shell on a machine behind NAT, a dev server a reviewer should see. If both ends are already on one network, or a VPN you already run reaches the machine, you do not need it. A site that must stay up while your machine is off belongs on a static host or CDN.
More: When to use NFLTR
How is it different from SSH, Tailscale, ZeroTier or NetBird?
Those join machines into one network; nfltr connects named machines and services through a relay, so no machine needs an inbound port or a route to the others, and groups decide which machines reach which. For one developer with a few machines a VPN already reaches, that VPN is simpler. SSH works with nfltr: nfltr cat ssh, or nfltr cat pipe as ssh's ProxyCommand, reaches a machine behind NAT, encrypted end to end. If your machines already share a private network, you can run the nfltr relay on it.
More: SSH to a machine behind NAT · Run your own relay (beta)
Can I run the relay on my own network?
Yes, in beta: nfltr relay serve runs the relay on a Linux VM or machine of yours, with your TLS certificate or a self-signed one your machines pin, and nfltr config set-relay points each machine at it. nfltr cat (messages, files, TCP and SSH tunnels) and nfltr up work on it, with each machine enrolled by a single-use code, and so do share links on a domain of yours (--share-domain) with a wildcard certificate on the machine that shares. Not in the beta: the dashboard, Postgres or Redis, automatic (ACME) certificates and failover (it is one process on one machine). With your own relay, nfltr contacts nothing but that relay on its own; any STUN or TURN server you name is contacted because you set it up.
Does my data go through nfltr.xyz? What can the relay see?
nfltr cat sessions between machines of your organisation are end-to-end encrypted, and so are services published with e2ee: true and a pin. Share links from nfltr http and nfltr share are encrypted end to end on nfltr.xyz: your machine holds their TLS certificate. Mailbox bodies are sealed to your key. The relay can read the signed-in tunnel address (/browse/...), tunnels started with --allow-path or --e2ee=false, and raw TCP tunnels unless the protocol inside is encrypted (SSH is). It always sees metadata: which machines connect to which, when, and how much data flows.
What happens if the relay goes down?
Traffic that goes through it stops until it is back, and then your machines reconnect by themselves. Keep your provider's console or SSH for emergency access. nfltr.xyz runs on one VM, so a deploy briefly interrupts it; clients ride out the gap for up to 2 minutes.
Which platforms are supported?
nfltr runs on macOS and Linux, amd64 and arm64, and in containers. The install page also has Windows builds of the CLI.
More: Getting Started · Install
Is nfltr open source?
No, nfltr is closed source. The relay you can run on your own network is the same closed-source nfltr binary you install on your machines.
What does it cost?
nfltr is free until further notice; prices are not set yet, and we will announce any change before it applies. When charging starts, it is prepaid: an account buys credit first and its use draws the credit down.
More: Pricing
How is the download verified?
Releases are signed. The install script checks the signature on the release's SHA256SUMS file and the binary's SHA-256 against it, and refuses the binary on a missing or bad signature or a mismatch; nfltr update --apply checks the signature and checksum itself. The release public key is in the install script, https://nfltr.xyz/install.sh. On Windows, compare the binary with certutil -hashfile against the signed SHA256SUMS in its release folder.
More: Install
How do I give feedback or report a problem?
Write to us on the contact page: feedback, a bug, a question, or what you ran nfltr on. A person reads every message; leave your email if you want a reply.
More: Contact
Where do I start?
Start with Getting Started: install the CLI, enrol the machine with nfltr config login, then share a local service with nfltr http 8080, which prints a share URL.
More: Getting Started · CLI reference