Working integrations

A common fabric for
mission data and control.

LINK connects mission systems, platforms, payloads, and sensors through their software interfaces, communications protocols, and message formats. LINK integrations translate those exchanges into a common data and control fabric while preserving each OEM’s protocols and system architecture. Operators use LINK’s common workflow without having to operate a separate OEM screen for each connected system.

Synchronize TAK and Lattice in real time.

Nemesys LINK™ normalizes TAK tracks and Lattice entities into common LINK subjects, enabling permissioned synchronization between the two systems.

Current integration scope
Mission systems

TAK

TAK Server and ATAK tracks synchronized through LINK, connecting the TAK mission picture with Lattice through common LINK subjects.

Track synchronization
Mission systems

Anduril Lattice

Lattice entities synchronized through LINK in Anduril’s sandbox, with permissioned synchronization between Lattice and TAK.

Sandbox connection
Payloads & sensors

Trillium Orion environment

Live EO/IR video, gimbal control, telemetry, and sensor footprint context through the Trillium Orion environment.

Gimbal control & video
Payloads & sensors

ADS B

Aircraft tracks from a connected receiver, displayed in the common operating picture.

Aircraft tracks
Vehicle systems

ArduPilot Rover

Ground vehicle telemetry and driving through connected LINK nodes, bringing vehicle control into the shared mission workflow.

Ground vehicle control
Vehicle systems

PX4 / MAVLink

Supported aircraft control, telemetry, and preflight information through the OEM autopilot, which manages flight execution and retains its safety controls.

Aircraft control
Modular hardware where required

The right integration
for the host platform.

Where platforms expose the interfaces and compute required, LINK works through them. Where additional hardware is needed, the Networked Modular Payload System provides modular compute, mounting, power, data, and payload specific interfaces.

This approach minimizes custom integration while preserving flexibility as platforms and mission requirements evolve.

Discuss platform integration
Compute where needed

Use capable onboard resources or add modular compute to suit the host platform.

Mechanical, power & data interfaces

Connect supported equipment through repeatable integration components, including the DEVCOM CLIK interface.

Payload specific modules

Address the retention, release, and interface requirements of the selected payload while bringing its status, mission context, and supported command and control functions into LINK’s common operator workflow.

Vertical Autonomy VA 150 platform configured with Nemesys modular integration hardware
Nemesys enabled VA 150 configuration.
Nemesys enabled platforms

Capability built
on proven vehicles.

Our integration work spans Group 1, 2, and 3 uncrewed aircraft systems (UAS), as well as unmanned ground vehicles (UGVs). LINK and modular hardware bring payloads into a common workflow without requiring every host vehicle to adopt a fixed architecture.

Mission configurations, payload compatibility, and delivery scope are established with the platform partner and customer.

Bring your platform requirements
Bring your mission requirements

Let’s connect what you need.

Scope a demonstration, technical evaluation, or funded integration.

Talk to Nemesys