Requirements first
Every subsystem starts from a defined mission need and measurable target.
Ottawa, Ontario, Canada
The operating software and field hardware stack for dependable uncrewed systems.
Software-defined uncrewed systems. Hardware-validated for the field.
00 Mission
We build autonomy software on the hardware required to trust it in the field. Kanatir develops the mission environment, the software products inside it, and the uncrewed systems that run it — validated step by step, not overclaimed.
01 Platform
Sahtune — the mission environment for uncrewed systems.
Sahtune is the mission environment for uncrewed systems. It connects aircraft, sensors, operators, autonomy, mission data, logs, and field hardware into one modular software environment.
Sahtune is the umbrella. The software products run inside it; the hardware platforms run it. Customers can adopt the base environment and activate the capabilities they need — autonomy, perception, fusion, ground control, or multi-UAV coordination.
02 Software products
Five products inside Sahtune.
Modular capabilities that run inside the mission environment. Each is in active development — status reflects where it is on the validation path.
In Development Sentinel
The autonomy layer that turns an uncrewed platform into a dependable mission capability.
In Development Perception
AI-assisted detection and scene understanding for uncrewed systems.
Under Validation Fusion
The layer that combines multiple sensor streams into one coherent operating picture.
Planned Ground Control
The operator workspace for planning, monitoring, and reviewing uncrewed missions.
Pipeline SwarmLink
Coordinated multi-UAV behaviour from a shared mission layer.
03 Hardware systems
The platforms that run and support the stack.
Uncrewed systems and power hardware. KX-1 Raven is the current development platform; the others are forward-looking platform concepts powered by the same architecture.
In Development KX-1 Raven
A multirotor development platform for proving autonomy, avionics, power, and payload integration.
Pipeline KX-2 Warden
A compact rapid-response UAV for close-range awareness and perimeter missions.
Pipeline KX-3 Vektor
A medium-range tactical platform for deployable field operations.
Pipeline KX-4 Boreal
A long-range uncrewed system concept for remote and northern operations.
Active Development KX-Power Rail
Intelligent power distribution for UAVs and field robotic systems.
04 Validation path
Evidence before claims.
01
Simulate
Model the mission logic, system behaviour, and expected operating limits before hardware risk is introduced.
02
Bench Test
Validate power, compute, sensors, payloads, and software interfaces in controlled conditions.
03
Ground Test
Verify integration, operator workflow, telemetry, failsafes, and repeatability before flight.
04
Flight Test
Mature the system through controlled flight envelopes, documented results, and structured failure analysis.
05 Approach
Documentation-led, test-driven engineering.
Tested in steps
Bench, ground, and flight testing are documented so results are repeatable and failures are understood.
Built to maintain
Field serviceability is treated as a design input: modular parts, clear interfaces, accessible logs, and maintainable hardware.
06 Operating context
Designed for northern and allied operations.
Canada's geography sets a hard baseline: cold-weather starts, long transit distances, intermittent communications, remote recovery, and limited field support. Kanatir treats these as engineering constraints from the beginning and aligns its systems with the reliability, documentation, and interoperability expectations of allied operators.
Engineering partnerships and briefings
For government, partnership, and technical discussions, request a briefing. Please keep all details unclassified and unrestricted.