The platform is autonomous. The link shouldn’t be the weak point.

Dual radio plus cellular across a changing route.

In covered areas cellular dominates; in open country the dedicated radio carries; the scheduler’s continuous scoring shifts the mix without a switchover event. Where the aircraft is reached both directly and through a relay, its commands take whichever path has room instead of queuing behind the video. The triplex pattern in the playbook

Where both ends run Atlas, the telemetry radio carries Atlas directly — no PPP, no IP plan per radio pair, about 29 bytes less on every voice packet — and writes are paced on the radio’s own buffer, so a command or a voice frame overtakes video in Atlas’s queue instead of waiting behind it in the radio’s: voice stays usable beside video on a 64 kbit/s radio. Atlas directly on serial radios

Across the dead zones, through each other.

Vehicles bond Wi-Fi and mesh and relay for each other — a shadowed vehicle reaches the controller through a neighbour instead of stopping.

The data comes home by itself.

Store-carry-forward holds the day’s data through coverage gaps and drains it — at full bonded throughput — the moment the vehicle re-enters range or passes another node.

The same holds for video. The live feed bends to the link and drops late frames; the vehicle keeps every packet, the ground asks for exactly what it missed, and the missing pieces come home on the lowest-priority lane, behind commands and live video, during the run or after it. Only the gaps cross, never the whole recording again. How the gaps are filled

The hill is on the map. The handover is early.

A UAV runs toward rising terrain carrying a fat 5 GHz link and a thin long-range radio. Projected geometry and the elevation data loaded on the node raise the short link’s risk while it still carries, and if the aircraft drops behind the crest the route moves through a relay that still sees it within about half a second, because the aircraft shares each new position as it flies; video thins toward the long link, and by the time the ridge cuts the beam, nothing is left on it to lose. With two cameras aboard, the primary feed outranks the thermal one inside the video lane, so when the long link cannot carry both, the thermal camera gives way first. The mechanics, with a live simulation The ridge, on the engineering site

Your ground station, their drones.

A customer’s fleet already runs its own network. Your control station joins it as a member under the customer’s rules and bridges it to your own: your operators reach the aircraft the customer chose to share, at addresses of your network, with nothing changed on board. The customer sees none of your topology and can revoke your station like any member. Opt-in. How the seam works

A customer who must only watch the mission gets a link, not a seat in your network: the feed gateway — a separate package beside Nexus Atlas — sends one feed outward from a read-only member to a feed server; the customer opens it in a browser with a token for that feed, until it expires or is cut with one click, and the player draws the viewer’s name across the picture. Your fleet opens no port, and nothing travels inward. How the gateway works

Preinstalled on the aircraft, operated from a web ground station.

The aircraft ships with Atlas in its companion image and two or three cellular modems. It dials out over every modem to two hubs in front of the ground station’s backend; commands ride the two best modems at once, video is paced behind them, and a removed aircraft is refused everywhere within seconds. A new aircraft joins from a pairing code the ground station shows, or by a certificate signed at the factory. When the hub that admits it cannot sign the fleet’s list, it hands the new aircraft to one that can, and the rest of the fleet knows it from the signed list about a second later. Each customer is a network of its own. Shipped. The pattern, for platform makers The reference architecture — nexusatlas.io

A push never strands an aircraft.

A fleet update that half the fleet took is the one you find out about in the air. Every aircraft record carries an update class: a release is complete only when each required aircraft has confirmed it; one silent or failed at the deadline withdraws the change on its own — the previous settings go back out, signed — and the abort names the aircraft; best-effort aircraft take it when next seen and never hold anyone up. Keys and the shared secret rotate on the same kind of signed schedule, in windows an aircraft out of contact can still catch: one back after a week comes in on its old key, receives the new one over its first connection and switches by itself. The release gate Keys without a flag day