Nexus Atlas developer portal

The integration surface of Atlas, documented.

Atlas bonds any combination of links — satellite, cellular, radio, Wi-Fi, mesh, wired — into one encrypted connection that survives link failure. This portal is where you make it run on your platform: the quickstart, every configuration key, the REST API, and the recipe for verifying that the binary you deploy is the binary we built.

Start the quickstart Configuration reference

Single binary, no controllerNo cloud dependencyRuns on compute you already own

node-a — the fifteen-minute outcome

$ atlasd status
nexus0  10.0.100.1/24  2 links alive  1 peer established
$ ping -i 0.2 10.0.100.2
64 bytes from 10.0.100.2: icmp_seq=41 time=1.9 ms
64 bytes from 10.0.100.2: icmp_seq=42 time=2.1 ms
#  ← primary uplink unplugged here
64 bytes from 10.0.100.2: icmp_seq=43 time=4.7 ms
64 bytes from 10.0.100.2: icmp_seq=44 time=4.4 ms
#  the connection never noticed

noise ik · x25519 · chacha20-poly1305seamless failover — no reconnect

Two kinds of pages

Public

The documentation

Quickstart, concepts, the full configuration and API reference, release verification. Readable by anyone — no account, ever.

Vetted

The evaluation set

Downloads with signatures and an evaluation licence, security deep-dives, field performance data, roadmap briefs. These pages are gated: they stay listed in the sidebar behind a lock, and until your organisation is approved they open at their abstract and contents list rather than the material itself.

Every page is one or the other, and the lock in the sidebar tells you which before you click. There is no third kind of content.

Three account states

Anonymous
Reads every public page in full, with no account. The locked pages open at their summary only.
Registered coming next
Gains capabilities, not content: request tracking, support, hardware-key sign-in, an audit log of your own access. An account on its own does not open a locked page.
Approved
The state that unlocks the vetted set — every locked page and download, granted per organisation and typically reviewed within a business day.

Until accounts ship, the access request is the front door — approval works with or without one.

Start here

Three doors in.

Most integrations follow the same path: prove a bonded tunnel on two machines, read the concepts that matter for your bearers, then wire the reference material into your own tooling.

15 minutes

Quickstart

Two Linux hosts, two links, one encrypted tunnel. Kill a link and watch the connection survive — the whole point, demonstrated on your own bench.

Run it Concepts

Understand the daemon

The core tunnel, link scheduling, mesh routing, NAT traversal, transport classes and telemetry — written for the engineer deciding how Atlas fits their system.

Read the concepts Reference

Configuration & API

Every key of config.toml with types and defaults, generated from the daemon's own schema — plus the REST API and CLI, documented endpoint by endpoint.

Open the reference Supply chain

Verify a release

Checksums, keyless signatures, SLSA provenance and SBOMs ship with every release. The verification recipe is public — run it before you trust a binary.

Verify Operations

Deploy it properly

The hardened systemd unit, an unprivileged service user with one capability, config validation, and the commit-confirmed apply lifecycle.

Deployment guide Evaluation

Request access

Downloads, the security documentation set and field performance data are granted per organisation. One form, one review, everything unlocked together.

Request access

The site network

One product, six destinations.

Each Nexus Atlas property answers a different question, so no audience wades through another audience's depth. You are on the developer portal — nexusatlas.io explains and convinces; this site enables: exact keys, exact commands, exact behavior, and the honest known-limitations page that tells you where the edges are.

nexusatlas.euBusiness

The case, the markets, the evidence and the engagement path — for decision makers.

nexusatlas.ioEngineering

Architecture, live demonstrations and technical evidence — for the advisor forming an opinion.

nexusatlas.devDevelopers — you are here

Quickstart, configuration and API reference, release verification, evaluation access.

nexusatlas.netTraversal

The managed reachability service: relay network, gateways, live network view.

console.nexusatlas.netOperations

Enrol nodes and run the estate: live map, per-link telemetry, alerts, audit.

nexusatlas.appDownloads

The applications: Linux and Android interface tours and evaluation builds.