Say the mission. Your robots run it.
Natural-language mission control for drones, boats, and underwater robots. TengwarOS is the common AI
mission layer for defense and commercial fleets: one console for your whole unmanned fleet. A
plain-English request becomes a validated, human-approved mission (drones today, boats next) and comes
back as an audit-ready record. Any vehicle, no lock-in, non-China stack.
See it run
"Inspect turbine 7 south face for surface cracks, then return." compiles into a verified mission plan:
launch, transit, scan (3 passes, EO/IR), uplink findings, return and auto-report, awaiting human approval.
You approve the plan. Then it flies, even where the link drops.
Stream it live, or upload for offline autonomous execution beyond the link. Nothing moves until a human
approves. A pre-declared link-loss policy (continue, hold, or return) governs a dropped link.
Every mission lands in a record you can query.
Telemetry, captures and findings: organized and auto-reported in a format your auditors recognize.
Defense
ISR patrols and counter-UAS screens: one sentence, executed link-loss-tolerant and GPS-degraded, tracks
published to the common operating picture. Counter-UAS is non-kinetic. TengwarOS is dual-use by design:
it builds the mission and command layer, not fire control; engagement authorization always rests with
a human.
Commercial
Hull, pier and cable surveys with ROVs. Blade and foundation inspection across a turbine fleet, defects
linked over time. Map, spray, survey, patrol: describe it, and it runs.
One platform
- Drones: PX4 / ArduPilot / Skydio, live and offline, today
- USV boats: field pilots scheduling
- Subsea ROV/AUV (ArduSub): offshore test in preparation
- Ground robots: same adapter pattern
The AI never touches the controls. Human approval is mandatory, enforced server-side, with guardrails at
the code layer. One operator controls and coordinates many machines: one live picture, one-click
takeover, on existing fleets or factory-embedded. Built on open standards: MAVLink, ROS 2, MCP, MCAP.
Why us
Built by a Naval Academy graduate and Marine Corps veteran, rooted in Taiwan's Blue-UAS-compatible,
NDAA-aligned supply chain, field-tested with a TWSE-listed drone OEM.
Book a demo
A 15-minute call, a live demo on real hardware, a straight answer on fit: cksun@tengwaros.com
Frequently asked questions
What is TengwarOS?
TengwarOS is the common AI mission layer for defense and commercial fleets: one interface to integrate
and control low-cost, mass-produced unmanned systems. Say the mission in plain English; one console
compiles it into a validated, human-approved mission, runs it across drones, boats, and underwater
robots (drones today, boats next), and returns an audit-ready, queryable record. Any vendor, no
lock-in, non-China stack.
Which vehicles and autopilots does TengwarOS support?
Aerial drones on PX4, ArduPilot, and Skydio today (live and offline). USV boats are next, with field
pilots scheduling; subsea ROV/AUV on ArduSub is in offshore test preparation; ground robots follow the
same adapter pattern. Built on open standards: MAVLink, ROS 2, MCP, MCAP.
Does the AI fly the drone directly?
No. The AI never touches the controls: it coordinates human-written, tested skill primitives and is
forbidden to emit MAVLink or ROS commands directly. Nothing moves until a human approves: the operator
either confirms each mission or pre-authorizes the AI to execute within approved guardrails (geofence,
altitude and depth ceilings, battery floor, link-loss behavior), and every override is recorded.
Does TengwarOS serve defense as well as commercial operators?
Yes, openly: TengwarOS is dual-use. It builds the mission and command layer, not fire control;
engagement authorization always rests with a human. On the defense side that means ISR patrols and
non-kinetic counter-UAS screens, executed link-loss-tolerant and GPS-degraded, with tracks published
to the common operating picture.
What happens if the communications link drops mid-mission?
Missions can be streamed live or uploaded for offline autonomous execution beyond the link. A
pre-declared link-loss policy (continue, hold, or return) decides what happens when the link drops, so
behavior on link loss is decided before launch, not improvised.
What does TengwarOS produce after a mission?
Every mission lands in a queryable record: telemetry, captures, and findings, organized and
auto-reported in formats auditors recognize; frames captured, findings flagged, manual interventions
counted.
Is TengwarOS built on a non-China, NDAA-aligned supply chain?
Yes. TengwarOS is a non-China stack rooted in Taiwan's Blue-UAS-compatible, NDAA-aligned supply chain,
built by a Naval Academy graduate and Marine Corps veteran, and field-tested with a TWSE-listed drone
OEM.