Use case · Mobile fleets

Let vehicles keep their identities while networks keep changing.

A fleet vehicle may change cell towers, private addresses, carriers, and access technology throughout one route. Atlas anchors communication in cryptographic identity and treats every reachable route as measured inventory.

Vehicle ↔ commandVehicle ↔ vehicleMulti-carrier
The mobility problem

An internet connection is not the same as a reachable vehicle.

Carrier NAT permits the vehicle to initiate traffic but usually prevents another endpoint from dialing back. Address changes make static tunnels brittle even when inbound reachability exists briefly.

01

Changing attachment

Tower and carrier transitions can replace the outer address without changing the vehicle’s Atlas identity.

02

Shared addressing

CGNAT means many subscribers share public addresses and inbound rules are outside the fleet operator’s control.

03

Correlated paths

Direct and relayed routes over one modem improve reachability but still share the same underlying radio failure.

Along the route

The secure tunnel stays boring while path availability changes.

Atlas applications continue to use the same interface and peer identities as the vehicle moves.

01

Depart

Relay sessions establish through outbound cellular connectivity.

02

Discover

A direct carrier path appears where current NAT policy permits it.

03

Roam

Authenticated packets adopt the vehicle’s valid new outer address.

04

Degrade

Measurements move traffic away from a weak or disappearing path.

05

Recover

Reappearing paths rejoin the scheduler without rebuilding the tunnel.

Fleet patterns

One service, several connectivity shapes.

Traversal supports the reachability layer; the wider Atlas configuration defines which peers, routes, and traffic policies each fleet needs.

Hub and spoke

Vehicle to operations

Every vehicle reaches one or more command sites through public, private, or hybrid relay estates.

Peer capable

Vehicle to vehicle

Peers can rendezvous through relays and add direct connectivity where carrier policy allows it.

Mobile edge

Vehicle as a local gateway

Devices behind the onboard Atlas node use the tunnel without each device needing traversal awareness.

Physical diversity matters. Multiple relay paths over one cellular modem provide route resilience, not a second radio. Carrier, modem, satellite, Wi-Fi, or wired diversity is what protects against loss of the underlying bearer.
Get early access

Bring us the network you cannot control.

Apply as a pilot partner if you have a deployment ready to test, or start evaluating Nexus Atlas Traversal as a future customer. Tell us enough to understand the endpoints, carriers, regions, and operational constraints involved.

01

Pilot partner

Run an early deployment with direct engineering contact and help shape priorities through real-world feedback.

02

Customer evaluation

Research architecture, security, deployment options, and commercial fit before committing to a pilot.

Already enrolled? Open the console
Early-access applicationUsually answered by the product team

Your application is sent to the Nexus Atlas product team. You can also email office@nexusatlas.io.