VECTOR / ARCHITECTURE

Connected by design.

One workspace. Independent services. A shared data layer.

SYSTEM COMPOSITION

One interface.
Independent components.

VECTOR presents the workspace. Services connect data and perform specialist tasks. Mesh links participating components through DDS.

VECTOR App

Operator interface + native DDS gateway

Supported state, requests & replies

Mesh / DDS

Publish / subscribe · typed data · configured domain

Independent service participants

Mission services

Geometry services

Device adapters

DIRECT TO THE APP

Video delivery

RTSP / WebRTC

Decoded media follows the configured streaming path.

Maps & models

Local datasets / data services

Prepared geometry and textures are loaded by the map renderer.
Connection diagram — DDS carries supported operational data; media and model assets use their own delivery paths.

DEPLOYMENT

Start on one machine.
Connect across hosts.

Place the services where the operation needs them. Connected DDS participants need a matching domain and reachable network configuration.

Single workstation

ONE HOST
VECTOR
Mesh / DDS
Selected services

Run the app and required services locally. Prepared maps and models remain available without online imagery.

Connected hosts

Workstation A
Workstation B
Mesh / DDS domain
Service host

Run services on reachable hosts and connect the workstations that need their data. App views and local datasets stay independently configured.

Windows & LinuxApp, Mesh and service builds target both platforms. Validate the chosen runtime and network combination for deployment; local model processing is currently verified on Linux.

EXTERNAL INTERFACES

Connect at the boundary.

Adapters translate source-specific protocols into the data and actions supported by the workspace.

Aircraft & traffic

Vehicle state, cooperative traffic and supported commands.

MAVLink 1 & 2 · NMEA · AIS · ASTERIX

Selected autopilot and surveillance adapters.

Sensors & video

Video streams, sensor metadata and supported payload control.

STANAG 4609 / KLV · RTSP · WebRTC

Media transport and metadata follow distinct paths.

Geospatial data

Prepared maps, external imagery and local model datasets.

Local map packages · WMS · OBJ / GLB / CityGML

Dataset format and geographic placement define the import.

External systems

Exchange supported operational objects with other applications.

MQTT · REST · TAK / CoT

Adapters map external messages into the common data model.

Available data and commands depend on the selected adapter, equipment and deployment configuration.

YOUR NEXT PERSPECTIVE

Bring your mission.
See it in VECTOR.

Explore the platform through the workflows that matter to your team.

Request a demo