What ATAK versions are supported?
Tactical AI DuckDB v1.3.0 targets ATAK-CIV 5.8.0 (plugin-api com.atakmap.app@5.8.0.CIV with the IPlugin lifecycle). The plugin requires Android 9.0 (API 28) or higher on ARM64 devices. For AI model performance we recommend 4GB+ RAM and a modern Snapdragon or equivalent processor.
Does it work completely offline?
The verified v1.3.0 core loop is offline-first by design: DuckDB spatial queries, in-app OGC tile/feature serving, on-device AI (once models are staged), H3/GARS grids, GraphHopper routing (once graph packs are staged), SAR planning, ATC-45 assessment, document extraction, and CoT workflows all run without connectivity. Features that inherently need a network — AOI downloads, website archiving, portal sync — are used to pre-stage data before going offline.
How does the in-app map serving work?
The plugin runs a loopback-only HTTP server inside ATAK. GeoPackage vector features and vector tiles, MBTiles OSM vector-tile basemaps, PMTiles archives, and DuckDB tables are exposed through OGC API Features (with CQL filtering) and OGC API Tiles endpoints, with dynamic vector tiles generated on demand. Because ATAK does not support GL JSON styles, sprites, or glyphs natively, the plugin renders them on device: GL stylesheets are applied to local vector tiles via MapLibre GL Native and served as dynamic PNG raster tiles ATAK displays as standard XYZ map sources. Cleartext scope is restricted to loopback for security.
What AI models are supported?
On-device inference uses Google MediaPipe with Gemma 3N for text analysis and Gemma 3 4B Vision as the supported vision-language model. ONNX MiniLM powers document embeddings, and a sideloaded MobileSAM decoder powers segmentation. Models are staged on the device at runtime; AI modes whose models are absent fail closed rather than guessing.
What is the status of C2 protocol messaging?
Native Cursor-on-Target dispatch to the ATAK bus is wired and verified in v1.3.0. Military format adapters for VMF (ACP 127), JVMF (MIL-STD-6017), Link 16 (STANAG 5516), and USMTF exist in source as roadmap modules: radio/socket transport is honesty-gated, adapters report OFFLINE, and send fails closed until transport is wired and validated end to end.
What does fail-closed mean?
If a feature's runtime dependency is missing — a model not staged, a dispatcher not available, a decoder not wired — the plugin reports that the capability is unavailable instead of returning fabricated or empty-success results. This is enforced in the code, which makes evaluation and certification straightforward: what a feature claims to do is what it actually does.
What hardware is recommended?
Any ARM64 Android 9+ device with 4GB RAM covers the core workflows; 6GB+ is recommended for larger AI models. The plugin supports external GNSS receivers via Bluetooth/USB with full NMEA parsing and RTK support, and MacroPad keypads for gloved-hand operation. ASTERIX radar feeds arrive over standard UDP unicast or multicast.
What licensing options are available?
Licensing is available for individual users, teams, and enterprise/government organizations, including per-device subscriptions and site licenses. Government and educational pricing is available, and evaluation licenses support pilot programs. Contact us for enterprise and IDIQ/BPA-compatible pricing.
How do I get support?
Support is available through our support portal at support.techmaven.net. Enterprise customers receive priority support with dedicated response SLAs. Documentation and operator guides ship with the plugin repository, and custom integration support is available for enterprise deployments.
