The mission lives on the vehicle.
Missions compile to a structured instruction set, delivered whole to every vehicle before any of them moves. Execution is onboard — it continues when the ground link does not.
Distributed Intelligence Systems
VELITAE is the coordination and autonomy layer for uncrewed fleets. One operator defines the mission. The vehicles execute it — onboard, peer-to-peer, under absolute operator authority.
The onboard intelligence that makes uncrewed vehicles behave as one resilient system — and the AI agent for mission planning and monitoring.
A mission is authored once — through voice commands or a chat with our custom AI agent — then compiled to a hardware-agnostic instruction set. Every vehicle carries the full mission and executes it onboard, coordinating with its peers over an RF mesh. The ground station observes and overrides — the fleet does not depend on it. Each node carries the mission. The fleet carries the resilience.
Missions compile to a structured instruction set, delivered whole to every vehicle before any of them moves. Execution is onboard — it continues when the ground link does not.
Vehicles coordinate directly over the mesh — roles, formation, synchronization points. There is no single coordinator whose loss stops the fleet.
One vehicle fails. The others detect it, promote a follower to lead, and continue the mission — in seconds, without waiting for instructions from the ground.
Pause, reposition, take manual control, or abort — any vehicle, at any moment. Autonomy serves the operator. It never outranks them.
An embedded assistant with live access to fleet state turns operator intent into an executable mission. Type it or say it — in any language. The assistant authors the mission, monitors its execution, and intervenes when conditions require. Every consequential action waits for operator confirmation.
Builds missions from intent. Describe the objective; the assistant produces a complete, editor-ready mission for review and dispatch.
Monitors and intervenes. It holds live fleet state and watches operator-defined trigger conditions — when X happens, do Y.
Commands at fleet scale. One vehicle or the entire fleet, directed from the same conversation — typed or spoken, any language.
Gated by design. Destructive actions require explicit operator approval, enforced server-side. The assistant never holds final authority.
Any airborne vehicle can be flown directly from its live video feed. The software holds the aircraft: altitude, position, stability. The operator supplies direction. Nothing else is their problem.
The system keeps it flying. Release the controls and the vehicle holds altitude and position on its own. Input moves it. Silence stops it.
Dead-man by design. Motion requires continuous proof of a held control. Release, lose the link, or close the tab — the vehicle brakes and holds position. Nothing keeps moving because a screen stopped answering.
Built for arrival on scene. The vehicle launches and transits autonomously. On station, the operator takes over and moves it like a camera — closer, lower, around.
Speed under command. ×1 / ×3 / ×5 velocity scaling, validated server-side — the interface can never command a speed the system has not authorized.
A mission authored at the ground station. Multiple vehicles executing it onboard. Live video on the operator's screen. A leader lost — a follower promoted. The mission continued.
Flown on real hardware, over a real RF mesh, in the field. Not a rendering. Not a simulation.
Coordinated field flight with live video to the operator. — Validated
Three-radio mesh — ground station and vehicles on one network. — Validated
Election-based promotion, proven on flight hardware over the live mesh. — Validated
Sub-500 ms glass-to-glass over WebRTC, self-healing pipeline. — Validated
The fleet appears in the command picture your operators already use.
VELITAE publishes the live fleet — every vehicle, every objective — as Cursor-on-Target, the language the TAK ecosystem already speaks. It arrives on the servers and clients already in the operations room. No second console to watch. No workflow to replace. VELITAE does not ask to sit at the centre of your architecture. It reports into it.
Vehicles and objectives render on the same map as everything else the operator is watching. Nothing new to install on their side. Nothing new to learn.
There is no inbound path — not disabled, not permissioned, absent. The command picture sees VELITAE. VELITAE takes no orders from it. Authority stays with the operator, on the operator's side of the link.
Detail is selectable. Reduced to its minimum, the feed carries presence and identity and nothing operational — a shared picture without a shared secret.
Tested against live TAK server and client software over encrypted transport — not a specification we intend to meet one day.
Any Linux computer
Coordination runs on any Linux-based companion computer — Raspberry Pi, Jetson, or your own custom board. Perception-grade compute is an option, not a requirement.ArduPilot today. PX4 by design.
The mission layer is autopilot-agnostic by contract — the instruction set does not care what flies it.Mesh-validated
Field-validated on industrial mesh radios. Transport-agnostic by design.No proprietary hardware
VELITAE sells no aircraft. It makes the fleet you already field behave as a system.Contact
For operator evaluations, partnership inquiries, or early access discussions.
contact@velitae.com