Skip to content

Choose a deployment

One AryaOS image runs every mission. You pick a device role in the web console. AryaOS turns on exactly the sensor pipelines that role needs - no reflashing, no reconfiguring.

The mission-based model

AryaOS is an all-in-one situational-awareness gateway. It decodes sensors at the edge and delivers a Common Operating Picture (COP) to ATAK, WinTAK, and iTAK over Cursor on Target (CoT). Every AryaOS device runs the same software. You select its mission at runtime.

The core services always run: the COTBridge hub, LINCOT host beacon, GPSCOT network GPS, and gpsd. The selected role controls the sensor pipelines. You can switch roles in the field.

Where the role lives

The role is stored as ARYAOS_ROLE in the site config (/etc/aryaos/aryaos-config.txt) and applied by the aryaos-role helper. You set it from the Device role card in Cockpit > AryaOS Site. See Device roles for the full reference.

Pick your scenario

  • Aircraft (ADS-B / UAT)

    Track crewed aircraft on 1090 MHz and 978 MHz with an SDR and antenna.

    Air - ADS-B & UAT

  • Vessels (AIS)

    Put ships and boats on the map from marine AIS, over the air or from an online feed.

    Maritime - AIS

  • Drones (Counter-UAS)

    Detect and track drones via Remote ID and DJI DroneID for C-UAS awareness.

    Counter-UAS

  • Own position

    Beacon the box's own GPS position to TAK and feed network GPS to your EUD.

    Own position / GPS

  • Everything at once

    Fuse air, maritime, and drone tracks into one COP on a single device.

    Multi-sensor

  • CoT router only

    Run a box purely as a COTBridge relay between networks and TAK Servers.

    Relay / routing

  • Forward to a TAK Server

    Push the picture upstream via a data package or tak:// enrollment URL.

    Connect a TAK Server

  • Display in ForeFlight

    Show the TAK air picture in ForeFlight, FlyQ, or Garmin Pilot via GDL90.

    ForeFlight / GDL90

  • :material-backpack: Fully offline

    Disconnected backpack ops with a Wi-Fi hotspot and Bluetooth PAN.

    Offline backpack

Role summary

Each role maps to a set of sensor units, which in turn dictate the hardware you attach.

Role Sensor pipelines enabled Typical hardware
multi ADS-B + UAT, AIS, and drone detection - all pipelines 2x RTL-SDR (1090 + 978), AIS SDR, drone-detection SDR/receiver, GPS
air ADS-B decoder (readsb/dump1090-fa), dump978-fa, adsbcot, gdlcot RTL-SDR + 1090 MHz antenna. optional 2nd SDR + 978 MHz antenna
maritime ais-catcher, aiscot RTL-SDR + marine VHF antenna (or an online AIS feed, no SDR)
cuas dronecot-dji, other dronecot-*, sikw00fcot Remote ID receiver and/or DJI DroneID SDR (e.g. AntSDR)
relay none - CoT routing only No sensors. just network (Wi-Fi/Ethernet/MANET)

The core always runs

Regardless of role, cotbridge, lincot, gpscot, and gpsd stay running. So a relay box still beacons its own position and forwards CoT. Every role can share GPS with a connected EUD.

The air role also enables gdlcot, which lets ForeFlight and other EFB apps display the air picture over GDL90.

How the picture flows

flowchart LR
    subgraph Sensors["Sensor pipelines (role-selected)"]
        A[adsbcot / dump978] 
        M[aiscot / ais-catcher]
        D[dronecot / sikw00fcot]
    end
    C[LINCOT + GPSCOT<br/>own position]
    A & M & D & C -->|udp+wo://127.0.0.1:28087| H[COTBridge hub]
    H --> O[site-output]
    O -->|default: Mesh SA<br/>udp+wo://239.2.3.1:6969| E[ATAK / WinTAK / iTAK]
    O -.->|or: TLS| S[TAK Server]

Local feeders publish CoT to the COTBridge hub on udp+wo://127.0.0.1:28087. COTBridge owns egress. Its site-wide output multicasts to the Mesh SA group udp+wo://239.2.3.1:6969 by default (which your EUD picks up automatically) and can instead point at a TAK Server. Advanced COTBridge lanes remain available for specialized routing.

Next steps