Endpoints
Identify the Linux machines, tunnel subnets, peer relationships, and applications that will use the Atlas interface.
Getting started
From two Atlas nodes to a verified traversal path.
Early-access onboarding combines node installation, cryptographic enrollment, relay discovery, real-network testing, and an explicit traffic policy.
Before installation
Define the two ends and every path underneath them.
Onboarding is faster when the intended peer topology and access networks are known before software reaches the field.
Bearers
List cellular modems, carriers, wired access, satellite, radio, Wi-Fi, or mesh links and which failures they share.
Policy
Decide whether the deployment values best delivery time, aggregation, duplication, strict priority, or a combination by traffic class.
Onboarding sequence
Five steps to an observable path set.
Exact package and configuration commands are supplied during early-access onboarding rather than published here without deployment context.
Install
Install the Nexus Atlas node software on the machines at both ends.
Claim
Create a one-time console code and let the node prove possession of its X25519 key.
Discover
Fetch and verify the signed relay map or apply organization-only relay identities.
Measure
Classify real NAT behaviour and confirm direct, punched, and relay path health.
Operate
Apply scheduler policy, observe the topology, and exercise the expected degraded modes.
Control boundary
The console owns enrollment. The nodes own the tunnel.
Loss of the customer interface should not become loss of the data plane.
| Responsibility | Console / control plane | Atlas nodes |
|---|---|---|
| Ownership | Organizations, projects, enrollment, authorized views | Possession of private node identity |
| Discovery | Publishes signed public relay inventory | Verifies and caches the last good map |
| Reachability | Shows supported operational metadata | Maintains outbound relay sessions and direct attempts |
| Data traffic | Does not carry the Atlas tunnel payload | Encrypts, measures, schedules, sends, and receives packets |
Early-access expectation. Installation and first-path verification are guided today. This page describes the intended stable journey; production package repositories and exact commands will be published when their support contract is ready.