TAK-native command and control
The COP that speaks CoT — connected or disconnected.
A production-grade TAK client lives inside the same 3D scene as your radar, imagery and terrain analysis. It reaches a TAK Server over STOMP mTLS-wss, drops to server-less UDP multicast on a disconnected LAN, and carries blue-force tracking, GeoChat, mission collaboration, after-action replay and TAK Server administration — ATAK/WinTAK parity from an analyst workstation.
STOMP mTLS-wssUDP multicast 239.2.3.1:6960Radio-mesh transportGeoChat + alertsMissions + AARMarti REST adminData packages
At a glance
- TransportsSTOMP-over-mTLS-wss to TAK Server (
wss://host:8444/Marti/api/cop, operator .p12) · server-less UDP multicast CoT (ATAK’s standard group) · radio-mesh; selectable per profile - Blue forceSSE fan-out of position CoT, per-UID latest-position store, persistence
- CollaborationGeoChat, alerts with ack, missions with tasks and safety check-ins, freeform annotations, collaborative SVG board
- AARDuckDB append-only event log; reconstruct mission state as-of any event time
- AdminMarti REST proxy — missions, channels, users, data packages
- SymbologyMIL-STD-2525 / APP-6 (SIDC via milscope) + 102-symbol NAPSG / NWCG emergency set
Capabilities
What the TAK tier does
Everything below is a rebuilt, modern service under the current engine — not the legacy collaboration tree.
Two wire protocols, one profile switch
Connect to a TAK Server with an operator certificate, or run entirely server-less on multicast for DDIL and MANET operations. Profiles are DPAPI-encrypted; the transport is chosen per profile.
- STOMP mTLS-wss (
/Marti/api/cop) - UDP multicast CoT — default 239.2.3.1:6960
- Radio-mesh transport for disconnected teams
Blue-force tracking and GeoChat
Position CoT fans out over SSE to every panel that needs it; GeoChat rooms and alerts with acknowledgement ride the same connection.
/api/tak/*— positions, per-UID store, persistence/api/tak/chat·/api/tak/alertswith ack- Friendly-UAS CoT from MAVLink, AIS→CoT, detections→CoT
Mission collaboration
Assignments and tasks, status, safety check-ins with an overdue watchdog, freeform annotations (pin, sketch, shape, text, image) and a collaborative SVG board window.
/api/missions/*— GPKG relational truth- Mission Board kanban
- Bidirectional CoT bridge to TAK Server missions (Marti REST) with echo suppression and last-writer-wins versioning
After-action review
Every mission event lands in an append-only DuckDB log. Scrub the timeline and reconstruct the state of the mission as of any moment — who was where, what was tasked, what was acknowledged.
/api/missions/{uid}/timeline- Exercise injects fire the production paths with wall-latency capture (force-protection tier)
- Deterministic HTML AAR export
TAK Server administration
A Marti REST proxy puts missions, channels, users and data packages in an admin dashboard inside the workstation — no separate browser session to the server.
- Missions, channels, users, data packages
- Data package create / export / import (manifest.xml + cot.xml)
- Round-trips with ATAK and WinTAK
Defense tools that publish to the net
Call-for-fire, CAS and MEDEVAC 9-lines, Bullseye, geofences and threat domes are built on the map and sent through TAK chat or as CoT shapes the team sees in ATAK.
/api/defense/cff— observer→target direction / distance in mils/api/defense/medevac·/api/defense/bullseye- Geofence publish as ATAK-compatible u-d-f shape with a __geofence detail block
Ops workflow
A mission from connect to debrief
The TAK tier is designed for the network going away mid-mission. Every step below works on multicast alone; the TAK Server bridge adds reach, not dependency.
- ConnectLoad the operator .p12 and connect over mTLS-wss — or pick the multicast profile when there is no server. Blue-force positions appear immediately.
- Build the pictureDrop MIL-STD-2525 symbols by SIDC, draw GRGs and range rings on MGRS / GARS / USNG graticules, overlay radar, ADS-B and Remote ID tracks fused from the sensor tier.
- Task and annotateCreate the mission, assign tasks, place pins and sketches on the shared board; safety check-ins run on a watchdog. Edits sync both ways with TAK Server missions.
- Push products to the fieldSend a CFF or 9-line through GeoChat, publish a geofence as a monitored shape, export a data package for ATAK.
- ReplayScrub the AAR timeline to any event time and export the review.
Specifications
Protocols, routes and formats
Transports
- TAK ServerSTOMP over mTLS WebSocket,
wss://host:8444/Marti/api/cop, operator PKCS#12 - Server-lessUDP multicast CoT, default
239.2.3.1:6960 - MeshRadio-mesh CoT transport
- ProfilesDPAPI-encrypted; transport selectable per profile
Routes
- Positions / chat / alerts
/api/tak/*·/api/tak/chat·/api/tak/alerts - Missions
/api/missions/*— tasks, check-ins, annotations, timeline, export / import - Defense
/api/defense/cff·/api/defense/medevac·/api/defense/bullseye·/api/defense/ballistics - Geofences
/api/geofences·/api/geofences/{id}/publish
Symbology & formats
- MilitaryMIL-STD-2525 / APP-6 via SIDC (milscope)
- Emergency102-symbol NAPSG Foundation + NWCG PMS 936 set
- CoordinatesMGRS · GARS · USNG · UTM; configurable graticule; draw-rectangle GRG builder
- PackagesCoT data packages — .zip with manifest.xml + contents/cot.xml
Honest scope
What ships, what is optional, what is next
Defense buyers get burned by overclaims. This is the plain-language scope for this capability, drawn from the product’s own documentation.
- Shipped TAK client, missions, AAR, admin — All rebuilt as modern services under the current engine and live in the build.
- Shipped MIL-STD-2525 / APP-6 symbology — Full SIDC-driven symbol rendering plus the NAPSG / NWCG emergency-response set.
- Roadmap CoT over mTLS-TCP (8088 / 8089) — The wss and UDP multicast transports ship today; the direct mTLS-TCP CoT transport is on the roadmap.
- Roadmap XMPP, VoIP, SMS and PTT — These legacy collaboration channels are excluded from the current build and are not marketed here.
- Roadmap Tactical data links — No Link 16 / VMF / JREAP message-set implementation is documented; interoperability is CoT, ASTERIX and STANAG 4676.
GeoTactical Insights · powered by 3D Map Explorer
See it on a disconnected machine.
A 30-minute guided demo on your own data: ingest, exploit, fuse, share to TAK and export — with the network cable out. We will also tell you exactly what is a sidecar, what is gated and what is still roadmap.
GeoTactical Insights
GEOINT and defense workflows powered by 3D Map Explorer, the air-gapped geospatial intelligence platform from Tech Maven Geospatial.