Ground station 01Base Alpha
atlas0UP
fiber0 8 msvsat0 612 ms
Choose platform
Multipath infrastructure for Linux
Keep sites connected across changing paths.
Run Nexus Atlas on Linux nodes, gateways, or servers. Bring fiber, cellular, satellite, and other IP-capable transports into one encrypted connection while Atlas measures and adapts underneath your workloads.
Live multipath topology2 ground · 1 air · 5 paths
VSATKu-band
Ground station 02Forward Bravo
atlas0UP
mesh0 21 mswwan0 47 ms
Air node 07UAV Raven
atlas0LINKED
meshVSAT5G
TerrestrialSatelliteMeshCellular
Connection bonding for Linux and Android
Stay connected when one network can’t.
Nexus Atlas combines the connections available to your device into one encrypted path. Wi-Fi drops, mobile networks change, links become congested—your applications keep using the same connection while Atlas adapts underneath them.
Wi-Fi18 ms
5G42 ms
Ethernet12 ms
Nexus AtlasConnected3 links
Ethernet12 ms
Wi-Fi18 ms
CellularStandby
One encrypted
connection
connection
The gap
Your device has several ways to connect. Most software still uses them one at a time.
Failover happens too late
A call, stream, or remote session drops before the backup link takes over.
Conditions are not binary
A connection becomes slow and lossy long before it disappears.
Mobile networks are hard to reach
CGNAT and changing carrier addresses make direct connectivity unreliable.
How it works
Several links. One connection.
Applications see a normal network interface. Atlas handles the changing paths underneath it.
Choose where to connect
Use your own Nexus Atlas node or select supported managed infrastructure.
Bring every usable path
On an atlasd Linux node or Android device, combine the IP-capable paths available—from Wi-Fi and cellular to Ethernet, mesh radio, and satellite.
Let Atlas measure and adapt
Atlas monitors delay, loss, jitter and availability, then applies the policy you choose.
Inside the Linux app
A quick tour of Nexus Atlas.
Explore the Linux control surface—from live link health and routing to topology inspection and a short spatial path visualization.
App gallery
View01/ 05
Operations
Watch every link from one operational view.
Compare status, latency, RTT, jitter, loss, quality, and scheduling contribution across every transport attached to the Linux node.
Switch galleryContinue with Nexus Atlas on Android.
12-second topology playback
Screens and video from the current Linux development build. Details may evolve before public release.
Built for change
The connection stays familiar. Everything beneath it can move.
Wi-FiCellularEthernetATLAS
Keeps alternatives ready
Atlas continuously measures available paths instead of waiting for the active one to fail.
One stable interface
Your applications keep using a normal encrypted network connection. No application integration is required.
Your infrastructure is welcome
Terminate on your own Linux node, use managed services, or combine both approaches.
Encrypted by default
Traffic is authenticated and encrypted between the Nexus Atlas endpoints you select.
Downloads
Get Nexus Atlas.
Public signed release packages are being prepared. Request an evaluation build for Linux or Android.
Desktop · server · edge
Linux
Run Atlas on a workstation, gateway, server, vehicle computer, or edge device.
- Current channel
- Evaluation
- Architectures
- x86-64 · ARM64
- Deployment
- Binary · systemd
Mobile
Android
Bond Wi-Fi, mobile connectivity, and other connections, from the device you already carry.
- Current channel
- Evaluation
- Minimum
- Android 10
- Architecture
- ARM64
Roadmap
Another platform?
Tell us which operating system, hardware, and deployment shape you need.
Request a platformYour route, your choice
Choose where your connection ends.
Managed connectivity is an option, not a hidden dependency. Use Atlas on infrastructure you control, use Nexus Atlas services for simpler onboarding, or keep both paths available.
Where it fits
Built for moments when one link is not enough.
Choose Linux for infrastructure and operational deployments, or Android for resilient connectivity on the phone you carry.
Use cases
01Nodes · gateways · servers
Run atlasd where the network meets
Deploy the Linux daemon on x86-64 or ARM64 workstations, gateways, servers, vehicle computers, and edge devices.
What Linux providesA stable encrypted interface for existing applications, without application-specific integration.
02Fiber · cellular · satcom
Combine unlike IP transports
Bring Ethernet, fiber, 4G/5G, satellite, mesh, radio, or other IP-capable bearers available to the node.
What Atlas doesMeasures delay, loss, jitter, and availability, then schedules traffic using the policy you choose.
03Field · sovereign · offline
Operate on your own infrastructure
Connect sites, devices, vehicles, and edge systems while retaining control of the Linux endpoints and data path.
Deployment choiceSelf-hosted operation is first-class; managed discovery and relays remain optional when reachability needs them.
01Calls · streams · browsing
Move between Wi-Fi and cellular
Keep the same application connection as signal quality changes at home, at work, or on the move.
Atlas responseMeasures available paths and shifts traffic before a weak link breaks the session.
02Everyday apps · no plug-ins
Keep the apps you already use
Android applications use one normal encrypted network interface while Atlas handles changing connections underneath.
On the phoneNo per-app Nexus Atlas integration is required; supported traffic uses the same system VPN interface.
03Your node · managed gateway
Choose where the connection ends
Pair the app with a Linux node you control or use supported managed infrastructure when simpler reachability is useful.
Deployment choiceUse a self-hosted endpoint, managed traversal, or both—without making the managed path mandatory.
Good to know
Straight answers.
Nexus Atlas is connection bonding first. We keep platform limits and product boundaries explicit.
Is Nexus Atlas a conventional privacy VPN?+
Its primary purpose is resilient connectivity and connection bonding, not changing your apparent location—although a full-tunnel exit through a hosted Nexus Atlas gateway, or through an exit node you operate yourself, does exactly that. (Relays are different: they only forward encrypted frames between your own nodes and provide no internet exit.)
Can I use my own server?+
Yes. Self-hosted Atlas endpoints are a first-class deployment option.
Does Android combine two SIM cards?+
Consumer Android devices generally cannot keep two cellular data sessions active simultaneously. Atlas can combine Wi-Fi and cellular, or use another phone or router as an additional link.
Can it run beside another Android VPN?+
Android allows one active VPN per user profile, so Atlas cannot normally run beside another VPN in the same profile.
What is Nexus Atlas.NET?+
It is the optional traversal and relay suite that helps Atlas endpoints connect through CGNAT and changing carrier networks.
Do my applications need to support Nexus Atlas?+
No. Applications use a normal network interface while Atlas manages the available connections underneath.
Explore Nexus Atlas
One product family. A clear place for every question.
nexusatlas.euBusiness
Deployment, procurement, pilots, and partnerships.
nexusatlas.ioEngineeringArchitecture, technical evidence, and product depth.
nexusatlas.devDevelopersDocumentation, configuration and API reference, evaluation access.
nexusatlas.netTraversalCGNAT traversal, relays, and managed reachability.
console.nexusatlas.netTraversal ConsoleManage organizations, projects, node enrollment, status, alerts, and audit.
nexusatlas.appDownloads — you are hereUnderstand the app, choose a platform, and install it.