Connectivity infrastructure for physical AI

Connect, understand and operate machines anywhere.

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.

Direct-first. Stable private IPs. Explicit device approval. No manual port forwarding.
Test Fleet · nfx_c666…● Control plane live
Robot Master10.80.1.11 · UbuntuDirect · 72 ms
Operator Mac10.80.1.10 · macOSDirect · 74 ms
Jetson Edge10.80.1.12 · ARM64Authorized
GPU Node10.80.1.13 · LinuxOnline
Netflux
control plane
Direct P2P data pathCloud coordinates peers; machine traffic stays peer-to-peer whenever a direct path is available.
One-command enrollmentInstall once, then join a private network with netflux join nfx_….
Path intelligenceSee RTT, endpoint, path type, candidate paths, jitter, loss and connection history.
Built for machinesDesigned for robots, edge systems, operator stations and distributed physical-AI fleets.
The platform

More than an overlay network.

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?”

01

Private machine identity

Every device receives a stable Netflux identity and private IP that follows it across changing local networks and Internet connections.

02

Direct path selection

Probe eligible IPv4 and IPv6 candidates, establish encrypted peer-to-peer paths and prefer the best stable direct route.

03

Device Control Center

Click any machine to inspect health, peers, path quality, interfaces, traffic, system state, security and event history.

04

Connection diagnostics

Measure latency, jitter, loss, NAT traversal and path stability instead of treating “online” as the only health signal.

05

Operator approvals

New users and devices remain controlled. Network owners explicitly authorize machines before peer access is granted.

06

Robotics-aware networking

Netflux is evolving toward ROS 2, DDS and edge-compute awareness so networking problems can be diagnosed in machine context.

Device intelligence

Understand every connection, not just every IP.

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.

Connection Health scoreA single operational score based on latency, jitter, loss, path stability and reachability.
Path IntelligenceCurrent direct endpoint, candidate paths, path type, RTT and why the selected path is preferred.
Historical telemetryReview latency and path changes so intermittent field problems can be investigated after they happen.
Machine contextOS, architecture, interfaces, agent version, peer state and evolving robotics telemetry in one place.
master · Device Control Center● ONLINE
OverviewConnectivityPeersTrafficSystem
Health96
RTT72 ms
Jitter3 ms
Loss0.1%
Why Netflux is different

Built around operating physical machines, not only connecting endpoints.

Netflux keeps the simplicity of a private overlay network, but moves the product center of gravity toward operational visibility, path quality and machine diagnostics.

Capability
Generic overlay networking
Netflux
Stable private addressing
Encrypted direct peer connectivity
Explicit device authorization
Live path RTT visible per machine
Often limited
Core feature
Candidate-path visibility and scoring
Network-centric
Built in
Jitter, packet-loss and path history
Usually external tooling
Device Control Center
Machine diagnostics and event timeline
Usually external tooling
Built in
ROS / DDS / robotics context
Not the primary focus
Physical-AI roadmap
Operations workflow
Connect devices
Connect + understand + operate

Netflux is not positioned as a clone of any specific VPN product. The differentiation is the operational layer built around distributed machines and robotics.

Physical AI

Networking that understands the machines using it.

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.

R

ROS 2 / DDS awareness

Surface ROS distribution, domain ID and middleware context, with future diagnostics for interface-selection and discovery failures.

E

Edge-compute visibility

Understand Jetson, Linux and operator-computer connectivity without forcing teams to stitch together multiple observability tools.

A

Actionable diagnostics

Move from “the VPN is connected” to specific findings such as path degradation, interface changes or middleware binding problems.

Robot fleets

Private addressing and direct connectivity across sites, customer networks and mobile Internet.

Remote operations

Keep operator stations connected to machines while continuously measuring connection quality.

Distributed labs

Connect developers, test rigs and edge systems without exposing them directly to the Internet.

Industrial edge AI

Manage connectivity for cameras, gateways, GPUs and autonomous equipment deployed outside the office.

How it works

From zero to a private machine network in minutes.

STEP 01

Create a network

Create a Network ID in the Netflux console. Netflux assigns the private subnet automatically.

STEP 02

Install Netflux

Use the Mac installer or Linux package, or install directly from the command line.

STEP 03

Join the machine

Run netflux join nfx_…. Identity, addressing and the background agent are configured automatically.

STEP 04

Authorize and operate

Approve the device in the console, then inspect direct-path health and machine telemetry.

Pricing

Simple pricing based on machines, not seats.

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.

Developer

For evaluation, personal projects and small robot labs.

Free
Up to 5 devices
  • Direct P2P networking
  • Stable Netflux IPs
  • Device authorization
  • Basic connection status
  • Community / evaluation use
Start free

Connect

Private machine connectivity for production edge deployments.

$2 / device / month
$20/month minimum
  • Everything in Developer
  • Multiple private networks
  • User and device controls
  • Path and latency visibility
  • API access
Create account

Fleet & Enterprise

Volume deployments, OEMs and fleets requiring dedicated controls or support.

Custom
Volume device pricing
  • Volume discounts
  • SSO / enterprise identity
  • Audit & policy controls
  • Dedicated regions / deployment options
  • SLA and onboarding support
Talk to us

Draft launch pricing. Relay bandwidth, if introduced for networks where direct P2P is impossible, will be metered separately so normal direct traffic stays economical.

Security model

Private by default, explicit by design.

Netflux separates user access from device authorization and keeps control-plane identity distinct from the peer data path.

Identity & access

  • Explicit user approval by a Netflux superuser
  • Explicit per-device authorization within each network
  • Stable device identities and private addresses
  • Network ownership and role separation

Transport & operations

  • Direct-first peer-to-peer connectivity
  • Encrypted peer data plane
  • Cloud control plane used for coordination and authorization
  • Device revocation and evolving security posture controls
Public installer available

Build your first Netflux network.

Install Netflux, join a Network ID and authorize the machine from the console.

curl -fsSL https://install.net-flux.com | sudo sh
See pricingCreate account