Skip to content
    Collaborative Autonomy Ecosystem / Operator layer

    Arc-UI

    Command the mission.
    Not the menus.

    A field-ready replacement for QGroundControl and Mission Planner that unifies planning, live aircraft control, telemetry, video, and edge-AI detections in one mission-native surface.

    Follow the operator loop
    WEB / PWA
    Desktop + tablet
    ANDROID
    Field handheld
    PX4 / AP
    Current flight stacks
    MAVLINK
    Vehicle integration
    Operator loop / map-first command

    Command the mission.
    Not the menus.

    Arc-UI replaces the fragmented ground-control workflow with one field interface for intent, routes, live aircraft state, detections, and contingencies. It is designed for phone, tablet, and desktop operation in daylight, low light, and degraded networks.

    Arc-UI / operational flowOperational flow model
    1. 01

      Express

      Voice, map gesture, or direct control

    2. 02

      Validate

      Geofence, route, and vehicle checks

    3. 03

      Translate

      Safe mission actions over MAVLink

    4. 04

      Observe

      Telemetry, video, and detections

    5. 05

      Intervene

      Hold, return, redirect, or halt

    Interfaces / modes
    WFB / Wi-FiMeshLTE / 5GSATCOM via Arc stack
    Operational result
    One operator picture / mission-ready control

    Configuration note / Multi-vehicle, swarm, and bearer options are delivered according to the connected Arc system and program configuration.

    Plan → Execute → Sense → Decide

    One mission loop.
    One operating picture.

    Arc-UI keeps the operator’s intent, aircraft state, mission geometry, and sensor findings connected from briefing through recovery. High-level behaviors remain with the deployed flight stack; the interface makes them visible, deliberate, and controllable.

    1. 01 / 04
      Plan

      Build the mission picture

      Create the operation around what the team needs to accomplish—not around a stack of vehicle menus.

      • Routes and waypoints
      • Zones and hazards
      • Mission-specific targets
    2. 02 / 04
      Execute

      Move from intent to flight

      Load the operation, confirm the action, and follow live progress from map, split, or stream view.

      • Launch and route execution
      • Live vehicle telemetry
      • Hold, return, and land
    3. 03 / 04
      Sense

      Keep video and context together

      See the aircraft, feed, route, and target-aware detections in the same operating picture.

      • Live video and map
      • Edge-AI detections
      • Track and vision health
    4. 04 / 04
      Decide

      Act without losing the thread

      Review confidence, time, source, and location before redirecting the aircraft or changing the mission state.

      • MGRS and coordinates
      • Target-match filtering
      • Deliberate intervention
    Arc-UI / Live operationTelemetry active
    Arc-UI live operation view with telemetry, vehicle detections, mission map, and camera feed
    Field console / Mission-native

    The aircraft.
    The feed.
    The decision.

    Switch between spatial awareness and sensor detail without leaving the mission. Arc-UI preserves the same route, telemetry, target, and safety context across every view.

    Map

    Follow the aircraft, route, zones, hazards, detections, and mission marks in spatial context.

    Split

    Keep the live feed beside the map and resize the working surface around the task.

    Stream

    Bring video forward while retaining telemetry, map context, and target-aware overlays.

    Mission planning / Before launch

    Plan around intent.
    Load what matters.

    Package routes, waypoints, zones, hazards, targets, and planned guardrails into the operation. Review it as one mission artifact, then load the same context into the live operator view.

    Geometry

    Mark the ground

    WAYPOINTZONEHAZARDRALLY
    Mission flow

    Build reusable routes

    GOSCANORBITHOLDCOUNT
    Mission targets

    Define the signal

    • Action + priority
    • Confidence threshold
    • Operation-specific watchlist
    Communications / Program-configured PACE

    One mission context.
    Configured pathways.

    Arc-UI operates through the connected Arc communications stack. Programs can integrate the operator layer over selected mesh, LTE / 5G, and SATCOM bearers without changing the mission workflow.

    Bearer availability, selection, and failover behavior depend on deployed hardware and program configuration.

    Arc-UI / communications relationshipProgram configured
    Operator

    Arc-UI

    Mission intent, aircraft state, video, and detections.

    Deployed system

    Arc communications stack

    LINK STATEQUALITYBANDWIDTH
    Mesh
    LTE / 5G
    SATCOM
    Collaborative C2 / When enabled

    Multi-vehicle and swarm command-and-control functions are delivered according to the connected Arc system, authority model, and program configuration.

    Integration / Known interfaces

    Fit the field kit.
    Keep the operator flow.

    Arc-UI is configured around the vehicle, payload, communications plan, and mission authority selected for the deployment.

    Operator clients

    Web / PWA + Android

    Responsive layouts for desktop, tablet, and one-handed field use.

    Flight stacks

    PX4 + ArduPilot

    Current supported deployments; vehicle and payload fit are confirmed per program.

    Vehicle control

    MAVLink-backed

    High-level operator intent is handed to the connected Arc flight stack.

    Mission network

    Optional TAK / CoT

    Telemetry and detection output can be enabled for configured deployments.

    Operator safety / Designed in

    Fast to read.
    Hard to misread.

    Arc-UI is built around deliberate operator actions and aircraft-reported truth. It helps the operator understand what is connected, what is happening, and what the system accepted.

    01

    Truthful state

    Arc-UI follows aircraft-reported state and command acknowledgements instead of assuming an action succeeded.

    02

    Deliberate transitions

    Flight-critical actions use visible gates, confirmations, and clear readback before the operator moves on.

    03

    Human authority

    The operator can hold, return, redirect, land, or take deliberate manual control when the mission requires it.

    04

    Field continuity

    Offline map caching and on-device speech recognition reduce dependence on cloud reachback in the field.

    Operator + aircraft + payload + network

    Bring the mission loop into one view.

    Program office / contact

    Put Arc
    on the mission.

    Defense inquiries

    [email protected]

    Partnerships & commercial

    [email protected]

    Powered by Rownd