SynapseCommand Integration with WinTAK
WinTAK is the Windows member of the TAK family, and it is typically found where there is a desk rather than a rucksack: command posts, operations rooms and coordination cells. SynapseCommand is designed to connect that staff-level workflow to multi-agent analysis and planning support, using the same Cursor-on-Target exchange the deployment already runs on.
What WinTAK is
WinTAK is the Windows situational awareness client published through the TAK Product Center. It works from the same shared picture as the rest of the TAK family, distributed by a TAK Server, and participates in the same Cursor-on-Target exchange.
Its operational context differs from the handheld clients. A Windows machine in a command post has a larger screen, a keyboard, mains power and, usually, a better network. That changes what the client is used for: monitoring a wider area, coordinating between elements, preparing overlays and working alongside other staff tools rather than navigating on foot.
This page describes a design relationship. No WinTAK-specific development has been carried out by Decent Cybersecurity, and no exchange with an operational WinTAK deployment has been validated.
Your C2 stays. SynapseCommand adds the decision layer.
The staff role is where the decision layer is most obviously useful. A command post is not short of situational awareness; it is short of time to reason about it, compare options and record why a choice was made.
SynapseCommand consumes the same picture the WinTAK operator sees, by attaching to the TAK Server rather than to the client, and puts planning and course-of-action agents to work on it. What comes back is analysis with its reasoning attached, presented to staff rather than injected into the tactical picture.
Because the operator is at a desk, products that would be impractical on a handheld are usable here: option comparisons, rehearsal results and the replay of a decision sequence. Those are consumed in SynapseCommand alongside WinTAK, with only authorised, map-appropriate products returned to the shared picture.
- 01WinTAK operatorsCommand-post and coordination clients, unchanged.
- 02TAK ServerThe shared exchange the deployment already operates.
- 03Authorised data exchangeCursor-on-Target events, under the deployment's own access policy.
- 04SynapseCommand integration layerPublished TAK adapter, inspectable before commitment.
- 05Canonical data modelPicture held with source, timing and confidence preserved.
- 06Planning and analysis agentsBlue force analysis and planning support at staff tempo.
- 07Course of action comparison and rehearsalOptions examined against constraints before commitment.
- 08Human decision gateStaff and commander decide; the platform records the decision.
- 09Decision record and replayReconstructable sequence for review and assurance.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Staff-level decision support
Analysis is presented in a form the staff can take into their own process, with constraints and reasoning visible rather than reduced to a single recommendation.
Course of action development and comparison
Options are generated against the commander's stated intent and compared on explicit criteria, which is work a command post has to do and rarely has time for.
Scenario rehearsal
An option can be examined before commitment, including how it behaves when an assumption turns out to be wrong.
Coordination across elements
Reporting from multiple elements is deconflicted into one picture with provenance intact, so coordination is not built on duplicate or stale contacts.
Decision record and replay
The information, analysis and authorisations behind a decision are recorded, which makes after-action review a matter of replay rather than recollection.
How the decision cycle runs
Monitoring to understanding
The shared picture is normalised and held over time, so a watchkeeper's question about how a situation developed can be answered from the record.
Understanding to planning
Planning agents work from the same picture the staff are looking at, developing options against stated constraints instead of a separate, out-of-date snapshot.
Planning to decision
Options are compared and put to the commander or authorised staff officer. The platform records what was approved, by whom, and on what basis.
Decision to coordination
Where the decision produces something the shared picture should carry, an authorised human releases it and it reaches the clients already in use.
Operation to review
The sequence is replayable for after-action review, assurance activity and lessons work.
How this sits in a real environment
Alongside the command-post client
SynapseCommand is used at the desk beside WinTAK rather than inside it. The client keeps its role as the shared picture; the decision layer is a separate, inspectable environment.
Server-mediated exchange
As with the rest of the family, the exchange path is the TAK Server. No WinTAK-specific interface is assumed or required.
Command-post conditions
A command post usually has better connectivity than the edge, but it is not guaranteed. The platform is designed to keep working disconnected and to resume from the record when links return.
Accreditation boundary
Deployment location depends on the classification of the environment. SynapseCommand is designed for deployment up to NATO SECRET in accredited environments.
Where the data goes, and where it does not
- Analysis runs self-hosted inside the customer boundary. There are no external AI calls at runtime, so staff work on a shared operational picture does not depend on an external service.
- Decision records are append-only and, in assured deployments, ML-DSA-signed, so what a command post decided and why can be demonstrated later without relying on notes taken at the time.
What is claimed, and what is not
Integration relies on an interface, protocol or data standard already supported by SynapseCommand.
Exchange with WinTAK users runs through a TAK Server using Cursor-on-Target, a publicly established mechanism that the published SynapseCommand TAK adapter supports. No WinTAK-specific work has been carried out and no validated exchange with an operational WinTAK 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 relationship described here rests on Cursor-on-Target exchange through a TAK Server. No WinTAK-specific interface, plugin mechanism or private API 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 WinTAK 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 WinTAK?
- No. WinTAK remains the shared situational awareness client in the command post. SynapseCommand adds analysis, planning support and a decision record beside it.
- How can WinTAK fit into a SynapseCommand workflow?
- The picture WinTAK operators work from is distributed by a TAK Server. SynapseCommand attaches to that exchange, normalises the reporting and applies planning and analysis agents to it, returning products to staff rather than to the map by default.
- What deployment options are possible?
- SynapseCommand is deployed inside the customer's own boundary, on premises or in a sovereign environment, with the exchange path running through the organisation's own TAK Server under its access policy.
- What is the current status of SynapseCommand alongside WinTAK?
- Standards-based. Cursor-on-Target exchange through a TAK Server is publicly established and supported by the published SynapseCommand TAK adapter. No WinTAK-specific development or validated exchange with an operational deployment has taken place.
- Is the integration vendor-certified?
- No. There is no certification, endorsement or accreditation from the TAK Product Center or any government authority, and none is implied.
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.