Edge UASCAPABILITY OVERVIEW

EXPEDITIONARY AUTONOMY

Built
forward.

Printed at the edge.
Commanded by AI.

Illustrative EDGE-1 quad-multirotor artwork
EDGE-1 / MULTIROLE UAS

Modular aircraft. Forward manufacturing. Operator-supervised mission coordination.

01 / BUILD

FORGE

Expeditionary additive manufacturing for structural parts. Controlled files, materials, process records, and inspection support repair and replenishment near the point of need.

02 / ADAPT

EDGE-1

A modular small-UAS platform with interchangeable mission payloads. Installed payload, radio, battery, and operating conditions define each configuration.

03 / COORDINATE

OVERWATCH

Mission software and an operator-supervised coordination approach. Flight safety, pilot authority, and approved recovery behavior remain configuration-specific.

One platform. Connected missions.SENSE / JAM / STRIKE / RESUPPLY / REACH ↗

Mission films illustrate possible workflows; they are not flight-test evidence.

Edge UASCONFIGURE / CONNECT

02 / MISSION-PAYLOAD PROFILES

Match the platform
to the requirement.

ModuleWeightEnduranceRadiusSwap
PL-01 / EO/IR observation1.8 lb48 min15 km90 sec
PL-02 / Medical resupply4.0 lb34 min10 km60 sec
PL-03 / RF sensing1.2 lb52 min18 km90 sec
PL-04 / Communications relay1.5 lb50 min20 km60 sec
PL-05 / General-purpose cargo4.4 lb31 min8 km45 sec

Representative figures published by EdgeUAS, not independently measured results. These are not specifications for the proposed lightweight EO kit or relay evaluation package. Request configuration-specific evidence before evaluation.

Connect the information.

EDGE-1 Relay

A proposed unarmed relay package combines an aircraft, selected communications payload, local gateway, and network-health display. The gateway is the intended mission-data endpoint.

Expression / VOR

A separate proposed observation workflow brings permitted aircraft status and source-linked reports into a human-reviewed workspace. VOR does not issue aircraft flight commands.

Pilot authority and aircraft safety remain separate from mission-data services. Interfaces and integrated performance require configuration-specific acceptance.