Capability matrix
Pick a mission, the kit the unit already has, and the model it is cleared to run. The same workflow holds from plan to review.
Plan
One mission pack carries the plan, roles, files, and approved models to every handheld.
Sense
Adapters read TAK reports, small-drone video, and the radio net into one mission vocabulary.
Fuse
The tracker runs on the team leader's handheld and keeps each track's source and trust level.
Ask
The team leader's handheld cannot hold that model, so the gateway places the largest model it can. Answers keep the same citation contract.
Task
Hand a drone search box to the platoon's cleared aircraft. Approval stays with the commander.
Sync
Devices sync peer to peer over whatever link is left. Each handheld holds the full mission.
Review
Every decision, task, and answer lands in one signed record for the AAR.
Change any of the three. The workflow, the mission vocabulary, the approvals, and the record stay the same.
7 of 7
open models passed the full answer contract with EdgeLance around them. Alone, the same models passed 45 to 97 percent of cases.
Two model families, 2B to 31B parameters, 420 cases each on our development test set.
7
mission templates ship today: air-gapped base, base with GPUs, mobile patrol, SCIF with no cloud, cloud-approved, disaster response, and training range.
Each template sets models, sync, retention, and approval policy for the mission.
8
mission apps built from the same blocks, from staff writing tools to drone coordination.
Most went from requirement to working prototype in days to two weeks.
0
network connections required to plan, sense, ask, task, and review.
Enterprise links are used when the team decides, never depended on.
Custom mission apps
Our forward-deployed engineers build custom apps on these same blocks. Eight are built so far, from staff writing tools to drone coordination.
How custom apps workRun EdgeLance
License EdgeLance and run it on the unit's own hardware. Mission templates set models, sync, and approval policy for the mission, and the team is planning, sensing, and tasking from the first day.
Build on EdgeLance
Our forward-deployed engineers sit with your operators and build the app your workflow needs on EdgeLance's working blocks. The engineering goes to your rules, your data, and your screens, not to rebuilding what already works.
Everything EdgeLance does
Every capability below runs on the team's own hardware and keeps working when the network is cut.
| Plan and coordinate | |
|---|---|
| Mission planning | MDMP and SOF workflows, courses of action, wargaming, orders, staff roles, and signed publications. |
| Team workspace | Mission channels, messages, acknowledgements, files, notes, and source links that work offline. |
| Radio and transcription | Radio nets, push-to-talk events, attributed transcripts, playback, search, urgency cues, and comms coaching. |
| Maps and shared picture | Offline maps, tracks, routes, overlays, GeoJSON and KML, and TAK projection. |
| Tasks and asset handoffs | Assignments, control ownership, acknowledgements, custody transfers, and mission-linked receipts. |
| Review and AAR | Synchronized replay of chat, radio, sensor cues, and decisions; evidence queries, AARs, and lessons. |
| Sense and identify | |
| Video and vision | Live and recorded video, detections, persistent tracks, re-identification, OCR, and evidence clips. |
| Video search | Ask the camera log what it saw and when, in plain language, offline. |
| Ground geolocation | Detections placed on the map only when the camera's position, pointing, and field of view are known. No guessed coordinates. |
| Identity checks | Face matching and NFC credential checks with confidence and attributable events. |
| RF and drone awareness | SDR ingest, ADS-B, TPMS, BLE and Remote ID, emitter context, and passive drone cues. |
| Acoustic intelligence | Local audio processing, acoustic event cues, timing, and mission linkage. |
| Multi-sensor fusion | Camera, RF, audio, identity, and wearable cues fused into tracks with source, confidence, and freshness. |
| Maritime EO/SAR | Vessel association, temporal tracking, cross-sensor reacquisition, and geolocated evidence. |
| AI and assurance | |
| Local and distributed AI | Any open or approved model, an inference gateway, node placement, compute budgets, and policy-controlled offload. |
| Mission retrieval | Scoped documents, SOPs, maps, and lessons with source citations. The AI cites or refuses. |
| Proactive monitoring agents | 31 agent definitions watching readiness, node health, sensors, comms, threats, operator health, and data leakage. |
| Agents and action permits | Triggers, role authority, tool permissions, approval queues, bounded execution, budgets, and receipts. |
| Model lifecycle | Model catalogs, mission AI profiles, evaluation, adapters, signed updates, canary, and rollback. |
| Autonomy and route planning | Distributed asset assignment, constrained routes, shadow plans, and simulation. |
| Operate and protect | |
| Operator health | Wearable vitals, fatigue and stress indicators, readiness, operator-down, and CASEVAC context. |
| Node and fleet management | Inventory, enrollment, node health, software and model loadouts, posture, compliance, and rollback. |
| Hardware enrollment and trust | Discover, prove, place, calibrate, activate, monitor, suspend, quarantine, and revoke devices. |
| Mesh and mission continuity | Signed sync, store-and-forward, multi-hop relay, partition recovery, failover, and successor nodes. |
| Bandwidth priority | Mesh traffic scheduled by priority so the critical message moves first on a thin link. |
| Mission burn and retention | Scope time limits, purge and zeroize, key rotation, client receipts, and proof of destruction. |
| Evidence and partner controls | Signed provenance, chain of custody, role and scope checks, redaction, and partner release receipts. |
| Deliver and build | |
| Air-gapped delivery | Signed packages with models and policies, courier delivery, receiver validation, and rollback. |
| Mission Blocks | Typed, reusable capability blocks that compose into new mission apps. |
| Block catalog over MCP | AI coding agents ask the catalog what blocks exist, which produce the output they need, and whether a package will deploy. |
| Signed audit to SIEM | Signed audit and decision records exported to the security team's collector over syslog or CEF, air-gap safe. |
| Drone mapping and rehearsal | Asset positions, routes, sensor coverage, and mission-map simulation before step-off. |
| Sustainment and optimization | Battery, capacity, and inventory context for resource allocation and mission tradeoffs. |
Integrations
Each format is translated once into one mission vocabulary, so the tracker, the AI, and the record treat every source the same way.
| System | Standard or interface | Direction | What EdgeLance does with it |
|---|---|---|---|
| Command and control | |||
| TAK | Cursor on Target | Both | Tracks and tasks out to every TAK screen; reports in as observations. |
| Enterprise C2 | Vendor SDK bridges | Both | Entity sync with local queueing while disconnected, caught up on reconnect. |
| Messaging | MQTT | Both | Mission events on a local broker for any approved subscriber. |
| Sensor web | OGC SensorThings | In | Standard sensor observations mapped into the mission vocabulary. |
| Intelligence products | |||
| Full-motion video | STANAG 4609 / MISB ST 0601 KLV | In | Platform and sensor metadata so every detection is geolocated. |
| Imagery and reports | NITF 2.1 | Out | Mission evidence packaged for the next echelon. |
| Mission features | OGC GeoPackage 1.4 | Both | Features handed off air-gapped in one SQLite file. |
| Overlays | GeoJSON, KML | Both | Plans, routes, and overlays in and out of any GIS. |
| Vehicles and robots | |||
| Drones and ground vehicles | MAVLink 2 | In | Position, battery, and health on one asset roster, any maker. |
| Robots | ROS 2 / DDS | In | Robot state read into the roster without opening a command path. |
| Sensors | |||
| Crewed aircraft | ADS-B | In | Crewed traffic on the same picture as the drones. |
| Spectrum | SDR (rtl_433, HackRF, others) | In | RF events normalized into the same evidence stream as cameras and TAK. |
| Drones and devices | BLE, Remote ID | In | Passive drone and device cues. |
| Vehicles | TPMS | In | Vehicle signatures from tire-pressure transmitters. |
| Cameras | RTSP and recorded video | In | Detections, tracks, OCR, and clips on local hardware. |
| Audio | Microphones and radio audio | In | Transcripts and acoustic cues tied to the mission clock. |
| Networks | |||
| Tactical radios | MANET management plane | In | Link health from fielded radios, used as the IP bearer. |
| Radio telemetry | SNMP | In | Read-only device telemetry on isolated management networks. |
| Low-bandwidth link | Meshtastic / LoRa | Both | Signed mission bursts small enough for LoRa. |
| Satellite | Starlink terminal (local API) | In | Terminal health from the dish itself, no cloud call. |
| EdgeLance mesh | UDP, radio, serial, and more | Both | Device-to-device sync with multi-hop relay. |
| Security and operations | |||
| Security monitoring | Syslog, CEF | Out | Signed audit and decision records to the SIEM. |
| Supply chain | SBOM | Out | A software bill of materials with every release. |
| AI coding agents | MCP | Both | The block catalog answers what exists and what will deploy. |
Mission evaluation
We will select the blocks, tailor them to your mission, and run it on your hardware.