Scope
Regions, endpoints, sovereignty, isolation, latency, and availability goals.
Private networks
Your relay estate. Your boundary. The same Atlas paths.
Dedicated traversal nodes can run in an organization’s cloud, data centres, edge locations, or isolated operational zones without appearing in the public nexusatlas.net relay map.
Meaningfully private
Absent from public discovery—not merely hidden in the interface.
Authorized Atlas nodes receive the private addresses and relay identities through customer-controlled configuration. Public clients are never told those nodes exist.
Organization-controlled
- Relay placement and hosting account
- Addresses, DNS, and network ingress
- Which Atlas nodes receive the configuration
- Retention and operational access policy
- Maintenance and change windows
Excluded from the public estate
- No publication in the public signed map
- No appearance on the public live-network page
- No availability to unrelated Atlas users
- No dependency on public regional selection
- No requirement to expose application payloads
Deployment sequence
From requirements to a measured private path.
Private deployments start with operational boundaries and traffic needs, then define placement and redundancy.
Place
Customer cloud, on-premises, edge facility, or a managed dedicated environment.
Identify
Generate and pin the relay identities trusted by authorized Atlas nodes.
Verify
Test reachability from the real carriers and sites that will use the service.
Operate
Monitor health and combine private, public, and direct paths according to policy.
Model comparison
Hosted, private, or hybrid.
The right model depends on administrative control, geography, resilience, and the cost of operating infrastructure.
| Model | Discovery | Operations | Typical fit |
|---|---|---|---|
| Public hosted | Signed nexusatlas.net relay map | Nexus Atlas operated | Fast onboarding and geographic redundancy |
| Private cloud | Customer configuration only | Shared or customer-controlled | Cloud tenancy, data residency, controlled access |
| On-premises | Customer configuration only | Customer environment | Sovereign, disconnected, or tightly governed networks |
| Hybrid | Public map + private configuration | Split responsibility | Dedicated primary paths with public fallback diversity |
Discuss a private deployment
Start with the boundary you must preserve.
Tell us the locations, carriers, expected node count, hosting constraints, and whether public relays may be used as additional paths. We can turn those requirements into a pilot topology.