Developer
For evaluation, personal projects and small robot labs.
- Direct P2P networking
- Stable Netflux IPs
- Device authorization
- Basic connection status
- Community / evaluation use
Netflux gives robots, operator stations, edge computers and AI systems a stable private network across Wi‑Fi, 5G, Starlink and the public Internet — then adds live path intelligence, device health, diagnostics and fleet operations on top.
A conventional private network answers “can these devices reach each other?” Netflux is designed to also answer “how healthy is the connection, why did it change, what is the machine doing, and what should the operator do next?”
Every device receives a stable Netflux identity and private IP that follows it across changing local networks and Internet connections.
Probe eligible IPv4 and IPv6 candidates, establish encrypted peer-to-peer paths and prefer the best stable direct route.
Click any machine to inspect health, peers, path quality, interfaces, traffic, system state, security and event history.
Measure latency, jitter, loss, NAT traversal and path stability instead of treating “online” as the only health signal.
New users and devices remain controlled. Network owners explicitly authorize machines before peer access is granted.
Netflux is evolving toward ROS 2, DDS and edge-compute awareness so networking problems can be diagnosed in machine context.
Netflux turns each machine into an observable network endpoint. Operators can see what path is being used, how well it is performing and how that changes over time.
Netflux keeps the simplicity of a private overlay network, but moves the product center of gravity toward operational visibility, path quality and machine diagnostics.
Netflux is not positioned as a clone of any specific VPN product. The differentiation is the operational layer built around distributed machines and robotics.
For robots and edge AI, network connectivity is only part of the problem. Netflux is being designed to correlate network health with the software stack running on the machine.
Surface ROS distribution, domain ID and middleware context, with future diagnostics for interface-selection and discovery failures.
Understand Jetson, Linux and operator-computer connectivity without forcing teams to stitch together multiple observability tools.
Move from “the VPN is connected” to specific findings such as path degradation, interface changes or middleware binding problems.
Private addressing and direct connectivity across sites, customer networks and mobile Internet.
Keep operator stations connected to machines while continuously measuring connection quality.
Connect developers, test rigs and edge systems without exposing them directly to the Internet.
Manage connectivity for cameras, gateways, GPUs and autonomous equipment deployed outside the office.
Create a Network ID in the Netflux console. Netflux assigns the private subnet automatically.
Use the Mac installer or Linux package, or install directly from the command line.
Run netflux join nfx_…. Identity, addressing and the background agent are configured automatically.
Approve the device in the console, then inspect direct-path health and machine telemetry.
Invite the people who need to operate your fleet. Pay for the devices Netflux connects and manages. Direct peer-to-peer traffic does not pass through the Netflux cloud when a direct path is available.
For evaluation, personal projects and small robot labs.
Private machine connectivity for production edge deployments.
Full network and machine intelligence for physical-AI operations.
Volume deployments, OEMs and fleets requiring dedicated controls or support.
Draft launch pricing. Relay bandwidth, if introduced for networks where direct P2P is impossible, will be metered separately so normal direct traffic stays economical.
Netflux separates user access from device authorization and keeps control-plane identity distinct from the peer data path.
Install Netflux, join a Network ID and authorize the machine from the console.