Pilot program

Validate Traversal on the networks you actually operate.

Early access is organized around bounded pilot deployments. We define the topology, instrument the paths, exercise real failure modes, and decide together whether the service fits the wider rollout.

Direct engineering contactReal carriers and sitesReviewable outcomes
Good pilot candidates

A concrete reachability problem beats a generic product trial.

The strongest pilots have identifiable endpoints, known access networks, and an operational reason to compare direct, relayed, and multi-bearer behaviour.

01

Named topology

You know what must connect: vehicles and command, sites and offices, or another bounded Atlas peer set.

02

Real constraints

CGNAT, third-party firewalls, changing addresses, latency, sovereignty, or relay-placement requirements are understood.

03

Observable outcome

We can agree what success means: reachability, path continuity, measured failover, policy behaviour, or operator visibility.

Pilot shape

Four stages, each with a decision.

The process is deliberately small enough to learn quickly and explicit enough to avoid an endless proof of concept.

01 · Discover

Map the deployment

Endpoints, access networks, traffic, security boundaries, and failure modes.

02 · Prepare

Configure the path set

Public or private relays, direct discovery, bearer inventory, and scheduler policy.

03 · Exercise

Run controlled scenarios

Carrier NAT, roaming, path loss, relay withdrawal, and expected degraded behaviour.

04 · Review

Decide what follows

Document results, gaps, operating model, and whether to expand, revise, or stop.

Working agreement

What each side brings.

A pilot works when product access is matched by operational access and honest feedback.

Nexus Atlas provides

  • Traversal and relay-network onboarding
  • Direct engineering contact during the pilot
  • Public, private, or hybrid topology guidance
  • Path and relay metadata for review
  • Documented findings and next-step recommendation

The pilot partner provides

  • Real endpoint and network requirements
  • Authorized access to the test environment
  • A technical and operational point of contact
  • Time to exercise agreed failure scenarios
  • Clear feedback on gaps and rollout constraints
Commercial note. Early-access scope and pricing are discussed during onboarding. A pilot is not represented as a production SLA, certification, or commitment to a general-availability date.
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.