SynapseCommand Integration with ATAK
ATAK is the Android situational awareness application used at the tactical edge, on the device the user already carries. SynapseCommand is designed to add higher-level analysis behind that picture, so that what the user sees can be supported by reasoning done at reachback, while ATAK remains the tactical user environment.
What ATAK is
The Android Team Awareness Kit is the mobile client of the TAK family published through the TAK Product Center. It gives a dismounted or vehicle-borne user a map-centred view of the situation, with position reporting, messaging, markers and mission overlays, on commodity Android hardware.
ATAK is a user environment first. Its value is that a team can see and share the same picture under conditions where heavier systems are impractical, using compact Cursor-on-Target events that survive poor bearers and short windows of connectivity.
It is used across military, special operations and public safety communities, with distributions and access governed by the relevant programme authority. This page describes a design relationship only. No ATAK plugin has been built by Decent Cybersecurity and no exchange with an operational ATAK deployment has been validated.
Your C2 stays. SynapseCommand adds the decision layer.
SynapseCommand does not attempt to replace ATAK or to put analytical products on the user's device that the device is not the right place for. The tactical edge needs a light, fast, familiar picture, and ATAK is already that.
The relationship instead runs the other way. Reporting produced by ATAK users flows through a TAK Server, and SynapseCommand consumes it there. What the edge observes becomes an input to operational-level analysis, and the analysis stays where the compute and the staff are.
Where a customer chooses, a product of that analysis can be returned as an event the ATAK client already understands, so the user receives a marker or an update rather than a new application to learn. The exchange path is the TAK Server, not a direct client connection, and it is a customer decision whether it is used at all.
- 01ATAK usersExisting tactical clients, unchanged, on their own devices.
- 02Tactical operational dataPosition reports, markers and observations as Cursor-on-Target events.
- 03TAK ServerThe authorised exchange point. SynapseCommand attaches here, not to the device.
- 04SynapseCommand integration layerPublished TAK adapter reading and producing Cursor-on-Target.
- 05Canonical data modelEdge reporting held with source, timing and reported confidence intact.
- 06Operational analysisSpecialist agents relate edge reporting to the wider operational picture.
- 07Options and rehearsalCourses of action developed and examined at the operational level.
- 08Human decision authorityAn authorised human decides what, if anything, goes back to the edge.
- 09Decision record and replayWhat was reported, analysed and authorised, reconstructable afterwards.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Escalation from tactical to operational
An observation made by one team becomes part of a picture assessed against everything else that is known, instead of remaining a marker only its own group can interpret.
Analysis that does not run on the device
Agent reasoning happens at reachback where power, compute and data are available, which keeps the edge client light and battery-sensible.
Mission context around a position report
Reporting is held with its history, so patterns of movement and activity can be examined rather than only the most recent event.
Decision support for the supported commander
Staff receive options and comparisons drawn from edge reporting, with the reasoning attached rather than summarised away.
Human-controlled return path
Anything sent back towards the tactical picture is authorised by a human first. Agents do not push markers to users on their own initiative.
How the decision cycle runs
Edge observation to shared understanding
Reporting from ATAK users is normalised on arrival and deconflicted with other sources, so the operational picture reflects the edge without inheriting duplicate or stale contacts.
Contact to assessment
A reported contact is assessed against recent history and the wider picture, so that the significance of an observation is examined rather than assumed from the symbol used.
Assessment to options
Where a response is required, options are developed at the operational level against stated constraints and compared on explicit criteria.
Authorised return to the edge
If a product is to reach the users who generated the reporting, a human authorises it and it is delivered as an event the existing client understands.
How this sits in a real environment
No change to the device
The design assumes ATAK stays as issued. Integration happens at the server, so there is no requirement for a new build, plugin or configuration on user devices.
Server dependency
An ATAK relationship in practice means a TAK Server relationship. Where no server is available to SynapseCommand, there is no exchange path.
Edge conditions
Intermittent connectivity is the normal case. Analysis continues on the information already received, and the record makes clear what was known at the time rather than presenting a retrospective picture as if it had been available.
Where the data goes, and where it does not
- Reporting drawn from a TAK deployment is analysed inside the customer's own boundary. Models are self-hosted and there are no external AI calls at runtime.
- Because edge reporting frequently identifies friendly positions, the return path is deliberately gated: nothing is published towards tactical clients without an authorised human decision, and that authorisation is recorded.
What is claimed, and what is not
Integration relies on an interface, protocol or data standard already supported by SynapseCommand.
Exchange with ATAK users runs through a TAK Server using Cursor-on-Target, a publicly established mechanism that the published SynapseCommand TAK adapter supports. No ATAK plugin has been built and no validated exchange with an operational ATAK deployment has taken place.
Qualification
Standards-based support does not imply certification, endorsement or accreditation by the TAK Product Center or any government authority.
- publication · 2026-08-25 · direct evidence
SynapseCommand integration layer published under Apache 2.0
The canonical data model, JSON Schema, reference adapters, SDK and validation harness are published for independent inspection.
Interfaces and data standards
The data contract behind these interfaces is published for inspection in the open integration layer.
What SynapseCommand implements for each of these standards, with the direction of exchange and the source files behind it:
Interfaces and data standards
The claim on this page is limited to Cursor-on-Target exchange through a TAK Server. No ATAK-specific plugin interface, private API or device-level integration is claimed. Interoperability documentation covering Cursor-on-Target and the TAK interfaces will be added to the SynapseCommand interoperability catalogue.
The SynapseCommand data contract is published for inspection in the open integration layer.
Open interoperability layer
SynapseCommand connects to external systems through an openly published interoperability layer rather than proprietary point interfaces. The canonical data model, the JSON Schema and the format adapters are inspectable before any integration is committed to. That layer describes what SynapseCommand implements; it is not a statement about ATAK and implies no interface to it.
Public sources
Factual statements about the named system on this page are drawn from these public sources.
Frequently asked
- Does SynapseCommand replace ATAK?
- No. ATAK remains the tactical user environment. SynapseCommand consumes the reporting that reaches a TAK Server and adds operational-level analysis behind it.
- How can ATAK data support SynapseCommand decision workflows?
- Position reports, markers and observations arrive as Cursor-on-Target events, are normalised with their source and timing preserved, and become an input to agent analysis alongside other sources feeding the operational picture.
- Does SynapseCommand require an ATAK plugin?
- No plugin has been built and none is assumed. The designed exchange path is through a TAK Server, which leaves user devices as they are.
- What is the current status of SynapseCommand alongside ATAK?
- Standards-based. Cursor-on-Target exchange through a TAK Server is a publicly established mechanism and the published SynapseCommand TAK adapter supports it. No validated exchange with an operational ATAK deployment has taken place.
- Can ATAK remain the tactical user interface?
- Yes, and that is the intent. Where a product is returned to the edge at all, it is delivered as an event the existing client already renders.
Where to go next
Relevant use cases
Discuss an integration
Briefings are available under NDA. SynapseCommand® integration work begins from the published data contract, so the interface can be reviewed before any commitment.
Third-party systems and trademarks
Product names, trademarks and registered trademarks referenced on this site are the property of their respective owners. References to third-party systems describe implemented, planned or potential technical interoperability as stated on each page and do not imply sponsorship, certification, endorsement or partnership unless expressly stated.
Category: Tactical edge. Last reviewed 2026-09-06.