PLUGIN DEVELOPMENT
ATAK, WinTAK, iTAK and TAK Server Plugin Development
Operators should not fight the tool. A well-built TAK plugin puts the right data and control on the map — or on the server that federates the picture.
DS2 develops custom ATAK, WinTAK, iTAK and TAK Server plugins for defense and mission partners. We turn external systems into CoT traffic, in-client UI and server-side services that hold up in operational use.
Client plugins
ATAK · WinTAK · iTAK
Server plugins
Messaging · translation · telemetry
CoT
Shared mission data format
TAKX
Also supported
WHY IT MATTERS
Why plugins
Baseline TAK clients and TAK Server cover the common operational picture. Mission-specific sensors, vehicles, AI services and planning tools need a plugin — on the client, on the server, or both — so the capability shows up where the operator already works.
HOW WE ENGAGE
Discover · Build · Test · Field
Discover the mission, data source and target client or Server plugin API. Prototype early on the real TAK surface. Harden, package and support through fielding.
ON DEVICE
Client plugins (ATAK, WinTAK, iTAK)
Client plugins add UI, symbology, device bridges and mission controls inside ATAK, WinTAK and iTAK.
- ASI — ATAK plugin for direction-finding control, line-of-bearing symbology and geolocation features
- REGENT — SQUIRE-TAK plugins for waypoint routes, telemetry, video and vehicle C2
- VATN — ATAK plugin for autonomous underwater mission load, command and status
- Attollo — ATAK plugin for handheld laser rangefinder data and CoT target handoff
- Matbock — ATAK ballistic (ARD) and TCCC / 9-line medical plugins
- Intellisense — ATAK Micro Weather Sensor integration; SREAF ATAK and WinTAK weather forecasting
- EOD / ADR — ATAK plugin for UXO mitigation workflows tied to GeoExPT / GAS
- Turbine One — ATAK plug-in with WebView and API hooks into an AI detection application
Direction-finding on ATAK — example of a sensor plugin DS2 builds for ASI.
ON THE SERVER
TAK Server plugins
- SOFWERX — TAK Server plugin translating POI and AI alerts into CoT for any TAK client
- Nauticus — TAK Server module with ROS2-to-CoT translation alongside an ATAK plug-in
- Turbine One — TAK Server bridge paired with the ATAK plug-in for AI detection workflows
CASES
Selected work
Read the public cases, then tell us what to plug in next.
Desktop and mobile TAK clients — where SOFWERX-related server plugins deliver CoT to operators.
ENGAGEMENT
How we engage
- Discover the mission, data source and target client or Server plugin API
- Prototype early on the real TAK surface
- Harden, package and support through fielding
We also support software integration discovery when the work is plugin or CoT integration — not Server deployment or training.
ENGAGE
Next step
Tell us the client or server surface, the data source and the mission outcome.
ANSWERS
FAQ
A client plugin runs in ATAK, WinTAK or iTAK and adds UI, symbology or device control on the end-user device. A TAK Server plugin runs on TAK Server and extends messaging, translation or services for connected clients. DS2 builds both.
Cursor on Target is the message format TAK uses to share points, alerts and related mission data across clients and servers.
No. We build plugins and integrations, not server deployments or training.
ATAK, WinTAK, iTAK and TAKX, plus TAK Server plugins where the integration belongs on the server.