Netflux connects a remote operator to a machine over a direct encrypted path, holds a latency budget tight enough to steer by, and keeps a record of who had control. Built for fleets that work behind satellite links, cellular modems and carrier NAT.
Agents keep their last working configuration and stay connected when the coordinator is unreachable. A ship can be offline for a week and its machines remain reachable from the bridge. Nothing tears down because a control plane blinked.
A Netflux ID names a network and is safe to publish. Joining takes a separate code that is eight characters, expires, and can be capped to one machine. Hand a technician a code for today without giving away anything permanent.
Every peer is scoped to a single address. A machine talks to its gateway and to an authorized operator, never to the machine beside it, so one compromised unit does not become a path to the rest.
Every piloting session is written down: which operator, which machines, for how long, over which path. When something is damaged, the question of who had control has an answer.
Netflux measures how each endpoint's network translates addresses and picks a strategy from that. Two hard cases go straight to a relay instead of spending a pilot's time on a connection attempt that was never going to succeed.
Install the agent, then run the join code. Someone approves the machine and its address is assigned.
# on the machine
netflux-cli join NFX-7K2M-9QRT
waiting for approval on 06G8228RDRFM8M21887TV58K88
machine AN566388MAT7K7Z40BBAKDCJ7R
Create an organization