For manufacturers & integrators
We bring your product into ATAK and keep the plugin up to date.
You build robots, sensors, rangefinders, drones or radios, and your customers work with ATAK. We develop the plugin that puts your device on the map and lets users control it from ATAK. We work for civilian manufacturers and for companies in the defense industry.
A laser rangefinder locks on to a target: 1,240 m, bearing 312°.
<event version="2.0" uid="LRF-7.ziel-1" type="a-u-G" how="h-e" time="2026-10-16T09:42:07Z" stale="2026-10-16T09:47:07Z"> <point lat="51.0912" lon="7.1189" hae="212" ce="4.5" le="2.1"/> <detail><contact callsign="Target 1"/> <remarks>1240 m, 312°</remarks> </detail> </event>
What we often hear from manufacturers
We don’t know how to build an ATAK plugin.
ATAK plugins are built with the official Android SDK and follow their own rules for the user interface, the map and signing. We take care of that. You provide the device, the protocol and the requirements.
We have a plugin, but nobody to maintain it.
We take over existing plugins, review the code and build, and handle bug fixes and further development.
Every ATAK update breaks our plugin.
Plugins are built against a specific ATAK version. When a new version comes out, roughly every three months, the plugin has to be adapted, rebuilt and tested.
What we do for manufacturers
You don’t need to become a software company. Hand us a complete plugin project or just parts of it.
Update service for new ATAK versions
A new ATAK version comes out roughly every three months. So that your customers don’t have to wait for your plugin, we follow the same process for every release.
Quarter 1 ATAK release plugin adapted afterwards
Quarter 2 ATAK release plugin updated
Quarter 3 ATAK release plugin updated
Quarter 4 ATAK release plugin updated
Schematic. The TAK Product Center sets the release dates.
Review the new version
Assess the changes in ATAK and the SDK and find the affected parts of the plugin.
Adapt and build
Adapt the plugin to new interfaces and build it against the new version.
Test
On real Android devices and, where available, with your hardware.
Deliver
Signed and documented, to you or directly to your customers.
Typical projects
What your customers see in ATAK once your device is connected.
Robotics and ground vehicles
The robot’s position, status and camera feed on the map, with simple commands sent straight from ATAK.
Drones
Telemetry, flight path and video in the operating picture at incident command.
Drone detection
Drones picked up by radar or RF detection appear as tracks on the map, with an alert to the team.
Air traffic via ADS-B
Aircraft and helicopters from your ADS-B receiver as tracks with ID, altitude and heading.
Cameras and body cams
Live video from body cams, fixed or vehicle cameras, opened right at their location on the map.
Trackers and satellite
Positions and SOS alerts from trackers, wearables or satellite messengers, even without cell coverage.
Sensors
Readings from CBRN, weather or water level sensors as points or warning areas, with thresholds.
Radios and mesh
Positions and messages over your own radio network, with a gateway to the TAK Server.
Specialist applications
Data from your software goes into the operating picture as CoT, and markers from ATAK go back into your software.
How a plugin project works
After each step, you decide whether to continue.
Initial consultation
We talk about the device, the interface and what your customers should see in ATAK. The consultation is free.
Concept
We describe the data flow, CoT types, user interface and effort in a written quote.
Development
In short iterations, with interim builds you test on your own devices.
Delivery
Signed plugin, documentation for your customers and a briefing for your support team.
Update service
Adaptation and testing for every ATAK release, for as long as you need it.
Terms
Plugin projects vary too much for fixed prices. We estimate the effort after the initial consultation and state it in a written quote.
Plugin development
time and materials
Depends on the interface, the feature set and the user interface.
Update service
on request
Adaptation, testing and delivery for every ATAK release as an ongoing agreement.
Plugin takeover
on request
Maintenance and further development of your existing plugin.
All prices plus VAT.
Questions from manufacturers
Didn’t find your question? Call or write to us.
Do we need ATAK expertise ourselves?
No. We need the interface specification for your device and, ideally, a test unit. We bring the ATAK knowledge.
How often does a plugin need to be updated?
Usually with every new ATAK version, so roughly every three months. Plugins are built against a specific version; without an update, ATAK often won’t load them after it is upgraded.
Does the plugin also work with iTAK and WinTAK?
ATAK plugins run on Android. WinTAK has its own plugin system, and iTAK is much more limited when it comes to extensions. An additional connection via CoT or the TAK Server often makes sense, because then every client sees the data.
Can you take over an existing plugin?
Yes. We review the code, build and dependencies and then tell you what it takes to keep it up to date.
How does the plugin reach our customers?
As a signed plugin that you ship with your product or provide through an update server. We document installation and configuration for your customers.
Tell us about your product
Which device, which interface, and what should your customers see in ATAK? We’ll get back to you with an initial assessment and a suggested meeting time.
Phone