Integrations
Any airframe.
Any autopilot.
OMNIVISION sits above the flight controller. Aircraft, simulators and onboard compute connect through one contract, so a new airframe inherits every mission.
The stack
Open at every layer. Locked to no airframe.
One console for your operators, an SDK for your engineers, and any flight controller underneath. Integrate at the level that fits your platform.
- Multi-aircraft planning
- Live 2D and 3D supervision
- Dynamic replanning
- Replay and debrief
- Operator authority: leases, authorisation and site guard
One operator console
One operator plans, authorises and supervises a mixed team of aircraft for surveillance, strike and interception.
- GPS-denied navigation
- 3D mapping and avoidance
- Lost-link fallbacks
- Safety guardian
Onboard autonomy
Runs on each aircraft, so the mission continues when GPS is jammed or the link drops.
- OMNIVISION SDK
- MAVLink 2
- ROS 2
- SITL and HITL on Gazebo and Unreal Engine 5
- Your mission or payload
SDK and open interfaces
Build your own missions, payloads and integrations on one documented contract, identical in simulation and in flight.
- PX4
- ArduPilot
- Pixhawk-standard hardware
- Any MAVLink 2 autopilot
- Multirotor, fixed-wing and VTOL
- Companion compute and depth cameras
- Your airframe
Any flight controller
Hardware-agnostic. Keep the autopilot and airframe you already fly; OMNIVISION sits above them, with no vendor lock-in.
One contract
Simulation and hardware are the same to the console.
Simulated and real aircraft share commands, acknowledgements, operator leases and the site guard. What you rehearse is what you fly.
- 01 / 03
Flight stays onboard
The autopilot keeps flying the aircraft. OMNIVISION coordinates the mission above it.
- 02 / 03
One operator experience
A new airframe connects to the same planning and supervision tools as every other.
- 03 / 03
Test before expanding
Each platform is validated in stages, from simulation to controlled flight.
Staged trial
Evaluate it in four stages.
Start with the operational need, and build evidence at each step before moving to the next.
01 Operational requirements
Agree the mission, the platforms and the safety boundary.
02 SITL and HITL
Validate interfaces and failure cases in the loop, before anything flies.
03 Controlled flight
Two to five aircraft on a test range.
04 Operator trial
A representative mission with your operators, and a review of the evidence.
Integration