How nfltr Works

Draft

This page is a draft for review.

nfltr connects machines you own through a relay: the hosted one at nfltr.xyz, or your own relay (beta). This page explains the parts, the flow of one connection, what the relay can and cannot see, and the limits today. Agent orchestration (nfltr-orch) is not part of nfltr and is not publicly available.


The parts

The flow of one connection

  1. Enrol. Each machine enrols once and keeps its certificate (Getting Started).
  2. Serve. A machine serves a local service through the relay, for example nfltr cat serve or a service in an nfltr up file.
  3. Connect. Another machine of the account connects by machine and service name, for example nfltr cat pipe; a browser opens a share link from nfltr http or nfltr up.
  4. Carry. The relay forwards the bytes between the two ends. It routes only inside one account, unless a group rule allows more (Organisations).

What the relay can and cannot see

Always visible to the relay: your account, machine names, which machine connects to which and when, and the size and timing of traffic. It holds no machine key: each machine's key is made on it and never leaves it.

FeatureWhat the relay sees
nfltr cat with --allow-group (cat pipe, cat cp, cat forward, cat serve --exec)Encrypted end to end between the two machines of your organisation (TLS with their machine certificates). The relay sees the two machines, the service, and sizes and timing; not the bytes, file names or commands.
nfltr http (tunnels and their share links)Encrypted end to end by default: TLS ends on your machine. Readable at the relay only in inspectable mode (--mode inspectable), which features that read requests at the relay need, such as routes.
nfltr cat serve (raw TCP tunnels, without --allow-group)Readable at the relay, unless the protocol inside is encrypted (SSH is).

Where it runs

Limits today

Next